Lesson 1 · Positioning, Why Now, and Value Proposition

Positioning, Why Now, and Value Proposition

Length: 21 minutes across 7 sections
You will be able to apply: The Value Triad Gate · The Repeatable Claim Test
You will produce: Commit Statement
You will work: 4 gated questions

Reading

What business outcome does your buyer gain, why is this quarter the moment it becomes urgent, and what single differentiator makes you the governed path to that outcome?
Core question

A seller who leads with capability is easy to compare. A seller who leads with a governed outcome the buyer already needs is difficult to displace. The discipline of positioning is not describing what your platform does. It is naming the outcome, the timing pressure, and the proof that you deliver it under conditions the buyer's own governance demands. When those three elements are precise, the buyer repeats them internally without your help. When any element is missing, the message decays into a feature comparison and the deal migrates to price.

You position by governing your own claim before the buyer tests it. That means the outcome is measurable, the urgency is verifiable, the differentiator is evidence-backed, and the whole proposition survives repetition by a non-expert. The standard is simple: if a colleague cannot repeat your value proposition from memory after hearing it once, the buyer will not repeat it to their committee either.

Next: The pathology: Feature Gravity

Section 2 of 7

The pathology: Feature Gravity

PrincipleFeature Gravity is the reflex of answering a buyer's business problem with a capability list. It appears when a seller hears a pain statement and responds with what the platform can do rather than what the buyer will gain. The tell is a response that begins with we can or our platform supports instead of you will reduce or your team will recover. Feature Gravity pulls every conversation toward comparison grids, proof-of-concept requests, and procurement timelines that favour the incumbent. It is not helpfulness: it is the absence of a governed value claim.

The counter is not withholding product information. It is sequencing: outcome first, urgency second, capability third, and only after the buyer has confirmed the outcome matters. Camille Okafor, senior account executive at OmniCorp Advisory, calls this the gravity check: before any capability enters the conversation, the buyer must have named the business problem in their own words and agreed the timing is real.

Interactive modelFeature Gravity versus outcome positioningcontrast · 2 elements

Feature Gravity

A capability list beginning with we can or our platform supports; invites comparison grids.

Feature lists create evaluation work; outcome statements mirror conversations the buyer is already having internally.

Feature Gravity: A capability list beginning with we can or our platform supports; invites comparison grids.
Outcome positioning: A governed result beginning with you will reduce or your team will recover; earns a reply.

Next: The Value Triad Gate

Section 3 of 7Framework

The Value Triad Gate

Definition

The Value Triad Gate is the seller's discipline for confirming that three elements are evidence-backed before an outreach message is sent or a meeting is booked: the outcome the buyer will achieve, the reason this quarter is urgent, and the differentiator that separates you from every alternative. If any element rests on assertion rather than evidence, the gate does not open and the message is not sent.

The gate is deliberately binary. A message passes or it does not. There is no mostly ready. The cost of sending a message that cannot survive scrutiny is not zero: it is a reply that never comes, a meeting that stalls at discovery, or a champion who cannot repeat the value to their own committee. The gate prevents that waste by requiring proof before exposure.

When to Use It

Use the gate before writing a first outreach email, before requesting a meeting with a new stakeholder, before presenting a value proposition in a discovery call, and before asking a champion to carry a message to their economic buyer. Use it any time the next step requires the buyer to believe the claim without your presence in the room.

Do not use the gate to delay internal brainstorming or early research. Teams should explore angles freely. The gate activates at the moment a claim moves from internal discussion to external exposure. That boundary is where rigour begins.

How to Apply It

Write the outcome in the buyer's language: a measurable change to a metric the buyer already tracks.
Name the urgency driver: the external event, regulatory deadline, competitive shift, or cost of delay that makes this quarter different from last quarter.
State the differentiator as a measurable contrast: what you deliver that the incumbent platform, the low-cost automation vendor, or the internal build option cannot match under the buyer's governance requirements.
Test: can a colleague who has not worked on this account repeat all three elements after hearing them once? If not, compress and revise.
Only after all three pass, draft the outreach or request the meeting.

The discipline is compression. Each element must fit one sentence. If it takes a paragraph to explain the urgency, the urgency is not clear enough to survive a forwarded email.

Interactive modelValue Triad Gate sequenceflow · 3 elements

Outcome

A measurable change to a metric the buyer already tracks, stated in their language.

