Feature Sprint
One Feature, Shipped.
Single production feature on existing codebase, 2 weeks.
actually get
Production is live. The roadmap has a feature your team can't quite get over the line — too complex for a junior, too small to hire for. Two weeks, one architect, one specific feature shipped end-to-end on your existing codebase: UI, server logic, persistence, tests, analytics, empty states, error states.
Scoping happens before the clock starts; the acceptance criteria are signed before week one. After handoff, you can scope another Feature Sprint or graduate to a Velocity Pod for ongoing capacity.
Hard limits
- Features1 (with defined acceptance criteria)
- User-facing screens≤ 5
- New database entities≤ 3
- New integrations≤ 2 third-party
In every Feature Sprint
- Acceptance criteria document (signed before week 1)
- All UI, server logic, persistence, tests
- Empty states + error states + edge cases
- Analytics events wired
- 30-day post-ship bug fix window
Explicit exclusions
- Feature spec / discovery (bring requirements)
- Net-new architecture (use Blueprint first)
- Cross-feature integration beyond the 1 feature
- UX research / user interviews
Opinionated by default
One default stack for 80% of builds. Same stack shipped wintura.ai. Same stack the architect knows cold and has a runbook for at 3 a.m. When you swap pieces, the timeline goes up — the scoping call surfaces the swap before work starts.
Operational rhythm
Not a process for show — the scaffolding that keeps a fixed-price engagement on track when life happens. Same rhythm across every Lift, Sprint, and Pod.
Daily commits
Every weekday, to a branch you can pull and run locally.
End-of-day async videos
3–5 min Loom summarizing decisions and blockers — review on your schedule.
Friday demo on Zoom
30 min walkthrough of what shipped that week — questions answered live.
Slack-first, decisions in 24h
Our workspace and yours linked. Questions get answered in a day, both directions.
Concrete deliverables
No slide deck. No "phase 2 proposal." The list below is what hits your repo, your inbox, and your stack on the last day of the engagement.
Most agencies say "fixed price" and reserve the right to add a change order the moment the brief shifts. Soatech doesn't.
The way fixed price stays honest is by being unreasonable about scope. The scoping doc lists every flow, every screen, every integration. If something isn't on that list, it isn't in this engagement. If you discover during the build that you need it, the current scope ships as planned, and v1.1 begins after handoff — at the next tier's price, or as a follow-on Feature Sprint.
This sounds rigid. In practice founders consistently report it's the most valuable thing about the process — the discipline of saying "v1.1" thirty times across six weeks is what keeps the timeline honest.
Teams with an existing production app needing one specific feature shipped fast. Post-MVP buyers who don't yet need an ongoing Pod.
Greenfield builds (use Blueprint + MVP Sprint). Ongoing feature pipelines (use Velocity Pod). Feature discovery / spec work.
Related from the blog
Fixed Price vs Time and Materials: Which Contract Model Is Better?
Compare fixed price vs time and materials contracts for software development. Pros, cons, risk distribution, and when each model works best.
The Wintura Playbook — Exactly How I Ship Production MVPs at Soatech
Day-by-day walkthrough of the 30-day MVP Sprint process Soatech runs, derived from the actual Wintura.ai build (Next.js 16, Claude Sonnet 4.6, multi-tenant Postgres, 24 e2e tests).
MVP Feature Checklist: What to Include and What to Skip
Use the MoSCoW method and prioritization matrix to decide which features belong in your MVP. Avoid the #1 mistake founders make.
Skip the sales reps. Book the Architect directly.
30 minutes. Scope your project with a senior architect — the same studio that shipped wintura.ai. Your assigned architect is confirmed after scope sign-off.
30-min Blueprint scoping call
Direct line to the Architect. No SDR. No nurture sequence. Confirmed within 24 hours.
- CET available · async time-zone friendly
- Calendar invite + Google Meet auto-sent
- Blueprint fee converts to Sprint One
- 30 minutes · free