Skip to content
02

Web ApplicationDevelopment

Dashboards, portals, internal tools and customer-facing platforms — built type-safe end to end and structured so the fifth developer to touch it moves as fast as the first.

Typical timeline
8 – 16 weeks
Engagement
Project based
Price
Quoted after a short call
Questions answered
7

Who it is for

Who this is for,and what you get.

Most applications do not fail because the framework was wrong. They fail because the data model was decided in a hurry, the boundaries were never drawn, and every new feature had to be threaded through six places. I start with the model and the boundaries, then build outwards. It is slower for a fortnight and considerably faster for the following two years.

Founders and teams maintaining a prototype that was never meant to reach production.

Businesses that need a customer portal, dashboard or internal tool that stays fast on real data.

Teams that want a codebase structured so the next developer is productive in days, not weeks.

Outcomes

01A typed application deployed on infrastructure you control.

02Authentication and role permissions working from the first week.

03A working build every week that you can click through.

04A structured handover document and a walkthrough with your team.

Signals

Signs you needthis work.

  • 01Your team is maintaining a prototype that was never meant to reach production.
  • 02Adding a feature now touches half the codebase and nobody can predict the blast radius.
  • 03The interface is fast on the demo account and slow on the real one.

Process

How the work runs.

Typically 8 – 16 weeks. You get a working build, with a short demo, every week, and on final payment the code, the accounts and the documentation are yours. The full process

01

Model

Entities, relationships and the invariants the system must never break.

02

Skeleton

Routing, auth, permissions and deployment working end to end in the first weeks.

03

Surface

Features built against the skeleton, deployable every week, with a demo.

04

Harden and hand over

Load, edge cases, error states, monitoring, then the handover document and walkthrough.

Included

What is included

Architecture and data modelling

Next.js App Router build in TypeScript

Authentication and role permissions

API design — REST, tRPC or GraphQL

Continuous deployment, monitoring and structured handover

Typical stack

Next.js

TypeScript

PostgreSQL

Prisma

tRPC

Vercel

Timeline
8 – 16 weeks
Price
Quoted after a short call

Questions

Questions,answered plainly.

Usually, yes. I start with a short audit — a few days — and come back with an honest answer about whether extending it or replacing part of it is the cheaper path over eighteen months.

You do, on final payment. Repository, infrastructure, credentials and documentation transfer in full.

Frequently. Handover is a phase with its own deliverables, not an email on the last day.

Because most of what clients need — public pages that must be found, and logged-in screens that must be fast — fits in one codebase, and a type system catches a whole class of mistakes before a user does. If your project is better served by something else, I will say so; the choice follows the project.

Typically 8 to 16 weeks, depending on scope. A short discovery phase ends with a written scope and a range, and a firm number follows once the architecture is settled.

No, and I would rather say so upfront than let a quote comparison do it for me. You are paying for senior attention on the whole build, not a junior rate with a senior's name on the proposal. If the brief can genuinely be done smaller and cheaper, I will tell you in the first call.

What you are trying to achieve, what exists today, who will use it, and whether this is the right first piece of work. You come away with an honest view even if you do not hire me.

The other core services

Design and website work is also available.

Start here

Have a projectthat needs this?

Tell me what you are trying to achieve and I will come back with an honest view on scope, sequence and whether web application development is really the thing you need first.