Sample brief

See what your rep walks in with

Enterprise deals are won on context.

LightGTM builds the outside-in business case before the first meeting. It includes who's in the buying committee, what each stakeholder cares about, and how to earn the next conversation.

The company and stakeholders below are fictionalized. The structure, depth, and judgment are exactly what customers receive. Every client brief is grounded in verifiable, source-linked signals.

This is the first brief, not the only brief. It gets your team into the account the right way. After discovery, the brief rebuilds around what the account actually said: updated buying committee, stakeholder-specific objections, demo strategy, and next-step messaging.

As the deal evolves, so does the brief. Every conversation, correction, and outcome sharpens the next version, so every rep walks into every meeting with the full picture, not yesterday's understanding.

The sample brief · rendered inline
Outreach · Sample
Acumen CRM (fictional seller) →
Cobalt Mutual Insurance
Policyholder-experience CRM · Committee mapped, entry sequenced · SAMPLE BRIEF
Date: Sample
Sample notice
Fully fictionalized. Company, people and signals are invented for illustration; any resemblance to real companies or persons is coincidental. Structure, depth and judgment are identical to client deliverables.
Account
Cobalt Mutual Insurance · US health & life insurer · ~$8B premiums · ~11,000 employees · HQ Columbus, OH
Scope
Group benefits & individual health lines, US
Committee
7 roles mapped across digital, CX, IT, compliance, distribution and finance
UVP line
Acumen layers policyholder intelligence onto the systems Cobalt already runs. Nothing gets ripped out. No parallel process.
01
Executive Summary

Why this account, why now

Cobalt Mutual is eighteen months into a publicly named "Digital Front Door" program and five months into a new Chief Digital Officer hire, and the two facts together define the moment. The program has budget and board visibility; the new leader needs a visible win inside her first year; and the service layer is where the pain is loudest, with complaint ratios on the individual health line running above peer benchmarks two years running.

The service stack is the opening. Policyholder interactions run on a custom CRM built in 2011 plus a single-department Service Cloud instance, which means no unified policyholder view across group and individual lines. Every signal in this brief points to a company that has already decided to modernize the experience layer and has not yet decided with whom.

The entry is the CDO, through the CX lens, in her first-year window. The case that carries the committee is complaint-ratio reduction and retention on renewal, not "modern CRM."

Insight

A named transformation program plus a new-in-seat digital leader is the highest-conversion pattern in enterprise outreach. The program supplies the budget line; the leader supplies the urgency. The entire entry plan below is built to land inside that window.

02
Why Now
#SignalStrengthStatusRead
1New CDO (Renata Voss), joined Feb 2026 from a top-five carrierStrongCurrentFirst-year-win window open. The entry point
2"Digital Front Door" program named in the annual report, year twoStrongCurrentFunded, board-visible modernization mandate
3Complaint ratio above peer benchmark, individual health, two consecutive yearsStrongCurrentThe measurable pain the case anchors on
4CX hiring wave: 14 open roles across service transformation and policyholder experienceStrongCurrentCapability build underway; tooling decisions follow headcount
5State regulator modernization filings referencing digital service standardsContextCurrentCompliance tailwind for the program
6Legacy custom CRM (2011) plus one-department Service CloudStrongCurrentNo unified policyholder view. The technical opening
03
The Incumbent Picture

Custom policy-CRM, built 2011. Deeply integrated with policy admin, owned by IT Applications. It will not be ripped out in year one, and proposing that is how a vendor loses this account. Position on top of it.

Salesforce Service Cloud, one business unit. Proof that Cobalt buys modern CX tooling, and proof the org knows the pain of fragmentation. Both facts help the case.

Play type: LAYERING. Unify the policyholder view across what exists. The vendor who proposes replacement fights the IT owner of a 14-year system; the vendor who proposes a layer on top recruits him.

Warning

Compliance is a silent veto in this account. Health-line data means HIPAA scope plus state DOI oversight, and the annual report's regulatory language suggests an empowered compliance function. Bring the compliance story to them before they ask, or the deal stalls in security review after months of good meetings.

04
The Value Hypothesis

What this is worth, before anyone has confirmed a number

Cobalt has not shared a single internal figure at this stage, so the case is built from what is public and stated in ranges. The job before the first meeting is to establish that the money is large enough to justify the conversation, and to name which number the committee will be measured on. Precision comes from their own enrollment, retention and service data in discovery.

LeverThe mechanismIllustrative scale
Retention on renewalThe unified view flags a policyholder at risk ninety days before the renewal date instead of surfacing the loss after it. Elaine Fischer's number.Individual health represents roughly a third of Cobalt's ~$8B premium base. One point of retention improvement on that line is on the order of $25M in retained annual premium.
Cost to serveAgents reconcile group and individual records by hand across two systems on every cross-line call. Unified context removes the reconciliation step, and the saving lands against a service headcount curve FP&A is already forecasting.A 10 to 15 percent reduction in average handle time compounds across every policyholder interaction at an 11,000-person carrier.
Complaint ratio and regulatory exposureEvery point above peer benchmark carries three costs at once: service hours absorbed by escalation, state DOI attention, and non-renewal. This is the metric the CDO can put in front of a board inside her first year.The individual health line has run above benchmark two consecutive years. Moving it back to benchmark is the first-year win the entry plan is built around.

