# Negotiation missing context: Outlook before/after | SourceX

Canonical: https://refer.sourcex.si/guides/negotiation-to-contract-missing-context
Last updated: 2026-11-04

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.

This comparison belongs to the [negotiation-to-contract guide](/guides/chain-negotiation-to-contract). 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.

| Date | What the export shows | What a reader concludes |
|---|---|---|
| March 2 | Customer asks for a three-year price lock "on everything we use" | A normal renewal request |
| March 6 | Account executive replies that a lock is approved, attaching draft 2 | The company agreed |
| March 9 | Customer returns draft 3 with tracked changes | Some wording was tidied |
| March 10 | Account executive replies "Fine by us, sending for signature" | Nothing material changed |
| March 12 | Notification that the envelope was completed | Deal 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

| Date | Event | System | What it adds |
|---|---|---|---|
| March 2 | Customer request | Outlook | Same as before |
| March 3 | Price-lock term set to 36 months on the opportunity | Salesforce field | The request exceeds the one-year policy |
| March 5 | CFO approves the 36-month lock, comment: "existing modules only" | Salesforce approval history | The approval had a scope condition |
| March 6 | Draft 2 attached to the approval request | Salesforce file | The approved draft is identifiable |
| March 9 | Draft 3 extends the lock to add-on modules bought later | Outlook attachment | The redline widened the scope |
| March 10 | Envelope sent with draft 3, never resubmitted for approval | DocuSign | The signed version skipped sign-off |
| March 12 | Certificate of Completion shows sent and completed events | DocuSign | Signature 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 needs | Outlook export alone | Salesforce alone | DocuSign alone | All three joined |
|---|---|---|---|---|
| Why the customer pushed back | Yes | Only a summary note | No | Yes |
| Which policy the request broke | No | Yes, if the term field and ceiling are recorded | No | Yes |
| Who approved, and on what condition | Only if forwarded | Yes, in approval history | No | Yes |
| Which draft was approved | Only by attachment date | Only if the draft was attached | No | Yes |
| Which draft was signed, and when | No | Only a closed-won stage | Yes | Yes |
| Whether scope changed after approval | Yes, but nothing flags it | No | No | Yes, 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](/guides/negotiation-to-contract-record-linkage) names the keys hop by hop, and the [completeness checklist](/resources/negotiation-to-contract-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](/resources/a-metadata-only-microsoft-outlook-inventory-template-for-company-introductions) helps with the mailbox side, and [how Microsoft 365 advisors spot referral opportunities](/guides/how-microsoft-365-advisors-spot-referral-opportunities-during-microsoft-outlook-projects) 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](/proof/why-sales-data-is-valuable); for the mailbox system, see [Outlook](/systems/microsoft-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](/register), check the company against [who qualifies](/who-qualifies) and read the [terms](/terms) before introducing its sponsor.

## Sources

- https://learn.microsoft.com/en-us/purview/edisc-search-mailboxes
- https://help.salesforce.com/s/articleView?language=en_US&id=platform.approvals_approval_history.htm&type=5
- https://support.docusign.com/s/document-item?language=en_US&bundleId=oeq1643226594604&topicId=gpa1578456339545.html
- https://refer.sourcex.si/terms
