Launch Approved vs. Hotjar, BugHerd & co
Feedback tools, heatmap tools and Launch Approved side by side: where your data lives, what you pay as you grow, and what each one really does.
Rent three tools, or own one
Testing a site before launch usually means renting several services. Feedback and bug tools such as BugHerd or Marker.io collect comments on the page. Heatmap and recording tools such as Hotjar or Clarity watch the visitors. None of them writes a test plan or gets the client’s signature.
Launch Approved takes another path: the whole acceptance test in one plugin, on your own WordPress, with one licence per site whatever the number of testers and rounds.
- Your data stays yours — answers, recordings and signatures live in your WordPress, on your server.
- Your costs do not grow with your testers — no fee per tester, no fee per session.
- Your client signs a proof — a report signed by the agency and the client, with a dated journey.
This page compares the approaches honestly. Each tool has its strengths; the right choice depends on your projects, your team and how much you want to own.
The three approaches at a glance
| Feedback and bug tools | Heatmap and recording tools | Launch Approved | |
|---|---|---|---|
| Examples | BugHerd, Marker.io | Hotjar, Microsoft Clarity | One WordPress plugin. |
| Where it runs | On the vendor’s servers. | On the vendor’s servers. | On your WordPress. |
| Where your data lives | At the vendor. | At the vendor. | In your WordPress, on your server. |
| How you pay | Every month, often per user or per project. | Free to start, then per volume of sessions. | One licence per site, every feature included. |
| Test plans and testers | Rarely: comments left on the page. | No: real visitors, no plan. | Steps, timer, invited testers, quality score. |
| Signed acceptance | No. | No. | Signed by the agency and the client, with its journey. |
These tools change their plans often: check their current offers before deciding.
What you pay as you grow
An agency often adds up several subscriptions: one for feedback, one for heatmaps and videos, sometimes one for usability tests. Each one grows with the number of users, projects or sessions. Launch Approved costs the same for one tester or fifty: one licence per site, every feature included.
| Your projects | Several rented tools | Launch Approved |
|---|---|---|
| 1 project, 5 testers | 2 or 3 subscriptions, every month | 2 sites: your site and the client’s |
| 5 projects, 30 testers | More seats, more sessions, every month | The 10-site plan |
| Every client in maintenance | The bill grows with each project | The 30-site plan, no fee per tester |
Features compared
| Feature | Often found elsewhere | In Launch Approved |
|---|---|---|
| Feedback with an annotated screenshot | Yes | Yes, as a finding with page, device and screen size |
| Heatmaps of clicks and scrolling | Yes | Yes, plus mouse moves, right clicks and the fold line |
| Video of each session | Yes | Yes, with a jump to every step |
| Test plan with steps and a timer | Rarely | Yes, with ready-made plans and import from Excel |
| Invited testers with a personal link | Sometimes | Yes, no account, tied to one computer |
| Testers’ contracts and pay statements | Rarely | Yes |
| Expert audit on the page (accessibility, contrast) | Rarely | Yes, accessibility by axe-core |
| Site health and e-mail of the domain | Rarely | Yes: links, SEO basics, SPF, DKIM, DMARC |
| Rounds compared before and after | Rarely | Yes, step by step |
| Report signed by the agency and the client | No | Yes, with a signed copy and its fingerprint |
| Cockpit and report in any language, every word editable | A few languages, some texts | Any language, every text |
| Your brand on every screen and e-mail | On higher plans | Yes, project by project |
Your data, your testers
A recording tool stores the clicks, the moves and the videos of your testers on its own servers, under its own terms: one more company to name in your privacy policy, one more transfer to justify. With Launch Approved, everything stays in your WordPress: you choose your host, your backups and how long videos are kept. Only positions are recorded, never what is typed.
Your site, your brand
Your testers open a cockpit with your logo and colours; your client reads a report signed by your agency, from your own domain. The only mention of Launch Approved is a small line at the foot of the report, and you can rewrite it like every other text.
When another tool is the better choice
We prefer to say it: another tool can suit you better if
- you want to watch all your public visitors, every day, at scale — that is the job of an analytics tool such as Clarity or Hotjar;
- you need testers provided for you — some testing platforms recruit panels of strangers, Launch Approved works with your own testers;
- you track bugs in your code — keep your developer tools; Launch Approved tests what users see and do;
- your product is not near a WordPress site and you do not wish to install one.
When Launch Approved makes the difference
- You deliver sites to clients — a test before launch, a report the client signs, a proof if anything is disputed.
- You run several rounds — fixes measured before and after, step by step.
- You work with your own testers — colleagues, client staff, users you recruit, paid or not.
- Your clients care about GDPR — nothing sent to another company, every recording on your server.
- You want one tool instead of three — plans, audits, heatmaps, videos, findings and signatures in one place.
Switching, or using both
- Install Launch Approved and create an example project to see every screen.
- Create the project of your next delivery and add a ready-made plan.
- Link the client’s site with the connector, then invite your testers.
- Keep your analytics tool for your daily traffic, if you wish: the two do not overlap.
See Getting Started and Pricing & licence to start.