Field guide 01
Designing CRM and revenue operations as one accountable system
A practical guide to lifecycle, pipeline, ownership, data quality, automation and reporting across the customer and revenue journey.
01Start here
The CRM is a record of the operating model
Before configuration, define how a person, company, opportunity and customer move through the organisation, which evidence moves them and who becomes responsible at each stage.
- Map the real journey, including workarounds
- Name the owner and next action at every transition
- Separate customer state from team activity
- Write the exception path as carefully as the happy path
02Definitions
Lifecycle and pipeline answer different questions
Lifecycle describes the relationship with the organisation. Pipeline describes controlled work towards an outcome. Mixing them makes both difficult to govern and report.
- Define evidence-based lifecycle stages
- Give pipelines a clear beginning and end
- Set required information and exit criteria
- Record rejection, recycling and loss reasons
03Data
Every important field needs a direction of truth
A data dictionary should record meaning, format, source, editor, validation and retention. Integration design follows those decisions rather than trying to resolve them later.
- One definition per field
- One responsible source system
- Validation at the point of entry
- Duplicate and merge rules
- Retention and deletion ownership
04Ownership
Lead routing is a timed operating process
Assignment only works when qualification, territory, availability, acceptance, follow-up and escalation are treated as one observable journey.
- Capture source and consent
- Resolve qualification before routing
- Assign a person, not just a team
- Start a visible response clock
- Escalate when ownership is not accepted
05Automation
Automate stable decisions, not unresolved disagreements
Each workflow needs an entry rule, suppression rule, re-entry decision, failure path and owner. If the team cannot explain the process, automation will make the ambiguity harder to see.
- Inventory existing workflows first
- Test overlapping enrolment
- Route failures to a responsible person
- Keep changes reversible
- Retire logic nobody can justify
06Measurement
Reconcile reporting before asking it to forecast
Operational reporting should trace counts and values back to source records, while revenue reporting needs shared definitions across marketing, sales and finance.
- Define every reported metric
- Reconcile stage counts and amounts
- Expose missing owner and next action
- Separate activity from progress
- Monitor data-quality exceptions
07Governance
The system needs a standing operating cadence
Ownership, access, data quality, workflow performance and reporting definitions need scheduled review so the CRM does not quietly become a record of old decisions.
- Monthly data-quality review
- Quarterly permission review
- Workflow and integration register
- Administrator runbook
- Prioritised improvement backlog
Related