Services

What we buildand what you get

Web apps · APIs · MVPs — three engagements, one way of working

Every project is one of the three below. This page says what each one starts from, what we build, and exactly what lands in your accounts at the end — so you can pick before you talk to anyone.

Scope
Written before code
Priced
One figure, up front
Cadence
A working URL weekly
Handover
Repo, docs, access
  • React
  • Next.js
  • Vue.js
  • TypeScript
  • Node.js
  • Python
  • Astro
  • Bun
  • GraphQL
  • REST

01What we build

Three engagements

Most work falls into one of these. If yours spans two, we say so on the first call and scope it as a single project rather than billing you twice for the seam.

WEB

Web development

The surface your customers use — a site or an app that stays fast as the content and the traffic grow.

Best whenYou have designs, or a site that has stopped keeping up.

Read the detail

In scope

  • React, Next.js or Astro front end
  • Screens and states agreed before the build starts
  • A content model you can edit without us
  • Core Web Vitals and keyboard access checked before launch

API

API development

The layer underneath — one place the data lives, that every client reads the same way.

Best whenTwo or more apps need the same data, or an integration keeps breaking.

Read the detail

In scope

  • Schema and endpoint design, REST or GraphQL
  • Authentication, roles and rate limits
  • Integrations with the services you already pay for
  • Reference docs and a staging environment

MVP

MVP development

The smallest version that proves the idea, built so version two is not a rewrite.

Best whenYou have an idea and a date, and need something real in front of users.

Read the detail

In scope

  • One flow, built end to end and actually working
  • Scope cut in the open, with you in the room
  • A foundation the next features can sit on
  • Analytics from the first release

02Side by side

Which one is yours

The same four questions answered for each. Read down the column that matches your situation — the row you care about is probably the third.

Compare onWEBWeb developmentAPIAPI developmentMVPMVP development
You start withDesigns, or a live siteSystems that must share dataAn idea and a deadline
We buildFront end and content modelSchema, endpoints, authOne flow, end to end
You get backDeployed site, repo, runbookDocumented API, tests, stagingWorking product, next-step list
Built onReact · Next.js · AstroNode.js · Python · GraphQLNext.js · TypeScript · Bun

PricingEvery engagement is priced from the written scope — one figure, agreed before code. No hourly billing, no change-request desk.

03In every build

What all three ship with

Not upsells. These sit in the base scope of every engagement, because leaving any of them out costs more to add later than to do now.

Typed end to end
TypeScript on both sides of the wire, so a rename breaks the build instead of production.
Tested where it counts
Automated tests on the paths that move money or lose data. Not a coverage number.
Fast and reachable
Core Web Vitals in the green and full keyboard access, checked before launch rather than after a complaint.
Documented to hand over
A runbook another developer can follow: how it deploys, what the variables are, what breaks first.

Next step

Tell us what
you need built

Send the idea in whatever shape it is in — a document, a sketch, or two sentences. You get a written scope and a fixed figure back before anything is committed to.