Foundry Academy · Sales Development · Lesson 6 of 6

Metrics, coaching, and iteration

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

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

Metrics, coaching, and iteration

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

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.

Before you begin

  • Confirm the supplied pilot scope, fit tiers, contact-quality conditions, qualification conflict, capacity, and budget ceiling.
  • No replies, complaints, wrong-contact events, accepted handoffs, revenue, customer outcomes, weekly results, or approved thresholds are supplied.
  • Define metric population, period, source, owner, and action before entering any calculated rate.

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

Term or field
Opt-out rate
Definition
Explicit opt-out events divided by contacts reached during the defined weekly review period; no outreach population or weekly events are supplied.
Allowed values or rule
0–100 percent only when numerator, denominator, deduplication, period, and suppression event records are complete; otherwise Unknown.
Evidence source
M06-I04 (F05, confirmed: eight prior opt-outs are a baseline exclusion, not a pilot rate)
Owner
Sales process owner and authorized privacy reviewer
Change trigger
Learner proposal: any missed suppression is an immediate stop-and-escalate event; approved threshold not supplied.
Status
Definition proposed — operational value not supplied

A well-handled evidence gap

Term or field
Accepted-handoff rate
Definition
Accepted discovery handoffs divided by reviewed handoffs in a stated period under one authorized qualification definition.
Allowed values or rule
Do not calculate while Sales and delivery definitions conflict or while record-level decisions are absent.
Evidence source
M06-I06 (F10, conflicting)
Owner
Sales process owner and delivery specialist lead
Change trigger
Shared definition, complete handoff records, reviewer decisions, period, and action threshold: not supplied.
Status
Gap open — metric blocked

Flawed approach — do not copy

Marking this sales metric dictionary “approved and complete” without the required evidence or reviewer is a flawed submission. Stop decision use when metric population, numerator, denominator, period, source, owner, action, or shared definition is missing.

Repair: Rework the sales metric dictionary as an evidence-backed draft, not an approved result. Capture each supplied baseline or risk condition with its module input ID, confidence, and limitation. Define separate metrics for relevant replies, accepted handoffs, opt-outs, complaints, wrong contacts, downstream outcomes, capacity use, and spend. For every metric, specify population, numerator, denominator, period, source, owner, refresh, and action; mark all operational values not supplied. Check the revision against this requirement: The dictionary includes relevant replies, accepted handoffs, opt-outs, complaints, wrong contacts, and downstream outcomes. 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 sales metric dictionary.

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

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

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.

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

Operating procedure

  1. Capture each supplied baseline or risk condition with its module input ID, confidence, and limitation.
  2. Define separate metrics for relevant replies, accepted handoffs, opt-outs, complaints, wrong contacts, downstream outcomes, capacity use, and spend.
  3. For every metric, specify population, numerator, denominator, period, source, owner, refresh, and action; mark all operational values not supplied.
  4. Preserve the qualification-definition conflict so accepted-handoff counts cannot be interpreted until Sales and delivery align the rule.
  5. Design a weekly review agenda that compares evidence quality, recipient harm signals, specialist capacity, and budget rather than rewarding volume alone.
  6. Predeclare learner-proposed continue, adjust, stop, and escalate conditions without claiming thresholds are approved.
  7. Quality-check metric definitions, source traceability, denominator integrity, decision actions, gaps, and absence of fabricated pilot results.
Field-by-field guidance
Term or field
Name one decision-relevant metric such as opt-out rate, wrong-contact rate, accepted-handoff rate, or downstream outcome.
Definition
State the exact event, population, numerator, denominator, and period; avoid vague activity labels.
Allowed values or rule
Define valid values and learner-proposed handling for unknown, duplicate, conflicting, or pending events.
Evidence source
Cite the exact supplied M06-Ixx input for baseline conditions; operational event records remain not supplied.
Owner
Use Sales process owner, delivery specialist lead, privacy reviewer, or budget owner as appropriate.
Change trigger
State the proposed observation that causes continuation, adjustment, stop, or escalation; do not imply approval.
Status
Use Definition proposed, Baseline supplied, Operational value not supplied, Conflict open, or Approval pending.
Sales metric dictionary · learning draft
Term or fieldDefinitionAllowed values or ruleEvidence sourceOwnerChange triggerStatus

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 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.

Inspect the artifact, not just your quiz answers

  • The dictionary includes relevant replies, accepted handoffs, opt-outs, complaints, wrong contacts, and downstream outcomes.
  • Each metric has population, period, source, owner, and action or an explicit not-supplied gap.
  • Continue, adjust, stop, and escalate logic is proposed before use, with no fabricated pilot result or approval.

Stop: Stop decision use when metric population, numerator, denominator, period, source, owner, action, or shared definition is missing.

Go: Go to bounded weekly review when balanced value, harm, capacity, and budget measures are defined and gaps remain visible.

Escalate: Escalate complaints, suppression failures, qualification conflicts, capacity overload, budget exceptions, and threshold approval to authorized owners.

04 · Evidence to keep

Leave with usable work.

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

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.

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 ↗

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.