Revenue & Customer Operations School · Learning track

Sales Development

Create relevant conversations through disciplined research, outreach, and follow-through.

Start Lesson 1

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 Learning plan

Know the work.
Produce evidence.

Public foundation 2026.10.08-learning-paths-1 · published 2026-10-08. Independent subject-matter review is pending; paid delivery and credential issuance remain closed. This track is organized around inspectable work, not attendance alone.

Workload

No validated completion time is published. Read the six modules, then complete the six case assignments and self-review across as many sessions as needed. This release has not yet been timed with learners; no facilitated capstone is included.

Prerequisites

  • A defined offer and a preliminary ideal-customer hypothesis
  • Access to a fictional or approved prospecting dataset and the organization's channel, consent, and suppression rules
  • Understanding that outreach law varies by channel, location, audience, data source, and context and requires qualified review

Outputs

  • Ideal-customer and exclusion profile
  • Account and contact research standard
  • Evidence-based message framework
  • Approved cadence with consent, stop, and escalation rules
  • Qualification, handoff, and improvement dashboard

Demonstrated outcomes

  • Define and research target accounts
  • Write relevant, honest outreach
  • Run a controlled contact cadence
  • Qualify and hand off conversations cleanly

Working vocabulary

Ideal-customer profile
A testable description of organizations most likely to experience the problem, gain value, buy responsibly, and be served well.
Buying role
A person's contribution to recognizing, evaluating, approving, using, securing, paying for, or blocking a purchase.
Value hypothesis
A supportable proposition about a prospect's situation and possible improvement that must be tested rather than asserted as fact.
Cadence
A controlled sequence of outreach steps with defined audience, channels, timing, ownership, stop rules, and measurement.
Qualification
A mutual determination of problem, relevance, authority, process, timing, constraints, and responsible next step.

02 Public foundation curriculum

Six foundation
learning modules.

Each module states what to understand, what to practice, what evidence to retain, and the criteria for moving forward. The case lab turns those standards into six realistic assignments.

01

Module 1

Ideal-customer profile and account field

Objective: Define a narrow, evidence-based account profile and exclusion rules before collecting contacts or sending outreach.

Open Lesson 1: examples, worksheet & feedback →

An ideal-customer profile is a hypothesis about fit, not a list of industries large enough to meet a quota. Define observable firmographic, operational, situational, and risk characteristics: geography, size, business model, technology or process, trigger event, problem cost, buying complexity, serviceability, and constraints. Include negative-fit conditions such as prohibited sectors, unsuitable budgets, unsupported locations, unacceptable data requirements, or use cases the offer cannot safely deliver. Tie each criterion to customer evidence, delivery economics, or a strategic reason.

Build the account field from approved, traceable sources and collect only what the prospecting purpose requires. Record source, date, confidence, owner, and reason for inclusion. Public availability does not automatically authorize every use, channel, or enrichment method. Respect applicable privacy, marketing, platform, and sector rules and the organization's suppression lists. Do not buy or scrape a large contact file to compensate for an undefined market. Sample the field, test whether the criteria identify real problems and reachable buying processes, then revise before scaling research or automation.

Practice

Create a twenty-account fictional field from documented criteria, including five explicit exclusions and a reason for every inclusion.

Evidence to keep

Ideal-customer profile, exclusion rules, source register, scored account field, sampling notes, and approval for permitted use.

Ready to move on when

  • Every inclusion and exclusion criterion connects to evidence, economics, serviceability, or risk
  • Every account has a traceable source, date, reason for fit, and confidence level
  • Collection and proposed use follow approved privacy, marketing, and platform rules

Module provenance

External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.

02

Module 2

Contact research and buying roles

Objective: Identify relevant roles and usable contact context without collecting unnecessary personal data or pretending to know the buying process.

Open Lesson 2: examples, worksheet & feedback →

Map the likely buying system before selecting a name. Relevant roles may include the person experiencing the problem, operational owner, technical or security reviewer, finance, procurement, executive sponsor, and final authority. The same person may hold several roles in a small company. State why a role is relevant and what question that person can answer. Do not assume a senior title is automatically the best first contact, and do not present an inferred role as confirmed.

