Setup Guide · CRM
Consultant CRM Setup Guide
Pipeline, Fields, and Follow-Up
Most solo consultants do not need a complicated CRM. They need a small, disciplined system that prevents lost leads, preserves context, and moves sold clients into onboarding.
⚡ Quick answer
Minimum viable CRM
A CRM for a solo consultant has one job: make the next right action obvious.
If your CRM cannot tell you who to follow up with today, what they care about, and where the opportunity sits, it is just a contact database.
The minimum viable consultant CRM is smaller than most people think. It does not need elaborate scoring, territory management, or enterprise dashboards. It needs a clean pipeline, a few required fields, a next-step habit, and a handoff into onboarding when work is won.
Most solo consultants begin with fragmented context: a LinkedIn message, a Calendly booking, notes in a document, a proposal in email, and a reminder in their head. The CRM should turn that scattered context into a single operating view.
| CRM element | Minimum version | Why it matters |
|---|---|---|
| Pipeline stage | New lead, qualified, discovery booked, proposal sent, won/onboarding, lost/nurture | These stages match the actual sales motion for most consultants. |
| Contact record | Name, company, email, role, LinkedIn, referral source | You need enough context to personalize follow-up without hunting. |
| Deal record | Problem, offer fit, estimated value, urgency, next step date | The deal record keeps the business opportunity separate from generic contact details. |
| Notes | Discovery summary, objections, decision criteria, promised next action | Notes should support decisions, not become a diary. |
| Tasks | Follow-up date, proposal reminder, onboarding trigger | Tasks protect revenue from memory failure. |
Pipeline stages
Use stages that represent decisions, not feelings.
A good stage tells you what happened and what needs to happen next.
| Stage | Definition | Exit criteria | Next action |
|---|---|---|---|
| New lead | Someone entered your world through referral, form, email, LinkedIn, or newsletter. | You know whether they have a real problem you can solve. | Qualify or move to nurture. |
| Qualified | The problem, audience, budget range, urgency, and fit are credible. | A discovery call is booked or declined. | Book discovery or send qualifying questions. |
| Discovery booked | A live conversation is scheduled. | The call is complete and notes are summarized. | Extract decision drivers and draft follow-up. |
| Proposal in progress | You are translating discovery into scope, assumptions, pricing, timeline, and risk. | Proposal is sent. | Set proposal follow-up tasks. |
| Proposal sent | The client has scope and price. | Client accepts, rejects, requests revision, or stalls. | Follow up at defined intervals. |
| Won / onboarding | Client accepted the proposal. | Contract, invoice, intake, kickoff, and workspace are complete. | Move to delivery. |
| Lost / nurture | Not a fit, not now, or no decision. | Relationship is tagged and placed in nurture if appropriate. | Send useful follow-up later. |
Do not create stages like “hot lead” or “maybe.” Those are feelings, not operating states. A stage should change the work required from you.
Fields to track
The right fields reduce cognitive load.
Track the information that changes your next action, proposal, or follow-up.
| Field | Example values | Why it matters |
|---|---|---|
| Lead source | Referral, LinkedIn, website, newsletter, prior client | Shows which acquisition channels produce qualified opportunities. |
| Problem type | Positioning, growth, operations, research, strategy, implementation | Helps you spot repeatable offers and segment follow-up. |
| Offer fit | Strong, uncertain, weak | Prevents over-investing in poor-fit conversations. |
| Estimated value | $2k project, $8k project, $5k/mo retainer | Supports prioritization and forecasting. |
| Decision driver | Speed, confidence, revenue, clarity, stakeholder alignment | Turns discovery into proposal language. |
| Objection | Price, timing, internal approval, unclear scope | Lets you follow up intelligently. |
| Next step date | Specific calendar date | Prevents silent pipeline decay. |
| Onboarding status | Contract sent, invoice sent, intake received, kickoff booked | Prevents “sold but not started” gaps. |
Start with these fields before adding custom complexity. If a field does not influence a decision, follow-up, or handoff, it can wait.
Setup paths
HubSpot, Notion, and Pipedrive each fit a different operating style.
The best CRM is the one that matches your lead volume and follow-up needs.
Use when follow-up matters
Best for consultants who want forms, tasks, email tracking, contacts, deals, and simple automation in one system.
Use when the CRM is also the workspace
Best for consultants with lower lead volume who want pipeline, notes, delivery docs, and checklists together.
Use when sales motion is active
Best for consultants who have multiple deals moving and want a focused pipeline experience.
HubSpot setup path
Create a deal pipeline with the stages above. Add custom properties for problem type, referral source, estimated value, urgency, decision driver, objection, and next step date. Connect a website form or lead magnet form. Create task templates for discovery booked, proposal sent, and deal won.
Notion setup path
Create a database called Client Pipeline. Use select properties for stage, source, problem type, fit, urgency, and next step. Add relation links to a Client Workspace database. Create templates for discovery notes, proposal notes, and onboarding checklist.
Pipedrive setup path
Use a clean deal pipeline. Add activities for follow-up and proposal review. Keep fields lighter than HubSpot: source, offer, value, probability, and next activity. Pipedrive shines when the activity habit is maintained daily.
Follow-up cadence
Proposal follow-up should be designed before you need it.
If follow-up depends on your mood or memory, revenue will leak.
| Moment | Action | Automation or human? | Example |
|---|---|---|---|
| Immediately after discovery | Send recap and confirm proposal timing | Human-assisted by AI | “Here is what I heard, what matters, and what I will send next.” |
| Proposal sent | Create follow-up tasks for 2, 5, and 10 business days | Automated task creation | CRM creates reminders with proposal link attached. |
| Two days after proposal | Ask whether the proposal matches the problem and decision criteria | Human | Short, specific note tied to their stated priority. |
| Five days after proposal | Offer to resolve objections or adjust scope | Human with template | Reference the likely constraint: timing, budget, stakeholder review. |
| Ten days after proposal | Close the loop or move to nurture | Human | “Should I keep this active, revise scope, or circle back later?” |
Good follow-up is not pressure. It is continuity. The goal is to keep the decision moving without making the prospect do extra administrative work.
Onboarding handoff
Won deals should not become a new manual project.
The CRM should trigger the first operating steps after yes.
When a deal moves to Won / Onboarding, the system should create or prompt the following:
- Send contract or agreement.
- Send invoice or payment link if applicable.
- Send intake form.
- Create client workspace.
- Schedule kickoff.
- Move discovery notes and proposal assumptions into delivery context.
- Create first deliverable or first-week action checklist.
This is where many consultants lose momentum. The client has emotionally said yes, but operationally nothing starts. The handoff should make the first week feel controlled.
Automation map
Automate handoffs, not judgment.
The CRM should reduce admin without hiding important decisions.
| Trigger | Action | Tool example |
|---|---|---|
| Lead form submitted | Create contact and deal in New lead | HubSpot form or Tally → HubSpot through Make |
| Discovery booked | Update stage, create prep task, attach intake context | Calendly → CRM task |
| Discovery complete | Add AI summary to deal record | Transcript → Claude summary → CRM note |
| Proposal sent | Move stage and create follow-up tasks | Proposal tool/email → CRM |
| Deal marked won | Create onboarding checklist and client workspace | CRM → Notion through Make |
| Deal marked lost | Add to nurture segment with context tag | CRM → Kit/Beehiiv |
If an automation requires nuanced judgment, pause. If it simply moves a known object from one place to another, it is a good candidate.
Downloadable asset placeholder
CRM pipeline template.
This page should eventually convert into an email asset.
Download placeholder: Consultant CRM Pipeline Template
Asset to connect later: a CRM template with recommended stages, fields, task cadence, discovery summary fields, proposal follow-up tasks, and onboarding handoff checklist.
Real scenarios
How the CRM should behave in actual consultant situations.
These examples show why fields, stages, and follow-up rules matter.
Scenario 1: referral with vague need
A past client introduces you to a founder who says they “need help with growth.” The CRM record should not stop at name and email. Create the contact, set source to referral, create a deal in New Lead, and add a qualification task. After the first reply, update problem type to positioning, demand generation, sales process, or unknown. If there is no budget or urgency, move the deal to nurture rather than letting it sit as active opportunity.
Scenario 2: strong discovery call, slow decision
After discovery, the prospect has clear pain and budget, but another stakeholder must approve. The CRM should capture decision driver, objection, stakeholder, and decision date. When the proposal is sent, the follow-up sequence should not be generic. The first follow-up should reference the stakeholder decision and offer a shorter summary the prospect can forward internally.
Scenario 3: client says yes by email
The moment the client accepts, move the deal to Won / Onboarding. Do not leave it in Proposal Sent while you manually send scattered next steps. The CRM should prompt the contract, invoice, intake form, kickoff link, and client workspace. If you use Notion for delivery, this is where the client record should connect to the workspace template.
Scenario 4: no response after proposal
After the third follow-up, move the deal to Lost / Nurture with a reason: timing, budget, internal priority, no response, or poor fit. This gives future you useful information. A silent prospect with a good problem can become a newsletter subscriber or six-month check-in. A poor-fit prospect should not continue cluttering active pipeline.
| Lost reason | What it means | Future action |
|---|---|---|
| Timing | Problem is real, but not urgent now. | Create 60- or 90-day check-in. |
| Budget | Fit exists, but price or capacity is constrained. | Send lower-commitment content or smaller offer later. |
| Internal approval | Stakeholders are not aligned. | Send decision support or executive summary. |
| No response | Interest was unclear or priority shifted. | Move to light nurture, not active pipeline. |
| Poor fit | You should not pursue. | Archive or refer elsewhere. |
The CRM becomes valuable when it preserves decision context, not just contact information.
FAQ
Frequently asked questions
What CRM pipeline stages should a consultant use?
A practical consultant CRM pipeline should include New Lead, Qualified, Discovery Booked, Proposal In Progress, Proposal Sent, Won / Onboarding, and Lost / Nurture.
Is HubSpot or Pipedrive better for consultants?
HubSpot is better when you want forms, contacts, tasks, marketing context, and light automation together. Pipedrive is better when you want a focused sales pipeline and activity-driven follow-up.
Can Notion work as a consultant CRM?
Yes, if lead volume is modest and you want notes, delivery context, and pipeline in one place. It becomes weaker when you need email tracking, forms, reporting, and automated reminders.
What fields should a solo consultant track in a CRM?
Track lead source, problem type, offer fit, estimated value, urgency, decision driver, objection, next step date, and onboarding status.
How often should consultants follow up after sending a proposal?
A simple cadence is two business days, five business days, and ten business days after sending the proposal, adjusted for the decision timeline discussed in discovery.
Should I automate CRM follow-up?
Automate task creation and reminders. Personalize the actual message when the project is strategic or high value.
How do I connect discovery notes to CRM records?
After each call, summarize the transcript into decision drivers, objections, scope clues, timeline risks, and proposed next steps, then paste the summary into the deal record.
When should I upgrade from a free CRM?
Upgrade when free-plan limits prevent follow-up, reporting, automation, or collaboration that directly supports revenue.
Build the $97/month Consultant Operating System
Use this guide as one layer of the full SoloClientStack: CRM, onboarding, discovery notes, proposal follow-up, delivery workspace, and nurture.