The Digital Developer Blog - Blogs by Computan

Client Handover Protocol: From Prospect to Customer

Written by Simranjeet Singh | April 8, 2025 at 10:03 AM

When a contact transitions from a prospect to a customer, it's a pivotal moment in the client journey. This change signifies a shift in responsibility, from the sales team, who have led conversations, handled estimates, scheduled calls, and answered questions, to the delivery team, who will now carry out the work promised.

The delivery team could be the HubSpot development team, WordPress development team, Shopify team, integration team, or others. This whole scenario came to light when I was working on the workflow and found it interesting enough to be a blog post on. So, I decided to share my experiences with the readers.

This document outlines how this handover should take place, what roles different team members play, and how we ensure a seamless transition that keeps the client confident and cared for.

1. The Moment of Transition

Once a prospect signs a contract and becomes a customer, it marks a formal handover of responsibility. Up to this point, the salesperson has been the client's main point of contact, handling communication, discovery, estimates, and coordination.

Now, the delivery begins, and with it, a new team steps in: Project Managers (PMs), Team Leads (TLs), developers, and other relevant team members.

2. Coordinating the First Handoff Call

The sales representative or the contact owner (in HubSpot jargon) is responsible for coordinating the initial handover call.

This call must include:

  • The Sales representative
  • The Project Manager (PM)
  • The Technical Team Lead (if applicable)

The goal is to start off on the right foot by making sure everyone is aligned, expectations are clear, and introductions are made. This gives the client confidence that the team is ready to deliver what was promised.

3. Responsibilities of the Sales Team Post-Handover

Even after the handoff, the salesperson should remain CC’d in communications, not to actively participate, but to stay in the loop. This gives the client reassurance that their original point of contact is still present and watching over the project.

However, once the delivery begins, the salesperson should not be involved in day-to-day project tasks or decision-making.

4. Minimizing Workload for Others

One key to being a good teammate is not creating extra tasks for others. Developers and PMs should not be bogged down with repeated or unnecessary questions, approvals, or coordination.

If you need something from a teammate (especially in sales), do the heavy lifting: write the question, suggest the answer, or draft the email.

When working with developers or PMs, don’t ask them to join unnecessary calls or review contracts. Respect their time, they are focused on delivery.

5. Filtering Tire-Kickers

Salespeople must be discerning. Not every prospect is serious. Some may simply be expressing interest without real intent.

Avoid bringing delivery team members into these interactions unless there's clear traction. Their time should be reserved for serious opportunities only.

6. When to Involve the Technical Team

Technical team involvement depends on the complexity of the opportunity:

  • Complex/technical projects: involve developers or PMs early during the prospect stage.
  • Simpler projects: wait until the contract is signed and ready for delivery.

Let there be common definitions of complex/technical projects and simpler projects among different departments in your company/agency.

If a trial task is involved, developers may be engaged earlier to estimate or execute the task, but that still follows a defined process.

7. Discovery and Option Presentations

In scenarios where the client needs guidance (e.g., deciding whether to fix an existing WordPress site or rebuild from scratch), the salesperson should lead the discovery process. Developers may offer technical insights and options, but:

  • Sales owns the conversation.
  • Sales drives the call.
  • Sales ensures both options are presented with clear estimates.

The developer’s role is to provide technical input, not to lead sales conversations. Respect their preferences, they're builders, not closers.

8. Final Notes

Handover should feel smooth, human, and reassuring.

Keep communication tight, roles clear, and the workload well-distributed.

The salesperson made the promise. The delivery team fulfills it. Both need to be respected in their zones of strength.

By following this protocol, we ensure a seamless experience for our clients and a respectful, efficient process for our team.

Frequently Asked Questions

What is a client handover protocol?

Answer: A client handover protocol is a structured process that transfers a prospect from the sales team to the delivery/operations team. It ensures all context, expectations, assets, and responsibilities move smoothly so the client experiences a seamless transition and the delivery team can start work without delays or confusion.

Who should lead the handover from sales/prospect to delivery/team?

Sales initiates the handover, but the Delivery/Account Manager should lead it. Sales provides the context, commitments,  and expectations; Delivery validates the scope, confirms timelines, and becomes the primary point of contact moving forward.

What information, credentials, assets, and access must be transferred during a handover?

A complete handover should include:

  • Client background (business model, goals, pain points, stakeholders)
  • Scope of work (what was promised, deliverables, exclusions, timelines)
  • Contracts & commercial details (pricing, terms, renewals)
  • Communication expectations (preferred channels, cadence, escalation path)
  • Technical credentials & assets: Website/CMS logins, Analytics, ads, social access,  Brand guidelines & creative, assets,  CRM or automation access,  Notes from sales conversations (red flags, decision drivers, priorities)

How do you maintain continuity of client experience and avoid “we’ve been sold this, but delivery looks different”?

  • Ensure sales and delivery align on scope before the proposal is shared.
  • Use standardized packages or clearly defined deliverables.
  • Include the Delivery/Account Manager in late-stage sales calls.
  • Provide a transparent Statement of Work and kickoff agenda.
  • Have Sales articulate “what was promised” during the handover call.
  • Reconfirm expectations during kickoff so delivery and the client hear the same message.

How can you avoid the most common mistakes in the handover from prospect to customer?

  • Don’t let sales oversell, but set realistic expectations.
  • Don’t skip internal handover calls.
  • Don’t start work without full access or a verified scope.
  • Don’t rely on Slack/DMs, but document everything in the CRM or PM tool.
  • Don’t assume delivery has the same context, but transfer it properly.
  • Don’t bombard the client with duplicate requests, but centralize asset collection.
  • Don’t rush the kickoff, clarify “what success looks like” before work begins.