A six-week build is a scoping decision rather than a heroic sprint. We fix the deadline, keep the team tiny, and cut scope until the first useful version fits. Quality comes from doing fewer things properly, not from working longer.
What does week one look like?
One week for the sharpest version of the problem: the single workflow the product must nail, written as a paragraph anyone can read. Everything not in that paragraph is a later release.
How do you keep AI features reliable?
Evaluations from day one. Every prompt has a small set of real examples with expected outcomes, so a model or prompt change is a measurable event rather than a vibe.
What gets left out?
Teams, permissions, billing tiers, integrations and settings screens. Almost all of it can wait until customers ask by name.
FAQ
Does six weeks mean a prototype?
No. It means a small product real people can pay for, with monitoring and support in place.
How large is the team?
Usually one or two people. Coordination cost is the main enemy of a short timeline.
What happens after launch?
We operate the product for the long term, iterating with customers instead of moving on to the next idea.