Revenue & Customer Operations School · Learning track
Make customer data usable, governable, and visible to the people doing the work.
Start Lesson 1No 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.
A different tab changed this track. Nothing was overwritten. Export your current draft first if needed, then load the saved version before editing and saving again.
01 Learning plan
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
Outputs
Working vocabulary
02 Public foundation curriculum
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.
Module 1
Objective: Map the CRM's purpose, core records, lifecycle, ownership, and system boundaries before adding fields or automation.
Open Lesson 1: examples, worksheet & feedback →A CRM should represent how the organization serves customers, not force every interaction into one sales funnel. Define the business purposes it supports, such as inquiry response, qualified opportunity management, onboarding, service, renewal, and reporting. Identify core records—people, organizations, opportunities, activities, cases, products, or contracts—and the relationships between them. For each important data element, name its system of record. Avoid copying billing, identity, health, payment, or other sensitive data into the CRM merely for convenience.
Map lifecycle states separately from opportunity stages. A person can be a customer while a new opportunity is still exploratory; an organization can have several opportunities. Write entry, exit, owner, allowed transitions, and exceptional paths for each state. Include consent, do-not-contact, inactive, duplicate, disqualified, and former-customer handling where relevant. The map must reflect actual responsibility across marketing, sales, delivery, support, finance, and privacy or security roles. Before implementation, review contracts, sector rules, privacy notices, and applicable law with qualified personnel. Operational training does not decide the legal basis for processing personal data.
Practice
Map a fictional lead-to-customer-to-renewal journey, including three exception paths and the authoritative system for every critical field.
Evidence to keep
Record model, lifecycle map, transition rules, system-of-record matrix, data-boundary list, and cross-functional approval.
Ready to move on when
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.
Module 2
Objective: Create a minimal, governed data dictionary that makes required fields useful, interpretable, and maintainable.
Open Lesson 2: examples, worksheet & feedback →A field earns a place in the CRM by supporting a defined action, handoff, control, or metric. Document label, internal name, definition, type, allowed values, source, owner, creation rule, update trigger, required stage, sensitivity, retention, and reporting use. Prefer controlled values where consistent comparison matters, but preserve an explanation field when judgment is needed. Do not make a field required at record creation if the information is not known then; require it at the point where the process genuinely needs it.
Apply data minimization and quality controls together. Collect only what the organization has a valid purpose and approved process to use. Establish formats for names, organizations, phones, locations, dates, currencies, industries, sources, and opt-out status. Define duplicate matching, merge authority, unknown values, stale-data rules, and correction procedures. Never overwrite a person's preference or consent record because a campaign wants a larger audience. Periodically sample completeness, validity, uniqueness, consistency, timeliness, and provenance. Privacy, retention, and legal requirements differ by jurisdiction and context; obtain qualified review before collecting or repurposing personal data.
Practice
Build a twenty-field data dictionary and use it to audit fifty fictional records, documenting every correction and unresolved exception.
Evidence to keep
Approved dictionary, purpose and sensitivity map, sample audit, duplicate queue, correction log, and field retirement list.
Ready to move on when
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.
Module 3
Objective: Operate timely follow-up without concealing automation, overriding recipient preferences, or creating unowned task noise.
Open Lesson 3: examples, worksheet & feedback →A task should name the desired outcome, due time, owner, relevant context, and completion evidence. Define which events create a task, when ownership transfers, how overdue work escalates, and which outcomes close or reschedule it. Sequences can support consistent reminders, but every step needs an approved purpose, audience, channel, timing, sender identity, stop condition, and exception path. Test automation in a sandbox and prevent duplicate tasks when records re-enter a stage.
Respect consent, opt-out, do-not-call, frequency, time-zone, and channel rules that apply to the organization. Commercial email is subject to CAN-SPAM requirements, and calls or texts may be subject to federal and state requirements; obtain qualified legal review for the actual outreach program. Stop automated outreach when a recipient replies, opts out, becomes a customer under a different workflow, or raises a complaint. Human owners remain accountable for accuracy and tone. Measure useful outcomes such as time to first response and next-step completion, not activity volume alone. Retain enough history to explain actions without keeping unnecessary personal information indefinitely.
Practice
Design a six-step fictional follow-up sequence with consent basis, stop rules, owner handoffs, exception cases, and a sandbox test plan.
Evidence to keep
Sequence brief, task-trigger map, approval record, test cases, suppression rules, opt-out handling, and monitoring dashboard.
Ready to move on when
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.
Module 4
Objective: Define opportunity stages by buyer evidence and required next decisions so forecasts do not rest on seller optimism.
Open Lesson 4: examples, worksheet & feedback →A pipeline stage describes the state of a specific buying process, not how busy the seller feels. Define entry evidence, required fields, owner, buyer commitment, next action, expected duration, and exit choices for each stage. Examples may include accepted discovery, verified problem and authority, solution fit, commercial review, decision, and closed outcome, but the model must fit the business. Do not advance an opportunity because a proposal was sent if the buyer has not agreed to evaluate it.
Require close date, amount, probability, and forecast category to have documented definitions and update triggers. Record lost, no-decision, disqualified, duplicate, and delayed outcomes honestly; do not leave dead opportunities open to protect the dashboard. Set aging thresholds based on observed cycle behavior, then review exceptions. Pipeline information can include confidential commercial and personal data, so access should reflect role and business need. Forecasts are management estimates, not guarantees. Contract probability, revenue recognition, credit, and regulated sales decisions require appropriate authorized or professional review.
Practice
Write entry and exit criteria for six stages and reclassify twenty fictional opportunities using only the evidence in their activity history.
Evidence to keep
Stage dictionary, decision tree, reclassification log, stale-opportunity queue, exception approvals, and forecast-definition sheet.
Ready to move on when
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.
Module 5
Objective: Build decision-focused reporting with governed definitions, traceable sources, and visible data-quality limitations.
Open Lesson 5: examples, worksheet & feedback →Start with the decision and audience. A sales manager may need response backlog, stage movement, aging, next-step coverage, forecast change, and loss reasons; an executive may need a smaller view of demand, conversion, cycle time, concentration, capacity, and risk. For each metric, document numerator, denominator, population, date logic, filters, currency, source, owner, refresh cadence, and action threshold. Use counts with rates so a small denominator does not create a misleading trend.
Exception reporting often creates more value than decorative totals. Show records missing a next step, opportunities past aging thresholds, lifecycle conflicts, ownerless records, failed automations, consent problems, duplicates, and unusual forecast changes. Allow users to reach the controlled records behind a metric according to permission. Display the refresh time and known limitations. Reconcile important dashboard totals to source reports and sample records after changes. Do not publish individual performance rankings from unreliable data or use CRM measures for employment decisions without governance, context, and appropriate human review.
Practice
Build a paper or sandbox dashboard with six defined metrics and four actionable exception queues for a fictional revenue team.
Evidence to keep
Dashboard wireframe, metric dictionary, source reconciliation, exception definitions, access map, and management action notes.
Ready to move on when
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.
Module 6
Objective: Reduce CRM security and integrity risk through least privilege, controlled bulk changes, tested automation, and recoverable releases.
Open Lesson 6: examples, worksheet & feedback →Map roles to the minimum records, fields, exports, administration, and integration privileges required. Separate ordinary use from configuration, bulk export, deletion, permission, and integration administration. Review service accounts, API connections, shared credentials, inactive users, contractors, and departed staff on a defined cadence. Require multi-factor authentication where supported and follow the organization's identity standard. Access decisions should reflect sensitivity and business purpose, not seniority alone.
Treat imports, merges, mass updates, automation, and schema changes as releases. Define owner, scope, source, field mapping, validation, duplicate logic, consent handling, test sample, backup or export, rollback, approval, and post-change reconciliation. Never import a purchased or scraped contact list merely because the file is available. Scan source files for unnecessary sensitive data and protect them before and after use. Keep a change log that explains who changed what, why, when, test result, approval, and rollback status. Security, privacy, records, and marketing-law questions require qualified review for the actual organization.
Practice
Plan and test a fictional 500-record import containing duplicates, invalid values, opt-outs, and unnecessary sensitive columns without touching production.
Evidence to keep
Role-permission matrix, access review, import plan, mapping, test results, rollback record, post-import reconciliation, and change log.
Ready to move on when
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.
Free operational lesson
Every important field needs a purpose, owner, allowed values, source, update trigger, and reporting use. A smaller governed data model beats a large field list nobody trusts.
Define the decision, service, handoff, or control the CRM must support before adding fields, stages, or automation.
Give every important field, stage, metric, and status a written definition, owner, source, and update trigger.
Collect only approved data, restrict access by business need, and keep sensitive records in their proper controlled systems.
Specify what happens with duplicates, unknown values, opt-outs, stale opportunities, failed automations, and unauthorized changes.
Use a sandbox or limited sample, preserve rollback, validate outcomes, and reconcile totals and records after every material change.
Worked example
The sales team moves every account that receives a proposal into a 75 percent probability stage, even when the buyer has not confirmed budget or process.
Proposal sent means the deal is likely, so set probability to 75 percent and keep it open until the prospect says no.
Commercial review requires a named buyer, confirmed problem, documented decision process, agreed evaluation of the proposal, current next step, and expected decision date. Sending a proposal without those conditions remains in solution fit or moves to delayed/no-decision under defined rules. Probability and forecast category follow observed historical behavior and documented management definitions, not seller preference.
Why it matters: A stage becomes useful when another trained operator can reach the same classification from the record evidence.
03 Control the work
Common failure modes
Users invent values when information is unavailable. Require data at the process point where it becomes known and necessary.
A person's relationship with the business and the state of one opportunity are different dimensions and should not overwrite each other.
Sequences must stop or reroute for replies, opt-outs, complaints, lifecycle changes, or ownership exceptions.
Bulk exports can bypass ordinary field and record controls. Restrict, justify, log, protect, and dispose of them.
Operating measures
Percentage of sampled required values that are complete, permitted, correctly formatted, and supported by the defined source.
Use it to decide: Low validity triggers definition, timing, training, integration, or required-field redesign.
Percentage of active opportunities with a dated, owned, specific next action supported by the current buyer process.
Use it to decide: Gaps create a prioritized follow-up or truthful reclassification queue.
Count and value of opportunities beyond the documented stage-age threshold without an approved reason.
Use it to decide: Review for blocked action, delayed buyer process, no-decision, or stale record closure.
Users or integrations holding administrative, export, delete, or configuration rights without current approval and business need.
Use it to decide: Remove or reauthorize promptly and investigate unexplained privilege changes.
04 · Applied case lab · 2026.08.31-practice-3
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 fictional training case uses fabricated company and contact records. It contains no real personal or confidential data and does not provide privacy, legal, employment, or technology-vendor advice.
CB01 · citable versioned case brief
OrbitWorks is a fictional business-to-business maintenance software company with 14 sales and service users. Its CRM holds 8,420 company records, 11,780 contacts, and 1,360 open opportunities. An audit sample finds 23 percent of open opportunities have no dated next step, 18 percent lack a decision-role contact, and 11 percent are assigned to former employees. Two pipelines use different meanings for qualified, yet both feed one forecast. Sales moves opportunities forward when a meeting is scheduled; customer success uses the stage only after a written problem and buying process are recorded. A marketing import of 2,100 contacts is waiting. The source contains 430 probable duplicates, 280 records without a documented marketing basis, 17 personal notes copied into a free-text field, and country values in nine formats. The proposed automation sends four emails and creates a call task, but it has no stop rule after opt-out, reply, disqualification, or opportunity creation. A dashboard reports a 72 percent win rate because it excludes closed-lost records older than 30 days. A regional manager requests administrator rights for all representatives to fix records faster. The CRM also has three integrations whose owners left the company; one export token has not been rotated in 19 months. Leadership wants a clean forecast by Friday and suggests overwriting all records from the import. Learners must design a controlled repair that improves lifecycle clarity, data standards, follow-up, stage evidence, reporting, permissions, and change management. They must minimize unnecessary personal data, preserve auditability, and avoid claiming that a configuration alone establishes lawful processing or accurate forecasts.
Judgment required: Choose an interim reporting treatment and identify the authorized owner and test needed for a durable definition.
Do not assume: Do not select the definition that produces the more favorable forecast.
Judgment required: Separate storage, service, and marketing uses and route lawful-basis and retention questions to qualified owners.
Do not assume: Do not equate possession of a business contact with permission for automated marketing.
Bounded case starter
Reconcile team meanings and map the customer lifecycle, systems, owners, and handoffs.
Deliverable: A lifecycle architecture map, definition decision proposal, and approval-request record; no lifecycle definition is represented as approved.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F01, F04, F09, 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 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.
Provided inputs
Evidence criteria
Debrief lens: Architecture should follow the approved process and preserve disagreements for decision. A diagram that hides conflicting stage meanings will reproduce the same reporting problem.
Bounded case starter
Create a data dictionary and remediation rules without inventing missing values.
Deliverable: A field dictionary, quality scorecard, and exception queue design.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F02, F03, F05, F06, F07, F08, 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.
Provided inputs
Evidence criteria
Debrief lens: Required fields should become available when the process genuinely knows them. Quality improvement cannot be achieved by guessing values or importing unnecessary notes.
Bounded case starter
Redesign the sequence so work stops or changes when the record state changes.
Deliverable: An automation specification with triggers, stop rules, owners, and test cases.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F09, 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.
Provided inputs
Evidence criteria
Debrief lens: Automation needs explicit state transitions and failure handling. The right cadence can differ, but every design must honor suppression and stop when its premise is no longer true.
Bounded case starter
Propose stage entry and exit evidence that both teams can apply consistently.
Deliverable: A stage dictionary, aggregate reclassification examples based on F02 through F04, and a blank twenty-row reclassification worksheet clearly marked for later record-level evidence.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F02, F03, F04, 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 25 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.
Provided inputs
Evidence criteria
Debrief lens: Stage criteria should describe observable buyer progress. Historical reclassification must remain traceable so improved definitions do not rewrite past performance invisibly.
Bounded case starter
Recalculate decision metrics using transparent populations, periods, and exclusions.
Deliverable: A dashboard specification and exception-report mockup.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F01, F02, F03, 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: 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.
Provided inputs
Evidence criteria
Debrief lens: The win-rate discrepancy is a definition problem before it is a performance problem. A useful dashboard exposes population and exclusions and connects exceptions to action.
Bounded case starter
Plan deduplication, import, permissions, integration ownership, rollback, and approval.
Deliverable: A change plan with test sample, permission matrix, backup, rollback, and acceptance record.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F05, F06, F07, F08, F09, 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: 4 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.
Provided inputs
Evidence criteria
Debrief lens: A bounded test and rollback are more credible than a Friday overwrite. Permission and integration reviews belong in the same change because data quality and security are connected.
Self-review standard
There is no single universal CRM configuration. Strong work makes lifecycle evidence, data purpose, access, exceptions, and rollback explicit for this operating context. The downloadable rubric is formative guidance only—not a grade, verified completion, credential assessment, or professional approval.
Route to: Qualified privacy or legal owner and the organization's data-protection lead where applicable
Learner boundary: The learner configures approved controls but does not determine legal compliance alone.
Route to: Authorized CRM administrator, security owner, and backup or platform specialist
Learner boundary: A training change plan does not authorize production access or destructive changes.
05 Editable working tool
Define one field or stage per row before configuration. State how it is used, who owns the definition, when it changes, and which decision or report depends on it. 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.
| Field or stage | Definition | Owner | Update trigger | Reporting use |
|---|---|---|---|---|
Completed example
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.
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.
07 Sources and handoffs
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.
nist-privacy-framework · Official guidance
Primary voluntary framework for identifying and managing privacy risk, governance, data processing, communication, and protection.
Open reviewed external source ↗ftc-protecting-personal-information · Official guidance
Primary business guidance on taking stock of data, limiting collection, access control, disposal, and incident planning.
Open reviewed external source ↗ftc-start-with-security · Official guidance
Primary guidance on minimizing data, sensible access controls, authentication, secure transmission, vendors, and security maintenance.
Open reviewed external source ↗ftc-can-spam · Official guidance
Primary compliance guidance relevant to commercial email workflows and opt-out handling in CRM systems.
Open reviewed external source ↗ws-crm-operating-standard · Academy internal operating standard
Academy-selected lifecycle, field, queue, stage, dashboard, change, and review 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 ownerUse a scoped technical engagement for approved CRM integration, automation, reporting, access, testing, or migration work.
Explore the handoff →Discuss trained operational capacity for governed data hygiene, task queues, research, documentation, and customer handoffs.
Explore the handoff →Future facilitated pathway · not open
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.
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
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