About this starter prototype
A little clarity
A lot of possibility
Turn the problem you see into a first release you can shape. Start with an editable plan, then explore a working prototype.
- 01DescribeThe user and their problem
- 02ShapeThe scope and assumptions
- 03ExploreA browser prototype
Or borrow a starting point
Use an example to fill the idea, then edit it before planning. Starter mode proposes a predefined app pattern; review its fit before generating.
Get the team aligned on the problem
Confirm the user and business goal, choose the first release, and prepare the brief for review.
Open decisions
These assumptions keep the first build manageable. Update the scope as you learn.
Make “done” observable
Example: a client can request a change on a deliverable and see the saved request after refresh. Replace template criteria with checks for your actual workflow.
Features & scope
Choose the features needed for the first release (MVP). Group them by workflow or user role, and keep later work in Post-MVP.
Planning estimates
Review how scope, hourly rate, and team size affect the estimate. These assumptions help compare scenarios before a delivery proposal.
Effort by discipline
Story estimates
MVP development sequence
Illustrative order by development effort. Dependencies and parallel work are not modeled.
BEFORE A DELIVERY COMMITMENT
Turn assumptions into an agreed delivery plan
A browser prototype lets you test the workflow. Production needs explicit engineering, operating, and review decisions.
People & capacity
Name the product decision-maker, engineering owner, design and QA responsibilities, and available review time. Confirm these in the proposal.
Architecture & access
The current prototype is HTML, CSS, and JavaScript with sample data. Production hosting, authentication, database, integrations, and recovery procedures are decisions to review with the technical owner.
Choose tools for the workflow, data sensitivity, existing systems, and operating ownership.
Operating budget
Estimate hosting, storage, service usage, AI volume, monitoring, backups, and support separately. Confirm vendor plans and limits against expected usage.
Use the budget workbookMilestones & acceptance
Agree the scope, owners, review cadence, test data, and evidence for each milestone. Accept work against observable criteria; review timing and cost before adding new scope.
See the review and handover approachBring the full scope to your review
Download the full brief to keep every story, note, and acceptance criterion. The project-review page receives a shorter summary.
Let's make it tangible
Turn your current scope into a browser prototype you can explore.
Keep building with the source
Inspect the generated files and download a runnable browser prototype with the full project scope.
How to run and review the download
- Download the source ZIP for your current scope.
- Extract it and open
index.htmlin a modern browser. - Test with sample data. The ZIP includes HTML, CSS, JavaScript, a README, and the full scope including deferred stories.
Browser prototypes do not provide production accounts, shared storage, or payments. Review security, licensing, accessibility, and integrations before production use.
Generate a prototype to inspect its source here.