Use approved sources and record provenance, date, business relevance, and permitted channel. Minimize personal data: a business role, work contact, source, and relevant account signal may be sufficient. Do not collect sensitive personal details, personal phone numbers, family information, private social content, or unrelated facts for decorative personalization. Maintain do-not-contact, opt-out, complaint, and correction processes. Verify unusual or high-impact details before use. If outreach includes automated calls, texts, recordings, commercial email, or jurisdictions with additional rules, obtain qualified legal guidance and configure the actual workflow accordingly.

Practice

Map six buying roles for two fictional accounts and prepare a minimal contact-research record that excludes irrelevant personal detail.

Evidence to keep

Buying-role map, contact-source log, relevance statement, confidence marker, permitted-channel field, and suppression check.

Ready to move on when

  • Each selected contact has a relevant business role and a stated reason for outreach
  • Inferred roles and facts are labeled and verified before material use
  • Research excludes sensitive, personal, unrelated, or unapproved data

Module provenance

Mapped sections or criteria: 47 CFR 64.1200; legal status checked against the FCC-hosted vacatur record

External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.

03

Module 3

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.

Open Lesson 3: examples, worksheet & feedback →

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.

Practice

Write three message variants for one fictional account: an evidence-led email, a concise call opener, and a referral-safe follow-up, each with claim support.

Evidence to keep

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

Ready to move on when

  • The message distinguishes observed facts from the problem hypothesis and invites correction
  • Every material claim has current, relevant support and no invented familiarity or outcome
  • Sender identity, subject, commercial purpose, valid physical postal address, and opt-out handling meet the approved channel and jurisdiction standard.

Module provenance

External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.

04

Module 4

Ethical multi-channel cadence

Objective: Design a proportionate sequence that respects recipient choice, channel rules, timing, and human accountability.

Open Lesson 4: examples, worksheet & feedback →

Define the cadence objective, approved audience, lawful and organizational basis, channels, sender, timing, frequency, content purpose, and maximum attempts before launch. Each step should add relevant information rather than repeat pressure. Coordinate email, phone, professional networks, mail, events, or referrals so a recipient is not contacted by several people without context. Apply time zones, business hours, account ownership, suppression, and current-customer rules. Test the actual system with internal records before activating prospects.

Stop or reroute the cadence after reply, opt-out, complaint, wrong person, legal restriction, closed account, active opportunity, or other defined event. CAN-SPAM applies to commercial email, including business-to-business email; calls and texts may implicate federal and state requirements that depend on technology, consent, number type, content, and context. This course cannot determine the legality of a specific campaign. Obtain qualified review and document the approved rules. Monitor delivery, replies, negative responses, opt-outs, complaints, and suppression failures—not only meetings. A high meeting count does not justify deception or ignored recipient choice.

Practice

Build a fourteen-day fictional cadence with six touches, then test reply, opt-out, complaint, wrong-contact, and active-opportunity stop scenarios.

Evidence to keep

Cadence brief, channel approval, suppression rules, test record, owner map, stop-event log, and monitoring thresholds.

Ready to move on when

  • Audience, channel, frequency, timing, sender, content purpose, and maximum attempts are approved
  • All defined stop and reroute events work in testing without further outreach
  • Monitoring includes opt-outs, complaints, suppression failures, and negative responses

Module provenance

Mapped sections or criteria: 47 CFR 64.1200; legal status checked against the FCC-hosted vacatur record

External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.

05

Module 5

Qualification and discovery handoff

Objective: Determine mutual fit through respectful discovery and transfer accurate context, commitments, and risks to the next owner.

Open Lesson 5: examples, worksheet & feedback →

Qualification should protect both sides from a poor-fit process. Confirm the problem and consequence in the prospect's words, current approach, priority, decision participants, evaluation process, timing, constraints, security or procurement needs, and agreed next step. Budget may matter, but demanding a number before value and scope are understood can produce weak information. Do not coach a prospect to invent urgency or authority. A disqualification, referral, or no-decision can be the responsible result.

