Three phrases arrive at the same place from different directions, and none of them is a product category so much as a description of what somebody wants: one dependable place holding who we serve and what we hold about them. Because the phrases are vague, the market answers them with everything from a spreadsheet template to an enterprise platform. Four questions cut through that range quickly.
Is a record a row, or a thing with a history
The dividing line in this category is whether a client is a row that gets overwritten or an object that accumulates. A row tells you the current state and silently forgets the previous one; an object tells you what changed and when. For a standing relationship the second is what you are paying for, because the questions that matter later are historical: when did this change, who agreed to it, what did we hold at the time. A system that overwrites cannot answer any of them.
Custom fields are where client information software lives or dies
Every practice holds something about its clients that no vendor anticipated: a scheme reference, a renewal month, a jurisdiction, a preferred contact route. Client information software that lets you add those as real fields, filter on them and export them stays useful for years. One that offers a single notes box for everything non-standard turns your most operationally important information into text nobody can query. Ask specifically how many custom fields, of what types, and whether you can filter and export on them.
Who can see what: a question software for client database work must answer fast
As soon as more than a couple of people use the book, access becomes a real question, and it usually arrives urgently: someone leaves, a contractor needs partial access, a client asks who in the practice can see their file. Software for client database work should be able to answer that in a screen. Answering it by reasoning about folder permissions is the state most practices are actually in, and it is the one that produces uncomfortable pauses when a client asks.
Getting out is part of choosing
The value of a customer database system compounds, which is exactly why the cost of leaving one compounds too. Before committing, establish what a full export contains, whether custom fields and history survive it, and whether documents come out with their client associations. This is quick to check and almost never checked, and it is the difference between changing systems in a week and never changing them at all.
Questions people ask about customer database system
How is this different from a CRM?
A CRM optimises the path to a sale. A customer database system is the durable record of people you already serve. The overlap is real but the priorities differ, and CRMs generally treat history as less important than pipeline position.
Is a spreadsheet a customer database?
It works genuinely well while one person maintains it and nothing needs history or per-client access. It fails at concurrency, at history, and at documents, and it usually fails all three at once and without warning.
What should I insist on in a demo?
Add a custom field, filter on it, and export the result including documents. If all three are easy the product is probably sound; if any is awkward, that awkwardness is what your next three years look like.