How we work
The seven-day sprint
One week, one team, one shipped MVP. Here's what each day looks like, what we ship, and what we refuse to do.
Operating principles
Cut, don't stretch
Every feature has to earn its slot in the MVP. The rest gets a v1.1 ticket and waits its turn.
Same-day responses
One Slack channel, one shared Linear, no PMs in the middle. Decisions in hours, not weeks.
Daily working builds
TestFlight + Play internal track every evening. You see real progress, not status decks.
Hard timeboxes
We pick a Monday and we ship the following Sunday. Scope flexes — the date doesn't.
The 7-day sprint
What a week looks like
A real MVP sprint, day by day. Not a pitch deck — the actual cadence.
Day 01
Kickoff & scope
Signed sprint brief, locked must-haves, killed the rest.
Day 02
Design sprint
Clickable Figma covering every core flow.
Day 03
Foundations
Auth, data model, design system, CI/CD live.
Day 04–05
Build the core
Daily TestFlight builds. You break it, we patch it overnight.
Day 06
Polish & instrument
Empty states, edge cases, analytics, crash reporting.
Day 07
Beta & handover
Real users on TestFlight + Play internal track. MVP shipped.
Day 08+
Store submission
We submit to App Store + Play. Review is 14 days minimum — that part lives with Apple and Google.
What we ship with
These are the defaults — the stack we know cold and reach for unless your team already runs something else. We'll meet you on whatever you use.
- Mobile
- Expo · native Swift / Kotlin · Flutter · Tauri
- Web
- Next.js · Vite · Astro
- Backend
- Node · Rust · .NET · Python
- Database
- Postgres (default) · NoSQL where it fits
- Auth
- Better Auth
- Infra
- Vercel · BYO cloud · VPS
- CI/CD
- GitHub Actions
- Monitoring
- Sentry · Google Analytics · PostHog on request
- AI
- LLM integrations, agents, embeddings — when it earns its place
- Also in scope
- PWAs · push notifications · transactional & marketing email
Got a Monday in mind?
Send a brief. We'll come back with a fixed quote and a sprint slot within 24 hours.
Send a brief