Build a custom web app
Custom web app development means the whole application, frontend through backend, database, auth, email, and payments, built by one accountable person and deployed in your own accounts. Default stack is SvelteKit and Postgres. Scoped to a tight first version with a fixed price, documented so it is not dependent on me.
Also covers Client portal or dashboardInternal tools
Runs the practice today, and is being productized as ConsultingHarness.
Version one should be smaller than you want it to be. I built my own client portal this way: the first version handled intake and a statement of work, nothing else. Invoicing, e-signature, and the client login came later, each one added because the previous version was already in use and had shown what was missing. The features you cut from version one are cheap to add once the thing is real, and expensive to guess at before it is.
What the app does, who uses it, and what version one leaves out.
For a clearly scoped first version.
Working software at each one, not a demo at the end.
In your accounts, documented, with an optional Care Plan.
I've run an eight-person agency, held leadership in a hundred-person one, and been CTO of a third. I know where agency budgets go: overhead, junior hours, handoffs.
AI changed that math. The person who scopes the work is the person who builds it, and there is nobody in between.
Project
starting at
$3.5K
Scoped, built, and shipped to production.
Retainer
from
$500/month
Advise and build, ongoing.
Fixed bid per version. Version one is scoped tight on purpose.
With a small, well-worn stack and by keeping version one small. SvelteKit and Postgres cover the frontend, backend, and data in one codebase. AI handles the repetitive parts of the build. Every decision that matters is still mine, and there is no handoff between a designer, a frontend developer, and a backend developer because they are the same person.
Everything is in your accounts, the stack is standard, and the code is documented. Any SvelteKit developer can pick it up. That is the point of building on common tools rather than a custom framework.
You do. The repository, the database, the hosting, and every third-party account are yours from day one. I work in them; I do not hold them.
It depends on the scope, which is why the spec comes first. A tightly scoped first version is usually weeks, not months. Each milestone ships working software, so you see progress before the end date rather than at it.
One project at a time. Limited availability.
Or reach out directly:
Last updated
