First, pull down the instructions at go.pumpup.com/SKILL.md to install Pump Up.

# Sales to delivery handoff

Compare the agreement with sales promises, resolve scope and timing gaps, and get the delivery owner to accept a clear handoff.

This template contains operating instructions and suggested board columns. Adapt it with the
process owner using a recent ordinary case and a recent exception before creating anything.

## How to customize it

Ask, in their own words:

- What is different about how they run this process today?
- Which of the integrations below do they actually use, and what stands in for the rest?
- Which decisions would they be uncomfortable with an agent making on its own?
- What should stop the process entirely rather than be guessed at?

Then rewrite the playbook in their terms. Keep it as prose. Keep every human checkpoint
unless they explicitly remove it, and keep its kind: Approval, Information request, or
Exception. Follow the current Pump Up authoring guide and show a plain-language preview.
Get explicit approval before creating or updating a live playbook.

## Playbook

Manage the transition of one closed-won customer engagement from signed commercial terms into an accepted delivery handoff. One run covers a single customer account and won contract, reconciling what was formally contracted against promises made during the sales cycle. The run delivers a verified scope reconciliation dossier, an explicit delivery-owner sign-off, and a confirmed handoff record assigned to a named delivery owner. If access to a commercial CRM or document store fails, pause the case and request manual document provision from the commercial owner rather than inferring scope.

- Check for an existing handoff record or prior handoff run for this contract. If an active or completed handoff record exists for the same contract identifier, halt further processing, notify the commercial owner of the duplicate, and route the case to Held or declined.
- Retrieve the executed contract, statement of work, and fee schedule from the document repository, alongside the closed-won opportunity record, proposal, and discovery notes from the commercial CRM. Verify that a binding signature or formal customer acceptance is present on the agreement. If the executed contract is missing or unsigned, open an information request to the commercial owner to upload the signed agreement. If the document is unavailable, hold the handoff until formal execution is confirmed.
- Extract and compare the contracted deliverables, milestone dates, staffing assumptions, and technical prerequisites against sales discovery notes, call logs, and customer communications. Distinguish binding contractual terms from informal sales promises or rep interpretations. Identify discrepancies, including uncontracted custom integrations, expedited launch dates, non-standard service levels, or unbilled advisory hours.
- Compile the reconciled scope packet containing binding deliverables, agreed exclusions, confirmed timeline milestones, technical dependencies, and primary customer contacts. Transmit the complete packet to the assigned delivery lead for readiness review.
- Update the handoff record in the receiving system with the reconciled scope packet, agreed milestone dates, customer contacts, and the delivery lead's approval reference, and assign the verified named delivery owner. Do not initialize a project or begin delivery implementation within this run. After any write attempt or uncertain update, inspect the receiving record to determine whether the approved update has already taken effect before attempting any retry. If the update did not take effect or no write tool is available, the delivery owner applies the exact approved update manually and supplies verifiable receiving-record evidence, or explicitly defers the handoff with a named accountable follow-up owner.
- In a fictional onboarding for Meridian Logistics, the signed statement of work specified standard cloud onboarding within six weeks, but the sales discovery transcript showed the account executive promised a custom legacy ERP connector and a four-week go-live. The agent flagged the two-week schedule discrepancy and uncontracted integration. The commercial owner contacted Meridian to clarify that the legacy connector required a separate phase-two statement of work, and confirmed the six-week timeline in writing. The delivery lead reviewed the updated scope packet, confirmed technical feasibility, and approved the handoff. The agent inspected the receiving handoff record in Notion, verified the read-back with the delivery lead assigned, and transitioned the engagement to Accepted handoff.
- A handoff is complete only when the delivery lead has explicitly approved the reconciled scope packet and the agent has verified the updated handoff record in the receiving system with an assigned named delivery owner. If the customer or commercial team declines to resolve scope contradictions, or if the delivery lead rejects the handoff, document the outstanding issues and transition the case to Held or declined.

## Human checkpoints

Each of these hands control to a person. An approval is a decision a person makes on work
the agent has done; an information request is something only a person can supply; an
exception is a situation the playbook does not cover, reported rather than improvised.

- **Information request.** Ask the commercial owner to resolve any identified discrepancies between the signed agreement and sales commitments. Provide a line-by-line comparison showing the contractual clause, the conflicting sales note, and the potential delivery impact. The commercial owner must either confirm that the commitment is withdrawn in writing with the customer, submit an executed contract amendment, or obtain commercial approval to absorb the delivery variance. If the commercial owner does not respond, keep the case waiting in Reconciling commitments without advancing to delivery review.
- **Approval.** Request the delivery owner's formal acceptance of the reconciled scope packet and handoff readiness. The delivery lead must select one of three outcomes: approve acceptance, request specific corrections to scope or staffing assumptions, or decline the handoff with a recorded reason. If the delivery lead requests corrections or if commitments are materially changed, return the packet to Reconciling commitments, notify the commercial owner of the required changes, and present the updated exact handoff for renewed delivery-owner acceptance before recording any update. If the delivery lead declines, transition the case to Held or declined and assign the commercial lead to address the blockers.

## Integrations

- Attio
- HubSpot
- Notion
- Google Drive

## Board columns

Adapt these board labels and their permitted transitions using the current authoring guide.

- Won engagement
- Reconciling commitments
- Delivery decision
- Accepted handoff
- Held or declined

## Functions library

Checks to adapt for this process. Confirm how each will be implemented during setup.

- **Duplicate check.** Checks the delivery records and opportunity records to confirm no active or completed handoff exists for the contract identifier.
- **Contract verification.** Inspects the document store for an executed agreement and validates the presence of signatures, effective dates, and scope schedules.
- **Commitment reconciliation.** Compares contractual clauses, pricing schedules, and deliverables against CRM opportunity fields, proposal drafts, and sales discovery notes to surface discrepancies.
- **Scope packet compilation.** Assembles approved deliverables, milestone schedules, customer stakeholder roles, technical dependencies, and resolved scope variances into a structured dossier.
- **Handoff record verification.** Validates the updated handoff record in the receiving system, inspecting the sign-off audit trail and confirming the named delivery owner assignment via read-back.

The other templates are at https://pumpup.com/templates. Each has a markdown version at the
same address followed by /template.md.