Web app development
Every web app is fast on day one. We build the kind that's still fast on day nine hundred.
Software gets slower the way people gain weight
Nobody decides to build a slow, tangled application. It happens a kilogram at a time.
A query that was fine with a thousand rows. A component that was simpler to copy than to refactor. A dependency added under deadline that nobody has updated since. Individually, all reasonable. Collectively, the reason a two-day feature takes three weeks by year two, and the reason your developers start using the word "rewrite."
The decisions that prevent this are made early, cost almost nothing at the time, and are invisible in a demo. That's why they get skipped, and it's most of what you're paying an experienced team for.
What we build
- SaaS platforms
- Multi-tenant products with the unglamorous foundations designed in from the start: roles, permissions, billing, audit logging, admin tooling.
- Customer portals
- Secure self-service where your customers manage accounts, documents, orders, and support without emailing anyone.
- Internal tools and dashboards
- The operational software your business actually runs on. Usually the highest-return thing a company can build and the last thing it gets funded.
- E-commerce
- Custom and headless storefronts integrated with your inventory, payments, and fulfilment.
- Marketing sites
- Fast, accessible, well-structured, and editable by your marketing team without a developer.
What we do differently
- Performance has a budget, like anything else
- We set a target for load and interaction time at the start and hold to it. Slow software gets abandoned regardless of what it can do.
- Accessibility is the baseline, not a line item
- WCAG 2.2 AA from the beginning. It's better for every user, it's substantially cheaper than retrofitting, and in most markets it's the law.
- Security is designed in
- Authentication, authorisation, input validation, dependency scanning, encryption at rest and in transit. Built during, not bolted on after a penetration test found something.
- The code is written to be read
- Typed, tested, documented. The measure of success is that the next developer to open the repository doesn't need to call us.
What you get
Production application · Full source code and IP · Technical documentation · Deployment pipeline · Handover session and training · `[30/60/90]` days post-launch support
Before you ask.
Usually React with Next.js. We'll recommend based on your team's existing skills and your hiring plans, not on what's currently fashionable.
Custom Software
You know the spreadsheet. The one that runs something important, that only two people understand, that everyone is slightly afraid of.
Software DevelopmentSaaS Product Development
The feature you're excited about is the easy part. It's tenancy, billing, and permissions that decide whether this becomes a business.
Software DevelopmentUI/UX Design
Most design doesn't fail in the design. It fails in the handover, where the beautiful file meets the loading state nobody drew.
Tell us what you're trying to build.
A 30-minute call, no charge and no pitch deck. Describe the problem and we'll tell you how we'd approach it, roughly what it costs, and whether we're the right team for it. If we're not, we'll say so.
30 minutes · No charge · No deck