Choose a CRM-centered model when the unresolved work is lead qualification, opportunity movement, or follow-up before an agreement. Choose a project-management-centered model when the main operating pressure begins after work is sold. Use both only when the signed-client handoff and record ownership are explicit.
The choice sets the center of active client operations. Product choice and the rest of the stack come later.
Locate the work that loses context
Review recent exceptions and ask where the missing next action occurred:
- before an agreement, while a lead or proposal needed follow-up;
- after an agreement, while tasks, milestones, approvals, or deliverables moved;
- at the transition between those states.
Use the client workflow guide first if you cannot locate the stage. Read system of record if the authority question itself is unclear.
Three operating models
| Model | Authoritative operating record | Accepted tradeoff |
|---|---|---|
| CRM-centered | Lead, relationship, opportunity, and pre-sale next action | Delivery detail needs a defined home or a deliberate handoff |
| Project-management-centered | Active work, milestone, owner, blocker, and deliverable | Pre-sale follow-up may require a lighter separate record |
| Hybrid | CRM before the signed-client boundary; project system after it | Two systems require a maintained transition and field boundary |
The model names describe ownership, not product capability. A CRM can contain tasks and a project tool can contain pipeline fields. The question is which record the operating routine treats as authoritative.
Test the boundary
Finish these sentences:
- Before an agreement, current client status lives in ________.
- The event that creates active delivery is ________.
- After that event, current client status lives in ________.
- The person responsible for the transition is ________.
- Billing status is authoritative in ________ and visible in ________.
A hybrid model is not ready when the same stage or next action must be updated independently in both systems.
Choose from the failure condition
Use a CRM-centered model
This model fits when pre-sale work needs the tighter control. It can address missed follow-up, long-running proposals, several open opportunities, or relationship history that must remain visible before delivery starts.
Define where delivery tasks and approval records move after the agreement. Otherwise the CRM becomes a strong pipeline with a weak execution handoff.
Use a project-management-centered model
This model fits when delivery is the recurring control problem. It keeps milestones, dependencies, deliverables, owners, and blockers close to the weekly operating view.
Define a lightweight place for leads and proposals before kickoff. Without it, opportunities depend on memory or inbox search.
Use a hybrid model
Use two centers only when both pre-sale and delivery require their own maintained records. The signed-client transition must identify which fields move, which remain, and who verifies the result.
Choose hybrid only when one system cannot support a required workflow condition and the extra handoff has an owner.
Keep adjacent choices separate
This decision does not answer:
- whether the stack should stay consolidated;
- which CRM or project tool to buy;
- where client-facing approval should happen;
- whether billing detail must be mirrored into the operating record.
Resolve those questions after the system center is clear.
Implement the choice
- For any model, build the surrounding roles with the lean software stack blueprint.
- For a CRM-centered model, define qualification and handoff rules in the intake workflow.
- For a project-management-centered model, establish the first active record in the client onboarding workflow.
- For a hybrid model, document field ownership with the system-of-record rules worksheet.
- When invoice state affects delivery, use the billing-status comparison.
Write down the authoritative record on each side of the signed-client transition and name the owner responsible for moving the client between them.
