Skip to content

Guides

Bug reporting for agencies with many client sites

An agency needs three things from a bug reporting tool that a single product team does not: a price that does not grow with every client and every hire, clients who can report without an account and see only their own sites, and each client’s reports going to that client’s own board. Broken Here is priced by sites for that reason: $79 a month covers up to 25 client sites, with the whole team and every client included.

What it costs with twelve client sites

Take an agency with twelve client sites, six people who look at bugs, and a login for each client. Most tools in this category are priced by team member: the bill is set by how many of the six get a seat, and it grows with each hire, so somebody ends up reading bugs over a colleague’s shoulder.

Priced by sites, it is one number. Up to five sites is the Team plan at $29 a month; twelve sites is the Agency plan at $79 a month, and it stays $79 with six people or sixteen, and with twelve client logins or none. The people who report, your clients, their customers and your own colleagues, are never counted. See Broken Here pricing, or how it compares with Marker.io and BugHerd.

What an agency needs, and how it works here

  • Clients report without an account. A button on the site; they click what is broken and write one sentence. The report carries the page, the browser, the element, a screenshot, and the console errors and failed requests your developer would otherwise ask for.
  • A client login sees their own sites and nothing else. Every report on their sites, whoever filed it, with its status and your replies, never your other clients or your internal notes. Free on every plan.
  • Each client site files into its own board. Trackers are connected per site, so one client’s reports go to their Jira and another’s to your Linear team or a Trello board.
  • A review round is one ticket. Before launch, a team member goes through the site and reports as they go; Finish sends the whole round as one ticket, not twenty.
  • Staging, previews and live are one site. One project covers every address the site runs on, previews included, so a client’s staging copy does not cost a second site.
  • The reporter hears back. Whoever reported and left an email gets a status link, no login, that says when it is fixed.
  • WordPress in a minute. A plugin for client sites on WordPress; one script tag everywhere else.

When another tool fits better

If your clients want to work the feedback with you on a kanban board, that is BugHerd’s whole idea. If you want session replay beside each report, Marker.io has it on its higher plans. If a client wants surveys and a feature portal too, look at Userback. The roundup puts all of them side by side.

Try it on one client site

The free plan is one site, with client logins, for as long as you like. Put it on the client site that sends you the most emails, and read its first report. Or break the live demo and read the ticket it files.