Where the job disappears
Sales closes a deal on Thursday. They send an email to operations with 'new one for you, details attached'. Operations are busy, the email sits under forty others, and on Tuesday the customer rings asking when the installation is booked.
Or the handover happens, but half the information is missing. The site contact, the special access arrangements, the agreed discount. So operations email sales back, sales are out, and the job sits waiting for an answer.
Every business with more than one team has a version of this. It gets worse as you grow, because the people who used to just shout across the office now sit in different rooms or different towns.
Why handovers leak
The obvious explanation is that someone forgot. The real one is that the handover is not a defined step. It is an informal message, sent in whatever way the sender prefers, containing whatever they think is relevant.
That creates three gaps. There is no agreed list of what must be handed over, so things are missed. There is no single place it arrives, so it can be buried. And there is no one whose job it is to accept it, so it can sit unowned while each team assumes the other has it.
The damage done in the gap
| Symptom | Who feels it |
|---|---|
| Customer chases for a start date | The customer, then whoever answers the phone |
| Operations start without key details | The team on site, and later the customer |
| Back-and-forth emails to fill gaps | Both teams, repeatedly |
| Promises made in sales not honoured | The customer relationship |
| Nobody can say how long handovers take | Management trying to plan capacity |
The last row matters more than it looks. If you cannot see the gap, you cannot measure it, and you cannot fix it.
How we build a handover that cannot be lost
- Map each handover point with the teams on both sides: sales to operations, operations to finance, operations to aftercare. For each one, list what the receiving team actually needs.
- Turn that list into required fields in the system where the work starts, for example a deal stage in HubSpot or Salesforce that cannot be marked won until the handover fields are filled.
- Trigger the handover automatically when the stage changes. The system creates a job or task in the receiving team's tool, carrying all the data and attachments.
- Assign a named owner in the receiving team, using simple rules such as region, product or workload.
- Require an explicit 'accepted' step. If a handover is not accepted within the window you set, it escalates to a team lead.
- Show every open handover on a shared board, with its age and owner, so both teams can see what is in the gap.
We build this in the tools you already use where they can support it, connecting them through their APIs, with n8n or a small custom service in the middle. If your tools cannot hold the structure, we build a lightweight handover app that sits between them.
What the teams notice
Sales cannot close a deal without the details operations need, so the follow-up emails mostly stop. Operations get a complete job in their own system, not an email to decode. Nobody has to wonder whether the other team has picked something up, because it shows as accepted or not.
And for the first time you can see how long work waits between teams, which tells you where to add capacity.
There is a softer change too. Handover arguments tend to be about blame: sales say they sent it, operations say they never got it. When the handover is a record with a timestamp, an owner and an accepted flag, that argument has nowhere to go, and the conversation moves on to fixing whatever caused the delay.
We also keep the checklist editable. When operations discover they need a new piece of information from sales, a manager adds the field and the next handover includes it, without a new project.
Is this happening between your teams?
- Handovers are done by email, chat message or a quick word.
- The receiving team often has to go back for missing information.
- Customers chase you for updates after they have signed.
- Each team thinks the other has the job.
- You cannot say how many jobs are currently waiting between departments.