Pre-launch review
Launch with nothing left open.
Go through the staging site with your team and your client, on desktop, tablet and mobile. Every issue is a pin on the exact element with an owner and a due date, so you can see what is left before launch.
Made slowly,
made to stay.
Stoneware, oak and linen from a small studio in Aarhus.
Thrown, turned and woven by hand, in small runs.
The headline is bigger than in the design. Can it go back to 104 px?
2 repliesBefore layernote
“Is it ready
for Monday?”
The week before launch, everyone checks a different screen and reports it somewhere else. In layernote each issue is a pin with an owner, a priority and a due date, so ready means nothing left open.
The dates field cuts off the end date on a 13-inch laptop.
Marc KellerReplies2
Marc Keller15 min agoThe field is 220 px wide. I will give it the 300 from the design.
Dino4 min agoDeployed. The dates fit now, can you check?
Cabins at the end
of the road.
42 off-grid cabins across Norway and Sweden.
Book a night or a week. The kettle is on.
★ 4.9from 1,240 stays this year
Open staging. Check every device.
Clear the list before launch.
01Open the staging site
Paste the staging URL. Nothing to install on the site, and no extension for anyone.
02Review on every device
Your team and your client open the link and pin what they see on desktop, tablet or mobile. Each device keeps its own comments.
03Clear the list before launch
Give every issue an owner, a priority and a due date. Fix it yourself or hand it to your coding agent, until nothing is open.
Everything a launch check needs.Nothing for anyone to install.
- 01
Desktop, tablet and mobile
Switch devices in the review. Each one keeps its own comments, so a phone bug points at the phone layout.
- 02
An owner and a due date
Assign every issue, set its priority and due date, and the right person gets a notification.
- 03
A board to zero
On Studio and Team every issue moves across the board from open to resolved, and your client can follow along.
- 04
Fixed by you or your agent
Hand the open issues to Claude Code, Cursor or Codex over MCP, and each one comes back with what changed.
Customers
From studios that ship client work.
Flowdough
“I expected another tool my clients would ignore. They actually use it: our last review round went from a week of email ping-pong to one afternoon, without a single call to explain what they meant.”
Yes, as long as the page opens in a browser without a login: from a staging link to the production domain.
Yes. Switch between desktop, tablet and mobile in the review. Each device keeps its own comments, so a phone issue points at the phone layout.
On Studio and Team, switch on Task board access in the Share dialog and your client gets a read-only view of the board, with every card and its column.
Yes. Connect Claude Code, Cursor or Codex over MCP. The agent reads each issue with its element and a screenshot, fixes it in your codebase and resolves it with a note on what changed. MCP is on every plan.
Solo covers staging review on every device, owners, priorities and due dates for up to 3 team members, and the MCP handoff. Studio and Team add the task board and folders. Every plan starts with a 14-day free trial.
Because feedback shouldn’t be the hard part.
One link for your clients to review, one list for your team to resolve.