Does your small business need a CRM? The honest answer

The three signs you already need one

It isn't team size or revenue. It's these three, and one is enough to make it worthwhile:

1. The important detail lives in someone's head. If your best salesperson goes on holiday and nobody knows where things stood with the client who was about to sign, you don't have a sales problem: you have a memory problem. That's the most expensive case and the most common.

2. You find out late that a client went cold. When follow-up depends on someone remembering, the one who doesn't remember goes unnoticed until the client has already bought elsewhere.

3. You have three places to look for the same thing. The quote is in email, the agreement in a WhatsApp thread and the phone number in a spreadsheet. Every time someone asks "where did we land with so-and-so?", someone loses ten minutes.

If none of the three sounds familiar, you don't need a CRM yet. Keep this article for when one does.

What a CRM actually solves

The catalogue promise is "increase your sales". It isn't false, but it isn't what happens either. What happens is duller and more useful: information stops getting lost. The conversation with the client is written down, the next step has a date and an owner, and anyone on the team can pick it up without calling whoever handled it.

The sales increase, when it comes, is a consequence of that: you stop losing to forgetfulness what you had already won through work.

The real prices, no fine print

This is where most articles go vague, so here are the numbers:

Look at the HubSpot row. The licence is what they advertise; the mandatory onboarding is what they don't. It's a real, one-off cost that on Professional with a partner sits around 30,000 pesos. Always ask about it before signing.

When an off-the-shelf CRM is the right answer

This runs against my own commercial interest, but it's what I believe:

• Your sales process is standard. Lead, quote, follow-up, close. If that describes you, free HubSpot will do the job and you have no reason to pay me.
• You need to start tomorrow. An off-the-shelf CRM is configured in an afternoon. A custom one takes weeks.
• You're fewer than three people. The free plan is more than enough, and the discipline of using it matters more than the tool.
• You don't yet know how you sell. If the process changes every month, building software on it is building on sand. Use something free, learn your process, then let's talk.

If you're in any of those four cases, save your money. Genuinely.

When a custom one is worth it

The argument in favour isn't the licence price. Zoho is cheap and HubSpot gives the basics away; competing on price there would be foolish. The argument is different:

When your process doesn't fit the mould. This is the most frequent case. You sell by routes and visits, not by funnel. You work on consignment. You invoice by construction progress. You have an approval flow that exists in no catalogue. When you adapt your operation to the tool instead of the other way round, you end up with a half-filled CRM and a spreadsheet beside it — which is exactly the place you were trying to leave.

When what you'll pay in rent, forever, exceeds what building it once costs. Run the numbers with your user count over five years. Sometimes it favours the off-the-shelf option and sometimes it doesn't; it depends on headcount and growth.

When the data has to live on your server. Because of regulation, because a client demands it, or simply because you don't want your entire client book on a third party's server.

When you already have systems that must talk to each other. Connecting your invoicing, your inventory and your CRM is where the money goes in off-the-shelf CRM integrations. If you're going to pay for that development anyway, building the whole piece sometimes works out better.

What I build, and you can try it now

I have a CRM running on sample data: companies, contacts, follow-ups, a task kanban and a calendar, with each client's full record one click away. It has real sessions and two-factor authentication — it isn't a mockup. It's linked from the home page; go in and break it if you like: every visitor gets their own copy.

If after trying it you think your process fits in HubSpot, use HubSpot. If you can see it doesn't, here's how I work.

Frequently asked questions

Can I migrate from a free CRM to a custom one later?

Yes, and it's the path I recommend. Start free, learn your process over six months or a year, and when you know exactly what doesn't fit, build that. Exporting contacts from HubSpot or Zoho is trivial.

How long does a custom CRM take?

Six to twelve weeks depending on scope, and you see the application working from the first one. Migrating your current data is included in that time.

What if my team doesn't use it?

That's the real risk, and the tool doesn't solve it. A CRM nobody fills in is worse than a spreadsheet, because it creates the illusion that the information is there. If deals close over WhatsApp, the CRM has to read WhatsApp; if anything has to be typed twice, nobody will do it.

Is the data mine?

In a custom one, yes: database, backups and code are handed over. In an off-the-shelf one it's yours too, but you live on their server and under their terms — and if you stop paying, access ends even though the data remains yours.

Does it work for a service business rather than a product one?

Yes, and usually better. In services follow-up is everything and the cycle is longer: that's exactly where things get lost to forgetfulness.