Prepare a review for each managed scope.

Use a repeatable process for source costs, findings and customer follow-up. Keep each customer's permissions, currency and reporting terms with its own review.

Explore a sample review

Scope register for a repeatable review

Managed-scope reviewRepeat the method. Keep the reviews separate.

Scope recordStart with the boundary.

Included scope: Account, subscription or project
Authorization: Read permissions for this scope
Financial window: Period · native currency · cost basis

Keep collection gaps and permission limits visible.

Review packetPrepare the customer’s next step.

Finding context: Source, owner and evidence limits
Decision: Customer review and rationale
Follow-up: Supporting measurement; outcome may remain inconclusive

External implementation stays with the customer.

Conceptual review templates, not customer data or a cross-customer dashboard. Managed-service onboarding, reporting terms and scope availability need agreement.

Discuss managed-scope terms

Your starting point

Scopes with different collection windows, access and reporting terms.

What Costframe adds

Read-only cost and finding evidence, explicit limitations and supported review records.

The next team discussion

A scope-specific report and accountable follow-up, with commercial/reporting terms agreed where needed.

Confirm customer boundaries and pilot eligibility.

MSP onboarding, custom limits, multi-tenant expansion and reporting terms depend on the agreed plan and validated scope. Customer-scope authorization and provider availability apply to every review.

Azure is generally available. AWS is a private pilot and Google Cloud a private preview. Evidence coverage, native currency and permissions remain explicit; your team implements changes outside Costframe.

Provider scope and setup

Agree the first managed scope.

Check account authorization, evidence coverage and commercial terms before onboarding that customer.

Start with Costframe