Skip to content
Process

How weship.

4–6 weeksTimeline to production
01
Discover
48h
02
Build
Scoped after discovery
03
Ship
Launch phase
04
Scale
Ongoing
Milestone-gated • Demo every weekFixed scope • Weekly demos • 4–6 weeks

Assembly — 04 stages

Every engagement runs the same four phases with visible milestones — you always know what ships next and when. 4–6 weeks to prod

Phase 01
Discover — Map the core user journey, cut nonessential features, and de
Discover
01 — Discover

Discover

Map the core user journey, cut nonessential features, and define the product architecture. The sprint ends with a clear build scope and decisions your team can act on.

  • Map the primary user flow
  • Define the first release
  • Outline system architecture
  • Agree on milestones and decisions
Next →02 — BuildNext
Start a projectFixed scope • No surprises
Phase 02
Build — Turn the agreed scope into a working product. Develop the in
Build
02 — Build

Build

Turn the agreed scope into a working product. Develop the interface, application logic, and database together, with preview deployments and regular demos throughout.

  • Build the core user experience
  • Implement APIs and database schema
  • Set up CI and preview deployments
  • Review working demos regularly
Next →03 — ShipNext
Start a projectFixed scope • No surprises
Phase 03
Ship — Test the complete product, resolve release blockers, and dep
Ship
03 — Ship

Ship

Test the complete product, resolve release blockers, and deploy with monitoring in place. Launch only when the experience is accessible, performant, and ready to operate.

  • Test critical user journeys
  • Audit accessibility and performance
  • Configure monitoring and alerts
  • Deploy with a rollback plan
Next →04 — ScaleNext
Start a projectFixed scope • No surprises
Phase 04
Scale — Improve the live product using usage data and customer feedb
Scale
04 — Scale

Scale

Improve the live product using usage data and customer feedback. Expand capacity where demand requires it, while maintaining reliability and keeping new work focused.

  • Monitor usage and product health
  • Prioritize improvements from evidence
  • Increase capacity as demand grows
  • Maintain and support the live product
Next →Production • 99.9% uptimeNext
Start a projectFixed scope • No surprises
Deep Dive

What ships every stage

Hard gates, not slides. Each stage must pass strict checks before wire advances.

Discover
  • Map the primary user flow
  • Define the first release
  • Outline system architecture
Build
  • Build the core user experience
  • Implement APIs and database schema
  • Set up CI and preview deployments
Ship
  • Test critical user journeys
  • Audit accessibility and performance
  • Configure monitoring and alerts
Scale
  • Monitor usage and product health
  • Prioritize improvements from evidence
  • Increase capacity as demand grows
Fixed scope • Weekly demos • 4–6 weeks

Timeline: 4–6 weeks to production

One team from discovery to production. Fixed scope after day two, a working preview by day three, and observability from the first deploy. Start in 48 hours, previews on day 3.

Fixed scope • Weekly demos • 4–6 weeks • Fixed scope • No surprises • 04 stages