Six things we build, two ways to buy the team

The work changes from project to project. What does not change is who does it - senior engineers who stay on your product long enough to understand it.

Build

Web development

Most web apps are quick at launch and slow two years later. We build on foundations that hold: server-rendered where it matters, measured against real budgets, and structured so adding the tenth feature costs about what the second one did.

Typical first release
8–20 wks

Typical first release

Target LCP on mobile
<1.5s

Target LCP on mobile

Code and IP handed over
100%

Code and IP handed over

Web Development in detail
Build

Mobile app development

Cross-platform used to mean an app that felt slightly wrong on both platforms. That stopped being true. We build in React Native so you maintain one codebase, and drop to native modules in the specific places where it genuinely matters.

iOS and Android
~1 codebase

iOS and Android

To first store release
10–18 wks

To first store release

Interaction target
60 fps

Interaction target

Mobile App Development in detail
Design

UI/UX design

Consumer apps get to be simple because the job is simple. Business software rarely has that luxury - the work itself is complex. The craft is in making that complexity navigable, not in pretending it is not there.

Typical design engagement
2–8 wks

Typical design engagement

Prototypes, not flat mockups
In-browser

Prototypes, not flat mockups

Design system and source files
Yours

Design system and source files

UI/UX Design in detail
Product

SaaS development

Every SaaS product needs the same foundation: accounts, teams, permissions, subscriptions, invoices, failed payments, trials, upgrades. It is a large amount of work that no user will ever praise, and getting it wrong quietly costs revenue for years.

To a billable product
12–24 wks

To a billable product

From day one
Multi-tenant

From day one

Subscriptions and invoicing
Stripe-native

Subscriptions and invoicing

SaaS Development in detail
Operate

Automation

Somewhere in your business, capable people spend hours a week copying data between systems, chasing approvals and re-keying documents. That work is predictable enough to automate and expensive enough to be worth it.

Typical build
4–14 wks

Typical build

Of a manual process removed
60–90%

Of a manual process removed

Every automated action logged
Audited

Every automated action logged

Automation in detail
Plan

Product strategy

The most expensive engineering decisions are made before any code is written. A short, structured strategy engagement is the cheapest opportunity you will get to change your mind.

Typical engagement
2–5 wks

Typical engagement

Of the initial list usually cut
40–70%

Of the initial list usually cut

Roadmap with real estimates
Costed

Roadmap with real estimates

Product Strategy in detail

Not sure which of these you need?

Most conversations start there. Tell us the problem rather than the solution and we will tell you which model fits, including when the answer is that you do not need us yet.