The handoff record should state verified facts, open questions, stakeholders, objections, promised materials, consent or channel preferences, next meeting, owner, and due dates. Separate prospect statements from seller interpretation. Never alter the record to make the opportunity appear more qualified. Do not include sensitive personal information, credentials, payment details, or confidential files in ordinary notes. If the next step involves regulated advice, technical claims, contracts, security review, credit, investment, or funding, bring in authorized specialists and state the boundary. Confirm the handoff with the prospect when doing so reduces confusion.

Practice

Run a ten-minute fictional discovery call and produce a handoff that another team member can continue without asking the prospect to repeat the conversation.

Evidence to keep

Discovery guide, consent-aware notes, qualification record, fact-versus-inference labels, handoff summary, commitments, and next-step confirmation.

Ready to move on when

  • Qualification covers problem, relevance, participants, process, timing, constraints, and mutual next step
  • The handoff clearly separates prospect facts, seller interpretation, and unanswered questions
  • Promises, specialist boundaries, preferences, owner, and due dates are preserved

Module provenance

External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.

06

Module 6

Metrics, coaching, and iteration

Objective: Improve sales development through cohort-aware measures, quality review, and controlled experiments rather than activity pressure.

Open Lesson 6: examples, worksheet & feedback →

Define the funnel from eligible researched account through delivered contact, meaningful reply, accepted conversation, qualified handoff, and downstream outcome. Use both counts and rates, with the population, time period, source, exclusions, and owner documented. Segment by profile, source, message, channel, role, and cohort where sample size supports interpretation. Delivery or opens are not proof of interest, and meetings are not revenue. Track negative replies, opt-outs, complaints, wrong contacts, and disqualification so apparent productivity does not hide poor targeting or conduct.

Coach from representative evidence: research records, messages, call notes or approved recordings, discovery handoffs, and outcomes. Follow applicable consent and employment policies for recording and monitoring. Diagnose whether the constraint is field quality, contact relevance, message truth, channel, cadence, skill, offer, capacity, or handoff. Change one material variable where practical and define the test period and stop rule before launch. Do not rank people using incomplete or incomparable data. Combine metrics with human review, context, and ethical standards, and document what changed, why, result, and whether the control becomes standard.

Practice

Analyze a fictional four-week funnel, identify one evidence-backed constraint, and design a controlled two-week improvement test with a stop rule.

Evidence to keep

Metric dictionary, segmented funnel, quality sample, coaching note, experiment brief, stop criteria, and change decision.

Ready to move on when

  • Counts, rates, populations, exclusions, time periods, and sources are documented
  • Quality and recipient-impact measures sit beside productivity measures
  • The improvement test changes a defined variable and includes review date and stop rule

Module provenance

External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.

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.

Free operational lesson

Write from a useful hypothesis

Lead with a plausible business problem, show why the account may experience it, offer a relevant next step, and make it easy to decline. Personalization is evidence of relevance—not decorative trivia.

01

Define fit before volume

Use customer evidence, delivery reality, exclusions, and risk to define the account field before collecting contacts.

02

Research for relevance

Collect only approved business context that explains why a role may care; avoid unrelated personal-detail personalization.

03

Message as a hypothesis

State what is observed, what may be happening, what can be supported, and invite correction without pressure.

04

Respect the stop

Make replies, opt-outs, complaints, wrong contacts, and active opportunities stop or reroute every automated channel.

05

Improve with complete measures

Evaluate relevant replies, qualified handoffs, downstream value, negative impact, and control failures—not activity totals alone.

Unscored self-reflection

Select each module standard that is already consistently true. This is a private reflection—not a test, grade, credential assessment, or claim of competence.

Your choices stay in this browser and are not submitted. Device-only saving is optional in the learning-work panel.

Worked example

Replacing decorative personalization with relevance

A coordinator finds that a target manufacturer opened a second facility and wants to offer supplier and operations support.

Weak approach

Congratulations on your exciting growth! I saw your CEO enjoys hiking. We help companies like yours cut costs by 40 percent. Can you meet tomorrow?

