Hand off a won deal

What the catalogue records

superseded by JTBD-DS-01, which is the current row for this job and carries its evidence. This row is kept because "hand off a won deal" is the phrasing a reader or an agent searches for; it said "there is no handover process, no delivery project and no acceptance" long after M13, M14a and M14b2 shipped all three, so the same file answered the same question two opposite ways. Activating a contract (M12) records explicit pending obligations from the signed order; M13 turns them into a Delivery Project with work packages and milestones, M14a runs it, M14b2 records deliverables and acceptance.

Evidence

Proved by these tests, which run on every push:

What this status does not mean

A status here describes this repository at this commit, nothing more. It is not a statement about what a CRM should do, and it is not a roadmap commitment. The whole framework is local-development-only: there is no authentication, tenancy or RBAC, so no status on this page implies you can deploy it. The boundaries are listed in full on the claims ledger.

Other jobs in CRM JTBD validation matrix

• Manage a custom CRM business object end to end — validated end to end
• Associate a generated CRM record with another generated CRM record — validated end to end
• Request commercial approval on a deal — validated end to end
• Manage a deal through pipeline stages — validated end to end
• Capture a lead — validated end to end
• Qualify (or disqualify) a lead — validated end to end
• Convert a qualified lead into Company, Contact and Opportunity — validated end to end
• Manage a custom object with an approval rule — partially supported

All 17 jobs in CRM JTBD validation matrix · the whole catalogue