Most product arguments are two people describing different screens with the same words, and the cheapest way to end one is to look at it: on 54 a screen is a real published page in minutes, with a link anyone on the team can open and a rollback for the version that was wrong.
A spec is a promise that everyone read it the same way. They did not. The useful move is to **put the screen in front of the three people who disagree** before anyone estimates it — and that only happens if making the screen is cheap enough to be wrong twice.
Swipe to compare all columns →
| The usual loop | 54 | |
|---|---|---|
| Deciding what to build | A document and a meeting | A screen people can click |
| Who can look at it | Whoever has the design tool | Anyone with the link |
| The second iteration | Next sprint | The same afternoon |
| Going back | Find the old file | Roll back to any version in one click |
| The internal tool nobody prioritised | A spreadsheet forever | A form, a list and a login, built by describing it |
Written from each product's public documentation. Products change: check theirs before you decide. No prices here for the same reason.
No. It produces a working page, not a picture of one.
Yes: records, a form and a list.
Yes, require a login.
Yes, from the link, and store what they type.
Download the files: standard HTML, CSS and JavaScript.
No, and that is the point: if it is good enough, keep building on it.
That is usually the best first thing to build here.
Publish one, keep the version, publish the other.
A plan is per account; the free one includes ten builds a day.
Yes, as records on the same site.