Before and after: one price-lock deal read from an Outlook export alone, then with its approval and signature records

Short answer

A single-system negotiation-to-contract export loses everything that happened outside that system. An Outlook export keeps the conversation and the draft attachments, but it loses the pricing policy the request broke, the approval and its conditions, and proof of which draft was finally signed. Salesforce alone loses the customer's reasons. DocuSign alone loses the approval. Only the three together show whether the signed terms match what was approved, which matters most when a late redline changes the promised scope.

Visual briefFull-size diagram
A deal timeline drawn from a mailbox export has three blank slots that fill as context blocks drop in from above: the pricing policy ceiling, the approval on draft 2 that excluded add-on modules, and the signed envelope carrying draft 3 with the lock extended.
Illustrative renewal. The email thread shows the conversation; the policy, the approval and the signed draft come from other systems.

This comparison belongs to the negotiation-to-contract guide. It reads one Illustrative deal twice: first from a mailbox export, then with the other two systems restored.

The deal: a three-year price lock (Illustrative)

A fictional 420-person facilities management software company renews a large customer. The customer wants prices frozen for three years. Company policy allows a one-year lock without sign-off and anything longer only with the CFO's approval. Every name, date and term below is invented.

Before: the deal as the mailbox export tells it

The company's administrators export the account executive's mailbox for the period. Read on its own, the thread is a plausible story.

DateWhat the export showsWhat a reader concludes
March 2Customer asks for a three-year price lock "on everything we use"A normal renewal request
March 6Account executive replies that a lock is approved, attaching draft 2The company agreed
March 9Customer returns draft 3 with tracked changesSome wording was tidied
March 10Account executive replies "Fine by us, sending for signature"Nothing material changed
March 12Notification that the envelope was completedDeal signed as discussed

The export cannot say that the March 6 approval had a condition, that draft 3 changed the scope of the lock, or that anyone with authority saw draft 3. It also cannot say what the policy was. A reader, or a model trained on threads like this, learns that "approved" plus "fine by us" equals a settled deal.

Getting even this view is an administrator's job. Microsoft's documentation describes Purview eDiscovery searches run inside a case, with results exported as PST files or individual messages, and export packages that expire 14 days after creation. That route returns messages, not the links between a message and an opportunity.

After: the same deal with approval and signature records

DateEventSystemWhat it adds
March 2Customer requestOutlookSame as before
March 3Price-lock term set to 36 months on the opportunitySalesforce fieldThe request exceeds the one-year policy
March 5CFO approves the 36-month lock, comment: "existing modules only"Salesforce approval historyThe approval had a scope condition
March 6Draft 2 attached to the approval requestSalesforce fileThe approved draft is identifiable
March 9Draft 3 extends the lock to add-on modules bought laterOutlook attachmentThe redline widened the scope
March 10Envelope sent with draft 3, never resubmitted for approvalDocuSignThe signed version skipped sign-off
March 12Certificate of Completion shows sent and completed eventsDocuSignSignature date and signer confirmed

Salesforce's Approval History related list records each step's status and the actual approver, which is why the March 5 condition can be read later. DocuSign's Certificate of Completion logs sent and completed events with timestamps, and it records an Envelope Updated entry if the document was corrected after sending; here there was none, because draft 3 went out as sent.

The joined record tells the real story: an approved exception with a condition, a late redline that broke the condition, and a signature nobody senior checked. That drift is often the most informative part of a negotiation history, and it is invisible in any one system.

The gap table: what each export keeps and loses

What a reviewer needsOutlook export aloneSalesforce aloneDocuSign aloneAll three joined
Why the customer pushed backYesOnly a summary noteNoYes
Which policy the request brokeNoYes, if the term field and ceiling are recordedNoYes
Who approved, and on what conditionOnly if forwardedYes, in approval historyNoYes
Which draft was approvedOnly by attachment dateOnly if the draft was attachedNoYes
Which draft was signed, and whenNoOnly a closed-won stageYesYes
Whether scope changed after approvalYes, but nothing flags itNoNoYes, by comparing drafts 2 and 3

Read down the last column and one join does most of the work: the draft number. If drafts are numbered and attached, the after view can be rebuilt. If they are not, even three systems leave the scope question open. The record chain page names the keys hop by hop, and the completeness checklist scores whether they were kept.

Describing the gap without reading a thread

A partner can state this gap from four answers: where negotiation email lives, whether approvals run in Salesforce and since when, whether drafts are attached and numbered, and whether redlines are ever accepted by email reply. None needs a message opened. The metadata-only Outlook inventory template helps with the mailbox side, and how Microsoft 365 advisors spot referral opportunities covers when the question comes up naturally.

The CEO authorizes any licensing discussion, often with the CFO preparing the case and the general counsel reviewing customer terms. The company needs 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.

Unknown until SourceX reviews it: what customer contracts permit, how much mailbox history departed staff left behind, and how many deals join on draft numbers. Partners never ask for or handle raw records and sign the Channel Partner Agreement first. For why sales records draw interest, see why sales data is valuable; for the mailbox system, see Outlook.

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's records can rebuild the after view, even for recent years only, register as a partner, check the company against who qualifies and read the terms before introducing its sponsor.

  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

Is a mailbox export on its own worth describing to SourceX?

It can be, described accurately: years of commercial conversations with attachments. Say plainly that policy, approvals and the signed version are not in it, and name the systems that hold them.

Can a partner run a Purview search to check what exists?

No. Searches and exports are run by the company's own administrators, and only after the company authorizes a discussion. A partner asks about mailbox locations and retention, not content.

What if the company never used Salesforce approvals?

Then approvals may live in email or chat, and the after view will be thinner. Note where sign-off was recorded, even if informally, and from which year.

Sources

  1. learn.microsoft.com/en-us/purview/edisc-search-mailboxes
  2. help.salesforce.com/s/articleView
  3. support.docusign.com/s/document-item
  4. 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