How we shipped a SaaS in 11 weeks

The project started with a three-hour scoping session that produced a single constraint: one user action must drive revenue within the first session. That constraint eliminated half the feature list immediately.

Weeks one and two were design and architecture. Weeks three through eight were parallel tracks: backend services and frontend in sync, with a shared type layer that caught integration bugs before they became integration days. Week eleven was a controlled launch to a waitlist that had been building during development.