CRM hygiene for tiny teams: the minimum that actually works
Every founder has had the same CRM twice. The first one was set up with enthusiasm, forty fields and a color scheme. It died in month two. The second one is a spreadsheet that is also out of date. The problem is not discipline. The problem is that CRM hygiene advice is written for sales ops teams with a person whose job is the CRM, and you do not have that person. Here is the minimum that works when the CRM is nobody's job.
Why small-team CRMs rot
- Too many fields. Every field is a question you have to answer after every call. Forty fields means you stop answering.
- Stages without definitions. "Qualified" means something different on Monday and Thursday. Deals drift into stages they have not earned and the pipeline number stops meaning anything.
- No next step. A deal with no dated next action is a deal nobody is working. The CRM cannot tell you that if the field does not exist.
- It lives away from the work. The conversation is in email, the CRM is another tab. Anything that needs a second tab loses to the tab you are already in.
The five fields
| Field | What it is for | Rule |
|---|---|---|
| Stage | Where the deal is | Only moves when the stage rule below is met |
| Next step | The one action that moves it | Never empty on an active deal. "Follow up" is not a next step; "send pricing for 3 seats" is |
| Next step date | When that action is due | Every active deal has one. Overdue means it is at risk |
| Owner | Who does the next step | One person, including when it is the buyer |
| Last contact | When you last heard from them | Filled from the inbox, not from memory |
Everything else (company size, source, notes, industry) is nice to have and can live in a notes field until it changes a decision. If a field does not change what you do this week, it is not a field, it is a form.
One rule per stage
The stage names do not matter. The rule for entering each one does. Four stages are enough for most founder pipelines:
- Conversation: they replied. Not "I emailed them". A reply.
- Qualified: you know the trigger, the cost of the problem and who decides. The discovery call questions exist to fill exactly this.
- Proposal: a number and a scope are in their hands, and a date to discuss it is on the calendar.
- Commit: they said yes and named a start date. Signature and payment are steps, not stages.
A deal that does not meet the rule stays where it is. That feels harsh on a Friday review and makes the pipeline number true.
The cap
Decide how many deals you can genuinely work at once (for a founder, 8 to 12) and hold the active list to that. Everything else goes to a nurture list with a trigger to come back on: a job change, a funding round, a date they gave you. The prioritization post covers the scoring. The cap is what keeps hygiene cheap: ten deals take ten minutes to check, forty take an afternoon you do not have.
The 10-minute Friday pass
- Sort active deals by next step date. Anything overdue: do it now or move the date honestly.
- Any deal with an empty next step: write one or move the deal to nurture.
- Any deal with no contact in 14 days: it is not active. Nurture, with a trigger.
- Any deal in a stage it has not earned: move it back. The number goes down and becomes real.
This is the weekly pipeline review compressed to its hygiene half. Ten minutes because of the cap and the five fields, not because of discipline.
The honest part: hands do not scale
Even the minimum decays. The Friday pass gets skipped in a launch week, the next step date drifts, "last contact" is guessed. The fix is not more discipline, it is removing the human from the update. The information the five fields need already exists: the reply is in your inbox, the call is on your calendar, the commitment is in the transcript, the buyer's silence is measurable. A CRM that reads those sources does not need a Friday pass.
That is the job Veora does with the CRM. She reads your email, meetings and chats, sets the stage from what actually happened, writes the next step from what was promised, dates it, and then works it: sends the follow-up, books the call, nudges the buyer who owes you an intro. The five fields stay true because she fills them from the conversation, not from your memory on a Friday. Whether the CRM is HubSpot, a sheet or nothing at all, the pipeline is the conversations, and she is the one reading them.
Frequently asked questions
What fields does a small team CRM actually need?
Five: stage, next step, next step date, owner, and last contact. Every active deal must have a specific next step with a date. Everything else (company size, source, industry) lives in notes until it changes a decision.
How do you keep a CRM up to date without a sales ops person?
Cap the active list at what you can genuinely work (8 to 12 deals for a founder), define one rule per stage so deals cannot drift, and run a 10-minute Friday pass: fix overdue next steps, fill empty ones, move stale deals to nurture. Longer term, connect the CRM to email, calendar and chats so stage and next step update from what actually happened, which is what an AI revenue partner like Veora does.
How many pipeline stages should a founder use?
Four is enough: Conversation (they replied), Qualified (trigger, cost and decision path known), Proposal (number and scope sent, discussion date booked), Commit (yes with a start date). The stage names matter less than the rule for entering each one.
A CRM that updates itself
Veora reads your email, meetings and chats, keeps every deal's stage, next step and date true, and works the next step for you. Free 3-day trial.
Start free trial →