A CRM database is one shared record of everyone you sell to and everything that happened with them. Keep the structure small, the fields strict and the updates fast.
- Five core objects cover most small businesses
- Picklists beat free text for anything you want to report on
- Every record needs one owner and a next step
A CRM database is the shared memory of your sales and service. It holds the people you deal with, the companies they work for, the deals you are chasing and every call, email and meeting along the way. One place, one version, visible to the whole team.
A spreadsheet can hold the same rows. The difference is structure and history. A CRM database links records together, keeps a timeline for each one and lets you ask questions across all of them: which deals have had no contact in 30 days, which customers bought twice, which lead source actually closes.
What goes in a CRM database
Most small businesses need five kinds of record, often called objects. Start with these and add more only when a real question needs them.
| Object | What it represents | Key fields |
|---|---|---|
| Contact | A person you talk to | Name, email, phone, role, owner, consent |
| Company | The organisation they belong to | Name, size, industry, location |
| Lead | Someone who might buy, not yet qualified | Source, status, interest, created date |
| Opportunity | A specific deal with a value | Stage, value, close date, next step |
| Activity | Something that happened | Type, date, note, linked records |
Contacts and companies are who. Leads and opportunities are what you hope will happen. Activities are what actually happened. When those three layers are linked, anyone on the team can open a record and understand the situation in thirty seconds.
Leads versus contacts
This is where many setups go wrong. A lead is unqualified: a form fill, a business card, a name from an event. You don't know yet whether they need you. A contact is a known person you have a relationship with.
Keep leads separate until someone qualifies them. Then convert the lead into a contact, a company and, if there is a real deal, an opportunity. This keeps your contact list clean and your pipeline honest.
How to structure it for a small team
Good structure is mostly about saying no. Every extra field is one more thing someone has to fill in, and one more thing that will be empty when you need it.
- Use picklists for anything you report on. Lead source, industry, stage and status should be dropdowns, not free text. 'LinkedIn', 'linkedin' and 'LI' become three sources otherwise.
- Make few fields required. Name, one way to reach them, owner and source. Everything else is optional until it matters.
- One owner per record. Shared ownership means no ownership. If two people care, one owns it and the other is a follower.
- Every open opportunity has a next step and a date. A deal without a next step is not a deal, it is a hope.
- Define your stages in writing. 'Proposal sent' should mean the same thing to everyone, with a clear rule for moving in and out.
Keeping the data clean
A CRM database decays. People change jobs, emails bounce, companies merge. Say you have 2,000 contacts and a modest share change role each year: within a couple of years a noticeable part of your list points at the wrong person. That is why cleaning is a habit, not a project.
- Block duplicates at entry. Match on email for contacts and on website domain for companies.
- Review bounced emails monthly and update or archive those records.
- Archive, don't delete. Old records keep history and help with reporting.
- Run a quarterly check on opportunities with a close date in the past. Either update them or close them as lost.
Activities: the part most teams skip
Contacts and deals get entered because someone has to. Activities get skipped because nobody notices when they are missing. Yet the activity timeline is what makes a CRM database worth more than a contact list. It tells you who spoke to the customer last, what was promised and what happened after.
Log the essentials only: calls, meetings, emails sent from the CRM and key decisions. A one-line note is enough. 'Wants a quote for 12 seats, budget approved in April' is more useful than a perfect transcript nobody reads. Link every activity to a contact and, where there is one, to the opportunity.
Reports worth building first
A database earns its keep through the questions it answers. Small teams rarely need dozens of reports. Three or four, looked at every week, change more than a wall of charts nobody opens.
- Pipeline by stage: how much value sits at each stage, and whether it is moving.
- Deals with no next step: the list to clear every Monday.
- Leads by source and conversion: where good customers actually come from.
- Records per owner: who is overloaded and who has room.
Spreadsheet or CRM database?
A spreadsheet is fine for a list. It breaks the moment you need history, links between records or more than one person editing at once. Signs you have outgrown it: you keep a separate tab for notes, you colour-code rows to show status, and two people have different versions of the same file.
Moving over is easier than it looks. Export the sheet, clean the columns into the five objects above, map each column to a field and import. Most of the work is deciding what to drop.
Make updating fast, or it won't happen
The best structure in the world fails if updating it is slow. Salespeople will skip a form with twelve fields. They will not skip typing one line. In Salesformics, the GX Box command bar lets you type new deal Acme 4,500 close end of month or log call with Priya, send pricing and the right records are created and linked.
Speed also matters for reading. A record page should show the owner, the next step and the last three activities without scrolling. If people have to hunt for context, they will ask a colleague instead, and the database stops being the source of truth.
Whatever tool you use, test it with the real daily tasks. If logging a call takes longer than making it, people will stop logging calls.
A one-week setup plan
- Day 1: list the questions you want the CRM to answer. Five is plenty.
- Day 2: define the five objects and only the fields those questions need.
- Day 3: set picklists, stages and owners. Write the data dictionary.
- Day 4: import and de-duplicate your existing lists.
- Day 5: build one dashboard that answers your top question, and start using it in the weekly meeting.
Questions
Is a CRM database the same as a CRM?
The database is the data layer: records, fields and links. A CRM is the software around it, with views, reminders, reports and automation. You can't have a useful CRM without a well-structured database underneath.
How many fields should a contact record have?
As few as your reports need. For most small businesses ten to fifteen fields on a contact is plenty, with only three or four of them required.
Should I keep customers who left in the CRM?
Yes. Mark them as former customers rather than deleting them. Their history helps with win-back campaigns, churn analysis and spotting patterns in who stays.
