Align specs, previews, and launch plans before they ship.
Review product specs, launch narratives, GTM content, static HTML pages, beta feedback forms, and opted-in live previews with cross-functional context in one workspace.
Commentary keeps the written plan and the preview surface close enough for product, design, and engineering to resolve feedback together.
- Product specs
- Forms feedback
- Live previews
- Cross-functional review
Plans and previews need the same review rhythm.
Launch plans, product specs, and messaging usually move across docs, previews, chat, and tickets. Feedback loses force when it is split by tool.
Teams need one place to review the written plan and point at the preview or draft that proves it.
Review the plan and the preview in the same rhythm.
Draft Reviews cover specs and launch content before Git, Forms collect launch readiness or beta feedback, HTML Review covers static pages and generated reports, and Live Preview Reviews add element-level context when the running surface needs review.
- Spec and launch narrativeKeep requirements, owners, rollout order, and GTM copy readable before work ships.
- Feedback and signoff formsUse launch readiness forms, beta feedback forms, response links, and anonymous responses only when explicitly configured.
- Static HTML pagesReview generated reports, static docs output, and HTML briefs without treating them like live app previews.
- Opted-in preview contextUse Live Preview Reviews when UI text, states, or docs-site pages need point-and-comment feedback.
Product review works best when the plan and surface stay together.
The written decision and the customer-facing preview should reinforce each other before launch.
Split launch feedback
- Spec comments, preview notes, and GTM edits live in different tools.
- Design feedback loses the product decision that motivated it.
- Launch readiness depends on manual status stitching.
Connected product review
- Specs and launch plans stay readable for every reviewer.
- Preview comments point at the UI or docs state under review.
- Final decisions stay tied to the artifact that ships.
Commentary keeps product decisions readable.
Review the document first, use draft reviews before Git, and add Live Preview Reviews when the UI or docs site needs element-level feedback.
A cross-functional review loop.
Use Commentary for the plan, the draft, and the preview when launch clarity depends on all three.
- 01
Open the spec, launch plan, static HTML page, or draft.
- 02
Comment on messaging, owners, and release sequence.
- 03
Collect launch readiness or beta feedback through review-hosted Forms when the answer should be structured.
- 04
Use Live Preview Reviews when UI context matters.
- 05
Resolve feedback before the plan ships.
Align before the plan ships.
Use Live Preview Reviews for UI context or Draft Reviews for specs and launch content before a PR exists.