Bespoke web applications · agile

When off-the-shelf
won't fit.

Bespoke web applications — internal tools, customer portals, APIs and integrations — built the agile way and run on infrastructure we manage ourselves.

01 / What we build

Tools that earn their keep.

The thing you actually need, not the nearest product you can bend to fit. Built to be picked up by the next person — including us at 2am.

P / 01Applications

Portals & internal tools

Booking systems, member portals, dashboards — the bespoke software that replaces three spreadsheets and a paper diary.

  • Customer-facing portals
  • Internal admin tools
  • Dashboards & reporting
P / 02Integrations

APIs & automation

Make your systems talk to each other. We build the API layer, the sync jobs and the small dashboard to watch them run.

  • REST APIs & webhooks
  • Accounts / CRM bridges
  • Scheduled automation
P / 03Data

SQL that holds up

Proper relational data models that don't fall over at scale, with migrations, backups and a sensible upgrade path.

  • PostgreSQL & MySQL
  • Considered schema design
  • Migrations & backups
02 / How we build

A stack we actually know.

No résumé-driven framework churn. We reach for tools we've shipped and supported for years — and we'll work in yours if your team already has one.

Front end

Interfaces with Vue and modern JavaScript — progressively enhanced, accessible, and quick on the connection your customers actually have.

JavaScript Vue3 TypeScript HTML / CSS Vite

Back end & data

Application logic in Python or PHP over a proper SQL backend. Boring, well-understood, and easy for the next person to pick up.

Python PHP8.3 SQL PostgreSQL MySQL REST

How we work

Agile 2-week sprints Fortnightly demos Git + CI Hosted in-house
03 / A project's shape

Agile, actually.

Most projects run six to twelve weeks. You see working software at the end of every sprint, and the people you met on the first call are the ones writing the code.

  1. Phase 01
    Discovery & scope
    A workshop to pin down what success looks like. You leave with a fixed scope, a rough budget and a sprint plan.
  2. Phase 02
    Sprint zero
    Repo, CI, environments and the data model stood up — so the first feature sprint builds on solid ground.
  3. Phase 03
    Build in fortnightly sprints
    Working software demoed every two weeks. You steer as it grows; nothing is a surprise at the end.
  4. Phase 04
    Launch & look after
    Deployed to infrastructure we run, then kept patched, monitored and evolving on a support retainer.

Got something that needs building?

Tell us the rough shape of it. We'll tell you whether it's a fortnight or a quarter — and whether we're the right people for it.