Stronger approach

Your public expansion notice says the new facility is expected to add two production lines this year. Teams in that transition sometimes need to qualify suppliers and make landed-cost assumptions visible before volume commitments. Wealth Synergy coordinates sourcing and operating specialists for that work. Is supplier qualification part of this expansion, or is another priority more relevant? I can send a one-page process overview. If this is not useful, tell me and I will close the outreach.

Why it matters: The improved message uses a relevant business signal, labels the problem as a hypothesis, avoids unsupported savings, and offers an easy correction or stop.

03 Control the work

Spot failure.
Measure the system.

Common failure modes

Buying scale before proving fit

A large list amplifies weak targeting, unverified data, legal exposure, and recipient harm. Validate a narrow field first.

Using personal trivia as personalization

Unrelated details can feel invasive and add no business value. Research the account, role, trigger, and plausible problem instead.

Counting sends as progress

Activity volume does not show relevance, truth, recipient impact, qualification quality, or downstream business value.

Ignoring negative signals

Opt-outs, complaints, wrong contacts, and negative replies are operational and ethical evidence that must change the system.

Operating measures

Eligible-account precision

Percentage of reviewed accounts that meet the approved ideal-customer and exclusion criteria with traceable evidence.

Use it to decide: Low precision pauses list expansion and directs work to profile or research correction.

Meaningful-reply rate

Relevant replies that confirm, correct, refer, decline, or advance the hypothesis divided by delivered contacts.

Use it to decide: Use with negative and opt-out measures to judge field and message relevance.

Qualified-handoff acceptance

Percentage of handoffs accepted by the next owner without missing required facts, commitments, or fit criteria.

Use it to decide: Low acceptance triggers discovery, documentation, or definition coaching rather than more outreach.

Recipient-impact exception rate

Opt-outs, complaints, wrong contacts, suppression failures, and policy breaches per delivered contact.

Use it to decide: Threshold breaches pause the affected cadence and require root-cause review before resumption.

04 · Applied case lab · 2026.08.31-practice-3

Practice on a
messy record.

The packet contains contradiction and incomplete evidence on purpose. Each assignment now identifies the exact fictional inputs available to the learner. Complete a bounded starter, mark missing records instead of inventing them, and compare your reasoning with the debrief—not with a pretend single perfect answer.

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.

CB01 · citable versioned case brief

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.

F01 · confirmedThe pilot covers 120 companies in Utah and neighboring states over four weeks.
F02 · confirmedSeventy-four accounts meet three fit indicators, twenty-eight meet two, and eighteen lack a traceable trigger.
F03 · confirmedThe field contains 162 contacts across five role groupings.
F04 · confirmedTwelve contacts have left their listed employer.
F05 · confirmedEight contacts have explicit prior opt-outs.
F06 · confirmedNineteen personal mobile numbers came from an unapproved vendor.
F07 · conflictingThe draft promises forty-percent time savings while the only internal test measured seventeen percent.
F08 · confirmedThe proposed fourteen-day cadence includes six emails, four calls, and two texts.
F09 · confirmedThe cadence has no documented channel review, weekend rule, reply handling, or referral stop condition.
F10 · conflictingSales and delivery teams use different definitions of a qualified meeting.
F11 · confirmedDelivery capacity is eight discovery calls per week with two technical specialists.
F12 · confirmedThe approved pilot budget ceiling is $6,000.

The internal demonstration indicates some improvement but does not support the forty-percent customer claim.

Judgment required: Decide whether to omit a number, qualify the limited evidence, or run a stronger test before outreach.

Do not assume: Do not extrapolate one controlled demonstration to customer savings or guaranteed results.

A calendar acceptance may indicate interest but may not establish problem, authority, or a useful technical handoff.

Judgment required: Set a threshold that protects specialist capacity while permitting early discovery when uncertainty is explicit.

Do not assume: Do not select the definition solely because it raises the meeting or qualification rate.

Six module assignments and debriefs

Module 1 · Prioritize the account field

Bounded case starter

Apply fit, trigger, exclusion, capacity, and evidence rules to select a bounded pilot cohort.

