A CRM alternative for independent consultants: pipeline, proposals and client notes in plain files

For most independent consultants, the best CRM isn’t a sales-team CRM. It’s a short pipeline you actually keep current, stored next to your proposals and what you know about each client, and one folder of plain markdown files does that job well.

Some practices do need a real CRM, and the signs are below.

Why a team CRM often doesn’t fit

A team CRM is built around a sales team: reps, handoffs, sequences and a forecast for a manager. You are the rep, the manager and the person delivering the work.

Your pipeline is different: a few open deals, much of the work by referral, and sales that can take months. What wins the next deal is rarely in a CRM: the framework you built for the last client, the result you got, the proposal that closed. A CRM tracks the deal. It doesn’t hold what you delivered.

And when the work is full, the pipeline goes quiet: updating one more tool is the first thing a busy week drops. Then an engagement ends and the calendar is empty.

The pipeline: six stages

Give each stage one meaning:

1. Lead. An intro, a referral or an inquiry. Record who sent them.
2. Discovery. A call is booked or done. Note the problem in their words, what it costs them and who decides.
3. Proposal out. Sent, with the date and the options. This is where deals stall.
4. Signed. The agreement is signed and the deposit invoiced.
5. Delivering. The work is running, and the deal links to the project.
6. Renewal due. The end date is close. Next: a renewal, an extension or a referral ask.

Every deal ends as won, lost or parked, with one line on why. One rule holds it together: a deal without a next step and a date isn’t in the pipeline.

Two notes you can copy

One note per deal, here with sample data:

---
type: Deal
client: "[[Lone Sock Supply Co.]]"
stage: proposal-out
value: 22500
source: referral
next_step: Follow up on the proposal
next_date: 2026-09-15
---

# The problem, in their words
Returns and the 3PL are eating the margin.

# Offer
Retainer: $7,500 a month, three months minimum.
Fallback: a fixed-fee audit.

# Log
- 2026-08-14 · discovery call
- 2026-08-24 · proposal sent

And one note per client, which outlives every deal:

---
type: Client
description: Who they are and where things stand.
status: active
renewal: 2026-12-01
referred_by: "[[Who introduced them]]"
---

# Who decides
# What they asked for, and when
# What you delivered, and the result
# Engagements
- [[Deal or project note]]

The results section is your next case study. And write the renewal date down the day the agreement is signed: a renewal nobody wrote down is the easiest revenue to lose.

A weekly pipeline routine

Twenty minutes, the same day every week:

1. Open every deal that isn’t closed, sorted by next date.
2. Fix the stale ones. No next step, or a date in the past: write one now, or close the deal.
3. Follow up on proposals ten days out with no reply. Offer a smaller first step.
4. Update the client notes from this week’s calls.
5. Check renewals due in the next 60 days.
6. Write down three numbers: open pipeline value, proposals out and where new leads came from.
7. Do one thing for next month’s pipeline, even in a full week: a referral ask, a post, a coffee.

Step seven keeps the calendar from emptying when an engagement ends. The routine fits inside a weekly review, and the same notes show what each client is really worth.

When a real CRM is the better choice

A CRM earns its price when:

• You run outreach at volume. Sequences, cold email and dozens of new contacts a week need automation a folder doesn’t have.
• More than one person sells. A partner or a business developer needs a shared pipeline, with permissions and history.
• You want every email and meeting logged for you. Inbox and calendar sync is what CRMs do best.
• Your accounts have many stakeholders. A dozen contacts per client, across dozens of clients, is database work.

If you already keep a CRM current, keep it. Either way, keep what each engagement taught you in files you own. The CRM tracks the sale. The files remember the work.

Where Oknola fits

Oknola is this folder with the upkeep done for you. You write, and Oknola types, tags and files what lands in it, so each engagement, proposal and invoice stays linked to the client it came from and the next discovery call starts briefed. It doesn’t send proposals or collect signatures: keep your proposal tool, and Oknola follows the proposal to signed and paid. An agent you allow your past proposals drafts the next one from them, and nothing is sent without your yes.

See it for consultants, and what is available today is on the roadmap.

Questions people ask

Is a spreadsheet enough for a consultant’s pipeline?

For the list, often yes: a row per deal with the stage, value and next date. But the call notes, the proposal and what you delivered end up somewhere else. A note per deal keeps them together.

How many pipeline stages should a consultant use?

Five to seven. With fewer, you can’t tell a warm lead from a signed deal. With more, you stop updating them. Each stage should tell you what the next step is.

What about retainer and fractional clients?

Give each one a client note with the renewal date, the scope or hours, and a short monthly log. Move it to the renewal stage 60 days before the end date, when that conversation should start.