Engineering
Level 5/5
Product architecture
Lvl 5
100%
We design and build web applications, portals, dashboards and internal tools that stay fast, secure and easy to change as you grow.
Overview
Most businesses run on solutions someone built in a hurry: a spreadsheet that grew into a database, an old tool nobody dares to touch. We design and build the web applications that replace them, from customer portals to operations dashboards and internal tools, and we build them to last: fast under load, secure by design and easy to change as the business moves.
Our guide What it takes to build a web application covers the decisions in detail.
Typical first release
10wks
Test coverage target
80%
What we build
Most application projects are one of four kinds.
| Application | What it does | Examples |
|---|---|---|
| Customer portal | Self-service for your customers: orders, bookings, documents and support | Shipment tracking, account management, quotes |
| Operations dashboard | One live view of the work, with the tools to act on it | Dispatch, scheduling, inventory |
| Internal tool | Replaces spreadsheets and manual steps with a real workflow | Approvals, onboarding, reporting |
| SaaS product | A product you sell, with accounts, billing and roles | Vertical software, B2B platforms |
Architecture
We start simple: one well-structured application with a typed API, a relational database and background jobs for anything slow, split into separate services only where the load or the team demands it. The diagram follows one request through a freight portal: the API checks who is asking, looks in the cache, reads the database and answers typically in 28 milliseconds.
Security
Broken access control tops the 2025 edition of the OWASP Top 10, the industry's list of the most critical risks to web applications. So we design who can see and do what from the first screen: roles, permissions and data rules enforced on the server, never just hidden in the interface.
The rest of the list shapes the build too: security misconfiguration, supply-chain risk from dependencies, injection, and logging good enough to spot an attack in progress.
Design system
A design system is the shared set of tokens and components that every screen is built from. It keeps the app consistent and makes change cheap: adjust a token once and every button, field and table follows. We build it alongside the first features, accessible from the start to WCAG 2.2 AA.
Delivery
Every change takes the same path: automated tests, a preview anyone can click, then production behind a feature flag, released to a small share of users first. We track delivery with the DORA metrics: how often we deploy, how long a change takes to reach users, how often changes fail or need rework, and how quickly we recover.
Reliability
In production we watch what users feel: response times, error rates and the jobs running in the background, against targets agreed with you. When a release misbehaves, an alert fires and rolling back takes minutes, because every release can be undone.
Process
Discover, shape, build, scale: a thin first release in real hands within weeks, then weekly releases from an open channel of communication between you and our team.
Discover
Map the users, the workflows and the constraints before a line of code.
Shape
Prototype the riskiest flows and agree on a thin first release.
Build
Ship in short cycles behind feature flags, with demos every week.
Scale
Harden, observe and hand over — or stay on as your product team.
Deliverables
The application, its API and integrations, the design system, an automated test suite and a delivery pipeline your team can run, with monitoring and runbooks. You own the code, the accounts and the data.*
- Product architecture
- Design system
- Web application
- API and integrations
- Automated test suite
- CI/CD pipeline
Stack
TypeScript throughout; React and Next.js for the interface; typed APIs; Postgres, Redis and background job queues; managed cloud hosting set up as code; automated tests, error tracking and monitoring.
Engineering
Level 5/5
API design
Lvl 5100%Frontend
Level 4/5
Interface engineering
Lvl 480%Platform
Level 4/5
Cloud infrastructure
Lvl 480%
FAQ
Answers to the questions we hear most often about application projects.
Do you work with an existing codebase?
Yes. We start with a short audit of the code, the infrastructure and how changes ship, then extend or refactor what's there. A rewrite is a last resort, and if we recommend one we'll show you why.
Who owns the code?
You do, from the first commit. The repositories, cloud accounts and domains live in your organisation.
How long does a first release take?
Usually about ten weeks to a first version in real users' hands: around two weeks of discovery and design, then weekly releases behind feature flags until the first workflow is complete.
How do you price application work?
A fixed-price discovery, then a monthly team working from a shared roadmap. You see what ships every week and can change priorities between sprints.
How do you keep the app secure?
We design access control from the first screen, since broken access control tops the 2025 OWASP Top 10, keep dependencies patched and scanned, log security events and test the riskiest flows before every release.
Will the app be accessible?
We build to WCAG 2.2 AA and test with keyboards and screen readers. Since 28 June 2025 the European Accessibility Act has required many consumer services in the EU, including e-commerce and consumer banking, to be accessible.
Which technology do you use?
TypeScript across the stack, React and Next.js for the interface, typed APIs, Postgres and managed cloud services. We pick well-supported tools your team can hire for.
How do you measure delivery?
With the DORA metrics: how often we deploy, how long a change takes to reach production, how often changes fail or need rework, and how fast we recover. We share them with you every month.
Can you support the app after launch?
Yes: monitoring, updates and on-call with agreed response times, or a handover to your team with runbooks and training.
All names, companies, people and figures in the examples and illustrations on this page are fictional and shown for demonstration only. They do not correspond to real clients, customers or results.