Deliverable: An aggregate fit-tier prioritization table from F01 and F02 plus a blank record-level account-selection log for later verified inputs.

Completion boundary: Complete a bounded starter and gap analysis using only CB01, F01, F02, F04, F05, F06, F11, F12, 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.

Workbook plan: 2 authored artifacts with 4 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.

Review the module lesson →

Provided inputs

  • M01-I01 · case-fact · F01
    The pilot covers 120 companies in Utah and neighboring states over four weeks.
  • M01-I02 · case-fact · F02
    Seventy-four accounts meet three fit indicators, twenty-eight meet two, and eighteen lack a traceable trigger.
  • M01-I03 · case-fact · F04
    Twelve contacts have left their listed employer.
  • M01-I04 · case-fact · F05
    Eight contacts have explicit prior opt-outs.
  • M01-I05 · case-fact · F06
    Nineteen personal mobile numbers came from an unapproved vendor.
  • M01-I06 · case-fact · F11
    Delivery capacity is eight discovery calls per week with two technical specialists.
  • M01-I07 · case-fact · F12
    The approved pilot budget ceiling is $6,000.
  • M01-B01 · case-brief · 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.
  • M01-S01 · assignment-scope · F01, F02, F04, F05, F06, F11, F12
    Build a starter version of “An aggregate fit-tier prioritization table from F01 and F02 plus a blank record-level account-selection log for later verified inputs.” 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.

Evidence criteria

  • M01-EC01: Explains why each aggregate tier fits, fails, or lacks the defined profile evidence
  • M01-EC02: Shows how stale, opted-out, and unsupported records would be excluded or quarantined without claiming individual account review
  • M01-EC03: Keeps proposed outreach volume within the supplied discovery and delivery capacity
  • M01-EC04: Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

Debrief lens: A smaller evidence-backed cohort is more useful than a larger arbitrary list. Ranking should be reproducible and preserve uncertainty rather than convert missing triggers into fit.

  • Traceable fit and exclusion rules
  • Capacity-aware cohort count
Module 2 · Map buying roles

Bounded case starter

Research relevant roles using current business sources without collecting unnecessary personal data.

Deliverable: A five-group buying-role hypothesis map and blank contact-verification log; no individual identity or role is treated as verified.

Completion boundary: Complete a bounded starter and gap analysis using only CB01, F03, F04, F05, F06, 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.

Workbook plan: 2 authored artifacts with 7 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.

Review the module lesson →

Provided inputs

  • M02-I01 · case-fact · F03
    The field contains 162 contacts across five role groupings.
  • M02-I02 · case-fact · F04
    Twelve contacts have left their listed employer.
  • M02-I03 · case-fact · F05
    Eight contacts have explicit prior opt-outs.
  • M02-I04 · case-fact · F06
    Nineteen personal mobile numbers came from an unapproved vendor.
  • M02-B01 · case-brief · 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.
  • M02-S01 · assignment-scope · F03, F04, F05, F06
    Build a starter version of “A five-group buying-role hypothesis map and blank contact-verification log; no individual identity or role is treated as verified.” 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.

Evidence criteria

  • M02-EC01: Distinguishes user, evaluator, approver, procurement, and blocker as hypotheses rather than verified people
  • M02-EC02: Includes fields for source date and confidence while marking individual source records not supplied
  • M02-EC03: Rejects unapproved personal mobile data and preserves prior opt-outs in the proposed verification process

Debrief lens: Buying roles are hypotheses until verified. Research should use business-relevant sources and minimize personal data, particularly when prior choice or source approval is missing.

  • Dated role sources
  • Suppression and source-approval record
Module 3 · Write a supportable message

Bounded case starter

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

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

Completion boundary: 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.

Workbook plan: 3 authored artifacts with 5 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.

Review the module lesson →

Provided inputs

  • M03-I01 · case-fact · F02
    Seventy-four accounts meet three fit indicators, twenty-eight meet two, and eighteen lack a traceable trigger.
  • M03-I02 · case-fact · F07
    The draft promises forty-percent time savings while the only internal test measured seventeen percent.
  • M03-B01 · case-brief · 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 · assignment-scope · 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.

