[ DELIVERY_PROTOCOL: v6 ]

How We
Operate

Six stages. No standups. One written brief. Working software every Friday.

01

Brief

Week 0 — 3 days

We co-author a 1-page document: problem, constraints, success metric, non-goals. Nothing else starts until this is signed.

// DELIVERABLES
Written brief
Success metric
Fixed-price quote
02

Architect

Week 1

Information architecture, technical stack decisions, motion principles, and the design tokens that will govern every pixel.

// DELIVERABLES
IA map
Token system
Stack ADR
03

Build

Weeks 2 — N

1-week iteration cycles. Every Friday a working preview ships to staging. Feedback in context, in code — not in PDFs.

// DELIVERABLES
Weekly preview
Live changelog
Slack channel
04

Harden

Final week

Performance budget enforcement, accessibility audit (WCAG 2.2 AA), security review, full E2E suite green.

// DELIVERABLES
Lighthouse 95+
WCAG audit
Playwright suite
05

Ship

Launch day

Zero-downtime deploy, real-user monitoring wired, on-call rotation in place. We watch the first 24 hours with you.

// DELIVERABLES
Production deploy
RUM dashboard
Runbook
06

Sustain

Optional

Monthly retainer covers monitoring, dependency updates, small features. Or full handover with documentation.

// DELIVERABLES
Retainer or handover
Source code
Architecture doc
[ PRODUCTION_STACK ]

The Tools

FRONTEND
  • React 19
  • TanStack Start
  • Tailwind v4
  • Motion
BACKEND
  • Cloudflare Workers
  • Postgres
  • Drizzle ORM
  • tRPC
INFRA
  • GitHub Actions
  • Vercel / CF Pages
  • Sentry
  • PostHog
TOOLING
  • TypeScript strict
  • Vitest
  • Playwright
  • Biome