The Work
A web application has users, data, permissions, and state. Records change, two people click the same button at once, and it has to still be correct afterwards. It is a different discipline from a website, and anyone quoting the same price for both has misunderstood one of them.
Common builds: an internal tool replacing a spreadsheet held together by one person's memory, a customer portal, or a booking and inventory system with rules no off-the-shelf product supports.
Cost Drivers
Roughly a fifth of the budget buys the screens you can see. The rest buys logins, permissions, data modelling, error states, and the behaviour that keeps everything correct when things go wrong. Cheap quotes drop that part. You meet it later at a worse price.
How I Build It
The same way I build everything, which you can verify rather than take on faith. Business rules go in one place, separated from the interface, so they can be tested without a browser open. Anything that must always be true gets enforced by the build itself instead of by everyone remembering.
That is not a philosophy I wrote for a website. It is how my own projects are structured, and the code is on the Work page if you want to check.
Buy Before You Build
If Airtable, Notion, or a subscription tool covers most of what you need, buy it. You get it today instead of in three months, someone else maintains it, and you can leave when it stops fitting. Custom earns its cost when the tool cannot bend to a process that is central to how you compete, or when per-seat fees have quietly grown past the cost of building.