Customer database and CRM for small business

One customer. One useful history.

Join useful enquiries, bookings, orders and follow-up without building a data warehouse you do not need. A focused customer-record system is usually £1,500 - £4,000.

Build an example record Spreadsheet or CRM?

Improve your current CRM, connect one to the website or build a focused private system. Migration and external-product access are checked before the quote.

Customer recordsynthetic example

CustomerAlex Morgan

alex@example.test · telephone preferred

Follow-up ready

Enquiry receivedwebsite form

Call bookedThursday, 11:00

Next action ownedone current record

Next actionPrepare for discovery callOwner: Ernest

One personmatched across useful activity

Minimumfields with a current purpose

Ownedstatus and next action

Controlledroles, export and retention

No signup and no data saved

Four incoming places. One current customer.

Choose a pretend activity and add it to Alex Morgan’s synthetic record. The example shows the source, useful detail, owner and next action. It does not send, store or import anything.

Incoming workChoose an activity

Website form

Asked about a six-page website

Budget and preferred launch month captured from the approved enquiry fields.

Private business viewAlex Morgan

synthetic

Alex Morganalex@example.test

telephone preferred

StatusNew contactOwnerUnassignedNext actionReview incoming activity

Choose an incoming activity to see how it changes the record.

What disconnected lists cost

The name is recorded. The relationship is missing.

The same customer can exist in an inbox, booking diary, order list and spreadsheet under slightly different details. Staff lose context, duplicate follow-up and keep information with no useful purpose. A dependable record matches the person, shows the source, names the next action and limits what each role can see.

Duplicate

One person becomes four contacts

Small spelling and address differences hide the shared history.

Follow-up

Nobody owns the next step

An enquiry can be visible to everyone and still answered by nobody.

Access

Every export exposes everything

Useful role boundaries disappear when the only control is a shared file.

Purpose

Customer becomes subscriber

A service relationship does not automatically create a marketing preference.

The minimum useful record

Enough context to act. No fields just in case.

A good CRM is not measured by the number of boxes. Each field needs a source, purpose, owner and useful life.

The record helps somebody make the next correct decision, then makes review, export, correction and deletion possible.

01
IdentityReliable match and contact route
02
HistoryDated activity with its source
03
WorkCurrent status, owner and next action
04
PreferencesService and marketing choices kept distinct
05
ControlRoles, retention and an activity trail

Choose the lightest dependable answer

Spreadsheet, connected CRM or private system.

Best for a small business that has outgrown one careful spreadsheet or cannot see the complete customer relationship across website enquiries and operational systems. Ernest can improve an existing CRM, connect one to the website or build a focused private system when off-the-shelf software would add more complexity than value.

01One careful owner and a small list

Shared customer list

A clean spreadsheet or simple record can be enough when ownership and follow-up are already clear.

Do not replace a tool that still works.

02Activity arrives from several routes

Connected CRM workflow

Keep or select a CRM, connect the useful routes and make status, ownership and next action consistent.

The usual answer for growing small businesses.

03The work itself is unusual

Bespoke operational system

Build the exact pipeline, roles and business actions when standard products force costly workarounds.

Useful only when the workflow earns the complexity.

One record from arrival to review

Capture, match, route, review.

Ernest maps the minimum useful fields and real workflow first. New activity is matched to the right person, added to a dated history, assigned an owner and turned into a visible next action. Permissions, marketing preferences, exports, retention and deletion are designed as operating rules rather than left as admin chores.

01
Capture
Collect only agreed fields
The source and purpose travel with the activity.
02
Match
Find the current person
Reliable identifiers and review rules reduce duplicates without unsafe automatic merges.
03
Route
Name the owner and next action
Status is useful only when somebody knows what should happen next.
04
Review
Correct, retain, delete or anonymise
Purpose and policy determine what remains after the work ends.

Connections checked before the quote

Keep useful context. Leave the clutter behind.

Ernest checks the existing website, CRM plan, export, API, permissions and failure route before promising a live connection. External product fees and access remain visible.

Website forms and enquiriesBookings, orders and paymentsOne customer historyEmail and calendar follow-upAccounting export or operational system

Duplicate and conflicting matches reach a review queue

