Log every version in sequence
Each named version records what changed from the one before it and why, building a chronological trail instead of scattered files.
Free MVP design tool
Revision Map
Log each design iteration with what changed and why, and get a clear version-by-version map instead of a folder of unlabeled screenshots.
- Calculated instantly from your inputs
- No signup or data submission
- A focused next step for MVP planning
Your entries remain in this browser session and are not sent to MVPHub.
Your inputs
Track what changed between design versions
Enter one version per line as Version label | what changed | reason (feedback/testing/bug/opinion/scope). List every named revision in order, oldest first.
Your calculated result
Your result
0/100
Planning score
Recommended next actions
How it works
Classify each change by driver
Every change is tagged as coming from feedback, testing, a bug fix, opinion, or scope change — showing what is actually driving the design forward.
Highlight churn vs. real progress
Repeated changes to the same area without testing or feedback backing them are flagged as potential churn worth stepping back from.
Frequently asked questions
How is this different from just naming files v1, v2, v3?
File names show a version exists but not why it changed. Revision Map requires and structures the reason for every change, so the history stays legible months later.
What counts as churn?
When the same screen is revised repeatedly on opinion alone, without feedback or testing between rounds — the tool flags this pattern so you can pause and validate before iterating further.
Can I track more than one screen at a time?
Run it once per screen or flow — mixing multiple screens in one log makes the change-driver pattern harder to read.
Does this store my actual design files?
No — this only organizes the version labels, descriptions and reasons you type in; keep your actual design files in your design tool of record.
How we compare
| Capability | MVPHub | Figma version history | A shared screenshots folder |
|---|---|---|---|
| Requires a documented reason for every change | ✓ | × | × |
| Flags opinion-driven churn automatically | ✓ | × | × |
| Actual visual diffing of design files | × | ✓ | × |
| No account, paste and get a revision map instantly | ✓ | × | ✓ |
MVPHub captures the reasoning behind each revision, which Figma's version history and a screenshots folder do not track. Use Figma alongside this for actual visual diffs.