The gate is binary: all three elements must be evidence-backed before any external-facing communication is sent.

Outcome: A measurable change to a metric the buyer already tracks, stated in their language.
Urgency: An external event or cost of delay that makes this quarter different from last quarter.
Differentiator: A measurable contrast with the incumbent, low-cost vendor, or internal build option.

Worked example 1 of 3

Dev Raghunathan, account executive at OmniCorp Advisory, prepared an outreach to Adaeze Okonjo, chief risk officer at OmniCorp Financial. The first draft read: Our platform helps financial institutions manage AI model risk with automated documentation and monitoring. Marisol Vega, sales enablement lead, stopped the draft at the gate. Outcome: missing. Urgency: absent. Differentiator: generic.

Dev revised. Outcome: reduce model-risk documentation rework by 30 percent within two quarters. Urgency: the regulator's updated model-risk guidance takes effect in 90 days and OmniCorp Financial's current manual process cannot produce compliant documentation at the required pace. Differentiator: governed AI documentation that meets the regulator's evidence standard, which the incumbent platform does not provide and the internal build option cannot deliver before the deadline. The gate opened.

Triad element	Before gate	After gate
Outcome	Helps manage AI model risk	Reduce model-risk documentation rework by 30 percent within two quarters
Why now	Not stated	Regulator's updated guidance effective in 90 days; current manual process cannot keep pace
Differentiator	Automated documentation and monitoring	Governed AI documentation meeting the regulator's evidence standard, delivered before the deadline

Marisol Vega: Read me the value proposition without looking at your screen.
Dev Raghunathan: OmniCorp Financial can cut model-risk documentation rework by 30 percent before the new guidance takes effect, because our governed documentation meets the evidence standard the incumbent cannot match in that window.
Marisol Vega: That passes. Adaeze can repeat that to her board without translation.

Why This Works

The gate works because buyers do not forward features. They forward problems and deadlines. When Adaeze Okonjo reads a message that names her metric, her deadline, and the gap in her current approach, the message earns a reply because it mirrors a conversation she is already having internally. Feature lists do not mirror internal conversations. They create new evaluation work.

It also protects the seller's time. A message that passes the gate reaches a qualified buyer with a real problem on a real timeline. A message that skips the gate reaches anyone, which means it reaches no one with urgency.

Worked example 2 of 3Optional depth

Camille Okafor prepared a meeting request for Dr. Ilona Reyes, chief medical information officer at OmniCorp Health. Outcome: reduce clinical AI documentation cycle time by 40 percent while maintaining patient-safety audit trails. Urgency: the health authority's new AI transparency requirement becomes enforceable next quarter and OmniCorp Health's current process requires manual safety attestation for every clinical model change. Differentiator: governed clinical AI documentation with embedded safety attestation that the internal build option cannot replicate before the enforcement date. Owen Brackley, principal sales engineer, confirmed the technical claim was defensible. The meeting was booked.

Worked example 3 of 3Optional depth

Dev Raghunathan targeted Ingrid Solheim, chief digital officer at OmniCorp Retail. Outcome: reduce time-to-compliance for new AI-driven pricing models from fourteen weeks to five. Urgency: OmniCorp Retail planned to launch three new pricing models before the peak trading season, and current governance review timelines would delay two of them past the revenue window. Differentiator: pre-validated governance templates that compress review cycles, which the low-cost automation vendor does not offer and which the internal build option cannot produce without hiring two additional compliance analysts. Selma Whitfield, vice president of sales at OmniCorp Advisory, approved the outreach after Marisol Vega confirmed the claim survived the repeat test.

Edge Cases and NuancesOptional depth

Some buyers do not have a deadline. That does not mean urgency is absent. The cost of delay is itself an urgency driver: every quarter without governed AI documentation costs OmniCorp Financial 1,200 hours of manual rework. State the cost in units the buyer measures. If you cannot find a cost, the account may not be qualified.

The gate does not require perfection. It requires evidence. A differentiator backed by three customer references and a measured outcome is strong. A differentiator backed by a product roadmap is not evidence: it is a promise. Promises do not pass the gate.

Knowledge check

A seller's outreach message reads: Our AI governance platform automates compliance workflows, reduces manual effort, and integrates with your existing systems. Which triad elements are missing?

Answer first, then check.

Next: The Repeatable Claim Test

