Code and content platforms
- AstroA web framework for content-rich sites. Pages are rendered to HTML ahead of time and JavaScript is only sent for the components that need it.Read more
- Next.jsA React framework for full-stack web applications, with server rendering, routing, data fetching and API routes in one project.Read more
- ReactThe library for web and native user interfaces. For new apps, the React team recommends starting with a framework such as Next.js.Read more
- SanityA headless content platform: content is stored as structured data and edited in Sanity Studio, an open-source editor customised with React.Read more
Site builders
Our custom build process
Scoped per project, four stages.
Timelines depend on scope, so we set them with you after architecture. Every stage has named outputs, and we decide the data model and structure before building rather than discovering it as we go.
Step 01
Architecture
We define the data model, stack and structure, and agree the approach before any code is written.
Outputs
- technical scope
- data model
- architecture plan
Step 02
Foundations
We set up the Next.js project, environments, database and auth as the base everything builds on.
Outputs
- project scaffold
- database schema
- auth and environments
Step 03
Feature Build
We build features in reviewable increments against the agreed scope, with integrations wired as we go.
Outputs
- working features on staging
- API integrations
- code reviews
Step 04
Testing & Launch
We test, harden, check performance and security, then deploy with the handover your team needs.
Outputs
- test coverage
- performance and security pass
- deployment and docs
Common questions
Questions about custom development.
Everything teams usually ask before the first call.
When do I actually need custom development instead of Framer?
You need custom when the product has real application logic, custom data models, user accounts or integrations that a site builder cannot carry, and that is the work this service is for. If your project is a marketing site or a mostly content-driven site, a builder such as Framer is faster and cheaper to run, and we will say so. We will tell you honestly which side of that line your project sits on rather than sell you the larger build.
What stack do you build on?
React and Next.js on the front end, Node on the back end, with the database and services chosen to fit the project. We favour a mainstream, well-supported stack so your build is easy to maintain and to hire for later. We agree the specifics during architecture rather than defaulting to whatever is fashionable.
Why scope the architecture before writing code?
Because the expensive mistakes in custom builds are structural, and they are far cheaper to fix on paper than in a running codebase. We define the data model and approach up front so the build is predictable and the cost does not drift. It also means you can review and agree the plan before committing to the full build.
Who builds it, and will I be handed between people?
One senior team, with no juniors, account managers or handoffs. The people who scope your architecture are the people who build it, which keeps context intact and decisions quick. At the end we hand over clean code and documentation so your team or another developer can take it forward.
Tell us what you are building.
A 30-minute call. We will look at where you are, what is not working, and what we would do about it. No deck, no pitch.