Single source of truth: how to put your business data in one place
Your client's phone number says one thing in the booking tool and another in the invoicing app. A single source of truth fixes that: it is one place where each client, quote, invoice and booking is stored once, and every tool you use reads from it. For a business of your size, that place should be one database you own, not a platform you rent. The rest of this page argues for that answer and shows how to get there.
What a single source of truth means for your business
Wikipedia's entry gives the precise rule: every data element is "mastered (or edited) in only one place." In plain words, each record has one home. Your client's phone number lives in one row, and the booking tool, the invoicing app and your calendar show that row instead of keeping their own version. When the number changes, you change it once.
You will meet the same idea under other names. Shopify's guide calls it a golden record or master data, and it is the same rule: one copy is the master, and every other copy reads from it and is never edited on its own.
Most pages written about this term are for large companies, or they sell a data platform or a knowledge base. A business of 1 to 20 people does not need a platform team. It needs one database that holds its records, and that it can open and export.
This page is by the clevrstart team. We run our own business on one database we own, and we moved everything into it on 2026-08-06.
What goes wrong without one
A client calls you with a new number. You change it in the booking tool, and the next invoice reminder still goes to the old one. That is life without a single source of truth, one small mismatch at a time.
Atlassian defines a single source of truth as "a central repository where all team members can find the most accurate and up-to-date information about a project or process." We agree as far as it goes. It does not say which repository, or who holds it, and for a small business those are the two questions that matter. None of the sources we read answers them for a business of your size; this page answers both from the system we run our own business on.
Three illustrations, not measured cases. We have not measured how often these happen or what they cost anyone, and we state no figure.
01
The booking
A client books online and then calls to book the same visit. The calendar shows two appointments, and the invoice knows about one.
02
The quote
You change a line on a quote after a call. The email shows the first price and the PDF shows the second, and the client asks which one is real.
03
The Sunday evening
The week's bookings sit in the calendar and the week's invoices sit in the books. Matching them by hand is the job that waits for the weekend.
A pass is one open file, such as CSV, per kind of record, with its links kept, so each invoice still names its client. A fail is a PDF per record, a file of totals with no lines, or a message that tells you to contact support. Our page on what a business operating system is sets out the ownership test.
To run it today, start with your clients. Export them from the tool that holds them and open the file in a spreadsheet. A passing file has one row per client and every field you typed in. If the tool fails, ask the vendor in writing for a full export before you put more records into it.
Our worked example: one database we own
We run our own business on one database we own, on Postgres, an open-source database. Every client, quote, invoice, booking and article of ours sits in it. This is our own system, not a client's, and we have not measured a client's results.
Counted on 2026-10-14, it holds 483 tables of business records and site content, 47 for the content engine, 11 for the agents service and 6 for bookings. Before the move on 2026-08-06, each of our apps had its own database and its own login tables. Since that date there is one database. Since 2026-08-18, one users table has served every app. Agents reach the data through one door: an API key checked on every request.
Before and after our move into one database
| Before 2026-08-06 | Since 2026-08-06 | |
|---|---|---|
| Databases | Each app had its own database | One database we own, on Postgres |
| Login tables | Each app had its own login tables | One users table for every app (since 2026-08-18) |
| How agents reach the data | Not recorded | One door: an API key checked on every request |
We built our own tools after using most tools on the market. When we build for a client, the same rule holds. As our hosting page notes, "Where your data lives is written down for your project, not assumed."
How to get there in four steps
You can start without buying anything. The order matters: records first, tools last.
01
List each record and where it lives
Write one line per kind of record: clients, quotes, invoices, bookings. Next to each, name every app that holds a copy. A line with two apps on it is a record without one home.
02
Choose one database you can export from
Run the ownership test before you commit. The database that passes becomes the home for every record on your list.
03
Connect the tools you keep
QuickBooks, your calendar and Google Business Profile can stay. They read from the one place instead of keeping their own copy, and the data flows to them from it.
04
Check the records once a month
Atlassian recommends auditing for duplicate or conflicting information. For a small service business, compare two pairs: every finished booking should have an invoice, and every client in the invoicing app should have the same name and number in the booking tool. A record that shows up two ways goes back to its one home.
For step one, a three-column list is enough. Here is the shape, filled in for a typical small service business:
Your records, one line each
| Record | Where it lives now | Its one home |
|---|---|---|
| Clients | The booking tool, the invoicing app and your phone's contacts | The one database you own |
| Quotes | Your email and a spreadsheet | The one database you own |
| Invoices | The invoicing app | The one database you own |
| Bookings | The booking tool and your calendar | The one database you own |
The monthly check, in four lines:
- Every finished booking has an invoice.
- Every client has one name and one phone number in every tool.
- Every accepted quote has a booking or a project.
- One export still opens in a spreadsheet.
This is the work we do for clients: "We connect the apps you keep and gather their data in one place you own."
Where to go deeper
Our page on how to organize business data gives you a record inventory sheet to start with. Our page on what a small business database must do gives seven checks to run on any option. Our page on centralized data shows what changed when we put our own business in one place. Before you buy or build anything, we recommend the software development cost calculator.
"Why I put my whole business in one database" covers a second brain for business. "Give an agent your business context through one door" covers how to connect ai to business data. "What our software stack costs a month" covers how to reduce saas costs. "Own your content: one CMS behind every site" covers how to own your content. The column titled Grow from structure before you buy clients covers the order of the work, and "Zapier alternatives, and when you need none" covers the zapier alternative question.
Start with your records this month
This month, write down your records: clients, quotes, invoices and bookings, and where each one lives. That list is the first step, whether you do the rest yourself or with us.
If you want help, our services page describes the first step as a call: thirty minutes. Scope, feasibility, complexity, then a number. The call and the number are free; you owe nothing until you accept one.
Whatever you decide, hold every tool to the ownership test. If you cannot export everything you put in without asking, it is not your single source of truth.
Questions about a single source of truth
01What is a single source of truth for a small business?
02How do I test whether a tool's data is really mine?
03How do I set up a single source of truth without buying anything?
04What should my monthly data check cover?
Start
Book a free call
Thirty minutes. Scope, feasibility, complexity, then a number. The call and the number are free; you owe nothing until you accept one.
