One source of truth per domain

Walk into almost any construction office and ask a simple question — "What have we spent on that job so far?" — and you'll get three answers. One from the estimator's spreadsheet. One from the accounting software. One from the project manager, delivered from memory with complete conviction. All three are different. All three are defended with feeling. Somewhere, a fourth number exists on a whiteboard.

When one question has three answers, you don't have three sources of truth. You have none. And you can live that way for years, honestly — humans are gifted at working around ambiguity. We ask a clarifying question, apply some judgment, split the difference. Then you introduce AI into the operation, and the whole arrangement collapses on contact, because software does not split differences. It picks one of your three numbers — whichever it happens to reach first — and builds on it with total confidence, at machine speed, hundreds of times a day.

So before the stack, before the agents, before anything with a subscription fee, comes one organizing rule that costs nothing and changes everything: every domain of your business gets exactly one system that owns the truth.

Four domains, four owners

At Nimble Development, the whole company reduces to four domains, each with one owner.

Money lives in the ERP. An ERP — enterprise resource planning software, which is a grand name for an accounting system with opinions — holds the general ledger. Every dollar in or out, every loan balance, every draw, every project's costs. If a number about money isn't in the ledger, it isn't real yet; it's a rumor with a decimal point.

People live in the CRM. The contact database — customer relationship management software — owns every name, number, and relationship: subs, lenders, buyers, the inspector whose cell number you'd otherwise be scrolling eleven months of texts to find. One record per human.

Time lives in the calendar. If a commitment matters, it exists as a calendar event. Not in a text thread, not in someone's head. The calendar is the schedule of record for the humans and — later, when you get to the AI that preps your meetings — for the machine.

Written Plans live in the vault. The vault is nothing fancier than an organized folder of plain-text notes: decisions and why we made them, meeting notes, project write-ups, strategy, standard procedures. Ours runs on a free tool called Obsidian, but the tool matters far less than the rule: thinking that isn't written into the vault is thinking that will be redone from scratch in six months, probably by me, probably annoyed.

Notice what the rule does not say. It doesn't say the owner must be the best system, or the fanciest. It says there must be exactly one, and everyone — human and machine — must know which one it is. A mediocre single source of truth beats two excellent competing ones every day of the week.

Everything else is a view

Here's the part that keeps the rule alive instead of decorative: everything that isn't a source of truth is a view — a window onto the sources, never a filing cabinet of its own.

A dashboard is a view. A weekly report is a view. The morning brief my system sends me is a view assembled from the calendar, the CRM, and the ledger. Views can be beautiful, and they can multiply as much as you like, because they all share one property: they are read-only. Nothing gets stored in a view.

This gives you a wonderfully cheap dispute-resolution mechanism. If a view disagrees with its source, the view is wrong. By definition. No meeting required. Either the view's plumbing is broken or it's stale, but the source is the truth, and you fix the plumbing rather than argue about the number.

And it gives you the write rule, which is where most companies quietly fail: when a fact changes, it changes in the owner and nowhere else. New phone number for a sub? It goes in the CRM — not in the spreadsheet, not in a sticky note, not in the estimate. Change it at the source and every view heals itself. Change it in a view and you've just minted a second source of truth, which is how the three-answers problem got started in the first place.

The same instinct applies inside each system. One of our ten operating principles is "one file, not seven" — when a document grows long, the urge is to split it into pieces for tidiness, and the urge is almost always wrong. Long and searchable beats scattered and lost. Consolidation is the same move as naming a source of truth, just at a smaller scale.

Why AI makes this non-negotiable

Everything above is just good operations, and plenty of well-run companies do it with no AI at all. So why is it the second chapter of a book about AI? Because an AI system is the least forgiving employee you will ever onboard.

Every automated worker you add needs two standing instructions per domain: where to read the truth, and where to write changes. That's it. With named owners, those instructions are one line each, and a machine can follow them perfectly forever. Without named owners, the machine improvises — and Chapter 1.1 — Start with your data covered what machine improvisation does to records: it doesn't fail loudly, it files things confidently in the wrong place at a pace no human could match. Ambiguity plus automation equals corruption at scale.

The payoff runs the other direction too. Once each domain has one owner, the AI work that looked hard becomes almost boringly straightforward. A morning brief is just four reads — calendar, CRM, ledger, vault — stitched into a page. Meeting prep is a calendar read plus a CRM read. The magic-looking stuff in Part II of this book is mostly plumbing between systems that each know exactly what they own.

What does the rule cost? Almost no money. It costs decisions — which is why most companies never do it. You have to name the owner, publicly, and demote the pretenders. The estimator's beloved spreadsheet has to become either a view of the ERP or a retirement party. Somebody's whiteboard loses its authority. These are uncomfortable conversations precisely because everyone knows the shadow systems exist and everyone has a favorite.

Have the conversations anyway. They're the cheapest part of this entire book, and every chapter after this one quietly depends on them.