Seven Days to One Source of Truth

Your CRM says you have one count of active customers. QuickBooks says something different. The spreadsheet your ops person built six months ago says a third number, and nobody is sure which one to trust before a board call. This is not a technology problem. The World Economic Forum surveyed SMEs across multiple regions and found 55 percent struggle to locate their own data, and 54 percent struggle to keep it maintained. The tools exist. The authority does not.

The real failure is not fragmentation — it is the absence of a designated authority

Most founders assume the fix is a better integration. Connect QuickBooks to the CRM, export to Sheets, run a VLOOKUP, done. The Albanna et al. research on SME digitization describes exactly why this fails: small firms lack defined roles for data management and lack knowledge about what data to collect in the first place. An integration without an authority rule is just fragmentation with extra steps. You end up with three synced systems that disagree in three new ways.

The intervention is simpler and harder than any integration. You pick one system to own each type of record, you assign a shared identifier, and you stop treating the other systems as independent sources of truth. That is the whole plan. Everything below is the execution.

Day 1: Decide what you are actually unifying

Resist the urge to unify everything. The MDM literature defines master data as the core information about key business entities — customers, products, suppliers. For a founder without a data team, two entities are the right scope: customers and invoices. Nothing else. Open a blank Google Sheet and create two tabs: Customers and Invoices. Leave them empty. You are building the schema, not migrating data yet.

On the Customers tab, create five columns: CustomerID, Name, Email, CRM Record ID, QB Customer ID. On the Invoices tab: InvoiceID, CustomerID, Amount, Date, QB Invoice Number. The CustomerID column is the spine of the whole system. Every other tool will reference it.

Day 2: Generate your customer IDs in QuickBooks

QuickBooks holds the authoritative financial record. Not Google Sheets, not the CRM. QuickBooks. This is not a preference — it is a constraint the spreadsheet accuracy research forces. The Decision Support Systems study on spreadsheet accuracy documents high error rates in real-world use, with underlying formulas and results frequently wrong. A system where the financial numbers live in a spreadsheet is a system waiting to misreport revenue.

In QuickBooks Online, go to the customer list and export it as a CSV. In the exported file, assign a sequential ID to each customer: CUST-0001, CUST-0002, and so on. Import that ID back into QuickBooks using the customer notes field or a custom field if your plan supports it. This ID is now permanent. You do not reassign it. You do not reuse it if a customer churns.

Day 3: Push the same ID into your CRM

Open your CRM — HubSpot, Salesforce, Pipedrive, whichever one you use — and add a custom field called CustomerID to the contact or company record. Go through your customer list and populate this field for every existing customer. For new customers going forward, the rule is: no CRM record without a CustomerID pulled from QuickBooks.

This step takes longer than you expect. Your CRM and QuickBooks will not have the same customer names. "Acme Corp" in one system is "Acme Corporation" in the other. Work through the mismatches manually. Do not automate this reconciliation on day three. The point of doing it by hand is that you find the duplicates and decide which record is correct before any sync runs.

Days 4 and 5: Build the Google Sheets hub

Return to the Customers tab. Paste your QuickBooks customer export into it, including the CustomerID you assigned. Add the CRM Record ID for each customer from the CRM export. The sheet now holds a crosswalk: one row per customer, one ID that connects their QuickBooks record to their CRM record.

On the Invoices tab, paste your QuickBooks invoice export. Every invoice row should carry the CustomerID of the customer it belongs to. If an invoice in QuickBooks does not have a matching CustomerID, that is a data quality issue to fix in QuickBooks before the row enters the sheet. The sheet is a read-only reference hub. Nobody enters data directly into it. Data flows in from QuickBooks exports and CRM exports. It flows out to whoever needs a combined view.

A shared customer ID without enforcement is a plan, not a record

The MDM study in the Review of Economic and Business Studies defines a single source of truth as requiring master data that stays precise, consistent, and accessible over time — and ties that outcome to governance structures, not to the presence of a shared field. A CustomerID column in a Google Sheet, with no validation rule preventing someone from typing "Acme Corp" in one row and "Acme Corporation" in the next, does not produce consistency. It produces a record of intended consistency.

This is the strongest objection to the seven-day plan, and it is partially correct. The WEF data shows 54 percent of SMEs already struggle to keep data maintained — which describes the exact population this plan addresses. A manually maintained Sheets hub will degrade. The research does not say how fast, but the spreadsheet accuracy literature says it will.

The rebuttal is not that the plan avoids this problem. It is that the relevant comparison is not this plan versus full master data management. It is this plan versus 55 percent of SMEs who cannot locate their own data at all. QuickBooks as the named authority, a shared CustomerID across three tools, and a read-only Sheets hub represent a measurable improvement over that baseline — even without deduplication logic or enforced field validation. The plan produces an operational shortcut, not a governed data asset. Treating it as the former is accurate. Treating it as the latter is how founders end up with false confidence in records they should be checking.

Days 6 and 7: Set access rules and a weekly reconciliation step

Access rules are not about security theater. They are about preventing the hub from becoming an input system. In Google Sheets, set the Customers and Invoices tabs to view-only for everyone except the one person running the weekly export update. In the CRM, restrict the CustomerID field so it cannot be edited without admin access. In QuickBooks, the financial records are already protected by default.

The weekly reconciliation step is non-negotiable. Every Monday, export the QuickBooks customer list and invoice list, paste them into the Sheets hub, and run a filter for any CustomerID that appears in the Invoices tab but not in the Customers tab. That is your orphaned invoice check. Run a second filter for any CRM contact without a CustomerID. That is your new customer check. Both filters take under ten minutes if you run them weekly. Skip four weeks and the backlog takes an afternoon.

On day seven, document the authority rule in writing — one sentence per system: QuickBooks owns financial records, the CRM owns relationship records, Google Sheets holds the crosswalk. Put it somewhere your team sees it. A Notion page, a pinned Slack message, the top row of the Sheets hub itself. The system degrades the moment the rule exists only in one person's head.