Skip to content
sanaan®
Process

A factory floor you can walk.

Software projects fail in the dark. Ours run in the open: five phases, weekly demos, a staging URL that gets better every Friday, and a support plan that outlives the launch party. This page is the actual operating manual, not marketing.

01The five phases
01

Discover

Weeks 1–2

We learn your business before touching your product. Stakeholder interviews, analytics teardown, competitive review, and technical audit — compressed into two weeks, ending in a scoped plan with a fixed price.

What you'll see

A written plan you could hand to any competent team — including one that isn't us.

Deliverables
  • Discovery brief
  • Scope & fixed quote
  • Technical architecture memo
  • Success metrics
02

Design

Weeks 2–5

Design runs as a five-day sprint cycle: map, sketch, decide, prototype, test. You see clickable work every Friday, not a big reveal at the end. The design system is built in parallel so engineering never waits.

What you'll see

A prototype in your hands by the end of the first design week.

Deliverables
  • Clickable prototypes
  • Design system & tokens
  • Copy deck
  • Usability test notes
03

Build

Weeks 4–10

Engineering overlaps design by design. Weekly staging deploys you can click, a shared issue board you can read, and demos every Friday. No black-box months — you watch the product assemble.

What you'll see

A staging URL that gets visibly better every week.

Deliverables
  • Weekly staging builds
  • Friday demos
  • Test coverage on critical paths
  • Performance budgets in CI
04

Launch

Weeks 10–12

Launch is a checklist, not a ceremony: performance passes, accessibility review, analytics verification, redirect maps, rollback plan. We ship in the morning, watch the dashboards, and stay on call.

What you'll see

A boring launch day. That's the point.

Deliverables
  • Launch checklist & rollback plan
  • Analytics verification
  • SEO/redirect map
  • Handover docs & training
05

Support

Ongoing

Software needs care after launch — we say so upfront instead of disappearing. Every project includes a 60-day warranty; after that, support runs on a transparent retainer with defined response times.

What you'll see

A named engineer answering — the same people who built it.

Deliverables
  • 60-day warranty on all work
  • P1 response within 4 business hours
  • Monthly health report
  • Roadmap reviews quarterly
02Inside the design phase

One week from question to tested prototype.

Design runs on a five-day sprint cycle. Here's one week, hour by honest hour.

  1. Mon

    Map

    Frame the problem, pick the target journey.

  2. Tue

    Sketch

    Competing solutions on paper, not opinions in meetings.

  3. Wed

    Decide

    One direction chosen, storyboarded screen by screen.

  4. Thu

    Prototype

    A realistic clickable prototype by end of day.

  5. Fri

    Test

    Five users, recorded sessions, decisions from evidence.

03After launch

Software needs care. We say so upfront.

Every engagement includes a 60-day warranty — anything we built that breaks, we fix, free, fast. After that, support runs on a retainer with response times we put in writing. The engineers who built your product answer the tickets; there is no “support tier” of strangers.

Support retainers from $49/mo · included in all growth retainers

Severity

First response

Target resolution

P1 — Production down

4 business hours

Same day

P2 — Feature broken

1 business day

Within 3 days

P3 — Cosmetic / minor

2 business days

Next release

Measured from your message, not from when we “triage” it. Misses are credited without being asked.

04Who does the work

The team you meet in the first call is the team that ships. No handoff to a “delivery office,” no rotating cast, no offshore bait-and-switch.

Six senior people, one standard. Meet them.