What the audit is The published checks, run against your store.
One page per check, what it is costing you, and what it would take to fix — whether or not that is me.
I run the published checks against your store and write up what I find. Not a sales document with findings attached — the standard applied to your store, in the same format I hold my own builds to.
What you get back, within 5 working days:
- One page per check, with what I found and how I found it — so you can re-run it yourself and get the same answer.
- What it's costing you, where that's calculable, with the working shown rather than asserted.
- What it would take to fix, in order of what's bleeding most — whether or not that's me doing it.
- What I couldn't check, and why. Some of it needs access I won't have; some of it needs a decision only you can make.
It costs $299, and if you go ahead with a fix or a build within 60 days, it comes off the price. Why it costs anything at all →
What it reports against
An audit that says "your developer did this wrong" is an opinion with a bias attached — mine, and I'd be the one quoting for the fix.
So it doesn't do that. Every finding is scored against the same published list, in the same words, in the order the list is written. If a check passes, it says so and moves on. The judgment belongs to the standard, not to me — which means you can take the document to a different developer and it still means something.
That also means the audit can come back mostly clean, and sometimes does. A store that passes eleven of them and fails two has a two-item problem, not a rebuild. Telling you that is worth more to me than a rebuild I'd have talked you into.
What happens after you send it
- You send the form. Store URL, what's going wrong, what you've already tried.
- I read it — me, not a filter. If it's not something I can help with, you hear that back within a day and you're not charged.
- You pay the $299 once I've confirmed I can do it. Not before. If I can't help, there's nothing to refund because there's nothing to pay.
- 5 working days. Four of them are the run — including the slow ones, the code read and the conversion-path walk. The fifth is writing it up properly.
- Then a call, if you want one. Thirty minutes, to go through what I found. There's no obligation to take it and the document stands on its own without it.
Send me the store
Four questions. They're the ones I need answered to tell whether I can help, and what you write is the qualification — there's no call before this, and no form robot reading it. Sending it doesn't charge you anything.
Your URL and what you write come to me by email and go nowhere else — no CRM, no ad platform, no list. If you're not a fit or you don't reply, it gets deleted rather than followed up. What I keep and for how long →
What it costs
$299. If you go ahead with a fix or a build within 60 days, it comes off that price — so if we end up working together, the audit was free and you found that out afterwards rather than being asked to believe it in advance.
What the $299 is actually for. Four days of running the checks on a store I've never seen, and a day writing up what I found in a form you can hand to someone else. It isn't a lead magnet with a price on it, and it isn't priced to be a profit line — it's priced so that the people who send the form are the people who want the answer.
This used to be free, and it's worth saying why it changed. The free version worked, in the sense that people took it. What it didn't do was get acted on — a document that costs nothing gets weighed as though it's worth nothing, and I watched a store owner agree with every finding and then go and buy the cheap rebuild anyway. Three hundred dollars is the smallest number that makes it a decision rather than a download.
What you're not paying for: the standard itself, which is published in full, free, with instructions for running most of it yourself. If you'd rather spend ten minutes than $299, do that instead — it's the same list. The audit is me running it on your store rather than you running it on mine.
There's no upsell attached and no sequence behind it. What happens next is in the section above, and it's the whole of what happens next.
Before you send it
If what you actually want is a quote, this isn't the fastest route — an audit takes 5 days and tells you what's wrong, not what a rebuild costs. Three quotes from three developers will get you a price range in an afternoon. It won't tell you which of them can tell the difference between the two, but if price is the deciding question, that's a reasonable trade and I'd rather you make it deliberately.
If you're not sure anything is wrong yet — read the checks first and run the free instruments on your own store. That costs you ten minutes and no email address, and if everything comes back clean you've saved us both $299 and a week. The published checks →
If you want the findings without the conversation — that's fine, and it's most of what this is. There's no obligation to take the call.