web development

web development that holds up after launch

We plan, build and deliver the whole system: the interface people use, the API behind it, the data model underneath and the infrastructure it all runs on. One team, accountable from the first architecture conversation to the version running in production.

what you get

  • the plan, first

    Before anyone writes a feature we write down what the system has to do, what it must never do, and where the hard parts are. That document is the first deliverable, and it is what the quote is built on.

  • the front end

    React and Next.js interfaces, typed end to end, that stay fast on the devices your users actually own rather than the laptop we built them on.

  • the back end

    Node and TypeScript services behind GraphQL or REST, built on a data model that still makes sense after the feature list doubles. That model is the part nobody can cheaply change later.

  • somewhere to run

    Cloud environments, deployment and monitoring, set up and handed over. Software nobody can deploy is not finished software.

  • a senior engineer on every line

    Coding agents scaffold, refactor, migrate and write tests from day one. A senior engineer reads, reviews and owns everything that reaches your repository. Nothing ships because a model sounded sure of itself.

  • a handover you can act on

    Documentation, a repository that is yours, and a team that is still reachable when something breaks at an inconvenient hour.

the stack

The stack is chosen for the product, not the other way round. This is what we reach for first.

  • React
  • Next.js
  • TypeScript
  • Node.js
  • GraphQL
  • Apollo
  • BlueLibs

systems we built end to end

We designed, built and shipped every one of these ourselves.

questions we get asked

How long does a web application take?
A working MVP takes about four weeks and lands under $10K, because AI does the repetitive parts of the build and our own boilerplate skips the parts every project repeats. Anything larger is scoped in the architecture plan we write first, and quoted before a line of feature code exists.
Do you take on existing codebases, or only new builds?
Both. Several engagements started as a rescue: The Wing came to us on Meteor and left on newer technology with payments migrated and response times cut, and Collecteurs moved off Blaze onto React with load times substantially down. Both kept serving users throughout.
Who owns the code, and is any of it used to train models?
You own it, from the first commit. Your code is never training data: we work only with zero-retention, zero-training AI providers, so nothing you own is stored on their side or learned from, and it never travels to another client's engagement.
Do you use AI to write our software?
Yes, and you hear that before you sign rather than after. Coding agents handle scaffolding, refactors, migrations, test suites and first-pass review. A senior engineer reviews and owns every line that reaches your repository.
What happens after launch?
Whatever you want to happen. Some clients take the repository and run it themselves. Others keep us on: we still maintain Novomed's platform and add features to it, years after the first release.

tell us what the system has to do.