Hand clients proof that your build works.
OKShip uses the site the way a person would, checks the goals you (or your client) set, and gives you a link your client can open: a replay video, screenshots from the run, and a plain-English verdict for each goal.
A real run on kidsqueue.com, a live site we run, as your team sees it in OKShip. Pick any point on the right to see where it lives.
kidsqueue.com
Blog Works
User should be able to select a non-member only blog post and read it
The user was able to navigate to the Blog page and open a non-member blog post ("The First Week of Daycare: What Nobody Actually Warns You About"), which loaded fully and was readable without requiring a login or membership.
0:00replay-84307fb9.mp4- 1. Followed a link from the home page to /tools-provider
- 2. Opened the webinar sign-up form
- 3. Filled "Your name*" with "Test Visitor"
- 4. Filled "Work email*" with "test.visitor@example.com"
- 5. Submitted the form; the page answered "School name is required"
- 6. Typed, with no field recorded
- 7. Opened the School list
- 8. Picked "a Place Where Kids Are Always First"
- 9. Submitted the form; the site replied 201 and showed "Registered successfully"
You wrote one sentence. OKShip worked out the steps, took them in a real browser, and recorded each one with a screenshot and a time.
Win the work, then keep it
The same report helps before the pitch, at handover, and long after launch.
- Before the pitch
Close more deals
Run a few goals on a prospect's current site and bring the report to the call. Real findings on their own site make a stronger case than a portfolio slide.
- At handover
Sign-off without the back-and-forth
Send the proof link with the launch email. Your client sees every goal pass, with the replay and screenshots, before the final invoice goes out.
- After launch
Upsell monitoring
Rerun the same goals on a schedule and offer it as a monthly care plan. Every run adds a fresh report that shows the site still works.
Share it on your terms
Send one link to every stakeholder. Each proof link has its own settings: keep it open, put it behind a password, or ask viewers for their email address first. Set when it expires, set a view limit, and add a button that brings them back to you.
From finished build to proof in four steps
- 1
Add the client's site
Paste the address of the staging or live site.
- 2
Write the goals in plain English
"A visitor can locate my form, complete the required fields according to my specifications, and successfully submit the lead capture form." OKShip turns each goal into steps. No test code.
- 3
OKShip runs them in a real browser
Every action is recorded with a screenshot and a timestamp, and the run is replayed as video.
- 4
Send the proof link
Everyone who needs to sign off sees what was checked and how it went.
How OKShip is different
You already have ways to check a build. None of them hand your client something they can read and trust.
| Compared on | Writing test code | Uptime and screenshot monitors | A walkthrough you record | OKShip |
|---|---|---|---|---|
| Who sets the checks | A developer, in code | A web address and a schedule | Whoever records it | You or your client, in plain English |
| What gets checked | Whatever the code asserts | That the page loads, or looks the same | Whatever was clicked that day | Each goal, tried the way a person would |
| What your client sees | Nothing they can read | A status page or an alert | A video with no verdict | A verdict for every goal, screenshots and a replay video |
| When something breaks | A failing test log | An alert that something is down | You find out later | The failing step, its screenshot, and why |
| If you want code later | You already have it | Nothing to take with you | Nothing to take with you | Export the run as a Playwright script |
Clients are paying more for work they can trust, and less for work when they have to take your word for it. OKShip turns that trust into something you can send.
What checking by hand costs you
Clicking through a site before handover, recording a walkthrough, answering "is it working?" emails. Put in your own numbers and compare.
An estimate from the numbers you enter, not a promise. See every plan on the pricing page.
Questions agencies ask
You can start for free. Plans and limits are on the pricing page.
Do my clients need an OKShip account?
No. They open the proof link in any browser. You can still put it behind a password, or ask for their email address first.
Do I need to write test code?
No. You write goals in plain English and OKShip works out the steps. If your developers want code, export the run as a Playwright script.
Can it check a staging site?
Yes. Point it at any public address, staging or live. It can't reach sites on a private network or behind HTTP basic auth.
Can it check pages behind a login?
Yes. Sign in once from the Connections page, and runs use that session. Runs that use a signed-in session are started by hand rather than on a schedule.
What happens when a goal fails?
The report shows the step where it went wrong, the screenshot from that moment, and OKShip's explanation. Fix it and run the goal again.
Can the report carry my branding instead of OKShip's?
On the Studio plan, you can hide OKShip's branding from the proof link.
Can I keep checking a site after launch?
Yes. On the Builder plan and above, schedule the same goals to run again and share each new report. It fits naturally into a monthly care plan.
Does it replace our QA?
No. It checks the goals you set and records the evidence. Use it as proof for what matters most, alongside the testing you already do.