The Configuration Gap
The CRM platforms available today, at almost any price point, are genuinely powerful revenue infrastructure tools. They can automate first response, manage complex follow-up sequences, score leads, route opportunities, generate reports, and provide a real-time picture of pipeline health at any moment.
The average business uses none of these capabilities. They have a pipeline with five stages they created on day one and have never changed. They have contacts that were imported but never touched. They have tags that mean nothing because nobody defined what they were for. They have a reporting dashboard that nobody looks at because the data in it cannot be trusted.
"The CRM is not the problem. The problem is that nobody built the logic the CRM needs to perform. The platform is ready. The architecture is missing."
Decision One: Stage Definition
The most important configuration decision in any CRM pipeline is what the stages actually mean, and specifically, what the exit criteria for each stage are. A stage without exit criteria is just a label. A stage with exit criteria is a conversion point with a defined standard.
Exit criteria are the conditions that must be true before a contact moves forward in the pipeline. For the Appointment Booked stage, the exit criteria might be: appointment date confirmed, pre-call intake received, brief sent to salesperson. Until all three conditions are met, the contact stays in Appointment Booked, not because someone is being pedantic, but because the stage represents a meaningful commitment about what has been done and what has not.
Most businesses have no exit criteria for any stage. This means pipeline movement is arbitrary, the pipeline view is unreliable, and forecasting from it is impossible.
Decisions Two Through Four
Automation Assignment
For each stage, define which automations are triggered by entry and which are triggered by exit. Entry automations might include a welcome email, a task creation, or an internal notification. Exit automations might include a stage transition confirmation, a next-step message, or a pipeline report update. If a stage has no automations, it is a label, not a system.
Stale Contact Logic
Define the maximum time a contact should spend in each stage before intervention is required. If a contact has been in Proposal Sent for 14 days without a decision, the system should surface it, automatically, to the relevant salesperson. Most businesses discover hundreds of stale contacts when they first run this logic against their pipeline.
Source Tagging Protocol
Every lead that enters the pipeline should carry a source tag from the moment of creation. This tag must be standardised, not free text, not whatever the salesperson typed, and it must persist through every stage movement. Without consistent source tagging, you cannot determine which lead sources are producing revenue and which are producing volume without conversion.
The Architecture Audit
A CRM architecture audit maps four things: stage definition quality, automation coverage, stale contact volume, and source tagging consistency. Each produces a score and a priority recommendation.
Average proportion of pipeline stages with no exit criteria in businesses we audit
Two-thirds of all stages are labels, not conversion standards. This is the single most common CRM architecture problem, and the one that most directly undermines close rate tracking, pipeline forecasting, and sales accountability.
The Phase 2 engagement produces a complete CRM architecture specification: stage definitions, exit criteria, automation maps, stale contact rules, and source tagging protocols. For businesses that are already on a capable CRM platform, this architecture, not additional software, is what unlocks the performance they expected when they subscribed.