A Website QA Platform Built To Scale
QualityHive came to us with an idea and a waiting list. We built them a Laravel platform that web design and development agencies now use to capture bugs straight from a client's website, assign them to developers and close them off, and handed it over as clean, documented code.
The Brief
Agencies were collecting website feedback the hard way: long email threads, shared spreadsheets and screenshots pasted into documents. Nothing was assignable, nothing was searchable, and the same bug was often reported three times by three different people.
QualityHive needed a platform an agency could roll out to a client in minutes, with a browser extension that captures a bug straight from the page, complete with a screenshot, the exact URL and the browser and screen it happened on, and an API their clients' project tools could talk to.
What We Built
One platform, three jobs: capture a bug on the page, triage it with the team, prove it fixed to the client.
Point-And-Click Capture
A browser extension pins a bug straight onto the client's site, grabbing a screenshot, the exact URL and the browser, OS and screen size, so nobody has to describe where it happened.
Assignment And Triage
Every bug routes to a developer with a status, a due date and a full comment thread. Duplicates are caught as they are raised, on a board the whole team shares.
Client-Ready Reporting
Open bugs, resolution rates and project progress export as clean, branded reports, which is what QualityHive's own agency customers renew on.
Roles And Permissions
Agency, developer and client each see their own view of a project, with per-project access managed by the account owner.
Billing And Trials
Per-seat subscriptions, trial expiry and proration wired through Stripe, so the team can price without touching code.
A Documented API
A REST API with webhooks and written docs, so their customers' project tools can pull bug data without our involvement.
How We Ran It
Four stages, weekly demos, and direct access to the developer writing the code. No account managers in between.
Two workshops with real agency feedback in hand, then a written spec and a fixed quote.
Every screen agreed in grayscale before a line of Laravel, so changes cost minutes rather than sprints.
Fortnightly releases to a staging site the team could hand to pilot customers and comment on directly.
Repository, environment notes and API docs transferred, with a retained day a month for support.
The Result
QualityHive launched to their pilot agencies in week 14 and replaced the email-and-spreadsheet routine entirely. Feedback that used to take an evening to chase down is now captured in a click from the page it happened on, and the API means larger customers can pull bug data into their own reporting without asking anyone.
We still support the platform on a retained day a month, and the code sits in their repository, not ours.
We built QualityHive because website QA was still being run through email threads and spreadsheets. Now an agency captures a bug in a click straight from the page, assigns it and closes it off, all in one place. It has become the tool teams open first thing in the morning, which is exactly what we set out to build.
Development Director, Zestcode
Got A Platform Idea In Mind?
Book in a call with us to see how we can support you from brief to launch and beyond.
