The AI Site Audit
€195
paid upfront · credited in full toward your build
You come out of it able to decide: finish this one, or start a better one — with a real number either way.
- What it needs
- What it costs
- Whether it is safe
Finish a v0 project
v0 is excellent at the thing it is for: generating good-looking components, fast. What comes out is a set of screens, not a site — and the distance between those two is larger than it looks.
React, Next.js and Tailwind are what we build in anywayYour components stay yours
The AI Site Audit
€195
paid upfront · credited in full toward your build
You come out of it able to decide: finish this one, or start a better one — with a real number either way.
Where v0 projects stall
v0 generates components and does it well. What stalls is everything that has to happen after the component.
Routing between pages, a layout to hold them, metadata and a site structure are all still to build. Each generation is its own island, and islands stay islands.
The contact form posts into thin air, prices are typed into the markup, and content has yet to be given a home. Changing a phone number means editing code and deploying.
Every generation makes its own choices, so spacing, type scale and colour drift between screens. It looks designed one screen at a time, because it was.
Generated markup gets close and then misses: unlabelled icon buttons, headings picked for size instead of structure, dialogs that trap focus, contrast just under AA. Close is a fail.
Page titles, descriptions, a sitemap, social images, analytics — all of it is still to write. The surface here is genuinely empty rather than weak, because it was never the ask.
Pasted components assume component-library and Tailwind versions your project lacks, so it runs on your machine and then fails on the real build.
v0 gets you further than most people realise — it just stops at the component boundary. We finish what it started in the same stack, so nothing you liked has to be thrown away.
The gap
None of this is a criticism of the tool. It is simply the part that was never in scope for it.
Titles, descriptions, structured data, a sitemap, and pages a search engine can read without running your app first.
WCAG 2.2 AA done properly: contrast, keyboard, focus, labels, motion. The standard European businesses are now measured against.
Your own domain, SSL, business email, redirects, backups, and hosting that stays up when a free tier changes its mind.
Not another generation. Somebody deciding what stays, what goes, and what the site is actually for.
Structure, naming and a build you can hand to anybody later. You own all of it, in your name, with no exit fee.
One studio, one named person at the other end, and a date. Not a chat window that forgets you tomorrow.
We build on your work where it is good and rebuild where it is not — and you own all of it either way.
How the finish works
There is nothing to upload on this page and no form to fill in. The audit starts with a payment and continues in email, with a person.
€195 through Stripe, on the same checkout as everything else we sell. You see the full terms on our own order page first, and nothing is charged until you are on Stripe's card form.
Within one business day, from a real address. We ask for the link to your site, the files or repository, and a couple of sentences about what you were trying to build.
Not a scan, not a bot, not a sales call. Somebody opens your site, reads what is there, and works out what finishing it honestly takes.
What it needs, what it costs as a single number, whether it is safe, and whether finishing or starting fresh is the honest answer. Say yes and your €195 is credited in full toward the build.
Why it works this way. We only take in someone else's site once we can look after it properly, so today we collect your files by email and tell you exactly how they are stored and how long we keep them. If you can, take your keys and passwords out before you send anything — and if we find any still in there, we will tell you what to change.
The AI Site Audit
One payment, one answer, one fixed price to finish. It is deliberately a decision you can act on rather than a repair manual — so here is exactly what arrives.
Finished, described as an outcome: it deploys on a real host, Google can index it, it passes WCAG 2.2 AA, it works on a phone, and the code is yours. Plus how much of your own work we would keep.
One fixed price to finish. A single number, agreed before the work starts — the same published, fixed way we price everything else on this site.
A plain verdict on the security and the quality of what you have, and how serious each thing is. If something is exposed, you find out from us rather than from somebody else.
This line is deliberate. How to fix it is the work itself — which is exactly what the fixed price buys.
€195 through Stripe · credited in full toward your build · you see the full terms before anything is charged
We write to you within one business day of your payment, from a real address.Would you rather we waited until your 14-day right to change your mind has passed? Choose that at checkout, at the same price.
You get the €195 back in full if there is no viable path and your submission was genuine.If we hand you a real fixed price and you would rather not go ahead, that is completely fine — the audit was the work, so the fee stays with us. You said so up front and so did we. Your €195 works for you exactly once: it either comes off your build or comes back to you, never both.
We take on the work we can stand behind.We say so plainly when yours falls outside that: anything built to deceive, anything you do not have the right to hand over, and anything we would not put our name on.
Your link, files or repository arrive by email and stay inside the studio - we use them only to do your audit, we never pass them to anyone outside it beyond the email provider that carries them, and we never publish or reuse your code. We delete them within six months of the end of your engagement - that clock starts when the work finishes, or when any subscription with us ends, whichever is later, and it is the same period we publish for every project file in our Privacy Policy. You can ask us to delete them sooner and we do it - that is your right under the GDPR. One honest detail: the audit intake arrives by email, so on this path the deletion is a mailbox review we run and log. Take your keys and passwords out before you send anything, and if we find any still in there we will tell you what to change.
What we have shipped
Everything above says what is unfinished: sign-in, data rules that hold, a real deploy, rules that pass in the EU. Here is the evidence that we have done those, rather than the promise that we can.
The same guarantee
A site finished this way carries exactly the same promise as one we build from scratch: if you are not happy, you do not pay. Being a rescue changes the work, never the terms.
The audit is the one part that stands on its own, and it is paid upfront because it is a person reading your code properly, not an automated scan. Everything after it is covered the way everything else here is covered.
Per tool
The wall looks different depending on where you started. These go into what usually stalls in each.
The app runs, the credits are gone, and the database rules were never really finished.
Finish a Lovable projectA whole site in minutes, and then a ceiling you cannot edit your way past.
Finish a Wix ADI sitev0, specifically
You stay exactly where you are. React, Next.js and Tailwind are what this very site is built in — your v0 components land inside a real project instead of being replaced by one.
It is the normal starting point, and it is exactly what the fixed price covers: forms that go somewhere, content you can edit without touching code, and a deploy that holds. The audit tells you which of those you actually need.
Yes. Keep generating components and send them over, or edit them yourself — it is your code. What we will not do is leave the site in a state where a paste from anywhere can quietly break it.
Only where they come apart across the whole site. Usually the work is making one system out of several good generations — spacing, type, states, dark mode, mobile — rather than starting the look again.
That is the common case now and it changes nothing. Mixed-origin code is normal; the audit reads what is actually there rather than what it was supposed to be.
When you are ready
Pay for the audit and we write to you within one business day to collect your link and your files. You get back what it needs, what it costs, and whether it is safe — and if you go ahead, your €195 is credited in full toward the build. You don't pay for tokens. You pay for finished.
€195 · credited in full toward your build · you see the full terms before anything is charged
Question 1 of 4