What do I hand to the delivery team when a deal closes so nothing sold gets lost?

By Ranjit Bhinge, founder of Blur Studio · Updated · 6 min read

Short answer: Hand the delivery team a one page brief, hold a 20 minute sync between the person who sold the work and the person who will lead it, and only then talk to the client about kickoff. A handover is the moment a closed deal becomes a project: the promises, scope, budget and context move from sales to delivery. Software can create the project, the folder and the tasks from the won deal, but a person must still say what the client really wants and what was promised.

Ranjit Bhinge

You want the promises made in the sales call to reach the people doing the work, with nothing sold but not delivered.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Why handovers fail

A handover fails when the person who sold the work knows things the delivery team does not. The client said the launch date is fixed because of a trade show. The proposal says "up to three rounds of changes" but the sales call promised "as many as it takes." The real decision maker is not the person on the email thread. None of that is in the contract, and all of it matters. Engineers call this a low "bus factor", the minimum number of team members who would have to disappear before a project stalls. A bus factor of one is a single point of failure. And per Wikipedia's article on delegation, a manager who delegates remains responsible for whether the task is carried out well, so the seller and the delivery lead both need the full picture.

Most guides on this topic come from software vendors, so they tell you to buy a tool and let it move the data. A tool can move fields. It cannot tell you what the client was worried about on the call. So the handover process has two parts: a human part that captures context, and a software part that removes the retyping.

The one page brief

Every closed deal gets one page, written by the seller, before the project starts. If it takes more than 15 minutes to write, you are writing too much. Use these fields.

FieldWhat to write
Client and who mattersCompany, day-to-day contact, who signs off, who has a veto
Why they boughtThe business problem in the client's own words
What we soldDeliverables, quantities and the contract or proposal link
What we did not sellAnything discussed and left out, so nobody does it for free
Promises madeAnything said on calls that is not in the contract
Dates that cannot moveLaunch, event, board meeting, and the reason
Budget and billingPrice, payment schedule, retainer hours, change rate
Risks and sensitivitiesPast bad experiences, internal politics, tools they insist on
Access neededLogins, brand files, analytics and who provides them
Success measureWhat the client will look at in three months to call it a win

"What we did not sell" and "Promises made" are the two fields most briefs skip, and they prevent most scope arguments later. My guide to agency client onboarding picks up where this brief ends.

The internal sync: a 20 minute agenda

Do not just email the brief. People skim emails. Hold a short call or meeting with the seller, the delivery lead and, if you have one, the account manager. Use this agenda.

  1. Two minutes: the seller says why the client bought and what worries them.
  2. Five minutes: walk the brief field by field. The delivery lead asks questions.
  3. Five minutes: what looks risky? Timeline, budget, scope, people.
  4. Three minutes: who owns each of the first three tasks and by when.
  5. Five minutes: agree what the client hears at kickoff, and who says it.

The delivery lead has one job in this meeting: to say "that is not clear" until it is. If the seller cannot answer, that is the point of the meeting.

The kickoff checklist

After the internal sync, the client kickoff goes better. Before the call, check:

  • The contract or statement of work is signed and filed.
  • The first invoice or deposit is issued, according to your terms.
  • The project exists in your project tool with the agreed tasks and dates.
  • The client has a named contact on your team and knows how to reach them.
  • You have the access, files and logins you need, or a dated request for them.
  • The scope and change process, in a few sentences, are ready to be said aloud.

For a longer version, see the client onboarding checklist template for agencies. If paperwork is slow, my guide to sending proposals, MSAs and SOWs in one signing flow shortens it, and agency client onboarding software and client onboarding software compare tools for the kickoff stage.

What to automate at each step

Handing work from one person to another is an old problem. The broader chain from a customer's order to payment is called "order to cash", and "quote to cash" adds the pricing and quoting stage at the front. The handover sits in the middle of that chain. Software is good at the mechanical parts of it.

