Foundry Academy · Sales Development · Lesson 3 of 6

Value hypothesis and messaging

Write honest outreach that connects a verified account signal to a plausible problem and a low-friction next step without deceptive claims.

Start the lesson

Your learning work, on this device

No signup, cloud storage, cross-device sync or verified completion. Saving is optional. This browser profile is shared with anyone who can use it; private mode, browser cleanup or storage limits may remove work. Use only fictional or non-sensitive material. Export a copy before relying on this device.

Not saved. Worksheets, answers and practice notes currently last only in this tab.

Practice markers are self-reported, never credentials.

01 · Explanation

Value hypothesis and messaging

Objective: Write honest outreach that connects a verified account signal to a plausible problem and a low-friction next step without deceptive claims.

A value hypothesis links an observed account signal, a plausible operational problem, a relevant capability, and a question that lets the prospect correct you. It is not a declaration that the prospect has a problem. Use plain language and distinguish evidence from inference. A strong message explains why this account, why now, what may improve, what proof can be shared, and what small next step is appropriate. Keep the message useful even if the prospect declines.

Claims must be truthful, supportable, and appropriately qualified. Do not fabricate familiarity, customer names, scarcity, referrals, results, security approvals, funding access, or personalization. Avoid implying that an automated message was individually researched when it was not. Commercial email headers and subject lines must not be deceptive; when CAN-SPAM applies, commercial email needs the required sender identification and advertising disclosure, a valid physical postal address, and clear opt-out handling; other channels and jurisdictions have different rules. Other channels have separate requirements. Approval should cover the offer, evidence, audience, channel, and variants. Preserve the source behind each performance or comparison claim and remove a claim when its evidence expires or does not fit the prospect's context.

Before you begin

  • Confirm the aggregate fit-tier evidence and the conflicting 40-percent promise versus 17-percent controlled internal demonstration.
  • No approved claim wording, account-specific signal, customer result, external validation, or completed review is supplied.
  • Define a message review boundary that includes Sales, authorized technical claims review, and privacy review where applicable.

Original overview module anchor →

02 · Compare the artifacts

Supported work. Visible uncertainty.

This is a fictional, sanitized training case using fabricated organizations and contacts. It contains no real personal or confidential data and is not legal, privacy, employment, or sales-results advice.

ClearBench ethical outbound pilot

ClearBench is a fictional supplier of modular quality-inspection workstations for small manufacturers. Leadership wants a four-week outbound pilot aimed at 120 companies in Utah and neighboring states. The proposed ideal-customer profile is plants with 25 to 250 employees, repeat inspection work, and a recent expansion, quality issue, or hiring signal. Research confirms 74 accounts meet all three fit indicators, 28 meet two, and 18 have no traceable trigger beyond industry. The list contains 162 contacts: 46 quality leaders, 39 operations leaders, 31 owners, 22 procurement contacts, and 24 people whose role is unclear. Twelve contacts left their listed employer, eight have explicit prior opt-outs, and 19 personal mobile numbers came from an unapproved list vendor. A draft email states that ClearBench will cut inspection time 40 percent, but the only evidence is one internal demonstration showing a 17 percent reduction under controlled conditions. The sequence proposes six emails, four calls, and two text messages over 14 days. It lacks channel-specific consent review, weekend restrictions, reply handling, and a stop condition after referral to another contact. Sales considers a meeting qualified whenever a prospect accepts a calendar invitation. Delivery specialists want a written problem, current process, stakeholder, urgency, and agreed next step before handoff. The pilot budget is $6,000, capacity is eight discovery calls per week, and only two specialists can conduct technical discovery. Learners must build a responsible account field, role research method, evidence-based message, controlled cadence, qualification handoff, and learning scorecard. The exercise does not promise response rates, revenue, or regulatory compliance; applicable outreach rules require qualified review.

Supported example — reference only

Draft ID
MSG-01
Audience and purpose
Operations-role hypothesis; ask whether repeat inspection work is a current priority.
Supported facts
Aggregate field includes 74 accounts meeting three fit indicators; account-specific identity and fit evidence: not supplied.
Proposed wording
Learner proposal: “If repeat inspection work is a current priority, would a brief conversation be useful? If I have the wrong context, please correct me.”
Prohibited or unsupported claim
Do not say the recipient is verified to fit or that ClearBench will reduce inspection time by 40 percent.
Reviewer
Sales process owner and authorized technical claims reviewer
Status
Learner draft — not approved for sending

A well-handled evidence gap

Draft ID
GAP-01
Audience and purpose
Any account-specific outreach message.
Supported facts
No account identity, current trigger, recipient role, or source record is supplied in this module.
Proposed wording
Not supplied; keep the account-specific message pending.
Prohibited or unsupported claim
False familiarity, verified fit, guaranteed savings, unqualified urgency, customer result, or technical approval.
Reviewer
Sales process owner, authorized technical claims reviewer, and privacy reviewer
Status
Gap open — no live message

Flawed approach — do not copy

Marking this supportable message variants “approved and complete” without the required evidence or reviewer is a flawed submission. Stop drafting or sending when a material claim lacks source, scope, limitation, account relevance, reviewer, or permitted-channel evidence.

Repair: Rework the supportable message variants as an evidence-backed draft, not an approved result. Capture each potential message fact with its exact module input ID, confidence, scope, and missing context. Separate audience relevance from performance claims; aggregate fit counts do not establish that any named account fits. Draft a bounded relevance sentence that requests correction and does not imply false familiarity or verified account-specific knowledge. Check the revision against this requirement: The draft uses aggregate evidence only and does not imply a named account or person was verified. If the required evidence is still absent, keep the decision blocked and identify the missing input or authorized reviewer.

Full case record, ambiguities and all assignments →

03 · Bounded practice

