Closed-Won Handoff Packet Generator
Turn every closed-won deal into a complete, validated handoff packet — what was sold, the terms, the promises, the contacts, the timeline — so customer success and delivery start with the full picture instead of chasing the rep.
A private internal app where reps fill a completeness-validated handoff form on a won deal, a packet is generated, and the receiving CS/delivery lead reviews and accepts (or sends it back) before onboarding is triggered — with a full audit trail and PDF/CSV export.
Before you start
- A free Supabase account
- A free Vercel account
- A free Resend account (for handoff notifications)
- Your won-deal data — from your CRM, or a Google Sheet / CSV export if you have no API yet
The problem this kills
A deal closes. The rep celebrates and moves to the next one. Then customer success and delivery inherit a mess: nobody knows exactly what was sold, what discount was promised, which contact actually signs off, or that the rep verbally agreed to a custom go-live date. So delivery spends the first week of a brand-new relationship chasing the rep for answers — and discovers surprise commitments only after the customer brings them up.
Incomplete handoffs aren't a paperwork problem. They're the reason onboarding starts slow, the customer's first impression sours, and revenue you already won leaks back out through churn.
What you'll build
A private internal web app that makes a clean handoff non-optional:
- The rep opens the won deal and fills a handoff form that won't submit until every required field is complete — line items, pricing and terms, key contacts, timeline, and any non-standard promises spelled out explicitly.
- The app generates a handoff packet the receiving team can actually read.
- The CS or delivery lead reviews and accepts the packet — or sends it back with the gaps flagged. Nothing is "handed off" until a human on the receiving side accepts it.
- On acceptance, the packet is committed, kickoff is triggered, and the receiving team is notified by email. You can export any packet to PDF or CSV.
What's inside the Implementation Plan
- It interviews you first. Before building anything, the plan has the AI agent ask you about your real handoff process — your CRM and field names, how you label line items and SKUs, who receives handoffs, your required-field rules, and the messy exceptions. It reads back a short tailored spec for your thumbs-up, then builds the tool around your business — not a generic template.
- A step-by-step build you paste into Claude Code one prompt at a time.
- The data model for deals, handoff packets, required-field rules, and versions.
- A completeness validator so half-baked handoffs literally cannot pass.
- The reviewer accept / reject flow, with rejection creating a new version of the packet — never a duplicate.
- Email notifications on acceptance, plus PDF and CSV export.
- A "No API yet?" fallback: pull deal data from a Google Sheet or CSV and export packets as PDF/CSV in the exact columns your system expects — so it's fully buildable today.
The governance it includes (this is the point)
- Login so only your team can use the tool.
- Row-level security so people only ever see their own organization's deals and packets.
- A complete audit trail — who filled, generated, accepted, or rejected each handoff, and when.
- A hard human-in-the-loop gate: the rep drafts, the receiving lead reviews, and only an accepted packet is committed and triggers kickoff.
- Duplicate guards keyed on the deal ID, so a won deal can have exactly one active handoff; a rejection spins up a new version instead of a second record.
Who it's for
Sales ops, customer success, and delivery teams plagued by incomplete handoffs and surprise commitments — anyone tired of the post-sale game of telephone between the rep and the people who have to deliver what was sold.
You've got this — paste the first prompt and let the agent interview you.