A CRM for three reps needs to do three things: track who you’re talking to, track where deals stand, and make it easy to follow up. Everything beyond that is premature.
This isn’t a popular opinion. CRM vendors want you to believe their platform is a strategic operating system from day one. Implementation consultants want you to believe that proper configuration requires a project plan. Neither is true when your team fits in a group chat.
The Only Three Jobs
Job 1: Know who you’re talking to. Every prospect, every conversation, in one place. Not in three inboxes, two spreadsheets, and someone’s notebook. The CRM is the single record of who’s in your pipeline and what you’ve discussed.
Job 2: Know where deals stand. At any moment, you should be able to answer: how many active deals, at what stage, and what’s the expected revenue this quarter? If you can’t answer that in under 60 seconds, the CRM isn’t doing its job.
Job 3: Make follow-up automatic. Not automated in the workflow sense. Automatic in the sense that the system surfaces what needs attention. Stale deals. Overdue tasks. Contacts you haven’t reached in two weeks.
If your CRM does these three things reliably, it’s working. If it does 47 other things but fumbles these three, it’s not.
What to Configure on Day One
Keep the initial setup to an afternoon. If it takes longer, you’re overbuilding.
Contacts: Name, email, company, and source. That’s it. You don’t need 30 contact properties. You need four that every rep fills out consistently. Consistency across four fields beats partial completion across thirty.
Deals: Amount, stage, close date, owner. Four properties again. The pattern is intentional. Fewer fields, higher compliance. Every additional required field reduces the odds that reps update their deals after calls.
Pipeline: Four stages maximum. Something like New, Qualified, Proposal, Closed. The names matter less than the number. With three reps and a small pipeline, you can see every deal in a single screen. That visibility disappears the moment you add substages and parallel tracks.
Tasks: One type. Follow-up. That’s the only task type you need. Create a follow-up task after every meaningful conversation. Set a due date. Review overdue tasks each morning.
What to Skip Entirely
This list is longer than the configuration list. That’s the point.
Lead scoring. Scoring requires historical data to calibrate. You don’t have it. Your three reps can look at each lead and make a judgment call. That judgment call will be more accurate than any scoring model you build with three months of data.
Complex reporting. You need a pipeline view and a list of stale deals. You don’t need a dashboard with twelve widgets. Every minute spent building reports is a minute not spent selling. When you need real reporting, you’ll know — the pipeline view won’t answer your questions anymore.
Workflow automation. Automation codifies a process. You’re still discovering your process. Build automation after you’ve seen the same pattern repeat 20 times, not before.
Sequences and email automation. With three reps and a manageable pipeline, manual follow-up is fine. It’s also better — a personal email from a human outperforms a triggered template at this stage. Save sequences for when volume makes manual follow-up impossible.
Custom objects and integrations. Unless you have a genuinely unusual data model, the default objects (contacts, companies, deals) cover your needs. And every integration you add is an integration you maintain.
The Spreadsheet Question
Some founders wonder whether they need a CRM at all. Maybe a shared spreadsheet works.
The honest answer: a spreadsheet works until it doesn’t, and the transition is painful. The specific moment it stops working is when two reps update the same deal on the same day and you lose information. Or when someone sorts a column and breaks a formula. Or when you hire rep number four and need to figure out assignment.
If you have one or two reps and a short sales cycle, a spreadsheet is fine for now. But move to a CRM before you hire your third rep, not after. The migration gets harder every month you wait.
Most CRM platforms offer a free tier that handles three reps comfortably. The cost isn’t the software. The cost is the time to set it up and the discipline to use it.
The Process Question
“Should we define our sales process before setting up the CRM?”
No. You should set up the CRM and let your process emerge from what you learn. A defined process at this stage is a guess. An educated guess, maybe, but still a guess.
What you should do instead: review your pipeline together once a week. Fifteen minutes. Look at every deal. Ask two questions about each one: What happened last week? What happens next?
After eight weeks of this, you’ll see your actual process. Deals follow a pattern. Certain stages take longer than others. Certain activities correlate with wins. That observed pattern is your process. Document it then.
Building process from observation beats building process from theory every time.
When Things Need to Change
Your 3-rep CRM setup has a shelf life. These are the signals that it’s time to invest in configuration:
- You can’t review every deal in one meeting. Pipeline volume has outgrown the weekly review. You need filtering, views, and probably stage definitions that are more precise.
- A new rep can’t figure out the system in a day. Onboarding complexity means the CRM needs documentation and standardization.
- You’re losing deals to follow-up gaps. Manual task management isn’t keeping pace. Time for automated reminders and maybe sequences.
- The board wants a forecast. “I think we’ll close about $200K” stops being acceptable. Stage-weighted pipeline with defined probabilities becomes necessary.
These inflection points are real, and they arrive faster than most founders expect. The good news: if you kept your initial setup simple, the upgrade is configuration work, not a rebuild.
The Mistake to Avoid
The most expensive CRM mistake at the 3-rep stage isn’t picking the wrong platform. It’s building as if you’re a 30-rep team. Complex configurations create maintenance burden. Fields nobody fills out. Reports nobody reads. Automations that fire into the void.
Simple systems get used. Complex systems get worked around. A CRM your team ignores is worse than no CRM at all, because it creates the illusion of pipeline visibility while the real information lives in inboxes and memory.
Build the minimum. Use it consistently. Expand when the simple version stops answering your questions.
If you want to benchmark where your current setup stands against common failure patterns, the diagnostic scorecard takes five minutes. It’s built for teams at every stage, including teams that are just getting started.
Designate Solutions helps B2B revenue teams build systems that match how they actually operate. If you’re early-stage, the scorecard shows you what to focus on first.
How healthy are your revenue systems?
Take the Revenue Systems Health Scorecard — a 5-minute self-assessment for B2B revenue leaders.
Take the scorecard →Diagnose your own revenue systems → Explore the console