Spend is visible but not attributable
Subscriptions, accounts, projects and licences appear on the bill, yet product owners and cost centres remain incomplete. Shared platform cost is left as an unexplained remainder.
Essential or OperateSingle cloud or portfolio
FinOps and cost management
Cloud spend with an owner, a decision and a record.
We connect billing data, allocation rules, engineering context and commercial commitments in one operating record. Essential establishes the model. Operate keeps decisions, actions and evidence current across the estate in scope.
Do not send billing exports, account identifiers, credentials or commercial rate cards through the public form. Data access and the client-owned evidence location are agreed after scope approval.
FOCUS-ready
Comparable cost data
Provider exports mapped into a consistent decision model
Read-only first
Controlled access
A baseline is agreed before a resource or commitment changes
No gainshare
Independent decisions
The service fee is not a percentage of claimed savings
Client-owned
Transferable operating record
Exports, policies, registers and history remain with you
Where cost control breaks
The invoice may be accurate. The operating model often is not.
Provider tooling can expose cost and recommendations. It cannot decide how your organisation allocates shared services, balances reliability against savings or assigns authority for a commercial commitment.
Recommendations lack engineering context
A rightsizing suggestion is not a change plan. Seasonality, performance, resilience, release timing and reversal still need an accountable decision.
A discount can become a liability
Coverage without utilisation, a term without demand confidence or a renewal without an owner can lock cost into the estate instead of reducing it.
Dashboards stop at observation
Reports accumulate while anomalies, allocation gaps and optimisation work have no owner, authority, due state or retained outcome.
The cost decision path
From provider charge to verified operating record.
The method keeps source data, assumptions, authority and engineering action connected. Potential savings remain potential until an approved change is verified in service health and billing data.
Observe
Collect cost, usage, price, commitment and ownership evidence.
Normalise
Reconcile providers, currencies, charge types and data quality.
Attribute
Map direct and shared cost to the business model.
Decide
Record effect, risk, authority, timing and reversal.
Change
Implement only the action that has been approved.
Verify
Check service health, billing effect and the retained record.
Control surface
A complete FinOps loop, without buying another dashboard by default.
We use the native tools and cost platforms already present where they fit. The service adds the missing operating layer: data quality, ownership, decisions, controlled action and evidence.
Cost ingestion and quality
Billing sources, export cadence, commercial scopes, currencies, corrections and missing periods are mapped before analysis.
Evidence
Source and data-quality register
Allocation and shared cost
Accounts, tags, labels and agreed allocation rules connect technical spend to products, cost centres and owners.
Evidence
Allocation policy and coverage record
Forecast and unit economics
Budgets and forecasts are separated, variance has an explanation, and relevant costs can be related to business units or drivers.
Evidence
Forecast and unit-economics model
Usage optimisation
Idle, oversized and poorly scheduled resources become an engineering backlog with evidence, authority and a safe change path.
Evidence
Ranked optimisation backlog
Rate and commitment decisions
Reservations and other commitments are modelled against utilisation, coverage, term, currency, portability and downside before purchase.
Evidence
Commitment decision register
Anomaly management
Native or existing platform signals enter a named workflow. Planned events and false positives are recorded instead of silently dismissed.
Evidence
Anomaly decision log
SaaS and licence economics
Selected licence and SaaS scopes connect assigned seats, observed use, renewal terms, owners and approved disposition.
Evidence
Licence and renewal register
Working artefact
Start with the model, not a sales deck.
The Cloud Cost Audit Workbook is a real delivery artefact with live formulas. It helps structure a baseline, backlog, commitment decision, allocation model and FOCUS mapping before any service purchase.
Cloud Cost Audit Workbook
Live formulas, open format, no sample client data
Billed and effective cost kept distinct
Potential, approved and realised effects tracked separately
Commitment assumptions and downside visible
No macros, proprietary add-ins or locked export
The evidence pack
A handover your next engineer and finance lead can inspect.
The artefacts are operating records, not screenshots from a temporary dashboard. The exact format can follow your repository, document system and finance workflow.
Named operating runbooks
Spend baseline auditUsage optimisationCommitment break-evenAnomaly responseTagging and allocation controlFinOps operating cadenceShowback and chargebackLicence optimisation
Estate and data
Cost estate map
Providers, billing scopes, accounts, subscriptions, projects, entities, currencies, owners and export routes.
Estate and data
Data-quality register
Freshness, completeness, corrections, credits, taxes, shared-cost gaps and source lineage.
Allocation
Allocation policy
Business dimensions, direct attribution, shared-cost drivers, exceptions and review ownership.
Planning
Baseline and forecast model
Billed, effective and allocated cost with assumptions, variance and agreed reporting views.
Decisions
Optimisation backlog
Opportunity, evidence, risk, owner, authority, action state and verified billing effect.
Decisions
Commitment register
Eligible spend, utilisation, coverage, term, downside, approver, expiry and review date.
Operations
Anomaly decision log
Signal, investigation, business context, disposition, owner and linked operating action.
Business value
Showback and unit economics pack
Cost by agreed business view, unit driver, forecast variance, open decisions and limitations.
Handover
Exit Kit
Current models, policies, runbooks, evidence index, access removal and remaining backlog.
Access and authority
Cost data is sensitive. Commercial authority stays with the client.
Billing exports can expose account structure, negotiated rates and business activity. The access model starts with the smallest useful read scope, keeps evidence in a client-owned location and separates analysis from authority to spend or delete.
Read-only baseline
Cost, billing, usage and selected licence data are observed before any enforcement or workload action.
Scoped data access
Access is limited to agreed billing scopes, export locations and reports. Production data-plane access is not a default requirement.
Client commercial authority
Commitments, contracts, budgets and licence purchases are approved and signed by the named client authority.
Action-specific elevation
A resource or policy change uses separately approved, time-bounded access with an expected result and reversal path.
Client-owned evidence
Exports, models, records and configuration evidence remain in the agreed client repository or document system.
Access removed at handover
Delegated roles, API access and temporary permissions are reviewed and removed or re-scoped at transition.
Included when scoped
The FinOps operating layer
- Agreed Azure, AWS, Google Cloud, Microsoft 365 and selected SaaS billing scopes
- Cost ingestion, FOCUS-ready mapping and data-quality controls
- Allocation, shared-cost rules, forecast and unit-economics design
- Usage, rate, commitment, anomaly and licence decision workflows
- Client-owned models, registers, runbooks and evidence handover
Client authority
Decisions ITSailor does not take alone
- Budgets, accounting treatment and the business allocation model
- Commitment, licence, contract and renewal approval
- Resource deletion, performance trade-offs and production change windows
- Risk acceptance, exception ownership and cost target approval
- Tax, capitalisation and financial-statement treatment
Separate scope
Adjacent work quoted explicitly
- Application refactoring, platform migration or architecture redesign
- Procurement negotiation, legal review, accounting or tax advice
- A staffed 24/7 cost desk or incident command
- Automatic deletion or purchase based only on a tool recommendation
- Guaranteed savings, provider rebates or a percentage-of-savings fee
Delivery options
Build the operating foundation. Keep it current when you need us to.
Essential is a fixed-scope foundation. Operate owns the agreed recurring FinOps queue. Both can cover one billing estate or a portfolio, with provider scopes, entities and service capacity written into the SoW.
Fixed-scope foundation
Essential
Establish the cost data, ownership, authority and evidence model your team can operate.
Best for: Teams that need a defensible baseline, decision model and operating backlog before recurring management.
Scope: Single cloud, multi-cloud or a defined billing portfolio
Included
- Cost estate, stakeholder, commercial-scope and data-route map
- Read-only ingestion and data-quality baseline for every in-scope source
- FOCUS-ready billed, effective and allocated cost model
- Tag, label, account and shared-cost allocation policy
- Budget, forecast, anomaly and unit-economics design
- Usage, rate, commitment and selected licence optimisation backlog
- Commitment decision model with coverage, utilisation, term and downside
- Eight named runbooks, evidence templates and a client-owned Exit Kit
- Prioritised operating roadmap with named client authorities
Cadence
- Foundation review and evidence readout
- Change work is quoted or handed to the client from the approved backlog
- No recurring service obligation
Outcome
A cost model, allocation policy and decision backlog your engineering and finance teams can continue without ITSailor.
Recurring FinOps operations
Operate
Keep the foundation current and move approved cost decisions through a controlled operating queue.
Best for: Organisations that want cost data, decisions and engineering follow-through operated as a recurring service.
Scope: An agreed queue across one estate or a provider portfolio
Included
- Essential mobilisation or verification of the existing foundation
- Recurring cost-ingestion quality and allocation-drift review
- Budget, forecast-variance and anomaly investigation queue
- Usage-optimisation backlog with engineering owner and decision state
- Commitment coverage, utilisation, expiry and renewal review
- Selected SaaS and licence assignment, use and renewal review
- Approved implementation with expected result, verification and reversal
- Showback, unit-economics and business review pack
- Multi-account, subscription, project or entity views within the agreed portfolio
- Service hours, capacity, response objectives and escalation fixed in the SoW
- Current registers, runbooks, evidence index and Exit Kit
Cadence
- Operating review at the cadence agreed in the SoW
- Decision queue and evidence updated through the service period
- Portfolio and executive views where included in scope
Outcome
A live FinOps operating record where every material cost action has context, authority, ownership and a verified outcome.
Method and source
Built on public standards and provider-native cost data.
The service uses the FinOps Framework as an operating reference and FOCUS as a common cost-data language where available. That is methodology alignment, not certification or affiliation.
Framework
FinOps Framework 2026
Current domains cover usage and cost, business value, optimisation and practice operations.
Data language
FOCUS-ready
Billed, effective, contracted and list cost stay distinct where the source supports them.
Provider tooling
Native first
Existing exports, cost platforms and alerting are reused before another tool is proposed.
Commercial claim
No guaranteed saving
Potential, approved and realised cost effects are reported separately.
FinOps Foundation
FinOps Framework
The operating framework for business value, accountability, optimisation and practice management.
Open official sourceFinOps Foundation
FOCUS specification
The open specification for normalising cost and usage data across technology providers.
Open official sourceMicrosoft Learn
Microsoft Cost Management
Official guidance for cost analysis, exports, budgets, anomalies, allocation and optimisation.
Open official sourceAWS Documentation
AWS Data Exports
Official AWS documentation for detailed cost and usage exports, including CUR 2.0 and FOCUS tables.
Open official sourceGoogle Cloud Documentation
Cloud Billing export to BigQuery
Official setup guidance for standard, detailed, pricing and commitment metadata exports.
Open official sourceQuestions before scope
The cost model, authority and evidence route should be clear before access is granted.
These answers define how the service treats data, savings claims, commitments, existing tooling and recurring operations.
Can this cover one cloud account and a multi-cloud portfolio?+
Yes. The scope can be one billing estate or a portfolio across Azure, AWS, Google Cloud, Microsoft 365 and selected SaaS. Each provider, entity, currency and account boundary is named in the SoW, and each retains its source lineage.
Do you replace our existing FinOps platform or native cost tooling?+
No. We use the native exports and tools already present, and can operate on top of an existing FinOps platform. A new tool is proposed only when a capability gap justifies its cost and operating burden.
What access do you need?+
The baseline starts with the smallest useful read scope for billing, cost, usage and selected licence reports. Production data-plane access is not a default requirement. Any later policy or resource change uses separate, approved and time-bounded authority.
Do you guarantee a savings percentage?+
No. A percentage before seeing the estate would be a sales claim, not evidence. We separate potential, approved and realised cost effects, and report the assumptions, exclusions and operating impact behind each one.
Will ITSailor purchase reservations or other commitments for us?+
Not from a tool recommendation alone. We model eligible spend, utilisation, coverage, term, currency and downside. The named client commercial authority approves and signs the commitment.
What counts as a realised cost effect?+
The definition is agreed with Finance during the baseline. Provider credits, negotiated rates, commitment effects, avoided future cost and invoice reductions remain separate so the report does not turn unlike-for-like values into one savings number.
Are you certified by or affiliated with the FinOps Foundation?+
No affiliation or certification is claimed. We use the public FinOps Framework and FOCUS specification as reference points, and link the official sources so the mapping can be checked.
Is Operate a 24/7 cost desk or an unlimited engineering retainer?+
No. Providers, request types, service hours, capacity, response objectives and escalation are written into the SoW. A staffed 24/7 desk, application refactoring and major platform change are separate scopes.
Make each material cloud cost action explainable and inspectable.
Scope one billing estate or a portfolio. Each provider and entity keeps its source lineage, authority, decision record and handover.