Most companies have more useful data than they think — and more quality problems than they realize. A structured one-week audit surfaces both. Here's the exact framework we use.
The phrase 'we need better data' is one of the most common things we hear when starting a new engagement. Usually, the underlying reality is more nuanced: the data exists, it's just fragmented, inconsistently formatted, or simply never been looked at systematically.
A one-week data audit won't solve every problem, but it will give you a clear picture of what you have, where the gaps are, and which fixes will have the highest business impact. Here's the framework we use when we kick off a new client relationship.
Day 1 — Inventory Everything
Start by listing every system in your company that generates or stores data. This is broader than most people initially think. The list typically includes: your CRM, billing/invoicing software, website analytics, customer support platform, email marketing tool, spreadsheets (yes, all of them), internal databases, and any third-party integrations or data feeds.
For each system, document: what data it holds, how far back records go, who owns it, whether there's an API or export capability, and who currently looks at it. Don't analyze yet — just inventory. The goal is a complete map of your data landscape, including the informal spreadsheets that live in someone's Google Drive.
- CRM: contact records, deal history, activity logs
- Finance: invoices, revenue records, expense categorization
- Marketing: campaign data, attribution, email engagement
- Operations: fulfillment, support tickets, SLA tracking
- Product/Website: user behavior, event tracking, conversion funnels
Day 2 — Map Business Questions to Data Sources
Write down the 10 most important business questions your leadership team asks regularly. Things like: 'Which customer segment has the best retention?' or 'Which marketing channel drives the most profitable customers?' or 'Where in the sales process do we lose the most deals?'
For each question, try to answer it using your Day 1 inventory. Mark each question as: Answerable (data exists and is accessible), Answerable but slow (data exists but requires manual extraction), or Unanswerable (data doesn't exist or can't be joined across systems). This exercise immediately reveals your highest-value data gaps.
Day 3 — Assess Data Quality
For the top five data sources on your list, run a basic quality check. You're looking for four things: completeness (what percentage of records have the key fields filled in), consistency (are the same things described the same way — for example, is 'New York' sometimes 'NY' or 'New York City'?), freshness (how recently was the data last updated?), and accuracy (spot-check 20 records against the source of truth — are the numbers right?).
Most teams find their worst quality problem is in the CRM — deal stages that mean different things to different reps, contacts with no company association, revenue fields left blank. Document what you find without trying to fix it yet. Fixing during an audit is how audits never get finished.
Day 4 — Identify High-Value Joins
The most powerful analytical insights usually come from connecting data across systems — not from any single source. On Day 4, look for cross-system join opportunities. The most common high-value ones are: CRM deals joined to billing records (to validate deal close dates and actual revenue), marketing attribution joined to CRM pipeline (to see which channels produce the best customers, not just the most leads), and support tickets joined to customer accounts (to find the correlation between support volume and churn).
Document which joins are possible given your current systems and data quality, and which ones are blocked by missing identifiers (for example, if your CRM and billing system use different customer IDs with no shared key, that's a critical infrastructure gap).
Day 5 — Prioritize and Build a Fix List
By Friday you should have a clear picture. Now score each issue you found by two dimensions: business impact (how much better would decisions be if this were fixed?) and fix effort (days of engineering or operations work required). Plot them on a simple 2x2. The high-impact, low-effort fixes are your immediate priority — these are often data hygiene issues that an operations person can fix in a few hours per week.
High-impact, high-effort issues (like rebuilding a data pipeline or consolidating two CRM instances) go into a roadmap. Low-impact issues get documented and deprioritized.
What Comes After the Audit
An audit is only valuable if it drives action. The output of this week should be a one-page summary: your current data landscape, the top three quality problems, the top three unanswerable questions, and a prioritized fix list. Share it with whoever owns budget for data and operations tooling.
In our experience, most companies that do this exercise find that 60-70% of their most valuable analytical questions are answerable with data they already have — they just need the right tooling and about two weeks of cleanup work to surface it. That's a very different starting point than 'we need to hire a data team.'
Analyze → Build → Measure
Ready to put this into practice?
We audit your data, operations, and processes — then build the systems that turn the findings into measurable results. No slide decks, no hand-off.