Features
Plans, testers, cockpit, audits, heatmaps, findings and signed reports: everything Launch Approved does, in one page, with a link to each guide.
One plugin instead of five tools
A serious acceptance test usually needs several tools stitched together: a bug tracker, a heatmap service, a screen recorder, a survey form and a way to get the client’s signature. Launch Approved puts all of it inside WordPress, on your own site, with your own testers and your own data.
- Your testers follow clear steps in one cockpit, click in the product and answer, in their own language.
- You and your team audit, sort the findings and write the report from the WordPress admin you already know.
- Your client reads the report, comments the findings and signs the acceptance online, through a private link.
Every option has its own switch and every text your testers and clients read can be rewritten, so you keep only what fits your projects. This page gives an overview of each feature; the detailed guides are linked in the table below.
Everything at a glance
| What Launch Approved does | Guide | |
|---|---|---|
| Test plans | Sections and steps, ready-made plans, import from Excel, A/B and five-second tests. | Getting Started |
| Testers | A personal link per tester, contracts, pay statements and a quality score for each test. | Testers: invite, pay & contracts |
| Expert tools | Inspector, contrast, accessibility, page weight, technology and plugins, right on the page. | Expert tools & site audit |
| Behaviour | Heatmaps of clicks, scrolling and mouse moves, and a video of each test. | Heatmaps, videos & behaviour |
| Reports | Findings board, rounds compared, a report signed by the agency and the client, a dated journey. | Reports, signatures & traceability |
| Client sites | A secure connector to test the client’s own site and switch plugins off in the test zone. | Connector & client sites |
| Languages | Admin in English, French and Spanish; cockpit and report in any language, with your brand. | Multilingual & white label |
| Team | Admin, project managers, experts and clients, each with their own rights. | Agencies, teams & clients |
Projects, campaigns and rounds
A project is what you test: a website, a web app, a document, a desktop software or a physical product. Each project holds its address, its client, its goals (clarity, accessibility, speed, conversion…) and its brand.
A campaign is one test of that project. Five kinds: an acceptance test signed by the client, an expert audit, a pilot with real users, a quick test through one shared link, and a practice run where nothing is recorded. A campaign opens and closes on the dates you set, or when you decide.
Fixes done? Create the next round in one click: the same steps, or only those that failed, the same testers invited again, and a report that compares before and after. Every round keeps its own date, testers and signatures.
Test plans and steps
A plan is made of sections and steps. Each step has an instruction, the expected result, a target time and a time limit, the page to open, and optional questions after the answer. Steps are reordered by drag and drop, and a plan can be saved as a template for the next project.
- Ready-made plans — first impression, contact form, checkout, account, accessibility, mobile… added in one click.
- Import — a CSV file, or rows pasted from Excel or Google Sheets.
- Special steps — first click on the right element, five-second test, A/B versions, a file to review, a measure to take on a real product.
- SUS questionnaire — the standard usability score out of 100 at the end of the test.
Testers, invitations and pay
Each tester gets a personal link: no account, no password. Invite them one by one, paste a list from Excel, or let candidates apply through a form on your site. Once the test starts, the link is tied to one computer: nobody takes it for someone else.
Before starting, the tester can confirm who they are, sign a contract and accept the video. After the test, a quality score reads the time spent, the answers, the clicks and the time away in another tab, and the team validates or refuses each test.
When testers are paid, Launch Approved keeps a statement per tester and per month: the amount due, the bonus, the budget used. It never pays anyone itself: you mark what you paid. A testers’ directory keeps everyone with their tags, devices and past campaigns.
The three-panel cockpit
Everything happens in one screen: the steps on the left, your product in the middle, the answers on the right. The tester reads the step (or hears it read aloud), acts in the product, then answers: it works, it fails, I am blocked, or not clear.
- Timer — the time of each step, against the target you set.
- Feelings and remarks — a few emojis, a comment, a follow-up question.
- Screenshots — annotated with arrows, frames and numbers, sent as findings.
- Devices — the product shown at computer, tablet or phone size.
A tester can take a break, and a test stopped by a reload goes on where it was, or is stopped, as the campaign decides. A practice run lets testers discover the cockpit before the real test.
Expert tools and audits
For the team, the cockpit adds the expert tools under the product: an inspector, colour contrast, accessibility checked by axe-core (WCAG 2.2, A and AA), page weight and requests, structure of the headings, technology and plugins detected, and the clicks of the testers. Each problem becomes a finding in one click, with a proposed CSS fix if you wish.
Three ways to open the product: this WordPress, the client’s real site through the connector, or an analysis copy locked in a sandbox. In the test zone only, plugins can be switched off to find the one that breaks a page, without touching what real visitors see.
Heatmaps and videos
Three views of all the testers together, on the picture of each page, alone or on top of each other: scrolling (from red, seen by all, to blue, seen by almost nobody, with the fold line), mouse moves (the reading path, often a Z) and clicks (left, right, rage clicks, clicks on what does nothing).
The picture of each page is taken by itself the first time it opens. Each test can also be recorded as a video, with the tester’s consent, a jump to every step and the browser’s bars cut off. Only positions are recorded, never what is typed.
Findings board
Every finding lands on a board: to do, in progress, to check, done, refused. Each card keeps its page, device, screen size and screenshots, before and after pictures, a proposed CSS fix and a discussion with the client.
Sort and filter by kind, severity or screen; give each finding an impact and an effort (quick win, big project…), a person who fixes it and a deadline, shown in red when it is late. When several testers report the same problem, the cards are merged and counted.
Report and signatures
The report writes itself from the answers and findings: key figures, steps tested with their colours, feelings, findings, testers and devices, comparison with the previous round. You add a summary, your reading of each step and a conclusion, then choose the findings and heatmaps the client sees.
- You sign for the agency — the report is frozen.
- You send it — a private link by e-mail, every sending kept with its date.
- The client signs — accepted, accepted with reservations or refused, or « read and acknowledged » for an audit.
A signed copy is kept with its SHA-256 fingerprint. The report exports to PDF, Word, Excel and CSV, and partial reports can be sent before the end of a campaign.
Journey and history
The Journey tab dates the essential steps of every round: created, opened, testers invited and finished, signed for the agency, sent, opened by the client, reminded, countersigned. The state of the report shows in colour, and the journey prints as a certificate. The History keeps every detail, for any dispute.
Site health and brand charter
Your server reads the site like a visitor: titles and descriptions, headings, language, noindex, canonical, structured data, broken links, robots.txt, sitemap and llms.txt, then the e-mail of the domain (MX, SPF, DKIM, DMARC…) and two or three competitors side by side.
A brand checker flags forbidden words, missing required mentions, brand names badly written, and colours or fonts off the charter. The reading is kept for the next round, and can be repeated on a schedule.
Client sites and the connector
Install Launch Approved on the client’s site and paste a key: the two sites are linked by a signed connector. Your testers then test the real site, logged as visitors, with clicks and heatmaps recorded, and the plugins you choose switched off for them only. The exact list of the client’s plugins and their versions shows in the Ecosystem tab.
Languages, brand and display
The admin speaks English, French and Spanish. The cockpit, the e-mails and the report speak any language: every word your testers and clients read can be rewritten. Each project can carry its own logo, colours and sender, so the client sees your brand, not ours. A dark display is offered in the admin, the cockpit and the report.
E-mails and reminders
Invitations, reminders to testers before the end, a thank-you, a notice when a reported problem is fixed, a summary by e-mail for the team and for the client, and reminders to the client who has not signed yet: automatic, proposed or off.
Everything can be switched off
No feature is forced on you. Timer, video, heatmaps, mouse moves, contract, pay, quality notice, dark display, client votes, reminders and many more each have their own switch. Start simple and turn on what your projects need, when they need it.
Every setting is described on the Settings Reference page, and common questions are answered in the FAQ.