Clients click the actual flow.
They see the browser behavior, copy, responsive states, and rough edges that screenshots miss.
Agencies
Walk clients through local work before staging exists.
Open a temporary link to the build on your machine. Clients review the flow in their browser while you watch joins, requests, and failures.
How it works
Three steps. One review window.
Start from the build in front of you, share a scoped link, and keep the session visible while reviewers click through.
01
Start from localhost
Run the app you plan to review. Point wiremaven at the port and set the access window.
$ wiremaven --port 3000 --expires 45m
relay active
tunnel: relay.wm/p/client-walkthrough
expires: 45m · overlay: enabled
02
Send the client link
Drop the relay URL into the meeting chat or project thread. The client opens the working build in a browser.
03
Watch the walkthrough
Viewer joins, request outcomes, and failures stay visible while the client moves through the work.
Why wiremaven
Client feedback works better in the real build.
Staging often waits on content, auth, or deploy chores. wiremaven lets agencies review the local build while the work still has momentum.
Access has an end time.
Set the expiry before the call. The link closes when the review window ends.
Issues show up during review.
The request feed shows broken paths, failed assets, and slow responses while the client clicks.
No staging queue.
Share the local build while deploy scripts, content, or credentials are still in motion.
The shift
From screen-share guessing to a review with session context.
Before
- Staging waits on content or credentials
- Screen share hides client browser issues
- Feedback arrives after the call with no trail
- The review URL stays open in old threads
- Developers chase vague bug notes
After
- Clients open your local build in their browser
- Viewer count shows who joined the walkthrough
- Request events point to the broken path
- Expiry closes access after the review
- Session context turns notes into fixes
What you get
Client walkthroughs stay scoped and visible.
Time-boxed links
Choose the review window before you share. Access closes when the window ends.
No client account
Clients click a URL and land on the build. They do not install tools or join your workspace.
Live viewer count
See who joined the walkthrough and when new reviewers arrive.
Request outcome feed
Keep successes, failures, and timings visible during the review.
Encrypted relay
Your machine connects outbound to wiremaven. You do not open an inbound public port.
Works before deploy
If the client-ready flow runs on localhost, you can put it in front of the client.
Start here
Run the next client review from localhost.
Start a tunnel, send the link, and keep the walkthrough visible while the work is still local.
Read the docs FAQ
Common questions
- Does the client need a wiremaven account?
- No. The client receives a URL and opens it in a browser. You keep the overlay and session events on your side.
- Can multiple client reviewers join the same walkthrough?
- Yes. Share one link with the group. The overlay shows viewer activity as reviewers join.
- What happens when the review ends?
- The link expires at the time you choose. After that, reviewers see the expired-link page.
- Can this replace staging for production signoff?
- No. Use wiremaven for local review and in-progress walkthroughs. Keep formal release signoff on your normal staging path.