The three levers compound rather than compete. Retention is the revenue story that carries the deal at budget review, cost to serve is what finance approves against, and the complaint ratio is what the economic buyer reports upward. The same unified view produces all three, which is why the case can be framed differently for each seat without changing what is being bought.

Insight

A pre-entry value case is a hypothesis, not a quote. Stating ranges and naming the four unknowns that would sharpen them reads as more credible to a CFO than a precise number nobody can source. The discovery questions in Section 08 are built to close exactly those gaps.

05
Buying Committee

Coverage: Buyer ✅ · Champion ✅ · User ✅ · Technical Influencer ✅ · Compliance Influencer ✅ · Business Owner ✅ · Finance ✅ · Procurement ⚠️ (validate in discovery)

In classic committee terms: economic buyer = the CDO holding program budget · decision shaped with the VP Customer Experience · gates at IT Applications and Compliance · business case carried by Distribution · finance sign-off below the CFO.

WaveSlotPersonSeatFrame
1Economic buyerRenata VossChief Digital Officer, 5 months in seatFirst-year metric, value at speed
1User + championMarcus BellVP Customer ExperienceOperational pain, one screen per policyholder
2Technical gatePriya RamanVP IT ApplicationsHer core stays; layer, not replacement
2Compliance gateDan KowalskiChief Compliance OfficerAudit trail by design, before he asks
2Business ownerElaine FischerSVP Distribution & AgencyRetention on renewal, the revenue story
2FinanceTom GarrityDirector FP&A, OperationsCost-to-serve, payback inside eight quarters
—FacilitatorVendor managementSeat unverifiedValidate in discovery
RV
Renata Voss
Chief Digital Officer · Cobalt Mutual
Economic BuyerChampion-candidate
Status: New in seat, five months. Owns the Digital Front Door budget. Came from a carrier that ran a unified-policyholder-view program, so she does not need the concept sold, she needs the fastest credible path to a first-year metric. Lead with complaint-ratio movement inside two quarters.
MB
Marcus Bell
VP Customer Experience · Cobalt Mutual
UserDay-to-day Champion
His team lives in the fragmented view daily and his complaint numbers are the ones above benchmark. The strongest internal advocate if armed with the operational story: one screen per policyholder, service history across lines, renewal-risk flags his agents act on.
PR
Priya Raman
VP IT Applications · Cobalt Mutual
Technical Influencer (gate)
Owns the 2011 CRM and its integrations. The one person a replacement pitch turns into an opponent. The layer-on-top frame makes her the technical sponsor instead: her system stays the core, Acumen consumes its data and takes the modernization pressure off it.
DK
Dan Kowalski
Chief Compliance Officer · Cobalt Mutual
Compliance Influencer (silent veto)
HIPAA scope, state DOI exposure, vendor-risk owner. Never in the first meeting, always in the outcome. The move is a proactive one-pager on data handling and audit trail in wave two, before security review begins.
EF
Elaine Fischer
SVP Distribution & Agency · Cobalt Mutual
Business Owner
Renewal retention is her number, and retention is where the unified view pays. She turns the project from a service-cost story into a revenue story, which is what carries it at budget review.
TG
Tom Garrity
Director, FP&A (Operations) · Cobalt Mutual
Finance Approver
The commercial mechanics below the CFO threshold. Cares about cost-to-serve per policyholder and program payback inside eight quarters.

Open seat, on purpose: vendor management surfaced only at transactional level. Whether software purchases route through a strategic sourcing gate or straight through IT vendor review is a discovery question, and the answer shortens or lengthens the close by a quarter. We flag what we could not verify rather than smoothing over it.

06
What Each Stakeholder Needs to Hear

Voss: a first-year metric. Complaint-ratio movement on the individual line inside two quarters, on top of existing systems, visible at board level.

Bell: one screen per policyholder. Service history across lines, renewal-risk flags, fewer escalations his team eats.

Raman: her core stays. Acumen reads from the 2011 system and Service Cloud; integration effort is weeks, not a migration.

Kowalski: audit trail by design. Data handling, HIPAA scope and DOI-ready reporting, offered before he asks.

Fischer: retention on renewal. The unified view catches the at-risk policyholder ninety days before the renewal date, not after.

Garrity: cost-to-serve down, payback inside eight quarters, priced against the service headcount curve he is already forecasting.

UVP propagation: the one line every seat must hear, in their own dialect, is the same line: intelligence on top of what Cobalt already runs, nothing ripped out. If it lives only with the champion, IT hears risk and compliance hears exposure.

