Foundry Academy · Sales Development · Lesson 1 of 6

Ideal-customer profile and account field

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

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

Ideal-customer profile and account field

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

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.

Before you begin

  • Confirm the four-week, 120-company pilot scope and the three supplied aggregate fit tiers before proposing a cohort.
  • Keep aggregate company counts separate from contact-level exclusions; record identities, account names, trigger dates, and dispositions are not supplied.
  • Treat the eight-discovery-calls-per-week capacity and $6,000 ceiling as boundaries, not evidence that any outreach plan is approved.

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

Item ID
TIER-01
Supported evidence
Seventy-four accounts meet all three fit indicators within a four-week field of 120 companies.
Source input ID
M01-I01 (F01, confirmed); M01-I02 (F02, confirmed)
Criterion or required state
Prioritize the strongest aggregate fit tier while preserving record-level verification and delivery capacity.
Gap or learner proposal
Account identities, individual indicator evidence, trigger dates, approved contacts, suppression results, and selected cohort: not supplied.
Owner or reviewer
Sales process owner and authorized privacy reviewer
Status
Aggregate evidence — record review pending

A well-handled evidence gap

Item ID
GAP-01
Supported evidence
Eighteen accounts lack a traceable trigger; individual records are not supplied.
Source input ID
M01-I02 (F02, confirmed)
Criterion or required state
Require a current, traceable business trigger before record-level inclusion.
Gap or learner proposal
Company identities, attempted source checks, source dates, trigger evidence, and authorized disposition: not supplied.
Owner or reviewer
Sales process owner
Status
Gap open — do not include by assumption

Flawed approach — do not copy

Marking this aggregate fit-tier prioritization table “approved and complete” without the required evidence or reviewer is a flawed submission. Stop cohort selection when account-level fit, trigger, suppression, source-permission, capacity, or budget evidence is missing.

Repair: Rework the aggregate fit-tier prioritization table as an evidence-backed draft, not an approved result. Capture the pilot scope, aggregate fit-tier counts, stale-contact count, opt-out count, capacity, and budget ceiling with their exact module input IDs. Create a separate table row for the three-indicator, two-indicator, and no-traceable-trigger account tiers without inventing company identities. Define the required state for each tier: traceable fit evidence, current trigger, approved contact source, suppression result, and capacity allocation. Check the revision against this requirement: The table preserves the 74, 28, and 18 aggregate tiers without creating company-level determinations. 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 aggregate fit-tier prioritization table.

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.

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.

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

Operating procedure

  1. Capture the pilot scope, aggregate fit-tier counts, stale-contact count, opt-out count, capacity, and budget ceiling with their exact module input IDs.
  2. Create a separate table row for the three-indicator, two-indicator, and no-traceable-trigger account tiers without inventing company identities.
  3. Define the required state for each tier: traceable fit evidence, current trigger, approved contact source, suppression result, and capacity allocation.
  4. Rank the aggregate tiers by evidence strength while leaving record-level inclusion and exclusion decisions pending.
  5. Calculate only a proposed capacity boundary from eight discovery calls per week across four weeks; do not convert it into a forecast or guaranteed cohort result.
  6. Route stale-record, opt-out, unsupported-source, budget, and final cohort decisions to the Sales process owner and authorized privacy reviewer.
  7. Quality-check counts, source IDs, missing-record labels, capacity logic, and status language before any bounded pilot recommendation.
Field-by-field guidance
Item ID
Use a stable aggregate-tier identifier such as TIER-01; do not insert a company or person not supplied.
Supported evidence
Record only the supplied population, tier count, exclusion count, or capacity fact with its limitation.
Source input ID
Cite the exact M01-Ixx input and fact ID supporting the entry.
Criterion or required state
State the observable evidence or control required for prioritization, exclusion, or capacity fit.
Gap or learner proposal
Identify missing record-level evidence or label a selection, review, or capacity method as a learner proposal.
Owner or reviewer
Use Sales process owner and, for contact permission or source issues, authorized privacy reviewer.
Status
Use Aggregate evidence, Learner proposal, Record review pending, Quarantine required, or Approval pending.
Aggregate fit-tier prioritization table · learning draft
Item IDSupported evidenceSource input IDCriterion or required stateGap or learner proposalOwner or reviewerStatus

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

Inspect the artifact, not just your quiz answers

  • The table preserves the 74, 28, and 18 aggregate tiers without creating company-level determinations.
  • The proposed cohort method accounts for exclusions and no more than thirty-two discovery calls across four supplied weeks.
  • Every omitted operational record or result is marked not supplied, and no outreach or approval is implied.

Stop: Stop cohort selection when account-level fit, trigger, suppression, source-permission, capacity, or budget evidence is missing.

Go: Go to bounded record review when aggregate tiers, exclusion controls, capacity boundary, evidence fields, and reviewer roles are defined.

Escalate: Escalate privacy, purchased-data, suppression, budget, and final pilot-volume decisions to authorized owners before outreach.

04 · Evidence to keep

Leave with usable work.

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

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 ↗

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

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.