StepAutomateKeep human
Deal marked wonCreate the project, folders and task list from a template; notify the delivery leadDeciding the right template
BriefPre-fill client name, price, contract link and dates from the dealWriting "why they bought" and "promises made"
Internal syncBook the meeting automatically and attach the briefThe conversation
Kickoff prepSend the access request and the intake formTone and what the client hears first
BillingDraft the first invoiceApproving it
Missing itemsRemind the seller if the brief is not complete in 48 hoursChasing a late one in person

As an example of the first row, HubSpot, a customer relationship tool (CRM, a system for tracking leads and deals), describes workflows that can send emails, assign contacts to a user, update associated records and run a Create task action, listed as available on its Professional and Enterprise subscriptions. Many CRMs and project tools offer something similar, and a connector service such as Zapier, which passes data between apps when something happens, can fill gaps. Check your own tool's plan and limits. For the general idea, see business process automation.

The value of a written process also shows up outside sales. A standard operating procedure is a documented step-by-step guide that helps people do a routine task the same way each time. Your handover is one, and it should be short enough that people follow it.

A worked example with made-up figures

A 15-person marketing agency closes a $24,000 website and ads package. The figures are invented to show how the brief catches problems.

  • Why they bought: the client, a dental group, wants more new-patient bookings before opening a second clinic in March.
  • Sold: a 12-page site and a three-month ad campaign.
  • Not sold: logo redesign, which the client mentioned twice. Written down, so nobody does it for free.
  • Promise made: weekly report by email on Mondays. It was said on a call and is not in the contract, so it goes on the brief.
  • Date that cannot move: site live by February 15, two weeks before the clinic's open day.
  • Risk: the practice manager will review everything, and the owner is rarely available.

Without the brief, the delivery team would have found out about the Monday report in week three, when the client asked where it was. With it, the promise became a recurring task on day one. That is the benefit, and it is the whole case for the process.

The version for a team of five

If you are a small agency, the seller and the delivery lead may be the same person, or the founder does both. You still need the brief, because it is for the person who joins the project later and for you, six weeks from now, when you have forgotten the call. Skip the meeting, keep the one page, and have a second person read it and ask one question about it. That second read is where gaps show up.

Common failure points

  • The seller writes the brief a week late, after the client has already emailed twice.
  • The brief is a copy of the proposal and adds nothing.
  • Promises made on calls never reach the page.
  • The delivery lead meets the client for the first time at kickoff.
  • The CRM project template is out of date, so the automated task list is wrong.
  • Nobody owns the handover, so it only happens when someone remembers.

How I'd approach this

I would start with the one page brief and the 20 minute sync, with no software at all. Use it on the next three closed deals and see which fields keep coming back empty. Those tell you what your sales process fails to capture, which is a better thing to know than any tool feature.

Then I would automate the dull parts: create the project from the won deal, pre-fill the brief and remind the seller if it is late. If your tools do not connect and a person retypes the deal into the project tool every time, that small gap is a good first custom fix. Blur Studio fixes and finishes start around $1,500, and I will say so plainly if a connector tool would do it for less. I would not automate the sync call or the "promises made" field. Those are where a person has to think.

Questions people ask

What is a sales to delivery handover?

It is the moment a closed deal turns into a project. The seller passes what was promised, the scope, the budget, the dates and the context about the client to the people who will do the work, usually through a short written brief and a short meeting.

What should a handover brief include?

Who matters at the client, why they bought, what was sold, what was left out, promises made on calls, dates that cannot move, budget and billing, risks, access needed and how the client will measure success. The table in this guide lists all ten fields.

How long should a handover meeting take?

About 20 minutes with the seller and the delivery lead. Longer means the brief was not clear. Shorter usually means nobody asked questions.

Can I automate the handover completely?

No. You can automate creating the project, pre-filling the brief and sending reminders. The context, such as why the client bought and what was promised on calls, needs a person. See business process automation.

What is the difference between handover and onboarding?

Handover is internal: sales tells delivery what was sold. Onboarding is with the client: access, kickoff and first tasks. Do the handover first. My agency client onboarding guide covers the next stage.

Who should own the handover?

Name one person, usually the delivery lead or an operations manager, who confirms the brief is complete before the project starts. If nobody owns it, it happens only when someone remembers.

More in this topic: Problem solving: automating service business work (21 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…