Built for desktopYou can preview it here on mobile. Open it on a desktop for the fuller, more advanced version.
synthetic account · client-side · no data collected
Post-close acceptance gate
Run the handoff. Read one decision.
4 of 6 checks are in. Still open: Stakeholder map (missing), Implementation readiness (missing).
Evidence ledger
4 present · 2 to resolveAccepted with a controlled hold
Accept, prepare, hold one milestone
Customer Success can take ownership and prepare, but 2 readiness items are unresolved, so the kickoff is held.
What the system does now
AssignCustomer Success Operations as receiving owner
Createthe first milestone: a value-planning kickoff
Holdthe affected milestone until readiness clears
Logroute, owner, and source links
Held · with a named owner
Stakeholder map · Account ExecutiveName the technical owner who can approve implementation.
Implementation readiness · Onboarding leadConfirm the migration owner; reset the kickoff if it moves.
The red line
Why a stage change is not a handoff
A deal reaching Closed Won looks like an ending. For the team that inherits the account it is a beginning, and often a blind one. The stage changed in the CRM, but the reason the customer bought, the signed scope, the person who can approve the work, and the plan for the first milestone can still be missing or contradictory.
This gate treats the stage change as a trigger, not a completion. It collects the evidence a receiving team actually needs, checks it against one fixed rule, and routes the account to one of four outcomes: accept, accept with a hold, return for completion, or escalate. Readiness gaps are prepared around and held. Missing hard evidence is sent back. Conflicting records go to a named person, never settled by the system guessing a commercial answer.
So the account never slips into follow-up messages, spreadsheets and verbal fixes between teams. The handoff counts as complete only when the receiving owner can act safely, and another operator can see in the record how any exception was recovered.
Generated automation recipe
TRIGGER Deal stage → Closed WonCOLLECT account · scope · brief · stakeholders · readinessVALIDATE outcome · commercial · people · readiness · ownership · evidenceROUTE Accept, prepare, hold one milestone → Assign Customer Success Operations; resolve the readiness queue before a value-planning kickoff.IF MISSING stakeholder map → Name the technical owner who can approve implementation.IF MISSING implementation readiness → Confirm the migration owner; reset the kickoff if it moves.PROOF Accepted only when Customer Success Operations acknowledges ownership and the first milestone exists.
The operating rule
Do not mark a handoff complete because a CRM stage changed. Mark it complete when the receiving team can act safely and another operator can see how to recover an exception.
What this models
A Mannvit concept build for making the handoff decision, its missing evidence, and its next owner visible. It is not a CRM or a contract review.