To design a CRM around the customer journey, define how account relationships develop, what information supports each decision, and who owns the next responsibility. Separate the ongoing relationship from individual sales opportunities. Then configure records, views, handoffs and automation to support how the business needs to operate.
Most CRM projects begin with questions about the software. Which fields do we need? How many pipelines should we create? What should the dashboard show? Those questions deserve answers, but the business has some decisions to make first.
How does a company become worth your attention? What earns a salesperson’s time? When does a potential purchase deserve an opportunity record? What does delivery need when the customer agrees to buy?
If those answers live in the owner’s head, the CRM implementation depends on somebody translating them correctly. If nobody asks, the software defaults become the process.
In Zero-Point Selling™, the Customer Journey describes the development of the durable account relationship:
Target → Suspect → Prospect → Customer
These classifications help the business understand where a relationship stands and what investment it has earned next. Their value depends on shared definitions and reliable information supporting the classification.
A Lead is a signal within that journey. An Opportunity, or Deal, represents a specific potential transaction. Those distinctions let the CRM preserve the relationship while coordinating different responses and purchases within it.
A company can send a new inquiry after becoming a customer. It can consider several purchases at once. It can decide against one service while continuing to buy another. The design needs room for those situations without repeatedly rebuilding the relationship.
Start by agreeing on what your journey classifications mean. Then establish how the CRM will preserve that meaning across Marketing, Sales and Delivery.
An existing customer considering an additional service already has a history with your business. You may know its organization, contacts, preferences and previous commitments. That information remains useful while the new purchase receives its own evaluation.
The new opportunity needs transaction-specific information: the relevant problem, proposed scope, participating people, timing and evidence of progress. A previous purchase provides context, but it doesn’t establish that this purchase is qualified.
The account does not restart from zero. The decision does.
Your CRM should preserve the customer relationship while allowing another opportunity to develop. Otherwise, a new deal can overwrite useful relationship information or trigger acquisition communication that ignores the customer’s history.
This also matters when a deal ends without a purchase. Closing that transaction should preserve what the business learned and leave the relationship in an appropriate state. The company may still fit your audience even when the particular purchase doesn’t proceed.
Before adding properties, decide what each record represents. That decision determines where information belongs, who maintains it and how other people find it.
The company or account record preserves organizational context that continues across interactions. The contact record preserves information about the individual and their relationship to the organization. The opportunity record holds information about a specific commercial evaluation.
Associations connect those records. They allow a salesperson to understand which people participate in a purchase without copying all their information into the deal. They also allow the business to manage several opportunities while retaining one shared account history.
A useful design question is: If this fact changes, where should someone update it? If the answer depends on which employee you ask, the architecture needs attention.
Information can appear in several views without being entered several times. Establish where the authoritative value belongs, then make it accessible where people perform their responsibilities.
A journey classification should help the business decide what attention a relationship deserves. Moving it forward has consequences: more research, more communication, salesperson capacity or preparation for delivery.
For each transition, define the condition that must be true and the evidence supporting it. Then identify the appropriate response. That gives employees a reason for the classification beyond satisfying a reporting requirement.
Engagement with a marketing asset gives you information to interpret. Its meaning depends on what happened, who responded and the context of the relationship. Downloading educational material and requesting a conversation about replacing a service provider create different decisions for the business.
The CRM needs rules that preserve those distinctions. Otherwise, a convenient trigger can assign more significance to an action than the business intended.
For each transition, answer:
Keep the definitions specific enough that different employees can apply them consistently. You can refine the rules as you learn, but people need a shared starting point.
A handoff requires the next person to understand and accept responsibility. A notification helps announce the work; the record must provide enough context to continue it.
When Marketing passes an inquiry to Sales, the seller needs to understand who responded, why the inquiry deserves attention and what has already occurred. The handoff also needs an owner, a response expectation and a way to record the disposition.
Sales may accept the inquiry, request clarification, redirect it or determine that further marketing development is appropriate. Preserving that response gives Marketing useful feedback and makes ownership visible.
The same principle applies when Sales hands a customer to Delivery. The receiving team needs the agreed scope, relevant commitments and expectations required to fulfill the promise. A closed deal doesn’t automatically establish that the handoff is complete.
Test the design with the receiving employee. Ask what they believe they now own and what they can do from the information available. Their ability to continue the work is the practical test.
AMCAF™ organizes marketing through Audience, Message, Marketing Channel, Marketing Assets and Follow-up. Those choices create context that should remain useful as the relationship develops.
The audience explains who the business intends to reach. The message addresses a relevant problem or decision. The channel and asset carry that message, while follow-up defines the response and next action.
When someone responds, preserve enough of that context for the next responsible person. A seller preparing for a conversation should be able to understand what prompted it. The buyer shouldn’t have to reconstruct the path because internal systems lost the connection.
This doesn’t require capturing every possible interaction before anyone can act. Zero Point is the minimum reliable information necessary to make the next appropriate decision. Apply that standard to what the seller needs now and what Marketing needs to learn from the result.
Once relationships, responsibilities and transitions are defined, the software choices become more concrete. You can determine which properties, associations and views help employees perform the work.
Give people access to relevant context where they need it. A salesperson managing active opportunities needs a different working view from a delivery employee accepting new customers. Both should use shared information without maintaining competing versions.
Keep relationship classification separate from deal progression. A pipeline coordinates work around a particular purchase, so its stages need definitions appropriate to that transaction. The account journey supplies the broader relationship context.
Automation can then support stable administrative decisions, such as routing work to an agreed owner or creating a reminder. Establish the trigger, expected result and exception owner before activating the workflow.
If a rule requires interpretation the business hasn’t resolved, automation will distribute the uncertainty. Settle the decision first, then determine what the system can reliably administer.
A process diagram can look finished while the actual CRM leaves employees guessing. Walk through complete situations using real records before expanding the configuration.
Include a new inquiry, an active opportunity, a relationship needing further development, a completed purchase and an existing customer considering another service. Follow the information across the people involved.
Can each person understand why the record exists? Can they find what supports its current classification? Is ownership clear? Does the receiving person have what they need? Does another purchase preserve the existing customer relationship?
Also test what happens when work stops or changes direction. The system should retain useful learning and make the next responsibility understandable. Otherwise, unusual situations will push people back into private tracking methods.
CRM architecture earns its value when one person can continue from another person’s work without reconstructing the relationship. That requires shared meaning, reliable information and visible responsibility across the customer journey.
Zero-Point Selling provides Sales Operating System architecture for connecting those decisions. The operating sequence is Strategy → Process → People → Technology. CRM configuration supports the resulting design and makes it available to the people doing the work.
Start with one journey, define the relationships and decisions within it, and test the handoffs. That gives you a practical foundation for deciding what information the CRM must require.
Contact Rethink Revenue if you’re planning a CRM implementation or correcting an existing environment. Bring one path from initial attention through purchase and delivery. We’ll help you identify the operating decisions your CRM needs to support.
