Sales to delivery handoff: a template for small teams
A won deal still has to become work someone owns. A short handoff template for small teams, and how an AI agent can prepare it the moment a deal is won.
5 min read
Key takeaways
- Handoffs break in small teams when the final agreement sits in a proposal, an email, and someone's memory, and nobody separates it from the conversation that led to it.
- A useful handoff covers five things: the agreed outcome, the source of the agreement, commitments and dependencies, a delivery owner with a first action, and open questions.
- Mark anything that was discussed but never confirmed as an open question with an owner, so delivery doesn't plan work nobody sold.
- An Opser agent can draft the handoff from the deal's notes, documents, and emails, and an automation can start it the moment a deal is marked won.
- The handoff is done when the person taking over can explain the commitment, open the agreement, and start the first task.
A three-person design studio closes a website project with a group of dental clinics. The proposal promises launch in six weeks, as long as the clinics send their copy by the end of week two. On the closing call, the founder also agrees to "take a look at" an online booking page. The clinics hear yes.
The designer who picks up the project reads the proposal and plans six weeks of work without a booking page and without chasing the copy. Two weeks in, the clinics ask how the booking page is going, and the launch date is already slipping.
Nobody did anything wrong. The final agreement just lived in three places: a proposal, an email thread, and the founder's memory. A short handoff fixes that. It says what was agreed, where the evidence is, who takes over, and what happens first, and it takes a few minutes to write. Our guide to never missing a customer follow-up covers keeping a deal moving until it closes. This is the next step: turning the win into work someone owns.
Why do sales-to-delivery handoffs break in small teams?
In a small company, sales and delivery might be two people, or the same founder on different days. You still have a handoff problem as soon as there's a gap between making a promise and carrying it out.
Most teams have plenty of notes. What they lack is a line between the conversation and the conclusion. Sales calls wander through options, extras, and maybes. The person delivering needs to know which of those became commitments, and which are still open.
So a good handoff does one job above all: it separates what was confirmed from what was only discussed, and points to the source for each.
What should a customer handoff include?
Keep it short enough that people actually write it, and specific enough that the next person can act without replaying the sale.
- The agreed outcome. What the customer is buying and what a successful first delivery looks like. "Website project" names a category. "Launch the agreed eight pages, with the clinics approving final copy before publication" describes an outcome. Write down exclusions that matter.
- The source of the agreement. A link to the accepted proposal or written scope, and to any customer email that changed it. The brief points to the agreement and explains the work it creates, so you never maintain a second contract by hand.
- Commitments and dependencies. Dates promised to the customer, kept apart from internal targets. What the customer has to provide, who approves the work, and what could stop you from starting.
- A delivery owner and a first action. One named person, and the first concrete step with a due date if one was agreed. "Confirm the copy deadline with the clinics' office manager" beats "start onboarding".
- Open questions. Anything discussed but never confirmed, each with a person who will settle it.
Sales to delivery handoff template
Copy this into your wiki and fill it in for every won deal:
| Field | What to write |
|---|---|
| Customer and deal | Links to the customer record and the won deal |
| Agreed outcome | What you'll deliver, including important exclusions |
| Agreement | Link to the accepted scope, and which version is current |
| Commitments | Confirmed dates, deliverables, and promises made to the customer |
| Dependencies | What you need from the customer or a teammate before work can move |
| Delivery owner | The person taking responsibility for the next phase |
| First action | A concrete task, its owner, and the agreed due date if there is one |
| Open questions | What still needs an answer, and who will get it |
For the dental clinics, the most valuable line in the whole brief would read: "Booking page discussed on the closing call, not in the accepted proposal. Founder to confirm with the clinics by Friday whether it's in scope and at what price." That one sentence saves two weeks of planning the wrong project.
How can an AI agent prepare the handoff?
Reading through a deal's notes, the proposal, and a long email thread is exactly the kind of work an agent does well. In Opser, your agent can read the deal and its notes and documents in Customers, and the customer's emails if your mailbox is connected. Ask it for a specific result:
Prepare a sales to delivery handoff for the dental clinics deal using our template in Wiki. Link each commitment to the note, document, or email it comes from. Keep confirmed scope apart from requests that were only discussed, flag dates that conflict, and list anything you couldn't find. Propose the first delivery tasks, but don't create them yet.
You read the draft, settle the open questions, and say go. The agent then saves the brief as a note on the deal, creates a project and the first tasks with owners and due dates in Tasks, and posts a short summary to your delivery channel. The template itself lives in Wiki, so every handoff follows the latest version your team agreed on.
Can the handoff start automatically when a deal is won?
Yes. Customers announces the moment a deal is marked won, and your agent can turn that into an automation. Tell it:
When a deal is marked won in Customers, draft a handoff brief from the deal's notes, documents, and recent emails, using the template in Wiki. Save it as a note on the deal, create a project with the proposed first tasks assigned to the deal owner for review, and post a summary in #delivery.
From then on, every won deal arrives in delivery with a draft brief and a starting task list, while the details are still fresh. The automation runs on its own, and setting it up approves what its instructions describe. That's why the example hands the tasks to the deal owner for review and leaves anything customer-facing to a person. Each run shows up in the automation's own chat, so you can see what it did for every deal.
How do you know the handoff is complete?
The handoff is done when the person taking over can answer yes to four questions:
- Do I know what's included and what isn't?
- Can I open the agreement and the material behind it?
- Do I know the first task and who owns it?
- Does every open question have someone who will answer it?
A short written "got it" on the brief is enough. After the first few weeks of the project, look back at the questions the delivery owner still had to ask, and add those fields to the template. Within a month or two the template fits how your team actually sells.
Frequently asked questions
- What is a sales to delivery handoff?
- It's the moment a won deal passes from the person who sold it to the person who delivers it. A good handoff records what was agreed, where the agreement lives, who owns the next step, and what's still unclear.
- Do we need a handoff if the founder sells and delivers?
- Yes, as soon as delivery starts days or weeks after the sale, or someone else joins the project. Writing the commitment down once saves reconstructing it from memory later, and makes it easy to hand the work to a teammate.
- Is a kickoff meeting enough?
- A kickoff is good for questions and introductions. The decisions it produces still need to land in the handoff brief, so the scope and owners are written down where the team works.
- Can Opser start the handoff automatically when a deal is won?
- Yes. Customers announces when a deal is marked won, and you can ask your agent to set up an automation that reacts to it, for example by drafting the handoff brief, creating the first tasks, and posting a summary to your delivery channel. An automation runs on its own and is allowed to do what its instructions describe, so ask for drafts if you want to review before anything is created.
- Can an AI agent decide what the customer actually bought?
- It can find every source that mentions scope and flag where they disagree. Deciding which promise stands is a call for the person who sold the deal, and the brief should record that call.
Founder · Senior Software Engineer
Simone Zamparini is a founder and senior software engineer.
