By the Onsites AI team · Last updated · 4-minute read
The failed CRM is easy to recognize: forty fields, six of them mandatory, two of them accurate, none of them consulted when a customer actually writes in. The CRM that works in a small business is closer to a good waiter's memory — who you are, what you buy, what we promised you, and how the money stands — carried by about ten fields that exist because they answer one question each, at conversation speed. This guide defines the ten (five on the contact, five on the account), the auto-linking that fills them without discipline (the CRM setup guide covers the plumbing), and the two habits that keep them true: capture as the conversation happens, review when the quarter turns.
The structural reason ten fields survive in a small desk is that the work of filling them was never assigned to anyone. The auto-linking does the structural labor: the first thread creates the contact (name, channels, language as given), contacts roll up to accounts, conversations attach themselves to whichever record they belong to, and money events — quotes, orders, invoices — write the account's history in the very act of happening. What remains for a human is the thirty-second class of additions: the role at the buying table noted while the thread is open, the language preference observed once and recorded once, the health flag set when the history makes it obvious. That division is the whole design principle — the machine captures the record; the human contributes the judgment — and it holds because no part of it depends on memory, discipline absent, or a Tuesday nobody has. The setup guide's promise is exactly this arrangement: the CRM builds itself out of the conversations the desk would be having anyway.
1 · Their name as they gave it — not "Client," not the invoice's legal name; the auto-created record pulls it from the thread, and correcting "Michael J." to "Mike" the first time he signs his reply is one of those five-minute habits that compounds for years. 2 · The channels they actually use: WhatsApp personal, email for documents — every thread lives in the same queue anyway (the omnichannel guide's whole argument), and the field records where this person answers. 3 · Their seat at the buying table: decision-maker, approver, blocker, or the operator who relays — sales calls it influence; support just needs to know whether this person can say yes. 4 · Language and formality — the translation guide's register rules start from this field. 5 · The last thing they told us: refreshed by the desk's summaries, this one field is the difference between "who are you again?" and "your March requote — the second one landed well."
6 · What they buy, at what price — not the catalog (that lives in products), but the account's standing shape: the 20ft reorders every March at agreed rates, the 40ft one-off in October. It is the field the quote inherits, which is why the document family stays honest. 7 · The money state: open orders, due invoices, overdue accounts — the trail both finance and support read, because "did my payment go through?" is a support question answered by this exact field. 8 · The open deal and its stage: the negotiation lane (drafted, sent, accepted, declined) so "did we win this?" is a lookup — the chat-to-quote flow writes it automatically. 9 · The promise log: what we committed — the production slot held to Friday, the 40% credit, the prepayment condition — written when promised; a buyer relationship is mostly a list of promises, and this field is where the desk keeps its word. 10 · Health: rising, flat, fading — set as honestly as the conversation history allows, because the quarterly KPI review reads exactly this field when it decides where the next hour goes.
Certain fields fail in recognizable ways, and knowing the failure shape saves a quarter of quiet decay. The manual status ("customer tier") that nobody can define — replaced by the machine's money state, which is at least a fact. The aspirational note ("strategic account" written in year one, never revisited) — health flags earn their place by being set from history, not mood, and the quarterly sweep is their audit. The duplicated data — an address in the contact, the same address in the invoice template, neither updated since the move; the shared-catalog principle (one field, one place, every document quotes it) is the fix, and fields that resist it get deleted rather than maintained twice. The general habit behind all three: whenever a field's truth can come from the desk's own activity — automation, conversations, documents — let it; reserve human keystrokes for what only a human knows, because those thirty seconds are the cheapest information a small business buys.
Fields decay when their maintenance lives somewhere separate from their use. Two habits keep a ten-field CRM breathing, neither costing a meeting. Capture at conversation: the desk's auto-linking does the structural work (contact from thread, account from contact, conversations attached forever); the human habit is smaller — when a thread reveals something the fields don't say ("buys in October," "approver is the spouse," "prefers voice notes"), spend the thirty seconds while the thread is open, because later means never. Review at the quarter's turn: the account list sorted by health, scrolled in one sitting — rising accounts get the relationship care, fading ones get the honest question ("still need us?") before the silence is months deep, and any field that went a quarter without being true gets fixed or deleted. A CRM that stays alive this way is not a maintenance burden; it is the desk's shared memory — and like the waiter's memory, it works because it is small enough to be true.
How many CRM fields does a small team actually need?
About ten that exist to answer one question each at conversation speed — five on the contact (real name, working channels, buying role, language, last context) and five on the account (what they buy at price, money state, open deal, promise log, health). Everything a field can't justify at reply speed is decoration that decays.
What is the single most useful CRM field for support?
The account's money state — open orders, due and overdue invoices — because it is the honest answer to "did my payment go through?" and the quiet precondition of every money conversation. Support reads it, finance trusts it, and the chase ladder runs on it.
Where do the records come from — who does the typing?
The desk's auto-linking does the structure: every conversation creates or attaches to a contact, contacts roll up to accounts, threads live on the record forever. The human habit is thirty seconds while the thread is open — capturing what only that conversation taught.
How does the CRM stay current without becoming a chore?
Capture-at-conversation (thirty seconds while the thread is open, later means never) plus a quarterly health sweep of the account list — rise gets care, fade gets the honest question, stale fields get fixed or deleted. Small, ritual, no meetings.
What makes a CRM field worth keeping?
It answers, at reply speed, a question someone at the desk actually asks about a customer or account — otherwise it is decoration that decays. Ten honest fields maintained at conversation pace beat forty aspirational ones nobody trusts.