Home/Process
How we cook

From brief to deploy
in four hot weeks.

No 6-month “discovery.” No 80-page SOWs. Just four sharp steps, daily updates, weekly demos, and a working product at the end. Here’s exactly how it goes.

01
Week 0 — Pre-kickoff · 2–3 days

Ingredients — discovery.

A 30-min intro call, a written brief, and a fixed quote within 48 hours. If we’re a fit, we sign and book a kickoff. If we’re not — we’ll refer you to someone who is. No pitch decks, no $5k “discovery” tax.

What we do

  • 30-min intro call (or async if you prefer)
  • Brief + reference review
  • Tech/scope assessment
  • Written quote & timeline
  • Contract + 30% deposit invoice

What you get

  • A fixed quote (no “TBD” line items)
  • A Notion workspace with goals + scope
  • Slack channel access
  • Calendar invites for first sprint
CalendlyNotionSlackDocuSign
02
Week 1 — Sprint 1 · 5 days

Prep — design & tech spec.

In week one we lock down design direction, write the technical spec, and stand up the dev environment. By Friday you’ve got real Figma screens (not mood boards), a clear data model, and a working “hello world” deploy.

What we do

  • Brand & design direction (2 concepts)
  • Core flows wireframed + designed
  • Tech spec, data model, API contract
  • Repo, CI/CD, staging environment
  • Friday demo + feedback round

What you get

  • Figma file with high-fidelity screens
  • Technical spec doc (Notion)
  • GitHub repo & staging URL
  • Project board with all tickets
FigmaGitHubLinearVercelLoom
03
Weeks 2–3 — Sprint 2 & 3 · 10 days

On the wok — building.

Two sprints of focused building. Daily 90-second Loom updates so you always know what shipped. Weekly demos every Friday. Async-first: no daily standups eating your morning. Just shipped tickets, working features, and Slack threads when needed.

What we do

  • 2-week sprints with planned scope
  • Daily Loom updates (90 sec, no meetings)
  • Weekly Friday demo on staging
  • Continuous deployment to staging
  • Tests, error tracking, perf monitoring

What you get

  • Working features shipping daily to staging
  • Loom videos archive (review at your own pace)
  • Live project board you can ping anytime
  • Direct Slack with the engineers
GitHubVercelLinearLoomSentryPostHog
04
Week 4 — Launch · 5 days + 90-day support

Served — launch & support.

Final QA, accessibility pass, performance tune-up, deploy to production. We hand over the keys: full repo access, docs, deployment guide, video walkthrough. Then 90 days of free post-launch support — bug fixes, small tweaks, you ping, we fix.

What we do

  • Production deploy + DNS handover
  • QA pass (security, perf, accessibility)
  • Documentation + Loom walkthrough
  • Team training (if needed)
  • 90-day free post-launch support

What you get

  • Live production deployment
  • Full repo + IP assignment
  • Setup & deploy docs
  • Direct Slack for support window
  • Optional retainer for v2 features
VercelAWSCloudflareSentryNotion docs
Receipts

What lands in your inbox
every week.

Daily Loom updates

90-second video updates Mon–Fri showing what shipped, what’s next, and any blockers. No meetings required.

Weekly Friday demo

Live 30-min demo on staging. Walk through new features. You give feedback. We adjust the sprint. Done.

Async Slack access

Direct line to the engineers. Reply in your timezone, your hours. We aim for <4 hr response during work days.

Kitchen rules

The principles we cook by.

01 — Ship small, ship often

Working software > perfect software

We’d rather ship a v1 in 3 weeks than a perfect v0 in 3 months. Real users beat imaginary requirements every time.

02 — Async by default

Your calendar is sacred

Loom over Zoom. Async PRs over standups. Two scheduled syncs per week, max. The rest is in Slack, on your schedule.

03 — Boring tech, bold ideas

Battle-tested stacks only

We don’t experiment with your codebase. Postgres, Next.js, Node — the stuff that runs at 3am without us. Bold lives in the UX, not the infra.

04 — One throat to choke

You have one project lead, period

No account managers, no project coordinators, no chain of vibes. The senior engineer who builds it is the one you Slack.

05 — No hourly billing

Fixed scope, fixed price

Hourly billing punishes speed and rewards bloat. We quote a price, lock the scope, and ship. No surprise invoices.

06 — You own it. Always.

Full code, full IP, day one

The repo lives in your GitHub org from day one. We’re collaborators, not landlords. Fire us tomorrow and you lose zero days.

Ready to cook
something special?