Promise-to-obligation metadata packet: a fill-in template for Salesforce, Gong and Ironclad

Short answer

A referral partner can collect the names of the systems, the years each has been in use, the object types, volume bands, the join behind each hop, how long each tool keeps its change history, and who owns each piece, plus a list of what nobody knows yet. That fits in one table and needs no access to calls, notes or contracts. Customer names, deal values, call quotes and clause text stay out. The packet's most useful line is the one that says whether anyone checks spoken commitments against the contract.

Visual briefFull-size diagram
A metadata packet card fills in field by field (systems, years, volume band, joins, history window, owners, unknowns) while a locked tray of raw records, calls, notes and contracts, stays closed beside it.
Illustrative packet for a fictional software company. Every line describes the records; none of them is a record.

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 fieldWhat to writeWho usually confirms itWhy SourceX needs it
CRMSystem, year live, objects usedSales operations directorAnchors the chain
Call recordingSystem, year live, share of calls recordedRevenue operations leadWhere spoken commitments live
Contract systemSystem, year live, where earlier contracts sitLegal operations managerWhere redlines and executed copies live
Volume bandOpportunities and executed contracts, as bandsSales operations directorScale, without exact numbers
Hop 1: call to opportunityAutomatic, manual or none; how often correctedRevenue operations leadTies a commitment to its deal
Hop 2: opportunity to contractStarted from the deal record or separately; since whenLegal operations managerTies the deal to its paper
Hop 3: versions to executed copyInside the workflow, or by emailLegal operations managerShows how terms moved
Field historyFields tracked; retention default or extendedSalesforce adminDecides whether event order survives
Spoken-promise reviewDoes anyone compare calls with the contract before signature?Sales or legal leadershipThe case most worth knowing about
UnknownsAnything nobody could answerGeneral counselTells 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 fieldExample entry (Illustrative)Who confirmed it
CRMSalesforce since 2016; opportunities and accountsSales operations director
Call recordingGong since 2020; most external calls recordedRevenue operations lead
Contract systemIronclad since 2021; earlier contracts in a shared driveLegal operations manager
Volume bandThousands of opportunities; hundreds of executed contracts a yearSales operations director
Hop 1: call to opportunityAutomatic, with manual corrections on multi-deal accountsRevenue operations lead
Hop 2: opportunity to contractStarted from the deal record since 2022Legal operations manager
Hop 3: versions to executed copyInside each workflow; some 2021 redlines by emailLegal operations manager
Field historyStage and amount tracked; default retentionSalesforce admin
Spoken-promise reviewNo routine check; raised ad hoc at renewalVice president of sales
UnknownsConsent terms for recorded calls; customer confidentiality clausesGeneral 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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

How long does it take to fill in the packet?

Usually one 30 to 45 minute conversation with the sales operations director, plus short follow-ups with the revenue operations lead and legal operations. Most fields come from admin settings and memory, not from records.

What if someone offers to forward a call recording or contract as an example?

Decline politely and point them to SourceX. A partner never handles raw records. If the company proceeds, it decides what to share under its own signed agreement.

Can I leave fields blank?

Write unknown instead of leaving a blank. An honest unknown tells SourceX what to ask in review; a blank looks like an oversight and a guess looks like a fact.

Sources

  1. help.gong.io/docs/manage-call-associations
  2. support.ironcladapp.com/hc/en-us/articles/12285599508119-Get-Started…
  3. help.salesforce.com/s/articleView
  4. help.salesforce.com/s/articleView
  5. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment