Project Requirements Generator
Generate a development-ready spec with user stories, acceptance criteria, T-shirt effort estimates, and a phased delivery plan. The AI cuts scope aggressively so your MVP ships in weeks, not months.
Free, no signup required. Results in 2-5 minutes.
How It Works
Describe Your Product
Tell the AI what you're building and who it's for. Business-level or technical — it sorts your input into the right categories automatically.
Define Core Features Together
The AI identifies your core differentiator, writes user stories with acceptance criteria, and classifies every feature as core, supporting, or generic.
Cut Scope Aggressively
Features get cut. For each one removed, you get a simpler alternative. The AI flags complexity traps like real-time, role-based access, and multi-tenancy.
Get Your Development Brief
A phased delivery plan with effort estimates, cost projections, and a clear MVP scope. Ready for developer handoff.
PRDs Written by Founders Miss the Hard Parts
You know what you want to build. But developers need acceptance criteria, edge cases, and effort estimates. This tool fills that gap — translating founder-speak into developer-ready specs.
Scope Kills MVPs
The biggest risk isn't building the wrong thing. It's building too much of the right thing. This tool actively cuts features and suggests simpler alternatives so your MVP ships in weeks, not months.
Estimates Without Context Are Useless
T-shirt sizing per feature, phased delivery mapped to weekly sprints, and complexity warnings for the features founders consistently underestimate. Real structure, not guesses.
Frequently Asked Questions
A BRD describes what the business needs. A PRD describes what the product does — features, user stories, acceptance criteria. Most founders mix the two, and that's fine. This tool accepts both and sorts them into the right structure. The business side is best handled in Business Model Canvas first.
Appetite-based sizing instead of hourly estimates. S: 1-2 days, M: 3-5 days, L: 1-2 weeks, XL: 2+ weeks. Each feature gets a size with brief reasoning. Fixed time, flexible scope — you decide how much fits, not how long it takes. The reasoning is in the Appetite, Not Estimates principle.
Yes. For every feature cut, you get a simpler alternative — presets over configuration, one user role before role-based access, email notifications before real-time. You can push back, but the AI flags scope risk when you keep everything. The discipline behind it is Scope Shaping.
Real-time features (+2-3 weeks), role-based permissions (L), file uploads (M), multi-tenancy (architectural decision). These are the features founders consistently underestimate. The AI calls them out with specific effort impact — and surfaces them in Build Cost & Plan.
Yes. The development brief includes user stories, acceptance criteria, technical constraints, and effort estimates — standard inputs for sprint planning with any team or freelancer. If you'd rather hand it to a single senior engineer, MVP in 6 Weeks is the build engagement that takes a PRD as input.
Where To Next
Next discovery step:Build Cost & Plan
Principles behind it:Scope Shaping, Appetite, Not Estimates
When you're ready to build:MVP in 6 WeeksPWA in 6 Weeks
Built & Maintained by Varstatt
Varstatt is a one-person product studio run by Jurij Tokarski, product engineer since 2011. These tools are free and open — no signup, no catch.