mission-finops services --other
Other engagements.
Cost investigation, commitment decision review, allocation and evidence foundation work, team enablement, and ongoing investigation partnership. These are available on request, alongside the five lead offers on the services page.
AWS Cost Investigation
One material AWS cost question, traced through usage, architecture, ownership, and commitments, ending in a documented answer you can act on.
Trigger
- Unexpected or disputed spend movement
- Finance and engineering reporting different numbers
- Optimization recommendations engineering rejects
- Ownership or cost attribution cannot be established
Method. The investigation isolates the charge movement, tests each candidate explanation against usage, architecture, ownership, and commitment evidence, and records where the evidence stops.
Deliverables
- Agreed investigation question and evidence record
- Conclusion and confidence; supporting, contradicting, and missing evidence
- Ownership, trade-offs, and recommended next decision
- Written decision memo and a 60-minute engineering and finance readout
Timing. Typically seven business days after the agreed evidence is complete and accessible. Customer-operated, export-based, or supervised read-level analysis.
Fixed fee, agreed in writing before work begins. The fee is scoped to the size of the estate and the complexity of the question.
This price applies when the question can be scoped as one defined investigation. Multi-estate, multi-question, urgent, or unusually complex work is scoped separately before work begins.
For standard investigations, 50% is due at kickoff and 50% on delivery. Enterprise procurement and purchase-order terms can be accommodated where appropriate.
AWS Commitment Decision Review
A Savings Plans/RI decision, an EDP, PPA, or renewal discussion, or a disputed forecast, with a planned migration, modernization, or demand change affecting commitment confidence.
Method. The investigation separates demand assumptions, coverage, utilization, downside exposure, and break-even conditions.
Deliverables
- Spend and usage baseline; coverage and utilization assessment where relevant
- Conservative, expected, and downside scenarios, with an assumption ledger
- Workload and ownership validation requirements
- Commitment recommendation and deferral boundaries, a risk register, and an executive decision memo
Fixed-fee custom engagement. No promised discount, savings value, or AWS commercial outcome.
FinOps Evidence Foundation
Allocation, tags, account structure, ownership, exports, or reporting definitions cannot support reliable decisions; teams repeatedly rebuild cost evidence by hand; finance, engineering, and FinOps use incompatible numbers.
Method. The investigation normalizes scope, dates, credits, refunds, amortization, and charge definitions until the numbers reconcile, or until the remaining disagreement is documented. It traces available billing, resource, identity, and architecture evidence to record where ownership cannot yet be proven.
Scope may include
- AWS Data Exports/CUR evidence readiness; Cost Explorer and billing-view reconciliation
- Allocation dimensions and definitions; account, workload, application, environment, product, and owner mappings
- Tagging and non-tag allocation strategy; shared-cost and platform-cost treatment
- Evidence gaps and operating runbook; prioritized implementation backlog
Deliverables are analysis, design, documentation, and working sessions unless an engagement explicitly includes implementation.
Fixed-fee project.
Team Enablement / Shadow Investigation
Work the investigation alongside me so the evidence method transfers to your FinOps, platform, engineering, and finance teams: question framing, accounting-view selection, evidence reconciliation, causal reasoning, confidence and missing-evidence practices, ownership resolution, and decision memo construction.
Workshop or engagement add-on. Ask about enablement.
Investigation Partner
Priority access when the next material AWS question appears, without creating a managed-service dependency.
- No 24/7 monitoring, no on-call obligation
- No staff augmentation, no implementation team
- No autonomous remediation
- Full investigations are scoped separately
Retainer.
Kulshan-assisted Evidence Review
Customer-operated analysis for organizations or practitioners that cannot grant direct AWS access.
- 1
- Customer or partner runs Kulshan.
- 2
- Customer reviews and approves the evidence package.
- 3
- Mission FinOps receives only the agreed output.
- 4
- Mission FinOps delivers an evidence assessment and identifies what can and cannot be concluded.
Fixed-fee review.
engage --init
How all engagements begin.
Thirty minutes, free. A live look at your bill, forecast, or the AWS decision behind it. No slides. Before work begins, the question, evidence requirements, deliverable, timeline, commercial terms, and definition of done are agreed in writing.
calendar → book