Evidence criteria

  • M03-EC01: Uses only approved business signals and source-backed statements
  • M03-EC02: Labels the seventeen-percent demonstration as limited internal evidence
  • M03-EC03: Invites correction and avoids urgency, guarantee, or false familiarity
  • M03-EC04: Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

Debrief lens: The message can discuss a limited demonstration if its scope is clear, but it cannot promise a larger outcome. Relevance and an easy correction path are stronger than exaggerated certainty.

  • Claim-to-source ledger
  • Approved wording with limitations
Module 4 · Control the cadence

Bounded case starter

Design a multi-channel sequence with channel approval, suppression, stop rules, and exception monitoring.

Deliverable: A fourteen-day cadence map and negative-path test checklist.

Completion boundary: Complete a bounded starter and gap analysis using only CB01, F05, F06, F08, F09, 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.

Workbook plan: 2 authored artifacts with 16 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.

Review the module lesson →

Provided inputs

  • M04-I01 · case-fact · F05
    Eight contacts have explicit prior opt-outs.
  • M04-I02 · case-fact · F06
    Nineteen personal mobile numbers came from an unapproved vendor.
  • M04-I03 · case-fact · F08
    The proposed fourteen-day cadence includes six emails, four calls, and two texts.
  • M04-I04 · case-fact · F09
    The cadence has no documented channel review, weekend rule, reply handling, or referral stop condition.
  • M04-B01 · case-brief · 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.
  • M04-S01 · assignment-scope · F05, F06, F08, F09
    Build a starter version of “A fourteen-day cadence map and negative-path test checklist.” 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.

Evidence criteria

  • M04-EC01: Stops on opt-out, reply, referral, disqualification, and accepted handoff
  • M04-EC02: Defines permitted channels, timing, owner, and escalation
  • M04-EC03: Tests suppression and wrong-contact handling before activation
  • M04-EC04: Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

Debrief lens: Cadence intensity should be bounded by policy, channel rules, recipient response, and monitoring. More touches are not automatically better and can increase risk and complaints.

  • State-based stop logic
  • Negative-path test results
Module 5 · Define the handoff

Bounded case starter

Resolve the meeting-versus-evidence disagreement and design a two-way sales-to-specialist handoff.

Deliverable: A qualification rubric, handoff record, and acceptance or rejection workflow.

Completion boundary: Complete a bounded starter and gap analysis using only CB01, F10, F11, 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.

Workbook plan: 3 authored artifacts with 6 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.

Review the module lesson →

Provided inputs

  • M05-I01 · case-fact · F10
    Sales and delivery teams use different definitions of a qualified meeting.
  • M05-I02 · case-fact · F11
    Delivery capacity is eight discovery calls per week with two technical specialists.
  • M05-B01 · case-brief · 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.
  • M05-S01 · assignment-scope · F10, F11
    Build a starter version of “A qualification rubric, handoff record, and acceptance or rejection workflow.” 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.

Evidence criteria

  • M05-EC01: Separates fit, problem, process, stakeholder, timing, and next-step evidence
  • M05-EC02: Lets specialists reject incomplete handoffs with a reason code
  • M05-EC03: Avoids promising technical feasibility or approval before specialist review
  • M05-EC04: Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

Debrief lens: A useful handoff captures verified context and unresolved questions. Different thresholds may work, but the design must protect specialist capacity and never imply unearned technical approval.

  • Observable qualification rubric
  • Acceptance and rejection feedback loop
Module 6 · Measure learning and harm

Bounded case starter

Build a scorecard that supports pilot decisions without rewarding uncontrolled volume.

Deliverable: A metric dictionary, weekly review agenda, and stop-or-adjust thresholds.

Completion boundary: Complete a bounded starter and gap analysis using only CB01, F01, F02, F04, F05, F06, F10, F11, F12, 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.

Workbook plan: 3 authored artifacts with 6 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.

Review the module lesson →

