Bug reports for founders who are also the QA team
One button that a customer, a contractor and you can all press, so everything you have to fix arrives in the same shape.
Nobody is going to standardise this for you
Four kinds of reporter, four shapes of report, and one person triaging all of it.
A customer emails a blurry photo of their own screen. A contractor drops a sentence into Slack at midnight. You spot something on your phone at the school gate and lose it by the evening. A friend testing the beta says "the signup thing is weird".
Every one of those arrives in a different shape, and you are the reporter, the triager and the person who fixes it. There is no QA lead who will insist on a template, and writing one would only mean you are the person chasing people to fill it in.
So the standard has to come from the capture instead of from a process. If the same button is what everyone presses, then every report carries the console, the requests and the browser whether the person sending it knew what those were or not.
Built for the founder doing four jobs at once
The cost that matters here is setup and handoff, not features.
One button for customers, contractors and yourself
The same capture whoever presses it, so you are not maintaining one process for the people who pay you and another for the people you pay.
Nothing for you to install on the product
Two lines in your layout put the button on every page. It comes off again by deleting them, and there is no SDK, no build step and no account for the person reporting.
Claim the domain, get one list
Every report filed against your product lands in the same place with a status on it, instead of living in four inboxes and a Slack channel you have muted.
Forward one link, no seat to buy
The contractor fixing it opens the report without signing up for anything. You are not paying for a seat so that somebody can read a bug once a fortnight.
Enough to debug it yourself at 11pm
Console output with stack traces, every request with method, status and timing, and the browser, operating system and window size it happened in.
It files into whatever you already use
Jira, Linear, GitHub, Slack or a webhook of your own, when somebody presses the button on that report. You do not move your work somewhere new to use this.
An afternoon to set up, and then it is there
Install the extension for yourself
Ten minutes, and from then on you can capture anything you hit yourself, on any site, without touching your product at all.
Put the two-line button on the product
A script tag and an empty element in your layout. The button that appears is ours, so there is nothing to design, and a visitor without the extension is offered it by the button itself.
Send the link to whoever is fixing it
Which is often you. Paste it into your tracker, your notes or a message to the contractor, and it opens with the page in the state somebody found it in.
What this costs while you are small
The button, the library and the extension are free, and so is every report your customers file: nobody reporting a bug on your product needs an account, a seat or a trial. If that is all you need, it stays free.
What a paid plan buys is what happens to the reports afterwards - claiming your domain so they arrive in one dashboard rather than only on the links people send you, and longer recordings. Reports keep for 30 days on the free and Starter plans, and for 90 days on Professional.
See pricingWhat this does not do
You are already paying for too many tools, so it is worth being clear about which one this is not:
- It is not a bug tracker or a project board. There is no backlog, no sprint and no assignment; a report goes to wherever you already track work.
- There are no seats to buy for the people reporting bugs, because they never have accounts in the first place.
- No always-on recording. Capture is deliberate: a person presses a button, and only then is anything recorded.
- No analytics, no funnels and no heatmaps. This tells you about one defect, not about how your product is used.
- Nothing is filed into a tracker on its own. A report becomes an issue when somebody presses the button on it.
Questions founders ask
One button, for every direction a bug arrives from
Set it up once while you are small, and stop rebuilding the same conversation with every person who tells you something is broken.