Almost every free CRM caps the thing that makes a CRM work
A free CRM tier is not a gift. It is the top of a funnel — a reasonable way to sell software, but you should read it as one. The restrictions come in four shapes: a ceiling on users, a ceiling on stored records, features that exist only on the next tier up, and a definition of "free" that quietly ends at a term boundary.
The seat cap is the one teams notice, because somebody has to decide who gets a login. The record cap does the most damage, because it negotiates against the reason you wanted a CRM. Feature gating is the easiest to miss: reporting, permissions, audit history and workflow automation commonly sit above the free line. A time limit is straightforward: free for a while, then read-only, or converted to a smaller plan without announcement.
We are not going to quote specific limits. Vendors re-cut their free tiers regularly, sometimes without much fanfare, and a number that was accurate last year is worse than none at all: it looks like evidence and it is out of date. Check the current terms on the vendor's own pricing page, and read the limits rather than the headline. "Free" tells you about price, not fit — and the only question that matters is whether the limit lands on something your team depends on.
Why a per-seat cap quietly kills a CRM
A CRM is not a personal productivity tool. It is a shared record, and its value comes from being the one place a customer exists completely.
Now put a seat cap on it. Eleven people touch customers — sales, support, accounts, the founder — and you have three logins. What happens next takes about a fortnight.
- The eight without a login keep working as before. Spreadsheets, shared inboxes, private notes, memory — nothing about their behaviour changed, because nothing about their tools did.
- The three with a login stop trusting what they see. Their view is partial by construction, so they keep a private record alongside the official one; the CRM becomes a summary rather than the source.
- Someone shares a login. The obvious workaround is worse than it looks: activity history credits one person's work to another, and a wrong audit trail is more dangerous than none, because people rely on it.
- Seat allocation becomes political. Logins go to seniority rather than to the people who speak to customers.
You end up with the cost and ceremony of a CRM and the fragmentation of not having one: ask what was promised to a customer last month and nobody can answer without opening three other applications.
The point is structural, not moral. A CRM holding a fraction of the customer conversation is one nobody trusts, and an untrusted CRM gets abandoned — usually without a decision, just a drift back to the spreadsheet. Coverage is the feature; dashboards, forecasting and automated summaries are downstream of the record being complete.
Why a record cap is worse than it looks
A ceiling on contacts prices your growth. The deeper damage is what it teaches people to do: when records are scarce, teams delete old ones to make room, keep the overflow in a spreadsheet, and skip the contacts that feel marginal — the supplier, the referral partner, the prospect who went cold eighteen months ago. The CRM becomes an archive of customers who already mattered, which is a list you could have written from memory. The records you need a system for are the ones nobody knows are important yet.
Free tiers rarely fail on capability. They fail on coverage — a record is only as trustworthy as the number of people allowed to write to it.
What a CRM actually has to do
Strip away the feature matrix and four things decide whether a CRM works. Everything else is a refinement of them.
- One record per customer. One organisation, one owner, one place the relationship lives. The test: two colleagues search for the same customer and land on the same record, not two near-identical ones.
- A pipeline whose stages mean something. A stage is a claim about what has already happened, not a hope about what might. Each needs a definition you could argue about and win — what must be true before a record moves — and few enough stages to hold in your head. Five to seven, not twenty.
- Activity history in one place. Calls, emails, meetings, notes, proposals, the decision to discount. The test: if the account owner goes on holiday, can a colleague pick the relationship up without asking them a single question?
- A follow-up that does not depend on memory. Every open record carries a next action and a date — not a status, not a colour. The test: on Monday morning there is a list of what is due, and it is short enough to read in one sitting.
Notice what is not on that list: reporting, forecasting, lead scoring, dashboards. Those are useful once the foundations are true and decorative before. Most CRM failures are not feature failures at all — they are coverage and discipline failures wearing a feature costume.
There is a layer above this where the manual work hides: reminders someone has to type, tasks someone has to reassign, updates copied between systems. That layer is automatable once the record underneath it is sound, and it is the part we work on in AI automation.
Our CRM, honestly described
We built a CRM and we run it ourselves. It is free, permanently, with no cap on contacts and no cap on users. Not a trial with a clock on it, not a free plan that expires, not a tier that stops making sense at eleven people.
Access is by request rather than instant signup. There is no self-serve URL to click: we set each account up with the team that asked for it. That is a deliberate trade, and the honest part of this offer.
What you get, and what not to expect
You get the product described above, with unlimited users and unlimited contacts, at no cost, without a card and without a licence review. You also get us: we built it, we run it, and the people who answer your email are the people who can change it — there is no support portal in between.
What you should not expect is a commercial agreement dressed up as a free product. Specifically:
- No enterprise service-level agreement. We will not publish a response time we cannot guarantee, and there is no contractual uptime commitment behind this. If you need a signed guarantee, this is not the tool for that requirement.
- No bespoke development inside the free tier. If you need custom objects, a specific integration or a workflow that does not exist yet, that is a project rather than a support request — exactly the kind our software development practice takes on, quoted separately.
- Not every feature of a large commercial suite on day one. This is a CRM built by an engineering team that uses it, and it does the four things above properly. If something you need is missing, tell us.
"Forever" here means the terms do not move underneath you: no clock, no cap, no upgrade path you are being nudged along. It does not mean we have solved every CRM problem, or that the product will never change. It means the price is not a lever.
Moving off spreadsheets without stalling the week
Most spreadsheet migrations do not fail; they half-finish, and the team runs both systems forever. The sequence that avoids that takes about a fortnight of part-time work.
What the spreadsheet column usually is What it should become
-------------------------------------- ----------------------------------------
"Company" - free text, many variants One organisation record, one owner
"Contact" - a name and an email A contact linked to that organisation
"Status" - whatever each person typed A pipeline stage with a written rule
"Notes" - a year of prose Dated activity records, oldest first
"Next step" - frequently empty A next action and a due date, always set
Any row with no owner Decide the owner before anything moves- Start with one team and one pipeline. Not the whole company, not every process — one group of people who already talk to each other, one journey from first contact to paid.
- Write the stage definitions before you touch the data. One sentence each, agreed out loud, including what disqualifies a record. Teams skip this, and it decides whether the pipeline is ever believed.
- Decide what identifies a customer. Company name plus domain, or company name plus billing entity. Pick one rule and apply it everywhere; retrofitting identity rules onto a full database is miserable.
- Move the sheet in, then deduplicate on purpose. Expect duplicates and settle the merge rule in advance — oldest record wins, or the one with activity attached.
- Put a next action on every open record. All of them, in one sitting. A pipeline without next actions is a report; a pipeline with them runs the business.
- Run in parallel for one week with the sheet read-only. Read-only is the important word: a sheet that is still editable is still the real system, and everyone knows it.
- Retire the sheet, then watch for workarounds. The moment of truth is not the migration; it is the first person who cannot find what they need and reaches for a new spreadsheet. Fix that cause, not the symptom.
- Review at thirty days and delete fields. Whatever nobody fills in or filters on is noise; a CRM that asks for eighteen fields gets four filled in badly.
Who should not use it
It is cheaper for both of us if this part is clear before you move any data.
- Teams whose CRM is really a custom application. If you need deeply custom objects, elaborate permission models, or a data model that does not resemble customers, organisations, deals and activities, you are describing a software project — and bending a general CRM into that shape costs more than building the right thing.
- Regulated workflows that require specific certifications. If your compliance team needs particular certifications or a written data-residency arrangement, raise it in the first email. We would rather tell you we do not fit than have you find out mid-migration.
- Teams that need procurement paperwork. A free product is not automatically an easy one to buy. If your process expects a signed agreement, a purchase order and a security review, say so early and check whether it is workable.
- Teams that need a large integration marketplace. If the CRM has to be the hub for twenty other systems using off-the-shelf connectors, verify your integrations first. Coverage of the customer record is the strength here; catalogue breadth is not.
The pattern is the one this article opened with: unlimited users and unlimited contacts, not unlimited everything.
How to get access
Email info@wethinkdigital.solutions with two or three lines: roughly how many people touch customers, what you use today, and the first thing you would want to move. We will set the account up and help you get the first pipeline into it — usually the difference between a CRM that sticks and one that becomes another abandoned tab.
If you would like the wider picture first, our current offers are the shortest route to what we do and how we work, and the contact page covers everything else.