Skip to content
  • There are no suggestions because the search field is empty.

Sales to Delivery Handoff Process

Standard Operating Procedure

SOP Overview

This document defines the official Sales-to-Delivery Handoff process at Zipcio. It establishes a standardized, accountable workflow from the moment a deal is marked Closed Won in HubSpot to the moment a client kickoff is confirmed and delivery is formally underway.

 

Purpose

The purpose of this SOP is to:

  • Eliminate Errors: Eliminate implementation errors caused by incomplete or verbal-only knowledge transfer
  • Avoid gaps: Prevent client expectation gaps between what was sold and what is delivered
  • Accountability: Create internal accountability so no handoff step is left without an owner
  • Ensure Preparation: Ensure the Solutions Architect (SA) team is fully prepared before any client kickoff
  • Standardization: Standardize communication across Sales, Delivery, and Leadership
  • Scalability: Create a repeatable, scalable process that survives team growth and personnel changes

 

Roles and Responsibilities

Ownership is non-negotiable. Every action in this SOP has a named owner.

Role

Team

Owns

Account Executive (AE)

Sales
  • Accuracy of the signed contract
  • Stakeholder mapping and relationship context
  • Handoff Checklist in HubSpot at closed won
  • Participates in the internal handoff sync if flagged as complex
  • Documents any custom promises made during the sales cycle
  • Does NOT disappear after close - remains accountable until kickoff

Solutions Architect (SA)

Delivery
  • Post-close client experience
  • Reviews handoff checklist and flags missing information
  • Kickoff deck preparation
  • Validates all timelines before they are communicated to the client
  • Flags scope ambiguity or technical risk before kickoff begins

Head of Delivery

Leadership
  • Monitors handoff completion and SLA (Service Level Agreement) adherence
  • Receives escalation alerts when SA is non-responsive or handoff is stalled
  • Reviews red flag accounts before kickoff
  • Owns this SOP and reviews it quarterly

Automation

Hubspot
  • Sends kickoff email w/ link
  • Creates Clickup Client Space

 

