The draft is part of the ERP vendor selection playbook. Use it after the 30-minute owner meeting has produced a yes, and keep it separate from anything you send about the selection itself.
Keeping selection advice and the introduction apart
An ERP selection advisor is paid for impartial advice. The introduction must not touch it. Before drafting, make sure three things are true.
- The owner opted in after the disclosure, in a conversation that was not part of vendor scoring.
- The recipient decides. The project manager or a key user may have helped, but the email goes to the person who can authorize a licensing discussion.
- Your partner agreement is signed. The Channel Partner Agreement comes before any introduction is submitted.
Send it from a separate thread, never as a reply to a selection status update. If the client's procurement policy asks advisors to declare outside interests, declare this one there as well.
The draft
Illustrative. Placeholders in brackets. Plain text, no logos, no attachments.
Subject: Introduction: [Company] and SourceX, ERP exception history
Hi [Owner name], copying [Controller name],
When we reviewed the migration scope for the new ERP, [Controller name] confirmed that "clean data plus [n] years of closed invoices" leaves the rest of the exception history in [legacy system]: price overrides, credit-hold releases, accepted three-way-match variances and write-offs, each with a reason and an approver, going back about [years] years. [Legacy system] is due to be switched off around [confirmed date].
You are the right person to decide whether that history is worth discussing with SourceX, which licenses approved business data directly from companies for AI training and evaluation and handles the agreement, rights review, data preparation, delivery and payout. I have not seen, exported or shared any records.
For transparency: I am a SourceX referral partner. If a qualifying license completes, SourceX may pay me a reward from its own funds; it never reduces what [Company] is paid, and my selection advice does not depend on your answer. Would a 20-minute call about record types, years and systems be useful?
[Your name]
Line-by-line notes
| Line | Purpose | Keep out of it |
|---|---|---|
| Subject line | Names the topic and both parties | The new vendor's name, "opportunity" or any figure |
| "Hi [Owner name], copying [Controller name]" | Decision-maker in To; the person who knows the history on copy | The project team, the shortlisted vendors or the implementation partner |
| "When we reviewed the migration scope..." | Anchors the email in a decision the owner already knows about | Vendor scores, pricing or demo notes |
| "...leaves the rest of the exception history in [legacy system]" | States the finding: what the clean scope does not carry | Any suggestion that the scope was a mistake |
| "price overrides, credit-hold releases, accepted three-way-match variances and write-offs" | Names exception types at metadata level | Customer names, amounts, approvers' names or examples of a single decision |
| "...going back about [years] years" | Gives the time span the controller confirmed | A count or span nobody at the company gave you |
| "[Legacy system] is due to be switched off around [confirmed date]" | The real reason the email is timely | An unconfirmed date or invented urgency |
| "You are the right person to decide..." | Hands the decision to the person with authority | Pressure or "before go-live" deadlines you set yourself |
| "...SourceX, which licenses approved business data..." | One accurate sentence on SourceX | Buyer names, prices or "this will sell" |
| "I have not seen, exported or shared any records." | Confirms nothing has left the company | Any hint of a sample or a report extract |
| "For transparency: I am a SourceX referral partner..." | Discloses the material connection and its independence from your advice | The reward percentage, or wording that suggests the company pays it |
| "Would a 20-minute call..." | A small, metadata-only ask | Requests for files, logins, reports or the legacy database |
Why name the variance row specifically
Accepted three-way-match variances are the clearest example of a decision a clean scope leaves behind. Microsoft's documentation for Dynamics 365 Finance describes three-way matching as comparing invoice price with purchase order price and invoiced quantity with the product receipt quantity, with a quantity difference treated as a matching error. Every accepted error carries a person's judgment and a reason. Naming the type tells SourceX what kind of history it is, without revealing a single transaction.
Why the independence sentence matters here
The FTC's Endorsement Guides, at 16 CFR 255.5, call for clear and conspicuous disclosure of a connection the audience would not expect and that could affect how much weight they give a recommendation. For a selection advisor, the reader's natural worry is whether the referral colors the vendor advice. Saying outright that it does not, in the same sentence as the disclosure, answers that worry before it is raised.
Edits to refuse
| Suggested edit | Why it sounds reasonable | Why to refuse it |
|---|---|---|
| "Mention that the new vendor can't store this history" | Explains the gap | A product claim you have not sourced, and the scope is a choice, not a limit |
| "Attach the exception summary from the workshop" | Saves the owner time | Moves company information out without authority |
| "Add that GP support ends in 2031" | Adds urgency | Only relevant if the company runs GP; otherwise it is a borrowed deadline |
| "Say the history is worth more than the migration costs" | Gets attention | An unsupported valuation |
| "Remove the independence line; it sounds defensive" | Shorter email | Leaves the owner to wonder whether your advice was neutral |
On the third row: Microsoft has announced the end of support for Dynamics GP, with security updates available until April 30, 2031. If the company's legacy system is GP, that date can replace the placeholder; if not, leave it out. The introduction email builder offers other openings, and the guide to introducing a portfolio company CEO covers tone for senior recipients.
Final checks
- Separation: separate thread, sent after the scope conversation, not inside a selection update.
- Company fit: 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.
- Facts: every type, span and date came from the company; the vendor selection archive context checklist holds them.
- Attribution: the first valid introduction within the 90-day window is credited when the company submits a verified application, one partner per company.
- Reward: nothing is payable on the email, a call or a signature alone. 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. See rewards for every condition, and the ERP referral fee comparison for how this differs from a reseller fee.
Unknown until SourceX reviews it: dataset fit, contract limits on reuse of transaction records, the rights review result and any offer.
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.
When the owner has opted in and the draft is kept apart from your selection work, register as a partner, confirm the company on who qualifies, and keep the program terms open while you send it.