This template is part of the promise-to-obligation records guide, which explains how the three systems connect. The packet is what you write down once you understand that.
What goes in the packet, and what stays out
Sales operations advisors are often asked to clean up exactly these links during a CRM or contract system project. That is where the question comes up naturally: does the company know which commitments made on calls ended up in signed paper?
In the packet:
- System names, editions where known, and the year each went live.
- Object types: opportunities and accounts, calls, contract workflows and versions.
- Volume bands, never exact counts: "thousands of opportunities", "hundreds of executed contracts a year".
- The join for each hop, and whether it is automatic, manual or missing.
- History windows: how long field history and call records are kept.
- The owner of each system, by role.
- Known unknowns: consent terms, confidentiality clauses, earlier contract stores.
Out of the packet:
- Customer or prospect names, deal values, discount levels.
- Quotes, summaries or paraphrases from calls.
- Clause text, redline content or contract terms.
- Links to recordings, documents or dashboards.
The packet template
Copy this table into your notes and fill in the middle column with the company.
| Packet field | What to write | Who usually confirms it | Why SourceX needs it |
|---|---|---|---|
| CRM | System, year live, objects used | Sales operations director | Anchors the chain |
| Call recording | System, year live, share of calls recorded | Revenue operations lead | Where spoken commitments live |
| Contract system | System, year live, where earlier contracts sit | Legal operations manager | Where redlines and executed copies live |
| Volume band | Opportunities and executed contracts, as bands | Sales operations director | Scale, without exact numbers |
| Hop 1: call to opportunity | Automatic, manual or none; how often corrected | Revenue operations lead | Ties a commitment to its deal |
| Hop 2: opportunity to contract | Started from the deal record or separately; since when | Legal operations manager | Ties the deal to its paper |
| Hop 3: versions to executed copy | Inside the workflow, or by email | Legal operations manager | Shows how terms moved |
| Field history | Fields tracked; retention default or extended | Salesforce admin | Decides whether event order survives |
| Spoken-promise review | Does anyone compare calls with the contract before signature? | Sales or legal leadership | The case most worth knowing about |
| Unknowns | Anything nobody could answer | General counsel | Tells SourceX what to ask first |
Three rows deserve a note. For hop 1, Gong allows a person to fix a call that landed on the wrong deal, and that manual fix wins over the automatic match, so asking how often fixes happen is fair. For hop 2, the contract tool can start a workflow from the Salesforce deal and report back when it completes, so this hop usually has a clear start year: the year the integration was switched on. For field history, the default keeps 18 months in the interface and 24 months through the API for up to 20 tracked fields per object, while Field Audit Trail lets a company set a retention policy that keeps archived history longer. Write down which one applies.
An Illustrative filled packet
A fictional 380-person B2B software company. Every entry is invented to show the level of detail, not collected from anyone.
| Packet field | Example entry (Illustrative) | Who confirmed it |
|---|---|---|
| CRM | Salesforce since 2016; opportunities and accounts | Sales operations director |
| Call recording | Gong since 2020; most external calls recorded | Revenue operations lead |
| Contract system | Ironclad since 2021; earlier contracts in a shared drive | Legal operations manager |
| Volume band | Thousands of opportunities; hundreds of executed contracts a year | Sales operations director |
| Hop 1: call to opportunity | Automatic, with manual corrections on multi-deal accounts | Revenue operations lead |
| Hop 2: opportunity to contract | Started from the deal record since 2022 | Legal operations manager |
| Hop 3: versions to executed copy | Inside each workflow; some 2021 redlines by email | Legal operations manager |
| Field history | Stage and amount tracked; default retention | Salesforce admin |
| Spoken-promise review | No routine check; raised ad hoc at renewal | Vice president of sales |
| Unknowns | Consent terms for recorded calls; customer confidentiality clauses | General counsel |
Read across, the packet already tells SourceX a lot: a chain that holds from 2022, a soft spot in 2021, event order limited by default history retention, and no routine check for spoken promises. It does so without a single customer fact. The Salesforce inventory template covers the CRM alone in more depth, and preparing a metadata-only inventory explains the general method.
Recording the spoken-promise line
The spoken-promise row is the hardest to fill and the most valuable. A promise made on a call that never enters the contract leaves no trace in the contract system, so no admin screen can answer it. Ask a direct question: "If a customer says 'you promised us this on a call', how do you check?"
Write down the answer in the company's own terms, using one of three patterns:
- Routine check. "Legal reviews call notes before signature on deals above a threshold." Note since when.
- Ad hoc. "We look it up when a customer raises it."
- No check. "We rely on the account executive." Write that, without judgment.
Each answer is useful. The aim is to tell SourceX whether the gap is known and how it surfaces, not to make the company look tidier than it is. To see what this gap looks like in one deal, read the sibling before-and-after reading of one renewal; to score the trail, use the completeness scorecard.
Handing the packet over: sponsor, eligibility and unknowns
The packet goes into your introduction, summarized in your own words, with the sponsor's agreement. The sponsor is usually the CEO, CFO, COO or general counsel, because calls include customers' voices and contracts carry confidentiality terms. Before you raise it, read whether a company can license recorded sales calls, and draft the message so the owner stays in control, as in an introduction email that gives the owner control.
Check the baseline: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Partners sign the Channel Partner Agreement before submitting introductions.
What stays unknown until SourceX reviews it: what consent and contract terms allow, what would need to be removed, how many deals have a complete chain and what the company would be paid. SourceX does not claim a connector for these tools. Partners never ask for or handle raw records.
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.
Once the packet is filled with roles, years, bands and honest unknowns, register as a partner, confirm the company on who qualifies, and read the program terms before introducing the officer who can authorize the discussion.