Must-have vs good-to-have (validate in discovery)

RequirementTag
Reads from the 2011 core and Service Cloud, no migrationMust-have
HIPAA-scope data handling with DOI-ready audit trailMust-have
A measurable complaint-ratio or retention metric inside two quartersMust-have
Renewal-risk flags in the agent workflowGood-to-have
Group-line expansion after individual-line proofGood-to-have, later
07
Entry Plan

Wave one: the CX lens, two doors

Open with Bell (operational pain, fastest to feel it) and Voss (budget, first-year window), Bell first, one week apart. A champion who has already nodded makes the CDO conversation twice as strong. Two departments threaded from day one, so the deal never hangs on a single reply.

Wave two triggers on whichever comes first: wave one fully out with no reply after three business days past the second touch, or any positive wave-one reply, in which case wave two opens selectively: a Voss conversation pulls Raman and Garrity forward, a Bell conversation pulls Fischer.

Wave 1 · Bell
LinkedIn connection request + 2-email thread
Send to: Marcus Bell
[Message copy redacted in this sample. Client briefs carry the full persona-tuned sequence here: connection note and a two-email thread, generated from your sales motion, voice and proof rules, one idea and one ask per message.]
Wave 1 · Voss
Email, 2-touch thread
Send to: Renata Voss
[Message copy redacted in this sample. The Voss thread leads with the first-year-metric frame above, in the seller's voice, with the proof reference the seller is permitted to use.]

Wave two frames, held until triggered: Raman gets the integration architecture (recruit the gate early), Kowalski gets the proactive compliance one-pager, Fischer enters once a meeting exists so retention joins the business case before budget review.

First-year window

The CDO's first-year window closes as budget season opens. Wave one lands now, the pilot conversation happens inside the program's year-two funding, and the business case is built before next year's plan locks. Six months from now this is a next-cycle conversation.

08
Discovery Questions

Deal-shaping

  1. Is the Digital Front Door program's year-two budget already allocated to named workstreams, or is there open scope? (Decides whether this is a land-inside-the-program deal or a new line item.)
  2. Who owns the experience-layer tooling decision, the CDO's program office or IT Applications? (Decides pilot sign-off and who must be in the second meeting.)
  3. Does software purchasing route through a strategic sourcing gate or through IT vendor review? (Closes the open committee seat.)

Pain-surfacing

  1. When a policyholder calls about a group policy and an individual policy in the same call, what does the agent actually see?
  2. Which complaint categories drove the ratio above benchmark, and which of those are visibility problems rather than policy problems?
  3. What happened the last time a renewal-risk case was caught late, and where did the miss live?
  4. What did the Service Cloud rollout teach the org about what the next tool must not do?
09
Objection Handling
"We're mid-program, the roadmap is set." (Voss, program office)
Then land inside it. The layer-on-top shape means no roadmap displacement: one workstream, one metric, two quarters, and the result feeds the program's year-two report rather than competing with it.
"We already have Salesforce in one unit. We'll extend it." (Raman)
Extending it is a migration wearing a smaller name: the 2011 core still has to feed it, and the group-vs-individual split is the hard part either way. The layer reads both systems as they are, which is why it lands in weeks. If a full-platform consolidation is the three-year plan, the layer is what makes the interim measurable rather than lost.
"Health data. Security review will take two quarters alone." (Kowalski)
Agreed, so the review starts in wave two, not after the pilot design. The compliance one-pager, data handling, HIPAA scope, audit trail, arrives before the first technical meeting, and the pilot is scoped to a data class that clears fastest.
"Where's the ROI?" (Garrity)
Complaint-ratio movement prices itself: every point above peer benchmark carries a known cost in service hours, regulatory attention and non-renewal. The pilot commits to a measurable move inside two quarters, priced against the service headcount curve already in the plan.
"We tried a CX tool before and adoption died." (Bell, Fischer)
Adoption dies when agents get a second screen. The layer goes into the workflow they already run, which is a design constraint here, not a promise, and the pilot's success metric includes agent usage, not just the complaint number.
10
How This Brief Evolves

This is the outreach-stage brief: it gets the right first conversations. After discovery, the next brief rebuilds around what the account actually said: discovery findings folded in, the committee updated with who really showed up, objection handling sharpened to the words they used, and the demo strategy for this specific committee. As the deal moves, the brief moves with it, so every person who touches the deal walks in with the full picture.

Outreach
Deal state
StatusWave one live, wave two held on trigger
What changedCommittee mapped, entry plan built
Next actionBell first, Voss T+7 · due sample
Relationship healthNo prior contact; cold entry by design

Your next enterprise account
has a way in.

See what it looks like.

Enter a target account. Get account intelligence in 2 hours.

Find the way into your next account
Intelligence takes ~2 hours. Account-specific, not a database lookup.