Build the supportable message variants.

Replace the unsupported savings claim with a relevant, testable value hypothesis.

Deliverable: Two message variants with claim ledger and review notes.

Complete a bounded starter and gap analysis using only CB01, F02, F07, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

Exact supplied inputs for this assignment
  • M03-I01 · F02 — Seventy-four accounts meet three fit indicators, twenty-eight meet two, and eighteen lack a traceable trigger.
  • M03-I02 · F07 — The draft promises forty-percent time savings while the only internal test measured seventeen percent.
  • M03-B01 · CB01 — Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment.
  • M03-S01 · F02, F07 — Build a starter version of “Two message variants with claim ledger and review notes.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it.

Operating procedure

  1. Capture each potential message fact with its exact module input ID, confidence, scope, and missing context.
  2. Separate audience relevance from performance claims; aggregate fit counts do not establish that any named account fits.
  3. Draft a bounded relevance sentence that requests correction and does not imply false familiarity or verified account-specific knowledge.
  4. Place the 40-percent promise and 17-percent internal demonstration in the claim ledger, preserving their conflict and controlled-test limitation.
  5. Prohibit guarantees, urgency, customer savings, external proof, and extrapolation until stronger evidence and authorized wording are supplied.
  6. Route any numeric or technical performance language to the authorized technical claims reviewer before activation.
  7. Quality-check source traceability, limitation language, correction path, tone, prohibited claims, review status, and absence of live sending.
Field-by-field guidance
Draft ID
Use a stable training identifier such as MSG-01; do not represent it as an approved campaign asset.
Audience and purpose
Describe a role hypothesis and bounded conversation purpose, not a verified individual or account condition.
Supported facts
Record only scoped aggregate evidence and its limitation; do not claim account-specific relevance.
Proposed wording
Write a concise learner-proposed sentence that invites correction and avoids urgency, guarantee, or false familiarity.
Prohibited or unsupported claim
Name the exact wording, inference, or outcome that cannot be used from supplied evidence.
Reviewer
Use Sales process owner and authorized technical claims reviewer; add privacy reviewer when data or channel questions arise.
Status
Use Learner draft, Claim conflict open, Technical review required, or Not approved for sending.
Supportable message variants · learning draft
Draft IDAudience and purposeSupported factsProposed wordingProhibited or unsupported claimReviewerStatus

Start with 2 rows; the complete workbook specifies 2 stable rows for this artifact. Add rows here or use the full download. No action is saved until you explicitly choose saving above.

Download complete six-module workbook (.md) · Structured case packet (.json)

Keep private client data, unpublished inventions, personal identifiers and credentials out of these public learning tools.

Module 3 · 2-item formative check

Value hypothesis and messaging

Choose an answer and request feedback. Read why each option does or does not fit the evidence. Answers stay in this tab unless you choose device-only saving; they are never submitted.

Question 1 of 2 · MODULE 3 · knowledgeWhich opening uses an observed business signal without converting a hypothesis into a claim?
Question 2 of 2 · MODULE 3 · scenarioHow should ClearBench report the conflict between its forty-percent claim and seventeen-percent internal test?

Answer either question to review its reasoning.

Inspect the artifact, not just your quiz answers

  • The draft uses aggregate evidence only and does not imply a named account or person was verified.
  • The 40-percent promise is prohibited, and the 17-percent internal result remains limited controlled evidence in the claim ledger.
  • The wording invites correction, avoids urgency and guarantee, and remains explicitly not approved for sending.

Stop: Stop drafting or sending when a material claim lacks source, scope, limitation, account relevance, reviewer, or permitted-channel evidence.

Go: Go to bounded editorial review when every claim is sourced, limitations are explicit, correction is invited, and prohibited language is logged.

Escalate: Escalate numeric performance, technical suitability, customer-result, privacy, and outreach-permission claims to authorized reviewers.

04 · Evidence to keep

Leave with usable work.

Account signal, problem hypothesis, claim-to-source matrix, approved message variants, channel requirements, and reviewer notes.

Download your artifact CSV and, if wanted, export the learning-work JSON above. Neither export is a reviewed submission or certificate. Device-only saving is optional; you must press Save my work now after edits.

When all six artifacts are ready, compare the full packet against the track rubric. Qualified human review is still required before real-world decisions.

Sales team discussing account strategy and outreach during an office meeting.
Learn the standard. Practice the work.
Business development professional holding a focused conversation with prospective clients.
Leave with evidence you can inspect.

Sources, scope and review boundaries

Curriculum 2026.10.08-learning-paths-1. External source dates below are record checks, not continuing guarantees. Verify current requirements before consequential use.

ftc-can-spam · Official guidance

FTC: CAN-SPAM Act Compliance Guide for Business

Primary guidance on commercial email identity, subject lines, advertising disclosure, postal address, opt-out, and vendor accountability.

Open reviewed external source ↗

ftc-advertising-faqs · Official guidance

FTC: Advertising FAQs — truth-in-advertising standards

Primary federal business guidance explaining that advertising must be truthful and non-deceptive, objective claims need evidence, and advertisements cannot be unfair.

Open reviewed external source ↗

ws-sales-operating-control · Academy internal operating standard

Wealth Synergy sales-development internal operating standard

Academy-selected evidence, research, message approval, suppression, cadence, handoff, and metric controls. This is an internal operating standard selected by Foundry Academy; it is not law, accreditation, licensure, or an external-standard requirement.

Version 1.0 · reviewed 2026-09-01 · owner: Foundry Academy curriculum owner

A future Wealth Synergy private professional-development certificate would be issued only after its assessment, capstone, identity, reviewer, retention, access, deletion, appeal, and issuance controls pass quality review. No credential is currently issued. Any future certificate would not be an accredited academic qualification, professional license, or government certification.