HOW WE WORK

A small studio process.

Four phases. Each one ends with a written artefact you sign off on before the next begins. No drift, no surprise invoices, no ten-page contracts.

01

Discover

2–3 weeks

We sit with the problem before the keyboard.

Stakeholder interviews, audit of your existing stack, and a written brief that you sign off. No mood boards, no buzzword bingo — just a concrete document that says what we are building and why.

Deliverables
  • Stakeholder interview notes
  • Technical & UX audit
  • Written project brief
  • Signed Statement of Work
02

Forge

6–10 weeks

Tight design and engineering loops.

Working software in weeks, not slides in months. We work in two-week sprints with a Friday demo, a Monday plan, and a single shared backlog. You see everything in production the moment it lands.

Deliverables
  • Two-week sprint cadence
  • Friday demo + Monday plan
  • Staging deploys from day one
  • Weekly written status note
03

Polish

1–2 weeks

The 5% of detail 95% of teams skip.

Performance budgets, accessibility audit, motion pass. We measure before and after — load times, Core Web Vitals, jank — and we hand you the numbers. Nothing ships rough.

Deliverables
  • Performance audit report
  • WCAG 2.2 AA accessibility pass
  • Motion + interaction pass
  • Pre-launch QA checklist
04

Ship

launch + 30 days

Production launch, monitoring, runbook.

Your team owns it from day one. We're on call for 30 days after launch — incidents, hotfixes, small adjustments — at no extra cost. A written runbook means the next engineer doesn't have to phone us.

Deliverables
  • Production deploy + monitoring
  • Written runbook + handoff
  • 30-day on-call window
  • Optional retainer continuation
PRINCIPLES

How we keep it small.

Write things down

Every decision lives in a Notion page that you can read at 11pm in three months when you need it.

Working software, weekly

You see the product running, on a real URL, every Friday. No slide-only progress reports.

Two-week sprints

Plan Monday, ship Friday. Long enough to do real work, short enough to course-correct.

One shared backlog

Your team and ours work from the same list. No private engineering wishlist.

Small teams

2–4 people on a project. Communication overhead grows as O(n²). We keep n small.

Boring tech

We use proven tools. Postgres, React, Flutter, Swift. We optimise for your team being able to maintain it.