Service
Web application development
Products, dashboards, portals, and marketing sites built on Next.js and React. Fast, server-rendered, and maintainable by someone other than us.
- Scoped per project
- UK based
- Founder-led delivery
Most of what we build lives in a browser. That covers a wider range than the phrase suggests: a SaaS product with authentication and billing, an internal dashboard that replaces a spreadsheet somebody is quietly terrified of, a customer portal, a booking flow, or a marketing site that has to load fast and rank.
We build on Next.js and React because it lets one team ship the interface, the server logic, and the deployment without three handoffs. It also produces server-rendered HTML by default, which matters more than it used to now that both search engines and AI assistants read your site by fetching it rather than running your JavaScript.
We have built this way for our own products, which changes the incentives. REQO and PULSX are software we have to maintain, on call, indefinitely. That has made us conservative in useful ways about dependencies, data models, and anything clever enough to be hard to debug at seven in the morning.
Every project is scoped and quoted individually after a first call, because the honest answer to what something costs depends entirely on what it turns out to be.
Included
What you get
Every engagement includes all of this. None of it turns up later as an extra.
Product and interface design
Screens designed against the real flows, not a mood board. You see the actual interface early enough to change your mind about it cheaply.
Full-stack build
Interface, server logic, database, authentication, payments, and third-party integrations, delivered as one coherent thing rather than assembled from parts.
Server rendering and Core Web Vitals
Content in the HTML, images sized properly, JavaScript kept to what earns its place. Speed treated as a feature rather than a cleanup task.
Technical SEO built in
Metadata, canonicals, structured data, sitemaps, and heading structure done during the build, which is roughly a tenth of the cost of retrofitting them.
Deployment, properly wired up
We go live on your domain, either into your own hosting account or onto infrastructure we run for you. The domain and the code stay in your name either way, so nothing here becomes a hostage situation.
Handover you can act on
Readable code, written documentation, and access to everything. If you take it in-house or to another team next year, you can.
In detail
How we approach it
How we decide what to build first
The most expensive mistake in software is building the right thing in the wrong order. We start from the single flow that carries the value: the thing a user does that makes the product worth paying for. Everything else is scheduled around getting that one path working end to end, because until it does, no amount of settings screens or admin tooling means anything.
In practice that means your first working version is narrower and more finished than you expected, rather than broad and half-done. It is easier to add a second feature to something that works than to finish six things that are all at eighty percent.
Why we prototype before we specify
Written specifications are a poor medium for user interfaces. Everyone reads the same paragraph and pictures something different, and nobody discovers the disagreement until the build is done. So we get a clickable version in front of you early, with the core features actually working in a browser, rather than a document describing them.
It is not a mockup. It is the real thing, early and rough, and it does the job a specification is supposed to do: it makes the disagreements visible while they are still cheap to resolve.
What we do not do
We do not build on page builders and we do not ship a theme with your logo on it. Both are reasonable choices for some businesses, and if that is genuinely what you need we will say so rather than sell you a custom build you will not benefit from.
We also do not take on more work than we can do properly at once. We are a small studio and the number of projects running in parallel is deliberately low, because attention is the thing that actually determines quality.
What happens after launch
Launch is the point at which you find out what you actually built. We stay close afterwards: monitoring in place, issues fixed, and a real person to contact. We run our own products in production, so we are not learning what that involves at your expense.
Process
How it runs
Four steps from first call to launch. No surprises, no disappearing acts.
Call
One focused call to understand what you need, who it is for, and what success looks like. You leave with a clear, written scope and a proposal.
Prototype
You are clicking through a working prototype with most of the core features live, early in the project. Real screens in the browser, not static mockups.
Refine
We shape the prototype into the finished product, folding in every amendment you ask for. Nothing ships until you have confirmed the final build.
Deploy
We take it live on the hosting provider and domain of your choosing, fully wired up, and stay close after launch to keep it running smoothly.
Proof
Projects built this way
Case studies with the reasoning, not just a screenshot.
FAQ
Web Applications questions
How do you scope a project?
On the first call we work out the flows involved, the kinds of user, and what has to connect to systems you already run. That is enough to define a scope precisely and quote against it. You know what is included and what is not before any work starts, and anything genuinely new is agreed separately rather than appearing on an invoice.
What makes one project bigger than another?
Four things, mostly. The number of distinct user types, because a customer view, an admin view, and a partner view are close to three products. Whether money changes hands, because payments bring subscriptions, refunds, invoices, and a far higher bar for correctness. What it has to integrate with. And whether your content is ready, which is the one entirely within your control.
Do I own the code?
Yes. The code, the repository, and the domain are yours, in your name, from the start, and we hand over documentation with it. Hosting can be in your own account or managed by us, whichever you would rather deal with. If you want to move to another team later, nothing about the way we build is designed to stop you.
Can you work with our existing codebase?
Often, yes. We will look at it honestly first. Sometimes the right answer is to extend what exists, and sometimes an old codebase costs more to work in than to replace. We will tell you which one we think it is and why, including when that answer is less profitable for us.
Will the site be fast and rank in search?
Speed and technical SEO are part of the build rather than an add-on. Pages are server-rendered, metadata and structured data are set per page, and Core Web Vitals are treated as a build requirement. Ranking also depends on your content and your market, which we will be straight with you about rather than promising positions.
Do you offer ongoing support?
Yes. After launch we stay available for fixes and changes. Some clients want a monthly arrangement, others prefer to come back when they need something. We are happy either way and we do not require a retainer to answer an email.
Related
Other services
Next step
Start here
Tell us what you need built. You will get a written scope and a proposal before any work starts.
Usually within one working day