What you built is
the brief, not the product.
You put something together with Lovable, Bolt, v0, Replit or Cursor that works as long as you are the one operating it. That is not wasted effort: it is the sharpest specification you will ever get, because you tried it out instead of writing it down. The assessment decides what of it can come to production and what the rest is going to cost.
In half a minute I show what almost always sits below the waterline in a project like this: everyone can reach all the data, payments that only work in the demo, and an environment that does not run outside the tool.
Recognise it? Send your link. The first opinion costs you nothing.
Four things that decide whether it can go live.
What you built
Screens, steps and choices. I walk through it as a user and as a developer, and record what the app actually promises. That part is almost always usable and becomes the scope.
What is missing underneath
Permissions at database level, migrations, error handling, secrets sitting in the code, and what happens at a hundred users instead of one. This is where the risks are that you cannot see yourself.
What it has to touch
Your accounting, CRM, stock or planning. An app that stands next to your existing systems means double work; an integration often decides more of the build time than the app itself.
What it costs
Not a range of 'somewhere between ten and forty', but a fixed price per part, along with what you can comfortably leave for now.
From your version to a plan with a price.
You send what you have
A link to the project or access to the repository, plus two sentences on what you ran into. That is all I need to start.
I read it through and call you
I go through the codebase, the database and the permissions, and then we talk for half an hour. Not to sell you something, but because half the context always sits in your head and not in the code.
You get the report
Within five working days: what stays, what gets replaced, which risks already exist, which integrations are needed and what each block costs. Written so someone else could execute it too.
- ✓What of your current app stays usable
- ✓Security and data risks, worst first
- ✓The integrations you genuinely need
- ✓Fixed price per block, with what can wait
- ✓Usable by a developer other than me
Settled in full if you have me do the rebuild. The report is and stays yours, even if you take it to someone else.
Not sure it is worth it? Just send a link first. If I can see in ten minutes that you do not need an assessment yet, I say so, and it costs you nothing.
You can carry on vibecoding.
The rebuild is not there to take away the tools you started with. What you get back is a codebase AI tools handle better: a clear structure, documentation that explains why something is the way it is, and tests on the paths where money and data pass through. Those tests are your guard rail. You keep prompting, you see in the pull request what changes and whether something falls over, and only then does it go live. Where you used to dare touch nothing, afterwards you can carry on yourself, and you only call me for the blocks you cannot be bothered with.
Why do I pay for an assessment when the scan is free?
What if the answer is that I have to start over?
Does it commit me to anything?
Does this work if I am not a developer myself?
Tell me what you
want to build.
A half-hour call. You get an honest answer about what it costs, how long it takes and whether building it is smart at all.