Section 4 of 7Framework

The Repeatable Claim Test

Definition

The Repeatable Claim Test is the standard for determining whether a value proposition is ready for external use. A claim is not ready until a colleague can repeat it accurately from memory after a single hearing, and then the buyer can do the same. If the claim requires notes, slides, or re-explanation, it is too complex to survive the internal conversations where deals are actually won or lost.

The test is not about brevity for its own sake. It is about fidelity under transmission. A champion who carries your message to the economic buyer will paraphrase. If the original is precise, the paraphrase preserves the outcome, the urgency, and the differentiator. If the original is vague, the paraphrase becomes we should look at their platform, which is a feature conversation waiting to happen.

When to Use It

Use the test after the Value Triad Gate confirms the three elements are evidence-backed. Use it before any external-facing communication: outreach emails, discovery call openings, proposal executive summaries, and champion enablement materials. Use it when preparing a champion to present your value to their committee without your presence.

Do not skip the test because you trust your own articulation. The test is not about you. It is about the buyer's internal echo. Every deal is won in a room you are not in. The claim must survive that room.

How to Apply It

State the full value proposition aloud in two sentences or fewer.
Ask a colleague to repeat it back without notes. Record what they omit or change.
If any of the three triad elements is lost in repetition, revise the phrasing until all three survive.
Once a colleague can repeat it, test with the buyer: after stating it in a meeting, ask the buyer to confirm what they heard.
If the buyer's restatement drops a triad element, note which element fails and revise before the next interaction.

The revision loop is fast. Most claims fail on the first attempt because the urgency driver is buried in a subordinate clause or the differentiator requires context the listener does not have. Move the failing element to the front of its sentence and remove every word that does not carry meaning.

Interactive modelRepeatable Claim Test revision loopcycle · 4 elements

State the claim

Deliver the full value proposition aloud in two sentences or fewer.

The loop continues until all three triad elements survive a single hearing by someone without prior account context.

State the claim: Deliver the full value proposition aloud in two sentences or fewer.
Colleague repeats: A colleague with no prior context repeats it back without notes.
Identify loss: Record which triad element was dropped or changed in repetition.
Revise: Compress or reorder the failing element until it survives the next attempt.

Worked example 1 of 3

Owen Brackley, principal sales engineer at OmniCorp Advisory, tested a claim with Dev Raghunathan before a call with Martin Hollis, head of consumer lending at OmniCorp Financial. Dev stated: OmniCorp Financial can cut lending-model documentation rework by 30 percent before the regulator's 90-day deadline because governed documentation meets the evidence standard the incumbent cannot match in that window. Owen repeated: You cut documentation rework by 30 percent before the deadline because you meet the evidence standard and the incumbent does not. All three elements survived. The claim was ready.

Why This Works

The test works because deals are decided in conversations sellers do not attend. Martin Hollis will describe the option to Adaeze Okonjo. Adaeze will mention it to Priyanka Venn, group chief financial officer at OmniCorp Group. Each retelling drops detail. A claim that survives the first repetition has the structural simplicity to survive the third. A claim that fails the first repetition arrives at the economic buyer as a vague request to evaluate another vendor.

It also disciplines the seller. Complexity feels like thoroughness. It is not. Thoroughness is compression that preserves meaning. The test forces compression until nothing can be removed without losing a triad element.

Worked example 2 of 3Optional depth

Camille Okafor prepared a champion enablement summary for Colm Byrne, head of clinical operations at OmniCorp Health. Colm needed to carry the value to Dr. Ilona Reyes. Camille stated: OmniCorp Health can reduce clinical AI documentation cycles by 40 percent before the transparency requirement takes effect because embedded safety attestation eliminates the manual step the internal build cannot remove in time. Colm repeated it to Marisol Vega during a practice round. Marisol confirmed all three triad elements survived. The champion was enabled.

Worked example 3 of 3Optional depth

Dev Raghunathan tested a claim for Yusuf Demir, vice president of network operations at OmniCorp Logistics. Claim: OmniCorp Logistics can bring three new AI-optimised dispatch models into governed production in six weeks instead of fourteen because pre-validated governance templates eliminate the re-review cycle the current platform requires. Owen Brackley repeated it back accurately. Dev then delivered it to Claire Beaumont, head of dispatch systems, during discovery. Claire restated: You compress our governance review from fourteen weeks to six with templates that skip the re-review. The differentiator survived. The urgency survived. The outcome survived.

