Policy system migration introduction email: an annotated draft for insurance software consultants

Short answer

Write to the underwriting or operations leader who can authorize a discussion, after your conversation established whether policy versions link to the decisions behind them. Use a subject naming the cutover, one paragraph on what the policy admin team said about endorsement history, one on SourceX with your reward interest disclosed, and one offering an introduction that asks only for a description. Attach nothing and name no policy. The draft and a line-by-line commentary follow.

Visual briefFull-size diagram
An email to a chief underwriting officer appears line by line on a letter-style sheet, with numbered margin notes on the left explaining the dated cutover, the version-to-decision question, the record types, the disclosure and the description-only ask.
The draft with numbered notes. Braced placeholders come from your notes with the underwriting and policy admin leads.

The draft is part of the policy system migration guide for insurance software consultants, which sets out the version-to-decision map. It usually follows the policy system migration meeting agenda.

The draft, ready for your placeholders

Replace each brace with what the company told you. Underwriting leaders forward email to counsel, so write as if a lawyer will read it.

Subject: Underwriting decision history before {legacy_system} cutover on {cutover_date}

Hi {first_name},

Thank you for including {admin_lead} and {uw_lead} on Tuesday. Before conversion locks, we asked one thing: are policy versions in {legacy_system} still linked to the decisions behind them? They described referral notes and rating worksheets tied to mid-term endorsements for {lines} since {first_year}, while older renewals hold documents only.

SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. Nothing is shared unless {company} agrees terms, and policyholder data is handled in that review. For transparency: I am a SourceX referral partner and may receive a reward from SourceX if a qualifying license completes. SourceX pays it separately, it never reduces what {company} would receive, and it has no connection to the conversion work.

I can introduce you if helpful. SourceX would start from a description: lines and years with linked history, a rough count of policy transactions, where the decision notes sit and who can approve a conversation. No policy files. Reply "yes" or "not now".

{your_name}

Line-by-line commentary

LineWhat it doesWhat must stay out
Subject with system and cutover dateAnchors the email to a documented conversion eventWords like "monetize" or a dollar amount
"Thank you for including..."Credits the facts to the company's own peopleNames of brokers, insureds or underwriters outside the meeting
"Before conversion locks"Explains why now without inventing pressureA date that the project has not confirmed
The version-to-decision questionUses the meeting's exact wordingA judgment that the history is valuable
Referral notes and worksheets tied to endorsementsNames the record types at metadata levelPolicy numbers, claim numbers, premium figures
"Older renewals hold documents only"Shows the gap honestlyAdvice to change the conversion design for the referral's sake
The SourceX sentenceSays exactly what SourceX doesNamed AI labs or claims that interest is certain
"Policyholder data is handled in that review"Answers the first worry an insurance leader hasPromises about de-identification outcomes
Disclosure sentencesStates your interest before any introduction"I may benefit" without naming who pays
"No connection to the conversion work"Keeps your consulting role separateDiscounts or fee offers tied to a referral
The description-only askSets the metadata boundaryA request for a sample endorsement or a data extract
"Yes or not now"Offers an easy declineChasers, deadlines, "last chance"

Why the email says "linked" and not "policy data"

Every insurer has policy data; the distinction worth an introduction is the link. The NAIC glossary defines an endorsement as an amendment or rider that adjusts coverage and takes precedence over the general contract, so each endorsement is a decision point. Systems record them as transactions: in Guidewire PolicyCenter's Cloud API, a policy change starts with an effective date and creates a job of type PolicyChange. Whether the referral note or rating override behind that job is linked depends on configuration and habit. The email repeats what the admin lead described about that link and nothing more. The underwriting notes data type page covers why the reasoning beside a policy matters.

Why the disclosure sits in the middle paragraph

The FTC's Endorsement Guides call for clear and conspicuous disclosure of an unexpected connection between an endorser and a seller that could affect how a recommendation is weighed, and they include the chance of payment. Putting the sentence next to the description of SourceX, rather than in a footer, makes it impossible to miss. Ask your own advisers whether the guides apply to your situation.

Swaps when the facts differ

SituationEdit
The company is an MGA writing on carrier paperAdd after the disclosure: "Your carrier agreements may decide what can be reused; SourceX's rights review starts there."
Decision notes live in email, not the policy systemReplace "tied to mid-term endorsements" with "kept in account mailboxes keyed to the policy number"
The legacy system will stay read-only for yearsDrop "before conversion locks" and write "while {legacy_system} remains readable"
Only one line of business has linksName that line only and drop the plural
The leader prefers a colleague to leadAddress both and name the colleague as SourceX's contact
The company is an agency, not a carrierReplace underwriting worksheets with "service and endorsement requests" and see the agency service request page

The introduction email builder fills braces from your notes, and the wealth advisor introduction email shows the same disclosure pattern in another profession. Brokers with commercial clients can compare the commercial insurance broker partner page.

What you must know before sending

  • Which records exist: lines, years and the form of the decision context (referral queue, worksheet, note), described by the company.
  • Who owns them: the company, its carriers, or both. For MGAs, carrier agreements matter.
  • Who can authorize: the named recipient of this email.
  • Whether the company fits: 50+ full-time employees at peak (contractors excluded), a 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: demand for endorsement decision histories, the rights review result, the de-identification scope, any offer and any reward. If the archive context checklist shows the links are being dropped at cutover, the email should say so.

After a reply

A "yes" means you submit the introduction through your partner account with the recipient's details, then let SourceX lead. A "not now" means you note the date and leave it. Sign the Channel Partner Agreement before submitting. Credit goes to the first valid introduction within the 90-day window, recorded when the company submits a verified application, with one partner per company. Illustrative only: if the company were paid $250,000 for a qualifying completed handoff, the reward would be $62,500. The rewards page explains every payment condition.

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.

Before sending the draft to the underwriting leader, register as a partner, check the company on who qualifies and read the program terms so the disclosure matches your agreement.

  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

Should the email go to the CIO running the migration or to the underwriting leader?

To whoever can authorize a licensing discussion about underwriting records. At a carrier that is usually the chief underwriting officer with legal; at an MGA it may be the CEO, because carrier agreements decide what can be reused. The CIO can be copied if they agree.

Can I mention a specific policy as an example?

No. A policy number, insured name or claim reference in an email is policyholder information leaving the company. Describe the pattern in general terms, such as mid-term endorsements linked to referral notes.

Do I need to explain what SourceX does with insurance data?

One sentence is enough: SourceX licenses approved business data directly from companies and handles agreement, rights review, preparation, delivery and payout. Questions about scope belong in the SourceX conversation, not your email.

Sources

  1. content.naic.org/glossary-insurance-terms
  2. docs.guidewire.com/cloud/pc/202411/cloudapibf/cloudAPI/topics/1…
  3. ecfr.gov/current/title-16/chapter-I/subchapter-B/part…
  4. refer.sourcex.si/terms
  5. refer.sourcex.si/rewards

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