Use delivery capacity where the work repeats and ownership is clear.
The model is strongest when a practice already has client trust but needs a defined operational lane. It is weaker when the real problem is sales, strategy, an emergency project, or unresolved accountability.
A consultancy is carrying too much recurring support.
Pressure: senior consultants are interrupted by user requests, account changes, and routine administration after projects finish.
Possible boundary: accepted service-desk and Microsoft 365 administration move into a recurring lane; the consultancy keeps architecture, advisory decisions, and the client roadmap.
Decision before fit: define which requests are routine, which require consultant approval, and how client identity appears at intake.
Design the client-facing boundary →An MSP wants capacity for a specific client group.
Pressure: a new or existing client group fits the commercial offer, but the internal team should not absorb every recurring task immediately.
Possible boundary: one named group enters an agreed support or stewardship lane while the MSP keeps the contract, retail packaging, approvals, and executive relationship.
Decision before fit: separate ordinary recurring volume from projects, inherited technical debt, after-hours needs, and specialist applications.
Review the required inputs →A service firm is turning project clients into managed relationships.
Pressure: clients ask for ongoing support after deployments, but the firm’s delivery motion is still organized around projects.
Possible boundary: recurring operational work receives an intake path and cadence; project change remains separately estimated and approved.
Decision before fit: write the managed promise before selecting a plan. A project history alone does not define a support service.
Read the operating-model definition →Some pressure should not be outsourced into ambiguity.
| Emergency rescue | An urgent, unknown environment needs discovery and risk control before recurring delivery can be promised. |
|---|---|
| Unbounded “everything IT” | No delivery team can safely price or own a service whose inclusions and decision rights are undefined. |
| No relationship owner | A delivery partner cannot replace the commercial and advisory accountability the client expects from the selling practice. |
| Project-heavy demand | Migrations, remediations, and specialist work need separate estimation and approval rather than being hidden in a recurring lane. |
Map the client group before discussing price.
Use the fit tree for a quick go/not-yet decision, then the composer to record retained duties and the first constraint.