You got far.
Now it gets serious.
With Cursor or Claude Code you get further than with any other tool: real files, real Git, real control. The only question is whether what is there survives the first hundred users and the first GDPR question. That is what I look at.
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.
Where self-built projects strain.
The architecture grew along
Every feature was bolted on separately. It works, but nobody can explain why something exists in three places.
Permissions are not locked down
The front end hides buttons the back end still happily executes. Row-level security is missing or set too wide.
Migrations are manual work
Columns were changed straight in the database. Setting up a second environment or rolling something back is impossible as a result.
No tests on what touches money
Payments, invoices and permissions are exactly the places where a silent bug catches up with you months later.
Dependencies are behind
Packages with known vulnerabilities stay put because updating might break something.
It stands or falls with you
Without documentation nobody can take it over, not even temporarily when you are away for two weeks.
Review, clean up, finish.
Code review
I read through the codebase asking: what breaks at a hundred users, and what is a security risk. You get a prioritised list.
Lock the foundation down
Permissions at database level, migrations in version control, secrets out of the code and the vulnerable packages updated.
Finish what keeps being left
Usually that is the boring part: error handling, email, invoicing, edge cases and a decent admin side.
Make it transferable
Documentation and tests on the paths that touch money or data, so someone else can carry on where you stop.
- ✓A list of what is genuinely a risk, and what is not
- ✓Permissions that hold without the front end
- ✓Migrations and tests on the critical paths
- ✓Documentation someone can take over with
- ✓Advice on what you can keep doing yourself
The first opinion costs you nothing: send me the repository or a link and I will tell you honestly whether building on beats starting over.
Clients rate me
5 stars on average.
Translated from the Dutch originals on Google.
I am Bas Voets. Since 2021 I have been building websites, client portals and business software for small and mid-sized companies, from Hazerswoude-Dorp in the Netherlands. From first call to launch you talk to me, not to an account manager.
I build myself, why would I bring you in?
Can you do only a review?
Do you work in my repository?
What if I want to finish it myself afterwards?
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.
Have your current site or tool scanned
You do not have to want to buy anything yet. Send what you have and I will tell you honestly what I would keep, what I would replace and whether that is worth the investment. Including when the answer is that you are better off doing nothing.
The scan is a first impression, not a security audit.
- 01Send a link to your site, your tool or your repository
- 02I look at speed, structure, data and security
- 03Usually within two working days you hear what I would replace and what that costs