Week 0

Discover

Weeks 1–2

Design

Weeks 2–8

Build

Week 8–10

Launch

Ongoing

Support

§ Phase 01

01

Week 0 · 60–90 min

Discover.

A single working call. We map the problem, the workflow, the constraints — and decide together if this is even a fit.

What we do

  • Walk the current workflow with whoever does it daily
  • Identify the 1–2 things that are actually broken
  • Pull the real numbers — volume, time spent, current costs
  • Stress-test the scope against the budget

What you get

  • A scoped problem statement, in writing
  • Clear yes / no on whether we're the right shop
  • If yes → a fixed proposal within 2 business days
  • If no → at least one referral that's better-suited
→ Deliverable: Scoped Proposal

§ Phase 02

02

Weeks 1–2

Design.

High-fidelity mockups for the three or four screens that matter most. Not every screen — the rest will be designed in code as we build.

What we do

  • Information architecture: routes, permissions, data shape
  • Hi-fi mockups for hero screens — designed in Figma
  • Token system: colors, spacing, type, components
  • Edge cases on the table: empty states, errors, loading

What you get

  • Figma file for the 3–5 highest-impact screens
  • Design tokens, ready to drop into code
  • One round of substantive revisions, baked in
  • Sign-off doc — what's locked, what stays flexible
→ Deliverable: Design Sign-Off

§ Phase 03

03

Weeks 2–8

Build.

Heads-down engineering, with a working build available at the end of every week. You see real progress, not slide updates.

What we do

  • Ship in milestones, each one demoable on a real URL
  • Friday demos — 20 min, not a whole afternoon
  • You get repo access from day one, not at the end
  • Tests written for the parts that'd hurt most to break

What you get

  • Staging URL, updated continuously
  • Weekly demo + written status (always under 1 page)
  • Direct Slack/email line — no support ticket queue
  • All code in your GitHub by milestone two
→ Deliverable: Production-Ready Build

§ Phase 04

04

Weeks 8–10

Launch.

UAT, content load-in, real users on it. We're with you through go-live and two weeks of stabilization after.

What we do

  • UAT round with your actual users (not stakeholders)
  • Production deploy + DNS cutover
  • Performance pass: Lighthouse, lazy-loads, caching
  • Two weeks of priority bug-fix coverage post-launch

What you get

  • Live production environment in your accounts
  • Admin onboarding session — recorded
  • Runbook: deploys, rollbacks, monitoring
  • Final architecture write-up, in your repo
→ Deliverable: Live Software

§ Phase 05

05

Optional · ongoing

Support.

Most clients run their own software after launch. Some keep us on a retainer for quarterly improvements and the inevitable "can we add…".

What we do

  • Monthly retainer — reserved hours, no minimum
  • Quarterly check-in: usage, friction, what to build next
  • Priority response on production issues
  • You can leave any month — no long contracts

What you get

  • Reserved monthly hours for changes & new features
  • Priority bug-fix SLA
  • Quarterly roadmap document
  • Optional: on-call coverage for high-stakes deploys
→ Deliverable: Reserved Bandwidth

§ Guarantees

In writing.

What you can
hold us to.

01

Fixed-price proposals.

Every project comes with a fixed scope and a fixed price. If we underestimate, that's our problem. The price you sign is the price you pay.

02

No surprise ownership.

Code, designs, infra — everything ships to your accounts from day one. We won't hold deliverables hostage. We won't slow-walk a handover. Ever.

03

Senior on every line.

We don't hand work down. The person who scopes the project is the person who builds it. No offshoring, no juniors learning on your dime.

Sound workable?

Book a
discover call.

60–90 minutes. We'll either come back with a proposal or a referral. Either way you leave with clarity.

Start a Project →