There's a pattern we've watched play out enough times to know it's the rule, not the exception.
A small business hires a consultant or an agency to build something — a website, a Shopify launch, an internal tool, an operations playbook. The build goes well. Launch happens. Invoice clears. Everyone shakes hands. Then the agency is gone.
Twelve months later, the founder calls us. Often it's because something is broken. More often it's because the business has moved — new product, new dealer, new market, new constraint — and the system that was the right answer in 2024 is quietly the wrong answer in 2025.
Almost nobody comes back of their own accord and says: "I want to audit what I built last year, including the parts I'm probably wrong about."
We do. Here's why, and what it actually looks like.
The shape of a year-later audit
A real post-launch audit isn't a status report. It's a four-phase look at what's actually true now:
1. Baseline data pull. What's the system actually doing? Pull every relevant data source — the Shopify Admin API, the analytics, the customer table, the catalog, the discount codes, the theme, every script tag. Cross-reference against what we thought we shipped. The gaps between "what we built" and "what's actually running" are almost always more interesting than the headline metrics.
2. Page-level walkthrough. Every revenue-relevant URL, mobile + desktop, with a real browser-automation tool capturing screenshots, console errors, network failures, and Lighthouse scores. Not a "everything's green" PDF — a 10-dimension scorecard for each page that surfaces which page is the lowest-performing entry to the funnel. Almost always not the page anyone expected.
3. Strategic gap analysis. Brand positioning vs. competitors. Customer-voice mining from forums and review sites for the language real buyers use. Pricing benchmarks. The thing this turns up most often is the thing that justifies the premium is buried where nobody reads it.
4. RICE-prioritized backlog. Not a wish list. Every finding scored on Reach × Impact × Confidence ÷ Effort. Sequenced into a 30 / 60 / 90 / 180-day plan. The ruthlessly honest version: most launches ship with the equivalent of three months of post-launch backlog hidden in plain sight. Doesn't mean the launch was bad. Means launches are launches.
What we look for that the founder usually doesn't
There's a category of finding that almost always shows up in a year-later audit and almost never makes it into a status report:
- The thing we shipped that we'd do differently now. A page that should be
noindex. A schema we didn't add. A CTA that's buried. An H1 that's missing from a template we built. Calling these out is the work — even when we're the ones who built them. - The thing that was deliberately under-engineered for launch and now needs to grow up. A manual workflow we left manual on purpose because automating it on day one would have missed the deadline. Now there's enough volume that the manual version is breaking.
- The thing nobody's measuring because nobody installed the analytics. Every audit we do, we find at least one critical piece of conversion or operational data that the team would benefit from seeing — and isn't, because nobody set it up after launch.
- The thing the market did while everyone was heads-down launching. Competitors shipped a feature. A platform changed an API. A category meta-narrative shifted. The system we built was right for the world it shipped into; the audit is about whether it's still right for the world it lives in.
Why this isn't a sales motion
Two reasons.
The first is that we don't market the audit. It's not packaged. It doesn't have a tier. We don't follow up at month 11 to "check in." When a founder calls us, the audit is just what we offer, sized to where the business is.
The second is that the work that comes out of the audit is itself scoped before signed, with every deliverable priced up front. Sometimes the audit produces six months of follow-on work. Sometimes a focused cleanup and a no for the rest. Sometimes it's "actually you don't need anything, we were checking." All three are valid outcomes, and we'll tell you which one we think it is before any invoice gets sent.
The honest reason we do this
We came up doing the work that disappears after launch. We watched what happens when nobody's accountable for the system at month 12. The product gets cobwebbed, the team works around the broken parts, the founder loses faith that any vendor will care once the check clears.
The audit isn't a customer-retention play. It's the version of accountability that actually makes us better at the next launch. Half the things we shipped well last year, we shipped well because we audited the previous year's work and learned what we kept getting wrong.
If you launched something with us a year ago and we haven't called, that's because we're waiting until you're ready. When you are: there's a list. We've already started it.