Provided inputs

  • M06-I01 · case-fact · F01
    The pilot covers 120 companies in Utah and neighboring states over four weeks.
  • M06-I02 · case-fact · F02
    Seventy-four accounts meet three fit indicators, twenty-eight meet two, and eighteen lack a traceable trigger.
  • M06-I03 · case-fact · F04
    Twelve contacts have left their listed employer.
  • M06-I04 · case-fact · F05
    Eight contacts have explicit prior opt-outs.
  • M06-I05 · case-fact · F06
    Nineteen personal mobile numbers came from an unapproved vendor.
  • M06-I06 · case-fact · F10
    Sales and delivery teams use different definitions of a qualified meeting.
  • M06-I07 · case-fact · F11
    Delivery capacity is eight discovery calls per week with two technical specialists.
  • M06-I08 · case-fact · F12
    The approved pilot budget ceiling is $6,000.
  • M06-B01 · case-brief · 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.
  • M06-S01 · assignment-scope · F01, F02, F04, F05, F06, F10, F11, F12
    Build a starter version of “A metric dictionary, weekly review agenda, and stop-or-adjust thresholds.” 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.

Evidence criteria

  • M06-EC01: Includes relevant replies, accepted handoffs, opt-outs, complaints, wrong contacts, and downstream outcomes
  • M06-EC02: Defines population, period, source, owner, and action for each metric
  • M06-EC03: Predeclares conditions for continuing, revising, or stopping the pilot
  • M06-EC04: Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

Debrief lens: Metrics should show value and recipient impact. High activity with poor fit, complaints, or rejected handoffs is evidence to change the system, not celebrate effort.

  • Balanced metric definitions
  • Predeclared action thresholds

Self-review standard

Inspect evidence, reasoning, completeness, boundaries, and traceability.

There is no single universal cadence or qualification threshold. Strong work aligns evidence, recipient respect, law and policy review, capacity, and learning goals. The downloadable rubric is formative guidance only—not a grade, verified completion, credential assessment, or professional approval.

Channel consent, telephone or text outreach, suppression, privacy, purchased data, or jurisdiction-specific marketing rules

Route to: Qualified legal or privacy reviewer and the organization's compliance owner

Learner boundary: The learner designs operational controls but does not determine legal permission from this case.

Technical performance, product suitability, safety, or customer-specific savings claims

Route to: Authorized technical specialist and claims reviewer

Learner boundary: Sales-development material cannot guarantee or approve technical outcomes.

05 Editable working tool

Use the template.
Inspect the example.

Use one row per account. Tie the signal to an official or approved source, state the possible problem as a hypothesis, use only supportable proof, and choose a respectful next step with an easy decline. Add as many rows as needed, export a CSV, or print only this tool. Entries are not transmitted. They last only in this tab unless you opt into device-only saving in the learning-work panel. No account or cross-device sync is provided.

Editable Sales Development public-foundation worksheet
Account signalProblem hypothesisRelevant proofMessage angleNext step

Completed example

Account signal
Official company announcement of a second manufacturing facility and two planned production lines.
Problem hypothesis
Supplier qualification, landed-cost comparison, and launch coordination may be harder during simultaneous expansion.
Relevant proof
Wealth Synergy's published Inventor Forge Source process; no savings or outcome claim without client-approved evidence.
Message angle
Ask whether supplier qualification is part of the expansion and offer a one-page process overview.
Next step
Send the overview only if requested; stop outreach after decline or opt-out.

Data boundary: Work only in an approved system. Do not place passwords, payment-card data, government identifiers, health information, export-controlled material, client secrets, or unpublished invention details in this public worksheet.

Practice one module.
Get useful feedback now.

Each two-question check works independently. Review any answered question immediately; you do not need to finish all twelve. Feedback is formative, not a verified grade or credential.

Module 1 · 2-item formative check

Ideal-customer profile and account field

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 1 · knowledgeWhat makes an account appropriate for inclusion in a governed outbound field?
Question 2 of 2 · MODULE 1 · scenarioWhich packet lets ClearBench's owner decide whether the aggregate account field is ready for a bounded pilot?

