> cat /process/workflow.md

> EXECUTION_PROTOCOL

No 12-step onboarding ritual. No discovery phase that costs more than the actual build. We keep it simple because complicated processes are what bad teams use to hide the fact that they’re not shipping.

STAGE_01

Discovery Call

ETA: 30–60 min

We hop on a call, you tell us what you’re building, we ask the questions your last agency didn’t. By the end you’ll know the rough scope, timeline, cost, and whether we’re the right fit.

OUTPUT:
[+] Straight-talk project assessment
[+] Tech stack recommendation
[+] Timeline and cost estimate
[+] Honest go/no-go advice
STAGE_02

Scope & Setup

ETA: 2–3 days

We nail down the spec, set up the repo, spin up the dev environment, and add you to our Slack. You’ll have visibility from day zero.

OUTPUT:
[+] Detailed project spec
[+] Repository access
[+] Communication channels
[+] First sprint plan
STAGE_03

Build & Ship

ETA: 2–6 weeks

The fun part. You’ll see working features every week—not wireframes, not “progress reports,” actual software you can click around. We deploy early and adjust based on your feedback.

OUTPUT:
[+] Weekly working demos
[+] Continuous deployment
[+] Feedback-driven iteration
[+] No “we’re 80% done” for 3 weeks straight
STAGE_04

Handoff

ETA: 2–3 days

We walk you through everything, document the non-obvious decisions, and make sure whoever touches this code next (even if it’s us on a retainer) can hit the ground running.

OUTPUT:
[+] Source code and documentation
[+] Deployment guide
[+] Architecture walkthrough
[+] 2-week post-launch support

WEEKLY_CYCLE <

Monday

Quick sync: what’s the priority this week?

Tue–Thu

Heads-down building. Reachable on Slack.

Wednesday

Mid-week check-in (if needed, not mandatory)

Friday

Demo day. You see what shipped.

> GUARANTEES.list()
[OK] Working software every week—not slide decks
[OK] All code reviewed and tested before it ships
[OK] You own every line of code from day one
[OK] 2-week post-launch support on every project
EXECUTE_PROTOCOL()