Digital Foundations

Build a simple customer database

You probably already have hundreds of customer details. The problem is that they’re scattered across your phone, inbox, accounting software and old messages.

You don’t need an expensive CRM. You need somewhere simple to keep track of the people who have already trusted your business. Let’s put the useful information somewhere you control.

Build my database Back to the DigitalIQ library

Your customers are an asset too.

A customer isn’t just someone who paid an invoice. They may:

need your service again
know someone who needs your service
need preventative maintenance
have bought something that requires servicing
become a long-term client
leave a review
refer someone else

But none of that is very useful if you can’t easily find them.

The real goal

The goal isn’t to collect more data. It’s to make the data you already have useful.

You don’t need a CRM. Let’s call it what it is: a list of customers.

The word “CRM” can make this sound much more complicated than it is. For a small trade or service business, you might only need:

Name + contact details + what they bought + when you last dealt with them + what happens next.

That’s enough to start. You don’t need an expensive CRM platform. This guide uses Airtable because it’s easy to understand, flexible, and has a free tier that’s suitable for getting started.

Open Airtable

Airtable’s features and free-plan limits can change, so check the current plan before building your system.

03Step 1

Create your customer list

Create a new Airtable base. Call it CUSTOMERS. Then create these fields:

Field	Type	Why you need it
Customer Name	Single line text	Who they are
Mobile	Phone number	Contact
Email	Email	Contact
Service	Single line text	What you did for them
Last Job Date	Date	When you last dealt with them
Status	Single select	Current / Past / Follow-up
Next Contact	Date	When you might need to contact them
Notes	Long text	Useful context

You don’t need to perfectly migrate every customer you’ve ever had. Start with your last 20 customers.

Useful beats perfect

Don’t spend six hours making the database perfect. Spend 20 minutes making it useful.

You already have most of this.

Xero / accounting software

Look at recent invoices and identify the customer name, contact details, service and date.

Phone

Look at recent customers you’ve actually dealt with.

Search for recent quotes, invoices and job confirmations.

Existing spreadsheets

Import the useful information.

Paper records

Start with the customers who are most valuable or most likely to need you again.

Stick to your own customers

This is about the customer relationships and records your business already has. Don’t scrape, purchase or import personal information without appropriate permission or a lawful basis.

Don’t migrate your entire business.

Your first version can contain 20 customers. That’s enough to prove whether this is useful.

Add 20 recent customers
Add their contact details
Add what service you provided
Add the date of the last job
Add anything you know they may need in future
Save the database

Congratulations. You now have a customer database.

The important column: “When might I have a reason to contact this person again?”

Add that one question to every record. This is where the database starts becoming useful.

ElectricianSmoke alarm check → 12 months

HVACAir conditioner service → 12 months

PlumberHot water system → maintenance/replacement lifecycle

Pest controlFollow-up treatment → 3 months

BuilderMaintenance/warranty follow-up → relevant date

PTClient hasn’t attended → follow-up

These are examples only — follow the intervals set by the manufacturer, your professional guidance or your own business. Don’t invent reasons to contact people. Record legitimate reasons that already exist in your customer relationship.

07Step 2

Create a “Next Contact” view — now make the database useful.

In Airtable, create a new view called FOLLOW UP. Filter it so it shows customers where Next Contact is today or overdue.

Instead of scrolling through your phone trying to remember who needs a call, you now have a list.

Monday3 customers to contact.

Tuesday2 customers to contact.

Next month8 customers due for maintenance follow-up.

This is the beginning of a customer system

A simple view that answers “who should I contact today?” is worth more than a complicated CRM nobody opens.

Don’t automate it yet. Use it manually first.

This is important. For the first couple of weeks, simply look at your Follow Up view and contact people yourself. Learn:

what reminders are actually useful
what customers respond to
what information you’re missing
what you keep doing repeatedly

Then you can decide whether a particular process is worth automating.

Manual → Proven → Automated

The DigitalIQ principle

Don’t buy software to automate a process you haven’t understood yet.

What this can eventually power. Now things get interesting.

Customer databaseThe foundation underneath everything
Job complete → Review requestA finished job triggers the ask
Time for maintenance → ReminderA due date triggers a helpful nudge
New customer → OnboardingA welcome that sets expectations
Customer hasn’t returned → Re-engagementA reason to reconnect
Customer needs something else → Helpful follow-upRelevant, not random

The database isn’t the exciting part. It’s the foundation underneath the other systems.

Your data should be yours. Know where your customer data lives.

If your business relies on customer information, you should know:

where it is stored
who has access
how you can export it
what happens if you change software
whether you can take it with you

This doesn’t mean every business needs to avoid commercial software. It means: don’t outsource your understanding.

Ownership is about control, not location

A system can be hosted somewhere else and still be an asset you control — as long as you understand the ownership, access and portability.

Five-minute maintenance. Keep it alive.

A customer database is only valuable if it stays reasonably current. Once a week:

Add new customers
Update completed jobs
Add useful notes
Check upcoming follow-ups
Remove obvious duplicates

That’s it. Don’t turn this into an administration project.

Your customer database is good enough when...

I can find my customers
I know how to contact them
I know what I did for them
I know when I last dealt with them
I can see who needs follow-up
I know where the data lives
I can access/export my data

Simple beats sophisticated

A short list you actually use beats a complicated system you avoid.

Now give your database a job.

You’ve created a list of customers you control. The next step is deciding what useful things should happen after a customer deals with you.

Job completeReview request

New clientOnboarding

Maintenance dueReminder

Customer hasn’t returnedRe-engagement

You’ve already seen this pattern in action. The review request system guide shows how one trigger — a completed job — becomes an automatic, useful action.

Next: Build a simple follow-up system

Build assets. Not dependencies.

Your customer list is a digital asset.

Start simple. Keep it useful. Make sure you can control it.

You don’t need to buy a platform to know your own customers.