Edge Cases and NuancesOptional depth

Technical buyers sometimes demand more detail than two sentences allow. The test does not replace technical depth. It ensures the opening frame is repeatable. After the frame lands, you expand. But if the frame itself requires expansion to be understood, the buyer's committee will never hear it accurately.

Some claims pass the repeat test but fail on evidence. Repeatability without truth is a slogan. The Value Triad Gate and the Repeatable Claim Test work in sequence: first truth, then compression. Never reverse the order.

Knowledge check

A colleague repeats the value proposition and drops the differentiator but retains the outcome and urgency. The seller decides to proceed because two of three elements are strong. Is this correct?

Answer first, then check.

Decision point

Dev Raghunathan is about to send an outreach email to Rafael Duarte, merchandising director at OmniCorp Retail. The message reads: Our AI governance platform automates compliance workflows, reduces manual effort, and integrates with your existing systems. Should Dev send this message?

Write your answer before you continue

Confidence before seeing the analysis

What evidence or assumption could change your decision?

Commit, calibrate, and name contrary evidence first.

Decision point

Camille Okafor has drafted a value proposition for Nadia Farouk, director of digital services at OmniCorp Public. Owen Brackley can repeat the outcome and the differentiator but cannot recall the urgency driver. Camille is confident Nadia will understand the urgency in context. Should Camille proceed with the outreach?

Write your answer before you continue

Confidence before seeing the analysis

What evidence or assumption could change your decision?

Commit, calibrate, and name contrary evidence first.

Next: Common Failure Modes

Section 5 of 7

Common Failure Modes

Failure modeCapability cascade. What it looks like in the moment: the seller responds to a buyer's problem statement by listing four or five platform features in rapid succession, watching the buyer's eyes glaze. The cost when this happens: the buyer requests a generic product demonstration instead of a strategic conversation, adding three weeks to the deal cycle and reducing the average contract value by 40 percent because the conversation anchors to feature comparison. The correction: pause after the buyer states the problem, restate the outcome in their language, confirm agreement, and introduce only the capability that directly serves that outcome.

Failure modeUrgency assumption. What it looks like in the moment: the seller states the value proposition without verifying whether the buyer's deadline or cost of delay is real, relying on industry knowledge rather than the buyer's confirmation. The cost when this happens: the deal stalls after discovery because the buyer has no internal pressure to act this quarter, wasting 60 hours of pre-sales time on a deal that will not close for two quarters. The correction: verify the urgency driver directly with the buyer before investing pre-sales resources. Ask when the cost of inaction becomes unacceptable.

Failure modeCompression avoidance. What it looks like in the moment: the seller insists the value proposition needs context and refuses to compress it below four sentences because important nuance will be lost. The cost when this happens: the champion paraphrases inaccurately to their committee, the economic buyer hears evaluate another vendor instead of the governed outcome, and the deal enters a six-week evaluation that a precise two-sentence claim would have bypassed. The correction: apply the Repeatable Claim Test until all three triad elements survive a single hearing by a colleague, then test with the buyer.

Failure modeDifferentiator drift. What it looks like in the moment: the seller states a differentiator that was true eighteen months ago but has since been matched by the incumbent platform, and the buyer's technical evaluator surfaces the gap during a proof-of-concept review. The cost when this happens: credibility is lost in the evaluation committee, the deal requires a new champion, and the sales cycle extends by one full quarter at a cost of 120 hours of delivery and pre-sales effort. The correction: validate differentiators quarterly with the product and delivery teams. A differentiator backed by a roadmap rather than current evidence does not pass the Value Triad Gate.

Failure modeEcho chamber testing. What it looks like in the moment: the seller tests the Repeatable Claim with a colleague who already knows the account context, and the colleague fills in gaps from memory rather than from the claim itself. The cost when this happens: the claim appears ready but fails on first buyer contact, costing the meeting outcome and requiring a second meeting to re-establish credibility, adding two weeks and 20 hours to the cycle. The correction: test with a colleague who has no prior context on the account. If they cannot repeat the three elements, the buyer cannot either.

Next: Worked scenario: OmniCorp Logistics uses the Value Triad Gate and the Repeatable Claim Test

Section 6 of 7

Worked scenario: OmniCorp Logistics uses the Value Triad Gate and the Repeatable Claim Test

