CRM setup: define lead stages before automating
Build a minimum lead handoff process with clear entry criteria, owners, next actions and loss reasons. Includes a stage dictionary and a practical test scenario.
1. Reconstruct one inquiry before selecting software
Choosing a CRM can postpone the harder discussion: who owns an inquiry after the form is submitted? I would start with several recent inquiries and reconstruct their paths. Where did each come from, when was it recorded, who saw it, when did someone respond and what next step was agreed? If half the answers live in private messages, new software will not automatically recover them.
Draw the shortest useful route from arrival to a clear outcome. Avoid copying every stage from a demo account. The first version should show where an inquiry is, who owns it and what must happen next. Bring marketing and sales into the same working document and ask each participant to classify one example inquiry. Different answers will expose the definitions that need agreement before anyone starts configuring software.
2. Separate status, sales progress and outcome
New inquiry, meeting agreed and budget mismatch describe different things. One is a processing state, another is a customer-confirmed sales milestone and the third is a reason the process ended. Combining them in one dropdown makes reporting difficult to interpret. Acquisition source also belongs in a separate field: moving a record forward should not overwrite how the person first contacted the business.
HubSpot's documentation distinguishes lifecycle stages, lead status and pipelines. That is a useful example of separating concepts, not a requirement that every business use the same labels. Write your business rules first, then map them to the selected platform. Test a returning customer with a new request. Their new opportunity should not erase the history of the earlier purchase or be counted automatically as a newly acquired customer.
| Field | Question it answers | Illustrative value |
|---|---|---|
| Source | Where did this inquiry originate? | Service page form |
| Processing status | What is happening now? | Contact established |
| Deal stage | What has the buyer confirmed? | Meeting agreed |
| Loss reason | Why did this process end? | Service not suitable |
| Next action | What will happen and when? | Send estimate Thursday |
3. Give every transition a rule and an owner
Define the entry and exit condition for each stage. Contact established should mean a completed conversation or a meaningful reply, not an unanswered call. Qualified should mean that the agreed suitability criteria have been checked. The criteria depend on the business. Budget, need and timing can be useful, but requiring the same information from every kind of inquiry can create unnecessary friction.
Assign an owner and a backup for absences. Set the response target around the actual staffing schedule and capacity. There is no universal five-minute promise in this guide. A realistic rule, a visible exception and an escalation path are more useful than a target nobody can maintain. Automated transitions should retain their basis, such as the form event, a recorded response or a verified deal update, so that the history remains understandable.
4. Test definitions with a small worked example
Illustrative example: a service business receives 40 inquiries in a week. Four are duplicate submissions, the team reaches 28 unique contacts and 12 meet its qualification criteria. These are teaching numbers, not results from a client project. Even this small funnel raises questions. Should contact rate use 40 records or 36 unique inquiries? What happens when someone first submits a form and then calls?
Use a stable contact identifier and preserve separate inquiry events where the system supports it. Describe the deduplication rule rather than silently deleting records from the analysis. Ask two employees to classify a small sample independently. Their disagreements reveal ambiguous definitions. Resolve those differences before using the stages to judge a channel, calculate commissions or compare individual salespeople. Otherwise the reporting dispute will arrive after people have already been rewarded for incompatible behavior.
5. Add automation only after the manual route works
Run one test through the whole process: the form creates a record, the source is retained, an owner receives a task, the stage change appears in history and closure requires a reason. Also test repeated submission, an invalid phone number, an after-hours inquiry and an absent primary owner. A successful form confirmation does not prove that the right employee can find and act on the record.
Enable necessary notifications and transitions one at a time. Test bulk rules on synthetic records or a limited group before widening them. Keep a change log and a rollback route. Use redacted examples and aggregate counts when asking a public AI tool to help inspect the process. Automation failures need an identifiable owner and a visible error record; otherwise missing leads simply move into a more expensive system.
6. Build a report that points to an action
The minimum report should show unique new inquiries, unassigned records, overdue next actions, transitions to qualified leads and loss reasons. Sales conversion needs time to mature. A fresh inquiry has not had the same opportunity to close as one created several weeks ago. Compare cohorts by inquiry date and give them comparable observation windows before concluding that a channel has deteriorated.
The funnel-check tool uses the stages and numbers you supply to suggest which transition deserves attention. It does not connect your CRM, inspect individual records or repair the pipeline. Provide redacted, reconciled aggregates, then verify its suggestions against the source data. Keep the stage dictionary beside the report and assign one person to maintain it. When a definition changes, record the date and explain whether earlier reports remain comparable.
Lead stage dictionary
Illustrative definitions to agree with the sales team. Set response deadlines separately based on actual capacity.
Download the working CSV template
Open in Excel or Google Sheets. Replace example rows and empty fields with your own data.
Frequently asked questions
How many stages should a new CRM have?
Use enough to represent transitions that require genuinely different actions and evidence. A short route from new inquiry to qualification and a clear outcome can be a useful start. If two adjacent stages trigger the same work, reconsider whether they need to be separate.
Can a spreadsheet come before a CRM?
Yes, it can help validate definitions for a small process. Assign ownership, control access and retain change history. When simultaneous editing, duplicate records and missed tasks become recurring problems, turn those limits into selection requirements for the CRM.