→ Loading process.runtime
Home / Process
Chapter 04 · Mission protocol · v 4.1

The runtime, step by step.

From the first conversation to 24/7 monitoring. Five phases, five tiers, zero black magic. We document every decision, publish our metrics, and you keep control at every checkpoint.

Phases5 tiers
Duration4 → 12 weeks
CadenceAsync-first · CET
See the timeline ↓
// 01 — Mission timeline

12 typical
weeks.

A trajectory, not a dead PDF. The NOW marker moves in real time along the path, we share daily progress on Linear and an async video standup in the morning.

Mission Replay00:00 / 00:18
  1. 01W1

    Discovery

    Scoping + audit

  2. 02W2–3

    Design

    UX + UI + tokens

  3. 03W4–5

    Build · S1

    Backend + auth

  4. 04W6–7

    Build · S2

    UI + integration

  5. 05W8–9

    Build · S3

    Stripe + polish

  6. 06W10

    QA + UAT

    Tests + UAT

  7. 07W11

    Ship

    Prod + handoff

  8. 08W12

    Runtime

    Monitoring

// Phase 01

Discovery
+ scoping

We always start from a conversation, never a PDF brief. Three workshops, two days of audit, one single doc: the mission spec. No agency slide-deck, just the decisions to make.

  • Existing audit: code, data, stack, technical debt
  • Targeted workshops: 3 personas max, their jobs-to-be-done
  • Mission spec: scope, milestones, explicit exclusions
  • Fixed quote or T&M depending on the brief's maturity
Duration 5 to 10 days Deliverable Mission spec PDF + Linear Price €2,800 flat
scope-calculator.tsx ● live
Complexity Standard
Estimated team 2 devs · 1 designer
Estimated duration 10 weeks
Estimate 42,000 €
// indicative simulation · firm quote after scoping
// Phase 02

Design
+ system

We don't design before we understand. We structure first in dense wireframes, then ramp up fidelity — and we generate a real design system in CSS tokens, not an orphan Figma file.

  • Low-fidelity wireframes reviewed live
  • High-fidelity mockups with reusable components
  • Design tokens exported as ready-to-code CSS variables
  • Clickable prototype to validate key flows
Duration 1 to 3 weeks Deliverable Figma + tokens.css Iterations 3 rounds included
design-stages.figma 3 layers
WIREFRAME MOCKUP PRODUCTION
──···
LogoMenu
⌁ OTTO● LIVE
// Phase 03

Build
+ sprints

Two-week sprints, demo on Friday. Everything is on GitHub, everything is commit-able by you. A preview URL per PR, a public Linear, a shared Slack channel.

  • Code in strict TypeScript, lint + tests mandatory
  • Automatic preview deploy on every pull request
  • Async video standup in the morning + demo on Friday
  • Linear / Jira shared read-write on the client side
Duration 4 to 8 weeks Cadence 2-wk sprint Visibility 100% GitHub + Linear
git log · main ↳ 142 commits
linear · sprint #14 23 of 31 done
Backlog 3
FEATEmpty state for filters@lou
BUGDate picker overflow mobile@max
CHOREBump expo SDK 51@max
In progress 2
FEATStripe checkout v2@theo
FEATMulti-tenant rls policies@max
Review 2
FEATOnboarding flow@lou
BUGiOS push token race@theo
Done 23
FEATMagic link auth@max
FEATOrg switcher@lou
// Phase 04

Ship
+ pipeline

Deployment is a green button, not a ceremony. CI/CD pipeline wired from day 1, preview environment per PR, one-click rollback. Go-live is a non-event.

  • GitHub Actions pipeline: lint → typecheck → tests → build → deploy
  • Preview env per PR + production on Vercel/Cloudflare
  • Sentry + Vercel Analytics wired before ship
  • Lighthouse audit + Web Vitals targeted ≥ 90 on every page
Duration 3 to 5 days Target Lighthouse ≥ 90 Rollback < 30 sec
github actions · #4218 running…
Install
npm ci
Lint
eslint .
Typecheck
tsc --noEmit
Test
vitest run
Build
next build
Deploy
vercel --prod
Stage 0 / 6 · click a stage to jump
lighthouse · /pricing desktop · mobile · throttled
0
Performance
0
Accessibility
0
Best Practices
0
SEO
// Phase 05

Runtime
+ monitoring

A living product isn't a product shipped and forgotten. Monthly runtime plan: 24/7 monitoring, security patches, small iterations, and an on-call dev for critical incidents.

  • Sentry + Better Stack monitoring + public status page
  • Security patches applied within 72h max
  • Monthly stand-up: roadmap, metrics, prioritization
  • Paid on-call for P0 incidents (response < 1h)
Commitment Monthly Plan from €1,200/mo SLA P0 < 1h · P1 < 24h
grafana · production / 7d healthy
Uptime · 30d
99.97%
↑ 0.02 vs last month
P95 response time
142ms
↓ 18ms vs last week
Error rate · 1h
0.03%
2 events / 7,840 req
// 02 — Principles

How
we work.

Six non-negotiable rules. They're not sales pitches, they're operational.

// p.01

Async-first

Video standup in the morning (Loom), no recurring meeting. Your afternoons are yours.

// p.02

Everything is readable

GitHub, Linear, Figma, Vercel: read access for all your stakeholders. No report to ask for.

// p.03

No nasty
surprises

An overrun > 10% triggers a check-in. We'd rather renegotiate than ship something half-baked.

// p.04

Code readable
by a human

Strict TypeScript, shared conventions, up-to-date README. No magic. Another dev must be able to take over.

// p.05

Ship small,
ship often

Sprints of 2 weeks max. Demo on Friday. If we have nothing to show, we got it wrong.

// p.06

Your data,
in your hands

Database, code, infra: everything is in your accounts. We have a session, not your business held hostage.

// 03 — Deliverables by phase

What you
actually
receive.

Four packs of tangible deliverables. Each signed on receipt, archived, transferable.

// Discovery
  • Mission spec PDF (15-25 pages)
  • Existing technical audit
  • Personas + jobs-to-be-done
  • Binding costed estimate
  • Macro 3-month roadmap
// Design
  • Figma 2 files: wireframes + UI
  • Design system (tokens.css)
  • Clickable prototype
  • Optimized SVG icons
  • Brand guidelines PDF
// Build
  • GitHub repo with clean history
  • README + ARCHITECTURE.md
  • Configured CI/CD pipeline
  • Preview env per PR
  • Unit + E2E tests (Playwright)
// Ship + Runtime
  • Prod live + DNS configured
  • Sentry + analytics wired
  • Public status page
  • Handoff doc + 30-min Loom
  • 30 days of warranty included
// Ready for takeoff?

We can start the
discovery this week.

No complex process. A 30-min call, a clear brief within 48h, an owned go/no-go on both sides.

K · for the curious