Sales & CRM Systems
CRM architecture: decide what the data means before you automate it
Three people, three meanings of “Qualified”
- Sales“They picked up the phone.”
- Marketing“They filled in the long form.”
- Owner“They’re in our area and want work we do.”
Qualified (agreed)
In the service area, a service we offer, within our booking window. Set by the qualification rules; changed only by them or by an owner override with a reason.
When a stage means different things to different people, reports disagree, automations fire at the wrong moment and nobody trusts the pipeline. One written definition per stage and per field is unglamorous work, and it's the part everything else stands on.
The records, and how they connect
Contact
a person
- name
- phone
- preferred channel
Accountowner
a household or business
- address
- type
- owner
- since
Lead
an inquiry
- request
- source
- channel
- status
- received
Opportunityowner
work that might be won
- value
- stage
- owner
- expected date
Activity
something that happened
- call, message, visit, note
- when
- by whom
- Contact— belongs to →Account
- Lead— came from →Contact
- Opportunity— belongs to →Account
- Activity— logged on →Lead
- Activity— logged on →Opportunity
Not every business needs all five. A service business may never need accounts separate from contacts; a B2B firm always does. The model follows how you actually sell.
Stages that mean one thing
01
New
- Means
- An inquiry exists
- Enters when
- Capture creates the lead
- Owned by
- Intake
02
Qualified
- Means
- Fits your criteria
- Enters when
- Qualification rules pass, or an owner overrides with a reason
- Owned by
- The assigned owner
03
Contacted
- Means
- A real conversation happened
- Enters when
- A call or reply is logged, not when a message is sent
- Owned by
- The assigned owner
04
Quoted
- Means
- A price is with the customer
- Enters when
- A quote is sent from the quoting tool
- Owned by
- The assigned owner
05
Won / Lost
- Means
- The outcome
- Enters when
- The job is booked, or the lead is closed with a reason
- Owned by
- The assigned owner
Every record has one system that's allowed to change it
| System | Contact | Lead | Opportunity | Appointment | Invoice |
|---|---|---|---|---|---|
| Intake | creates | creates | — | — | — |
| CRM | updates | updates | creates, updates | reads | reads |
| Scheduler | reads | — | reads | creates, updates | — |
| Phone system | reads | — | — | — | — |
| Invoicing | reads | — | reads | reads | creates, updates |
| Reporting | reads | reads | reads | reads | reads |
Two systems that both “own” a phone number will eventually disagree about it. Each record gets one system that creates it and a short list that may update it; everything else reads. The CRM keeps the relationship and pipeline truth. Reporting derives what happened from the CRM and its event history, so it never quietly becomes a second customer database.
Adapt the CRM you have, or build what you need
Most businesses don't need a new CRM. They need the one they have to mean something consistent: cleaner stages, fewer fields, clear ownership, and integrations that respect those rules.
When the work doesn't fit a sales CRM's shape, such as complex jobs, multi-step approvals or field operations, the same architecture can define a custom application instead. The workflow decides, not the brand of software.
What you get
01
An entity model
The records you need and how they relate.
02
Stage definitions
Each stage with its entry rule and its owner.
03
Field definitions
Required fields, and identity rules for matching people and businesses.
04
A responsibility map
Which system creates, updates or reads each record.
05
Boundaries
For automation and reporting, so both read the same truth.
Worth doing before the next automation, not after the fifth
Good fit
- Leads come through several channels or teams and land in the CRM inconsistently.
- Reports from different people disagree about the same pipeline.
- Automations keep firing at the wrong moment, or on the wrong records.
Not the right fit
- The CRM already reflects how you work, and the problem is one missing integration. Fix that instead.
Questions about CRM architecture
Do we need a new CRM?
Usually not. Most problems come from what the records mean and who changes them, and those can be fixed in the CRM you have. Replacement makes sense when the CRM can't represent how you work at all.
What's the difference between a lead, a contact and an opportunity?
A contact is a person. A lead is an inquiry from them. An opportunity is work you might win. Keeping them separate lets one person send several inquiries and lets one inquiry become several jobs, without losing the history.
How many pipeline stages should we have?
As few as you can define precisely, each with one way in. If two stages can't be told apart by a rule, merge them.
Where should reporting data live?
Reporting reads from the CRM and its event history. It shouldn't keep its own copy of customers, or it will drift from the truth.