Chapters
- 01 · One Business, Four Kinds of Records
- 02 · Define Leads and Contacts
- 03 · Build the Person Lifecycle
- 04 · Build the Account Lifecycle
- 05 · Define Opportunity Stages
- 06 · Assign Owners and Handoffs
- 07 · Define Important Fields and Sources
- 08 · Resolve Conflicts and Open Questions
- 09 · Capstone: Publish the Business Truth Map
10 min · Interactive exercise
One Business, Four Kinds of Records
Map people, companies, transactions, and qualification work without flattening them into one status.
Priya Shah downloads a guide from GTM Lab. A Sales rep later hears that Acme Manufacturing may want a new implementation. The CRM has a person record, an Acme record, and a field on Priya that says Evaluation.
That field looks harmless until the questions start. Is Priya evaluating something, or is Acme? Which potential purchase does the field describe? What happens when Acme considers an expansion later? One field is trying to answer three questions at once, and it can only ever hold one answer. The fix isn't a better field. It's giving each business fact a home.
What the four records mean
A CRM is easiest to reason about when a record stands for one thing in the real world: a Lead holds an early person before the ongoing person model applies; a Contact is the ongoing identifiable person; an Account is the company relationship; an Opportunity is one specific potential purchase with its own sales process and commercial history.
Qualification work is separate from all four records. It shows work someone is doing right now, not a new meaning for the person, company, or purchase. Person lifecycle, consent, fit, and ownership answer different questions again.
Tracing the same situation without flattening it
Start with Acme as a target Account. Priya's guide download gives an early person record. Her walkthrough request gives Marketing qualification work to review. That request can make Priya Engaged. It does not make Acme a customer, and it does not make the initial Opportunity late-stage.
Active companies come from Account lifecycle; walkthrough requests come from person activity; initial-implementation value comes from the Opportunity. Each report has a defined population, because each population lives on its own record.
Carry this into your business
Before you build a workflow, take one real business event and ask what actually changed: a person relationship, a company relationship, a purchase, or work someone needs to do. Do this for the three or four events your team argues about most, and you'll already know where your next reporting dispute is going to come from.
GTM Lab
Saved locallyBusiness Truth Map · 0 of 9 sections started
Saved locally to your browser.
Build the entity and relationship map
Assign each sample fact to the record that owns it, then run the trace.
Sample situation
Priya Shah at Acme Manufacturing
GTM-LAB-CANONICAL- Person
- Priya Shah
- Company
- Acme Manufacturing
- Interaction
- Downloaded a guide
- Later request
- Requested a product walkthrough
- Potential purchase
- Initial implementation
- Later potential purchase
- Expansion
These definitions describe one business. Confirm its scope before you assign anything.
B2B software, sold through inbound, outbound, and expansion motions
Everything below assumes this shape. A self-serve or transactional business would need different answers.