# Sales delivery handoff referral: what to ask | SourceX

Canonical: https://refer.sourcex.si/guides/sales-to-delivery-handoffs-a-clue-to-operational-context
Last updated: 2026-11-04

A handoff from sales to delivery is a clue, not a dataset. It suggests a company writes down what it promised and what it then had to build, the kind of operating context AI developers look for, but it proves nothing about rights or demand. Use it to ask four teams, sales, solution design, delivery and support, which records each one writes, where and for how long, who wrote each layer, and whether the CEO wants a conversation. Ask without requesting a single file.

Specialist advisors see handoffs from the inside. A revenue operations consultant rebuilds the opportunity stages, a professional services advisor redesigns kickoff, an operator who once ran delivery sits on an advisory board. Each sees one seam well and assumes the others look the same. They rarely do, and the seams you have not seen decide whether the company holds a connected history or a pile of disconnected notes.

## What a handoff record is, in plain terms

A handoff is the moment a deal stops belonging to the people who sold it and starts belonging to the people who must deliver it. Around that moment sit the CRM opportunity, call notes and emails, the quote or order form, the statement of work, a kickoff deck, a handoff checklist and the first project tasks.

SourceX's guide to [sales handoff implementation datasets](https://sourcex.si/insights/sales-handoff-implementation-dataset) is the technical reference for suppliers, and two of its points matter for a referral. CRM opportunity fields record a deal's state, not the content of what was promised, so a tidy pipeline can hide an empty handoff. And signed agreements and statements of work outrank quotes, notes and CRM fields, so the documents with the most authority are also the ones most likely to carry a customer's confidentiality terms. Why the documents around a decision interest AI developers at all is covered in [context engineering and operational data](/guides/context-engineering-enterprise-operational-data).

## The cross-function workflow discovery guide

Four seams, each a place where one team's record becomes another team's input. For each, the guide names what gets written on both sides, the question to put to the person who runs it, what a useful answer sounds like and what even a good answer leaves open.

| Seam | Written on the sending side | Written on the receiving side | Ask the person who runs it | A useful answer sounds like | Still open after a good answer |
|---|---|---|---|---|---|
| 1. Sales to solution design | Discovery notes, opportunity record | Scoping notes, solution outline | "When a rep brings in a solutions engineer, what is written down, and where?" | "Every scoped deal has a scoping note linked to the opportunity, going back years" | How much of the scoping note is the customer's own requirements text |
| 2. Solution design to delivery | Signed statement of work, order form, assumptions | Project plan, kickoff notes, first tasks | "What does the delivery lead receive at kickoff, and does it stay linked to the deal?" | "A handoff checklist in the project tool, carrying the deal number" | Whether the customer's agreement allows any reuse of the statement of work |
| 3. Delivery to support | Go-live notes, configuration decisions, known issues | First tickets and escalations | "When a project goes live, what does support inherit?" | "A go-live note and an open-issues list on every account" | How much ticket text is in customers' own words |
| 4. Delivery to finance | Milestones, change orders | Invoices, credits, disputes | "How does a change order reach billing?" | "Each change order has a number tied to the project and the invoice" | Whether prices may travel at all; SourceX's guide drops or bands them only with counsel's approval |

Score each seam on three plain questions: is something written on both sides, does it stay linked across the seam, and for how many years. A company where all four seams are written, linked and years deep holds cross-function context. A company with one handoff email per deal holds a habit, not a history.

**Method note.** The seams and questions come from SourceX's sales handoff guide and its screening criteria, both checked on 2026-10-27, arranged for a partner who cannot see the records. The guide has not been tested against outcomes: no figures on how seam scores relate to acceptance or payout have been published.

## Who wrote each layer: original work, customer pages and a reseller's notes

Authorship decides whose records they are, and every seam mixes authors.

**The company's own work.** Scoping notes, checklists, project tasks and go-live notes written by its employees as part of their jobs are the layer most likely to be the company's. Section 201 of the U.S. Copyright Act treats the employer, or other person for whom a work made for hire was prepared, as its author, owning the rights unless the parties agreed otherwise in a signed writing. Contracts can still restrict even this layer, which is what rights review checks.

**Customer pages.** Requirements documents, RFP text pasted into a scoping note, redlines on the statement of work, the customer's emails. SourceX treats material that belongs to clients as usually not a fit, and its handoff guide warns that de-identifying a statement of work does not by itself create a right to license it, because a customer's agreement may limit reuse of its order forms, statements of work and communications.

