What this is
You cannot fix a system you have never seen in one place. Most owners have a rough sense of their stack and an exact sense of the pain, but nothing in between. This audit builds the in-between.
It runs in three passes. First you list every tool. Then you record what actually lives in each one. Then you find the objects living in more than one place, because those duplicates are where the chaos comes from.
The output is one document. It becomes the input for everything you build after, starting with your core objects.
Before you start
Three rules keep this honest.
- Count everything you touched in the last 90 days. Not the tools you like. Not the tools you meant to cancel. If it held business information in the last quarter, it goes on the list. Check your credit card statement, browser bookmarks, and phone. The statement never lies.
- Spreadsheets and docs count as tools. That lead-tracking spreadsheet is a database. That “master offers” doc is a system of record. If information lives there, it is part of the stack.
- Do not fix anything yet. You will want to cancel subscriptions and merge lists mid-audit. Resist. An audit with repairs in the middle never gets finished. Capture now, decide later.
Part 1: The tool inventory
List every tool, one row each. For each one, capture:
| Field | What to write |
|---|---|
| Tool | Name of the tool, spreadsheet, or doc |
| Job | The one thing you actually use it for, in plain words |
| Cost | Monthly cost. Annual plans divided by 12. Free is $0, not a blank |
| Last real use | The last time it did the job, not the last time you opened it |
| Who touches it | You, a contractor, a client, or an automation |
Write the job in your own words, not the vendor’s. “Email marketing platform” is what they sell. “Sends the newsletter” is what it does for you. If you cannot name the job in five words, that row is already telling you something.
Part 2: The object map
Now go tool by tool and record what lives inside. Use the eight core objects as your checklist: ideas, content, campaigns, offers, leads, clients, tasks, and assets.
For each tool, note which objects it holds and whether that tool owns the object or just displays it. Owning means edits happen there. Displaying means it shows information that officially lives somewhere else.
This distinction will feel fuzzy on the first pass. That fuzziness is not a flaw in the audit. It is the finding. If you cannot say whether your email platform owns your leads or displays them, then right now, nobody owns your leads.
Part 3: The duplication check
Build one simple grid. Objects down the side, tools across the top. Mark every cell where an object lives in a tool. Then read across each row.
- One mark: healthy. That object has a home, even if it is not the right home yet.
- Two or three marks: a leak. The same object is being edited in multiple places, which means versions are drifting apart right now.
- Four or more marks: this is the object that generates your fires. It is almost always leads or content. This row is why you feel behind.
Count your total filled marks and subtract eight. That number is roughly how many duplicate records your business maintains by hand. Every one of them is a job you are doing that a connection should be doing.
Reading your results
Three patterns show up in almost every completed audit.
- The zombie stack. Tools with a cost and no real use in 90 days. Do not cancel them yet, but total the monthly spend and write it at the top of the page. That number funds the build you are about to do.
- The shadow database. A spreadsheet or doc quietly owning a core object, usually leads or offers. This is not a moral failure. It is a sign that no proper tool ever earned that object’s trust. The fix is a real home, not a nicer spreadsheet.
- The hero object. The one row with marks everywhere. Circle it. In the Core Objects Guide, this object gets its source-of-truth decision made first, because it is the one bleeding the most.
What to do next
Do not act on the audit directly. No cancellations, no migrations, no new tools. The audit is a map, and a map is not a route.
Take your completed audit into the Business OS Guide. Move 1, naming your core objects, is now a review instead of a brainstorm because Part 2 already surfaced your nouns. Move 2, picking one source of truth per object, is where your duplication grid earns its keep.
Then work through the Core Objects Guide with this document open beside it. Every decision gets easier when you can see what you are actually working with.