The business task the packet describes
The task is turning a non-standard request into a signed order. A customer asks for a discount, a payment term or a scope change outside policy. Someone logs the exception, someone senior approves it, and the agreed terms go out for signature. The history of those decisions, across hundreds of deals, is a record of how a company prices, concedes and controls risk.
The packet does not try to capture any of that judgment. Its job is narrower: to tell SourceX where the judgment is recorded, how far back it goes, and how confidently the pieces can be joined. That is enough for SourceX to decide whether a conversation is worth having, and it keeps the partner well away from customer names, prices and contract language.
What each system can tell you without opening it
A partner asks about the shape of the records, never their content. These are the questions per system, and what the vendor documentation says is usually recorded.
- Outlook. Where do negotiation threads live: individual sales mailboxes, a shared deal desk mailbox, or logged to the CRM? How long are mailboxes of departed staff kept? Microsoft Purview eDiscovery can search mailboxes within a case and export results, and its export packages expire 14 days after creation, which matters later, not now. For the packet, the answer is a location, a date range and a retention rule.
- Salesforce. Which objects and fields hold the exception (a discount field, a term field, a custom object)? Is there an approval process, and since when? Salesforce's Approval History shows statuses such as Submitted, Approved, Rejected and Recalled and names the actual approver. Field history matters too: without Field Audit Trail, Salesforce keeps it for up to 18 months, and 24 months through the API, so the packet should say whether Field Audit Trail is on.
- DocuSign. Are envelopes sent from Salesforce, and since when? Is the opportunity ID stored on the envelope? DocuSign envelopes can carry custom fields used for sorting and tracking that recipients do not see, and the Certificate of Completion logs sent and completed events and an Envelope Updated entry for corrections. The packet records whether the custom field exists and from which year it was filled in.
Sample packet, filled in
Illustrative: a fictional 260-person logistics software company; every figure is invented to show the level of detail.
| Packet field | Outlook | Salesforce | DocuSign |
|---|---|---|---|
| Object types | Negotiation threads with draft attachments | Opportunities, discount and term fields, approval history | Envelopes, signed documents, certificates of completion |
| Date range | 2017 to today in active mailboxes | 2017 to today; approval process since 2019 | 2020 to today |
| Rough volume | Not counted; about half of deals logged to opportunities | About 900 closed opportunities a year; one in five with an exception | About 1,000 envelopes a year |
| Link field | Opportunity name in subject, sometimes | Opportunity ID | Opportunity ID custom field, new envelopes only |
| Draft marker | Draft number in file names | Draft attached to approval, sometimes | Signed draft only |
| Administrator | IT director | VP Revenue Operations | VP Revenue Operations |
| Retention to confirm | Departed staff mailboxes | Field Audit Trail status unknown | No deletion policy known |
| Known gap | Redlines accepted by email reply | Later drafts not resubmitted for approval | None known |
| Decision-maker | CEO | CEO | CEO |
Keep the packet at this level. "One in five deals carries an exception" is useful; the size of any discount is not. For the commercial value of negotiation records in general, point SourceX to the negotiation data overview instead of restating it.
How the packet flags a late redline
The case the packet must surface is a redline that changes the promised scope after the approval. In the illustrative company, the VP of Sales approved a 12% discount on draft 3 with onboarding excluded. Four days later the customer returned draft 4 by email with two weeks of onboarding added, the account executive accepted it in a reply, and DocuSign carried draft 4 to signature. The approval and the signature describe different deals.
A partner does not need to find such a case. The packet only has to make it findable: the "Draft marker" row shows whether drafts are numbered, and the "Known gap" row records that redlines are sometimes accepted by email and later drafts are not resubmitted. Those two answers tell SourceX that the history contains drift between approval and signature, which is often the most informative part of a negotiation record.
Who authorizes the discussion, and does the company qualify?
The VP of Revenue Operations is usually the right person to answer the packet because they own the systems. The CEO decides whether to explore a license, often with the CFO preparing the case, and the general counsel reviews customer contracts, since signed orders and negotiation emails contain customer terms and sometimes customer confidentiality obligations. The customer contract restrictions guide and the note on assessing contract materials without sharing privileged work cover what counsel will check.
The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, 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.
What stays unknown until SourceX reviews it: what customer contracts allow, how much history each system still holds, which deals a buyer would want, and the company's offer. Partners never ask for or handle raw records. Partners sign the Channel Partner Agreement before submitting an introduction, and attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. For more on each system, see the systems hub, the Salesforce and Outlook pages, bulk-downloading DocuSign envelopes and Salesforce field history retention.
Go deeper on negotiation-to-contract records
- Negotiation-to-contract record linkage: the record chain, step by step, with the identifier that joins each hop and where it breaks.
- Negotiation-to-contract completeness checklist: a pass, partial or fail scorecard for judging whether the trail is complete enough to discuss.
- What a single-system negotiation export loses: a before-and-after reading of one deal, with and without its surrounding 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.
If a client can fill most of this packet and name its gaps honestly, register as a partner, check the company against who qualifies, read the program terms, and send the packet with the unknowns marked.