What Sales is NOT Allowed to Promise

  • Specific go-live dates without Delivery sign-off
  • Custom feature builds or integrations not approved by scoping SA
  • Dedicated SA assignments (SA allocation is Head of Delivery's decision)
  • Implementation timelines faster than Zipcio's standard delivery windows
  • Support SLAs or response times not defined in the contract

Required Systems and Tools

 

Tool

Role in Handoff Process

HubSpot (CRM)
  • Source of truth for deal data
  • Handoff checklist properties
  • Workflow automation
  • Client email templates
  • All handoff steps must be logged here.

ClickUp (PM)
  • Client project management.
  • SA creates the client Space from the standard template post-close.
  • All implementation tasks live here.

Slack
  • Internal team communication.
  • SA receives automated handoff notification.
  • Client channel created during handoff window.

Gamma
  • Kickoff deck creation.
  • SA owns the client-specific kickoff deck built from the standard Gamma template.

Supered
  • Internal knowledge base and SA enablement.
  • Handoff SOP and training guides published here for SA onboarding.

 

Pre-Handoff Requirements

These are the AE's responsibility and must be completed at the time of Closed Won.

AE Must Confirm Before Handoff Initiates

  • Contract signed -
    • executed copy linked on the HubSpot deal record
  • Payment initiated -
    • first payment link sent and confirmed received (or payment terms documented)
  • Scope documented - in quote and contract:
    • Hubs purchased
    • Tiers
    • Add-ons recorded
  • Primary stakeholders identified - at minimum:
    • Main point of contact
    • Billing contact
    • Technical contact
  • Promised timeline recorded - communicated to the client in quote & email
    • Go-live date
    • Milestone dates
  • First value moment defined -
    • What does the client expect to see first
    • By when
  • Key client outcomes documented -
    • 2-3 things the client said they most want to achieve
  • Custom promises logged -
    • Any verbal commitment must be documented in the quote
  • Integration flags noted -
    • Any third-party tools the client needs connected are listed
  • Risk flags noted -
    • Anything that makes this engagement non-standard or higher risk is documented in the deal

 

 

Step-by-Step Handoff Workflow

There are four phases in the handoff. Each phase has a defined owner, trigger, and completion criteria. No phase begins until the previous one is complete.

 

Phase 1 - Deal Closed (AE Ownership)

Trigger: AE moves deal to Closed Won in HubSpot

STEP 1 AE MARKS DEAL CLOSED WON

  • AE updates deal stage to Closed Won in HubSpot
  • HubSpot automation fires immediately:
    • Head of Delivery is slacked/email to assign Solutions Architect Owner
  • HubSpot automations AFTER Solutions Architect Owner = KNOWN:
    • SA receives a Slack DM in #new-deal-assignment
    • ClickUp client space created
    • Slack client channel created
    • Hubspot client project created - stage set to ‘Schedule Kickoff’
    • Kickoff email sent to associated contacts includes:
      • Kickoff Booking Link
      • Call Overview

STEP 2 AE COMPLETES THE HANDOFF CHECKLIST

  • AE opens the Handoff Checklist task on the deal record in HubSpot
  • AE completes ALL required fields (see Section 6 for full list)
  • AE links the signed contract and proposal to the deal
  • AE sends the payment link if not already sent
  • Deadline: 1 business day from Closed Won

STEP 3 AE INTRODUCES DELIVERY TEAM

  • AE drafts Handoff Email - [TEMPLATE - Kickoff]
  • Updates relevant team members in template
  • AE sends Handoff Email with all parties copied (Delivery team & client stakeholders)

Escalation: AE Does Not Complete Checklist in 24 Hours

  • HubSpot workflow fires: Slack alert sent to Head of Delivery

  • Head of Delivery pings AE directly and logs a note on the deal

  • If not resolved within 4 business hours of escalation, Sales Manager is looped in

  • No SA work begins until checklist is complete - timeline does not start until this gate clears

 

Phase 2 - Internal Handoff (SA Ownership)

Trigger: AE marks Handoff Checklist complete in HubSpot

STEP 4 SA REVIEWS THE HANDOFF CHECKLIST

  • SA responds to Handoff Email with warm introduction (other relevant delivery team members respond as well)
  • SA reviews:
    • Handoff checklist - not a skim, a full review
    • Signed quote, contract linked on the deal
  • SA flags: tagging Sales in the #new-deal-assignment channel in thread
    • Missing information
    • Scope gaps
    • Unclear promises
  • If the engagement is complex: (custom integration, aggressive timeline, large account)
    • SA schedules a 15-minute sync with the AE or Scoping SA before proceeding
  • If no blockers: SA proceeds to Step 4

STEP 5.a SA SETS UP PROJECT INFRASTRUCTURE

  • SA updates ClickUp space task lists: (approx 1hr time commitment)
    • Imports SOW tasks from Quote
    • Adds time tracking template
    • Adds relevant Hubs templates
    • Creates detailed subtasks within itemized quote tasks
    • Assigns task owner, due date, & estimated time
  • SA adds contacts to client Slack channel:
    • posts the welcome message in the client Slack channel

STEP 5.b HUBSPOT AUTOMATION FOR KICKOFF EMAIL

  • Kickoff email sent via automation post-closed won to associated contacts includes:
    • Warm introduction
    • Details on Kickoff Agenda
    • SA scheduling link for kickoff
  • HubSpot automation monitors kickoff booking completion
    • If kickoff not booked in 48 hours:
      • SA slack notification in #new-deal-assignment channel
      • Kickoff reminder email sent to associated contacts
    • If kickoff not book in additional 48 hours:
      • SA & AE slack notification
      • Kickoff final reminder email sent to associated contacts
    • Once kickoff booked:
      • Project pipeline staged = Kickoff Scheduled
      • Day before kickoff agenda email sent to associated contacts

Phase 3 - Client Onboarding Preparation (SA Ownership)

Trigger: Client books kickoff

STEP 6 SA BUILDS THE KICKOFF DECK

  • SA creates Gamma kickoff presentation from implementation or retainer template
  • Required deck sections:
    • Introductions
    • Scope Confirmation
    • Proposed Timeline
    • First Value Milestone
    • How We Work Together (communication cadence)
    • Next Steps
  • SA confirms go-live dates internally and then adds in the deck
  • SA shares draft deck with Pod Leader for review before kickoff (if necessary)

Phase 4 - Kickoff (SA Ownership)

Trigger: Definition of Ready criteria met (Section 6)

STEP 7 SA SCHEDULES AND RUNS KICKOFF CALL

  • SA runs the kickoff:
    • Covers scope
    • Timeline
    • First value moment
    • Communication cadence
  • SA confirms:
    • Client primary contact
    • Decision-maker
    • Who approves deliverables
  • AskElephant captures meeting notes in the client project

STEP 8 SA HANDOFF COMPLETE

  • SA updates HubSpot project stage to ‘Buyer’s Journey 1 Scheduled’

 

Internal Communication Standards

Slack Channels

Channel

Purpose

#new-deal-assignment
  • Deal assignment notifications
  • Kickoff scheduling issue notifications
  • SA to AE communication back-and-forth for new deals within notification thread

#[clientname]-zipcio
  • External client channel
  • Meeting Recaps + Agendas
  • Client questions/asks & updates

SLA Standards

Action

SLA

AE completes Handoff Checklist

At the time of Closed Won

AE sends Handoff Email

Within 24 hours of Closed Won (ideally 12)

SA responds to client handoff email

Within 24 hours of Handoff Email sent

SA preps for kickoff & alerts of red flags

Within 48 hours of client assignment, at least 24 hours before kickoff

Kickoff held

Within 10 business days of Closed Won (standard)

 

Client Communication Standards

All client-facing communication during the handoff window is SA-owned unless otherwise specified.

Client Handoff Email Template

Automation Trigger: Deal = Closed Won ; Solutions Architect User = Known

 

 

QA Checklist

This checklist is completed by the SA before the kickoff is confirmed.

 

Pre-Kickoff QA - SA Completes

Checklist Item

Owner

Signed contract linked on HubSpot deal record

AE

Proposal or SOW linked on HubSpot deal record

AE

All Handoff Checklist fields complete in HubSpot

AE

Payment initiated or payment terms documented

AE

ClickUp space created from standard template

Automation

Client Slack channel created with correct naming convention

Automation

Kickoff deck created

SA

Timeline validated by SA

SA

All open questions resolved - no pending blockers

SA

 

Risk Mitigation and Escalation Process

Red Flag Account Criteria

An account should be flagged as a red flag if ANY of the following are true at the time of handoff:

  • Timeline is aggressive or out of the ordinary to close the deal
  • Scope is ambiguous or the client's expectations appear broader than what was sold
  • Multiple stakeholders with conflicting priorities
  • Custom promises were made outside the signed SOW
  • Client has had a bad experience with a previous HubSpot implementation
  • Deal closed significantly below standard pricing
  • AE flagged difficulty managing expectations during the sales cycle

 

Red Flag Account Process

  1. SA flags the account as Red Flag in HubSpot by changing the project status to “At Risk”

  2. SA notifies Pod Leader in Slack with a summary of the concern

  3. Pod Leader reviews before kickoff is scheduled

  4. Pod Leader and SA align on a risk mitigation plan

  5. Kickoff prep is adjusted accordingly (additional discovery, scope call, etc.)

  6. AE is looped into the call if expectations need to be reset

 
 

Handoff Completion Criteria

The handoff is officially complete when ALL of the following are true. This is not a soft milestone - it is a hard gate.

  • Kickoff call has been held
  • Scope has been verbally confirmed with the client on the kickoff call
  • Timeline has been agreed upon by both the client and the SA
  • First value milestone has been communicated and acknowledged by the client
  • Communication cadence (check-ins, updates) has been agreed upon
  • Kickoff recap has been sent to the client

 

Common Failure Points

These are the most frequent places this process breaks. Knowing them is the first step to preventing them.

Failure Point

What Happens

AE verbal-only handoff
  • Critical context shared over Slack or in conversation
  • Never logged in HubSpot
  • SA starts with incomplete information.

Checklist completion treated as optional
  • AE marks checklist done without actually filling out every field.
  • Gate is bypassed.
  • SA inherits gaps.

SA doesn't review the contract
  • SA relies entirely on the checklist
  • Contract details that don't match checklist notes go unnoticed until kickoff or later.

Timeline promised before SA validation
  • AE tells the client a go-live date.
  • SA later finds the date is not achievable.
  • Client relationship starts with a reset conversation.

Kickoff scheduled too early
  • Kickoff happens before infrastructure is set up, deck is ready, or scope questions are resolved.
  • Client's first impression is disorganized.

No escalation path used
  • SA notices a red flag but does not escalate because they feel it is manageable.
  • Issue surfaces 3 weeks into delivery.

Custom promises not documented
  • AE verbally commits to something during the sales process.
  • Not in the contract, not in the checklist.
  • SA delivers the contract scope.
  • Client is disappointed.

 

Metrics and KPIs to Track

These metrics are tracked in HubSpot and reviewed by Head of Delivery on a weekly basis.

Metric

Definition

Target

Time to Kickoff

Business days from Closed Won to confirmed kickoff

Target: 10 business days or fewer

Escalation Rate

% of handoffs that require a scope or timeline escalation

Monitor for trends

Red Flag Account Rate

% of Closed Won deals flagged as red flag

Monitor for trends

Client Satisfaction at Kickoff

Short survey sent post-kickoff (optional but recommended)

Target: 4.5+/5

 

Best Practices

For Sales

  • Complete the checklist the same day the deal closes - do not wait for the 1-day SLA. Momentum matters.
  • Brief the SA verbally if the deal is complex. The checklist captures facts but not nuance.
  • Never tell the client a timeline before looping in Delivery. Say: 'We'll confirm your go-live timeline with our implementation team and get back to you within 24 hours.'
  • Document every custom promise in the notes field of the HubSpot deal at the time it is made - not after the fact.

For Delivery

  • Read the quote and contract, not just the checklist. The contract is the legal record of what was sold.
  • Flag scope ambiguity early and loudly. The longer you wait, the harder the conversation becomes.
  • Use the kickoff call to confirm scope, not just introduce yourself. Verbal confirmation protects you later.

For Leadership

  • Build a quarterly retrospective into this SOP review. Ask: what broke, what was slow, what do we wish we had known at handoff.