Sales-to-delivery agency handoff
A closed sale becomes a controlled launch: commercial readiness, access, workspace and delivery ownership converge before kickoff.
Case note
The implementation was treated as a small operating system: visibility first, ownership next, automation only after the workflow was clear.
Use case
Sales-to-delivery agency handoff
A closed sale becomes a controlled launch: commercial readiness, access, workspace and delivery ownership converge before kickoff. A growing digital agency was winning work faster than it could standardize the handoff. Sales context lived in the CRM, commercial readiness in documents, access requests in chat and delivery setup in individual habits. Kickoffs repeated discovery because no single launch state was trusted.
Result: Delivery receives a launch package, not a forwarded sales conversation. Each readiness lane has an owner, blockers stay visible and the workspace, first tasks, agenda and client responsibilities are created only after the project is genuinely ready.
Workflow map
Handoff workflow from sold deal to kickoff pack
The workflow turns sales context into delivery tasks, folders and access checks before kickoff.
Main database: Supabase
The workflow uses Supabase as the source of truth: it stores each record, status, and key event so the team can see what happened, retry failures, and debug without searching every tool.
Tool icons
System rationale
A handoff is not one event; it is a readiness system
The handoff only works when commercial, legal, access and delivery setup are connected. This case turns accepted work into a kickoff-ready state, then creates the workspace and first tasks.
Readiness comes first
A client should not create delivery noise until contract, payment, owner and access questions are visible.
Access needs rules
The workflow asks for access with purpose, owner and credential handling rules instead of collecting secrets in chat.
Workspace creation should be repeatable
Folders, kickoff pack, questionnaire and first tasks are produced from the same source so every project starts cleanly.
Add-ons that fit on top
The starting point
A growing digital agency was winning work faster than it could standardize the handoff. Sales context lived in the CRM, commercial readiness in documents, access requests in chat and delivery setup in individual habits. Kickoffs repeated discovery because no single launch state was trusted.
The diagnosis used real volume, connected tools, decision points and exceptions. The question was not only what to automate, but what proof would show that the workflow had completed correctly. The operating proof mattered as much as the automation.
The implementation
Ductio split handoff into readiness and workspace creation. Proposal accepted creates commercial/legal/access checks; safe access requests and credential rules are drafted; required items determine whether the client is ready for kickoff; once ready, Google Workspace folders, kickoff agenda, discovery questionnaire and ClickUp delivery tasks are prepared.
The implementation separated rules, free-text context, human decisions and external effects. That let the system improve daily work without turning every exception into a black box. AI as support inside the process, not as autopilot.
What was used
Tooling was chosen from the process outward, not from a pre-decided technical preference. Each piece needed a clear owner, a stable integration path and a simple way to inspect errors.
In practice, the build combined Supabase, Python/FastAPI, OpenRouter, Google Workspace adapter, ClickUp, Resend-ready email. The tools visible to the team stayed close to their daily work, while integration logic was documented and kept separate from sensitive commercial decisions.
The improvement showed up in daily work.
Rather than treating the result as a dashboard, the team felt it in three specific moments: less manual preparation, less context hunting, and fewer doubts about who needed to act.
Handoff prep: Ops time before kickoff moved from 120 min to 15 min.
Missing access: Unresolved access blockers moved from Untracked to Queued.
Brief consistency: Delivery-ready context moved from Variable to Standard.
Before/after proof
What changed in the operation
Before
After
Visible artifacts
- Commercial readiness checklist
- Access inventory
- Safe access request draft
- Kickoff agenda
- Discovery questionnaire
- Folder structure
- First delivery tasks
- Launch criteria
Controls
- No secrets stored
- Access requests use least privilege
- Checklist blocks kickoff when required items are missing
- Credential rules included in client email
- Human review before client-facing message
What changed after launch
Delivery receives a launch package, not a forwarded sales conversation. Each readiness lane has an owner, blockers stay visible and the workspace, first tasks, agenda and client responsibilities are created only after the project is genuinely ready.
The result was not only saved minutes. The team gained a shared sequence for reviewing inputs, understanding context, deciding, acting and checking that the workflow had been recorded. 15 min handoff
The workflow in one line
How it was built
The workflow uses client_readiness, access_inventory, onboarding_workspaces, onboarding_tasks and event logs in Supabase. OpenRouter drafts access packages and kickoff packs; Google Workspace creates folder structures when configured; ClickUp receives first delivery tasks when configured.
The stack was pragmatic: Supabase, Python/FastAPI, OpenRouter, Google Workspace adapter, ClickUp, Resend-ready email. Tools were chosen for ownership, integration and maintainability, not for theater. The result is a system the team can understand and operate.
What was delivered
- Proposal-accepted trigger
- Commercial/legal checklist
- Access inventory
- Credential rules
- Client folder plan
- Kickoff pack
- Discovery questionnaire
- ClickUp task sync
- Launch criteria
- Handoff preparation moved from around 2 hours to about 15 minutes.
- Kickoffs started with sales context, scope, access state and first tasks already visible.
- Missing access became a tracked exception with owner and review date.
- Credential handling rules made access collection safer and more professional.
- Delivery owners received the same kickoff pack instead of interpreting sales notes differently.
- Clients only moved to workspace creation after readiness checks passed.
- Every launch blocker carries an owner and next review point instead of disappearing into chat.
