Scope checklist

Define what the package really covers

The scope step should protect the operator from accidental overpromising by forcing a clear client outcome, included work, and required input.

State the client problem in plain language

A good service builder step should clarify what calms down after the service is delivered.

Define what is included and what is explicitly out of scope

The early package should trade breadth for clarity so the operator does not sell a vague all-services promise.

Write the first client input requirement

Every service needs a clear first handoff so the engagement can start without confusion.

Input surface

Capture the first scope anchors

Use simple builder inputs so the package can later feed the proposal and engagement work areas without rework.

Client outcome

Primary client input

Continue to pricingBack to service type

Standard viewNeeds-attention view