HOW WE WORK

A process built around you.

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

I understand your problem before I build anything.

Stakeholder interviews, an 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 I am building and why.

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

Forge

Tight design and engineering loops.

Working software early, not slides. I work in short sprints with a regular demo, a clear plan, and a single shared backlog. You see everything in production the moment it lands.

Deliverables
  • Regular sprint cadence
  • Demo + plan check-ins
  • Staging deploys from day one
  • Regular written status notes
03

Polish

The 5% of detail most teams skip.

Performance budgets, accessibility audit, motion pass. I measure before and after: load times, Core Web Vitals, jank, and 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

Production launch, monitoring, runbook.

Your team owns it from day one. I stay on call after launch for incidents, hotfixes, and small adjustments, at no extra cost. A written runbook means you're never stuck waiting on me.

Deliverables
  • Production deploy + monitoring
  • Written runbook + handoff
  • Post-launch on-call support
  • Optional retainer continuation
PRINCIPLES

How we keep it small.

Write things down

Every decision lives in an Obsidian vault you can read at 11pm in three months when you need it.

Working software, regularly

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

Short sprints

Plan, build, ship, check in, repeat. Long enough to do real work, short enough to course-correct.

One shared backlog

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

Direct line

You work with the person doing the work, not a rotating cast of account managers.

Boring tech

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