**A reseller's or outside firm's notes.** When a reseller sold the deal or an implementation firm delivered it, their people wrote in their own systems, and whether any of that belongs to the company depends on the agreement between them. Buyers care about this layer for their own reasons: NIST's AI Risk Management Framework, under GOVERN 6.1, calls for policies addressing AI risks from third parties, including infringement of a third party's intellectual property or other rights.

Illustrative. Three generic companies with invented facts; no outcome implied.

| What we looked at | Original work | Customer pages | A reseller's notes |
|---|---|---|---|
| Company | 320-person ERP consultancy | 150-person marketing software company | 110-person security software vendor |
| The seams | All four written by its own staff in one project tool since 2015 | Scoping notes built largely from customers' RFP text | About 60% of deals sold and delivered by resellers |
| What the layers hold | Mostly the company's own notes | The company's own commentary beside customers' pages | Summary milestones in-house; the detail sits with resellers |
| Question that matters most | Does the CEO want a conversation? | How much of each scoping note is the company's own writing? | Where do the resellers' notes live, and under which agreement? |
| Who settles the rest | SourceX's rights review | SourceX's rights review, with customer pages left out | SourceX's rights review, after counsel reads the reseller agreements |

## Find the owner of each layer, and the person who decides

Each seam has someone who knows it: the CRM administrator or revenue operations lead for seam 1, the head of solutions for seams 1 and 2, the professional services or PMO lead for seams 2 and 3, support operations for seam 3, billing or finance operations for seam 4. None of them decides on licensing. The CEO agrees to a licensing discussion and signs for the company, and an introduction made without the CEO's knowledge is usually not a fit.

Your own relationship may run through just one of these people. That is enough to start, provided they are willing to ask the others and, in the end, the CEO. The [sales-to-customer-success handoff page](/data-types/sales-to-customer-success-handoff) covers seam 3 as a record type, [customer success handover records](/guides/customer-success-handover-ai-data) traces what happens after it, and [implementation partners](/for/software-implementation-partners) who run seam 2 for clients have their own page.

## Bounded questions to send before any call

Send these through the person who owns the relationship. None asks for a document, a field export, a screenshot or a customer name.

1. Which systems hold each side of the four seams, and since which year?
2. Roughly how many deals a year reach a formal handoff?
3. Do handoff records stay linked to the deal and project numbers across systems?
4. Who wrote most of each layer: your staff, customers, resellers or an outside implementation firm?
5. What share of deals did partners sell or deliver, and where do their notes live?
6. Are statements of work and order forms stored with the deal? Their confidentiality terms are for counsel to read later, not for you.
7. Has any of this been licensed for AI training before? Data already licensed for that purpose is out.
8. Does the CEO want a conversation?

SourceX's own first step asks a company a few questions and takes no files, so these questions never need to go further than it does. Statements of work raise their own confidentiality questions, set out in [ERP implementation SOW confidentiality](/guides/erp-implementation-sow-confidentiality) and the [statement of work archive page](/data-types/statement-of-work-archive).

## Where a handoff clue misleads

- **Recent tidiness.** A handoff template introduced last year says nothing about the years before it. Ask when each seam started being written down.
- **Handoffs held in meetings.** Some teams hand off on a call and write nothing. The habit can be excellent and leave no record.
- **Demand is separate.** Whether a current program needs these records is checked in SourceX's review, however well the seams are kept.
- **Contracts can close the best layer.** Statements of work carry the most authority and often the strictest customer terms.
- **Size still applies.** A company whose full-time headcount never reached 50 is outside the program, however good its handoffs.

How often a strong handoff clue leads to an accepted company has not been measured or published. To learn it for your own practice, record each company's four seam scores before the CEO conversation and what happened after.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

When the seams are written, linked and years deep, the authorship of each layer is known and the CEO wants a conversation, [sign up for a partner link](/register), check the company against [who qualifies](/who-qualifies) and read the [program terms](/terms); the person who submits signs the SourceX Channel Partner Agreement before the introduction goes in. More partner guides are in the [guides hub](/guides).

## Sources

- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/terms
- https://sourcex.si/insights/sales-handoff-implementation-dataset
- https://sourcex.si/how-it-works
- https://www.law.cornell.edu/uscode/text/17/201
- https://airc.nist.gov/airmf-resources/airmf/5-sec-core/
