Web Development
Customer-facing web applications, the backend services behind them, and the APIs in between. For companies whose product lives in a browser and has outgrown a template or a no-code tool.
Who this is for
- A product with real users that needs new features shipped every week.
- A customer portal or dashboard that has to pull from several systems at once.
- A marketing-built site that now needs accounts, payments, or real-time features.
- A team with designers and a backlog but no frontend or backend engineers.
What is included. Tick what you need.
Artefacts, not adjectives. Each is something you can point to at the end. Tick the ones your project needs and send the list with your enquiry; we reply with a written scope.
Technologies we use for this
The relevant slice of our technology matrix. Nothing here that we cannot staff today.
- React
- Next.js
- TypeScript
- Vue
- Nuxt
- Tailwind CSS
- Redux Toolkit
- TanStack Query
- Vite
- Three.js and React Three Fiber
How we deliver it
The five steps every engagement goes through, in the form they take for this service.
Scope
A call with an engineer, then a written scope: what is in, what is out, and what it costs.
Architecture
Data model, API contract, and infrastructure plan, approved before code is written.
Build
Weekly releases to a staging URL you use daily, with a demo every week and a written summary every Friday.
Harden
Tests on the paths that matter, error tracking, a performance pass, and a security review.
Launch and hand over
Production deployment, monitoring, documentation, and every repository transferred to you.
From the blog
- AI coding agents in production: the review gates that make them safeCoding agents now write a lot of software. What we put between an agent's output and production: five review gates, why each exists, and what we measure.
- The three architecture decisions that are expensive to reverseMost early technical decisions can be changed later at reasonable cost. Three cannot. How to recognise them, and how to make them well in the first week.
- Postgres is enough, until it is notOne database can be the queue, search index, vector store, and analytics layer for most products. The boring-stack case, and the signals that say add something.
Questions we get asked
How long does a web application take?
A focused MVP takes six to ten weeks. A full platform with billing, roles, and integrations takes four to eight months. The written scope gives you a date before you commit.
Can you work with our existing codebase?
Yes. We start with an audit of what is there, agree what to keep, and work in your repositories from the first day so there is never a separate handover.
Who owns the code?
You do, from the first commit. Repositories, infrastructure configuration, documentation, and IP are yours whether or not the engagement continues.
Do you handle hosting?
We deploy to your cloud account, usually AWS, Google Cloud, or Cloudflare, and set up monitoring. The bills and the accounts stay in your name.
What if the requirements change halfway through?
Fixed-scope work absorbs small changes and re-quotes large ones in writing. Dedicated-team work simply reprioritises the backlog each week.
Tell us what you are building.
We reply within one business day with how we would build it, what it would cost, and which engagement model fits.
- 01Tell us what you are building
A short form or an email. No deck required, and "not sure yet" is a fine answer.
- 02A call with an engineer
Within one business day. Technical questions get technical answers, from the person who would build it.
- 03A written scope and quote
Fixed price where the scope is defined. The document is yours whether or not you go ahead.