OmniCorp Advisory identified OmniCorp Logistics as a qualified account after Yusuf Demir, vice president of network operations, mentioned at a conference that manual governance reviews were delaying AI dispatch models. Dev Raghunathan owned the account. He began by drafting an outreach to Claire Beaumont, head of dispatch systems.

Dev's first draft read: Our governance platform can help OmniCorp Logistics automate AI model documentation and streamline compliance. Marisol Vega rejected it at the Value Triad Gate. Outcome: vague. Urgency: absent. Differentiator: generic. Feature Gravity was pulling the message toward a product demonstration request.

Dev applied the gate. Outcome: reduce governance review time for AI dispatch models from fourteen weeks to five, enabling three models to reach production before the peak shipping season. Urgency: OmniCorp Logistics had committed to the peak-season launch window and current review timelines would delay two of three models past the revenue deadline, costing an estimated 2.1 million dollars in overtime and late penalties. Differentiator: pre-validated governance templates that eliminate re-review cycles, which neither the incumbent platform nor the internal build option could deliver in the available window.

Dev then applied the Repeatable Claim Test. He stated the compressed claim to Owen Brackley: OmniCorp Logistics can bring three dispatch AI models into governed production in five weeks instead of fourteen before peak season because pre-validated templates eliminate the re-review the current platform requires. Owen repeated: You cut governance review from fourteen to five weeks before peak season with templates that skip re-review. All three elements survived.

Claire Beaumont received the outreach and replied within two days. In the discovery call, she confirmed the timeline pressure and named Anders Nilsen, platform engineering lead, as the technical evaluator. Dev asked Claire to restate the value. She said: You get our dispatch models through governance in five weeks instead of fourteen so we hit peak season. The outcome and urgency survived. The differentiator was implicit but present in the mechanism. The claim had passed both gates and the deal advanced to a structured evaluation with a named timeline.

Mark the level that describes you today. Nothing is submitted.

Behaviour	Ready	Developing	Not yet
Applying the Value Triad Gate before outreach	In the OmniCorp Logistics scenario, identifies that the first draft fails all three triad elements, revises with measurable outcome, verified urgency, and evidence-backed differentiator before sending.	Identifies that the draft needs an outcome but sends with a vague urgency statement because the deadline seems obvious from context.	Sends the first draft because it accurately describes the platform and assumes the buyer will infer the value.
Applying the Repeatable Claim Test with a colleague	In the same OmniCorp Logistics scenario, tests with Owen Brackley who has no prior account context, confirms all three elements survive repetition, and revises any element that does not.	Tests with a colleague but accepts a repetition that drops the differentiator because the colleague understood the general point.	Skips the test because the value proposition sounds clear when read aloud and trusts personal judgment over external validation.
Confirming buyer repetition in discovery	In the same scenario, asks Claire Beaumont to restate the value during the call, notes which elements survived, and plans to reinforce the differentiator in the next interaction.	Delivers the value proposition clearly but does not ask Claire to restate it, relying on her engagement signals instead.	Moves directly to product demonstration after Claire expresses interest without confirming what she will tell her committee.

Next: Commit

Section 7 of 7

Commit

Commit Statement

Complete before your next outreach sequence. Use the account where you are most tempted to lead with features. Sign and share with your manager as your operating standard for the next 30 days.

I commit to

I will stop

I will start

I will know I succeeded when

Signed Date

Window	Field application
Days 1 to 7	Select one active account. Apply the Value Triad Gate to your next outreach message. Revise until all three elements are evidence-backed.
Days 8 to 14	Test the revised claim with a colleague using the Repeatable Claim Test. Record which element fails first and revise until all three survive repetition.
Days 15 to 21	Deliver the claim in a live buyer conversation. Ask the buyer to restate what they heard. Note which triad element survives and which requires reinforcement.
Days 22 to 30	Review three outreach messages sent this month. Score each against the gate. Replace any message that fails with a revised version that passes.

DisclaimerGeneral guidance only. All organisations and people named in this lesson are fictional, including OmniCorp Advisory, OmniCorp Financial, OmniCorp Health, OmniCorp Retail, OmniCorp Logistics, and OmniCorp Public. Sales messaging must follow the seller's reviewed materials and applicable regulations. Outcomes described are instructional and must not be presented as guarantees or typical results.

Required practice must be complete.