A failed connection keeps the original source recoverable

Bulk export and destructive actions have named permissions

Useful data has operating rules

Know why it is kept. Know when to review it.

The system can support your privacy process, but no database can make a business compliant by itself. Purpose, lawful basis, customer information and retention decisions remain yours to confirm.

MinimiseAdequate, relevant and limited fields

SeparateService history is not marketing permission

ProtectRoles follow tasks, not convenience

ReviewRetention is tied to a documented purpose

Current UK guidance says personal data should be adequate, relevant and limited to what is necessary, and should not be kept indefinitely just in case. The build turns your chosen rules into practical controls.

Real private-system proof

Built around the work, not a generic dashboard.

Ernest built a private Projects CRM in React and Node that orders work by priority and creates invoices from the same operational record. It is a private system, so there is no public login presented as a demo.

Read the Projects CRM record

Projects CRM20+active projects managed in one tailored system

A private CRM that orders projects by importance and writes invoices from them.

React · Node · private infrastructure

Acceptance is an awkward record handled well

Test the exceptions before people depend on it.

01Duplicate personA likely match is reviewed instead of silently merged.

02Simultaneous editsOne staff change does not quietly erase another.

03Changed detailsCorrection preserves a useful dated activity trail.

04Marketing withdrawnFuture campaigns respect the current preference.

05Retention reviewDue records can be found and handled according to policy.

06Connection unavailableIncoming work is recoverable and clearly marked for retry.

Customer records and CRM price

A range with visible reasons.

The written proposal confirms the records, workflow, roles, migration, connections, acceptance tests and handover before work starts. The timeline follows that audit rather than a generic software promise.

See all website and system prices

Typical one-off build£1,500 - £4,000timeline quoted after record and workflow audit

Minimum useful record and workflow map
Roles, preferences and retention controls
Agreed website or system connections
Migration test, acceptance tests and handover

Price rises with messy or several data sources, complex duplicate rules, custom pipelines, many roles, detailed reports, sensitive records, external APIs or business-critical actions.

Standalone support£35 - £45/moorRun Growthincluded in £199/mo

Support is optional. CRM, email, hosting, automation or other providers may charge their own fees directly.

Before choosing a CRM

Customer record questions.

Is a spreadsheet enough for customer records?

It can be. A carefully owned spreadsheet may be the right answer when one person maintains a small list and there are no connected workflows or sensitive permissions. A CRM becomes useful when the same customer appears in several systems, multiple people need a current history, or follow-up is being missed. I will not recommend a larger system merely to replace a spreadsheet that already works.

Can you improve or connect the CRM I already use?

Yes, if the product provides suitable access, exports or an API. I first check ownership, plan limits, authentication, available fields and failure behaviour. The useful answer may be a website connection, a simpler workflow inside the existing CRM, a careful replacement, or no migration at all.

Can old customer records be imported and deduplicated?

Yes. Before import, we agree the reliable identifiers, required fields, duplicate rules, incomplete-record treatment and a recoverable test batch. Poor or unnecessary data is not copied automatically. The scope and price depend on the source format, volume and condition of the records.

Who can see and change a customer record?

Access is based on real roles and tasks. A team member may only need contact details and the next appointment, while an owner may need exports, deletion controls and configuration. Sensitive fields, bulk exports and destructive actions can have tighter permissions and a dated activity trail.

Does adding a customer give permission to send marketing?

No. A service enquiry, booking or purchase and a direct-marketing preference are different purposes. The record should show the source and current preference, support withdrawal, and keep marketing automation from treating every customer as subscribed by default.

How long should customer records be kept?

There is no single retention period for every field and purpose. You decide and document what is needed for service, contracts, tax, disputes or other obligations, then review, delete or anonymise information when that purpose ends. The system can make those review dates and actions practical, but it does not replace legal or accounting advice.

Bring one list and five real examples

Find the smallest system that keeps the history useful.

Show Ernest where customer activity arrives, what somebody needs to do next and which current tool causes the problem. You will know whether to tidy the existing process, connect a CRM or build a focused private system.

Discuss your customer records Explore every system and add-on Email or telephone only. No obligation and no CRM reseller pitch.