Answer either question to review its reasoning.

Module 2 · 2-item formative check

Contact research and buying roles

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 2 · knowledgeWhat is the most responsible way to identify a likely buying role before outreach?
Question 2 of 2 · MODULE 2 · scenarioWhich test would most improve ClearBench's buying-role map without inventing record-level evidence?

Answer either question to review its reasoning.

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.

Module 4 · 2-item formative check

Ethical multi-channel cadence

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 4 · knowledgeWhat should a recipient's opt-out trigger across an approved outreach workflow?
Question 2 of 2 · MODULE 4 · scenarioWhich control turns ClearBench's missing cadence rules into an observable stop-or-rework signal?

Answer either question to review its reasoning.

Module 5 · 2-item formative check

Qualification and discovery handoff

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 5 · knowledgeWhich information belongs in a reliable qualification and discovery handoff?
Question 2 of 2 · MODULE 5 · scenarioWhat may ClearBench conclude from its confirmed discovery capacity and conflicting qualification definitions?

Answer either question to review its reasoning.

Module 6 · 2-item formative check

Metrics, coaching, and iteration

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 6 · knowledgeWhich metric set best supports ethical improvement of a sales-development pilot?
Question 2 of 2 · MODULE 6 · scenarioWhich sequence should ClearBench follow before deciding whether to continue, revise, or stop its pilot?

Answer either question to review its reasoning.

07 Sources and handoffs

Verify the standard.
Know when to escalate.

Module provenance distinguishes external authorities, legal-status evidence, and Wealth Synergy internal operating standards. Requirements change; verify current source text and obtain qualified advice when a decision carries legal, financial, technical, employment, safety, or regulatory consequences.

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 ↗

nist-privacy-framework · Official guidance

NIST Privacy Framework

Primary voluntary framework for governing privacy risk in data collection, use, communication, and protection.

Open reviewed external source ↗

fcc-47-cfr-64-1200 · Current codified text

eCFR :: 47 CFR 64.1200 -- Delivery restrictions.

Current codified FCC delivery restrictions. eCFR is authoritative but unofficial. Technology, consent, number type, content, context, state, and jurisdiction affect the applicable rule; obtain qualified legal review before configuring outreach.

Open reviewed external source ↗

fcc-one-to-one-consent-vacatur · Context only—not a positive rule

Insurance Marketing Coalition Limited v. Federal Communications Commission, No. 24-10277

FCC-hosted Eleventh Circuit opinion documenting vacatur of Part III.D of the 2023 order. Legal-status evidence only; it is not a positive instructional rule.

Open reviewed external source ↗

fcc-one-to-one-consent-status-2025 · Context only—not a positive rule

Opposition to Motion to Intervene — Insurance Marketing Coalition Ltd. v. FCC, No. 24-10277

FCC/DOJ filing confirming that the one-to-one-consent rule was vacated and the government did not seek further review. Legal-status evidence only.

Open reviewed external source ↗

sba-plan-your-business · Official guidance

Plan your business

Current SBA consolidated guidance containing the market-research section used for account-field hypotheses.

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

Future facilitated pathway · not open

Practice with feedback.
Finish with evidence.

The public case lab is available now. A future facilitated cohort may add assignments, feedback, and human capstone review only after a named qualified facilitator and reviewer, schedule, rubric, privacy controls, support, price, refund terms, and delivery terms are published in writing. No enrollment or payment is accepted here.

Clear boundaries.

Course material supports professional development. It does not replace legal, tax, accounting, cybersecurity, engineering, regulatory, employment, translation, or other qualified professional advice where that expertise is required.

The public knowledge check and portal review markers are learning aids only. They do not award a credential. Pilot curriculum and credential assessment are in quality review; Foundry Academy is not currently representing these pages as accredited instruction or an automatic path to a certificate.

Participation does not guarantee employment, client work, funding, licensure, certification by a public authority, or any business outcome.

Use the public foundation

Read. Practice.
Inspect your evidence.

All public materials and case files are available without enrollment. A fit conversation is non-binding and does not reserve a place in a future pilot.

Ask about this track