I Didn't Need a Kanban Board. I Needed to Know What Broke.

I've shipped a handful of things over the years. Some my own, some through my day job. Different products, different users, different stacks. The one thing that's stayed the same every time: bug reports with zero context.

No screenshot. No steps. No idea what browser they'd been using. Just "it's broken," and me losing an entire day trying to reproduce something I couldn't see.

So I went looking for something that would fix that. I found it, sort of, tools like BugHerd and Marker.io do exactly this kind of thing, and they do it well. Click an element, leave a comment, and it gets pinned right there with a screenshot and the browser details attached. That part is genuinely great.

But then I looked at the pricing page. And the integrations list. Jira. Trello. Asana. ClickUp. monday.com. A Kanban board. Client permission tiers. Guest seat management.

I didn't need any of that. I'm one person, shipping one product, and I just wanted to know when something broke and what the browser said when it did. I wasn't going to route bug reports through a project management pipeline I don't have, into a Kanban board I'd check once and forget about.

I didn't want to pay enterprise pricing for tooling built around a workflow I don't run.

So I built the version I actually wanted

SiteSay is a single script tag. No SDK, no build step. It adds a small floating button to your site. When someone clicks it to report a bug, an idea, or general feedback, the report already comes with the browser's console errors, uncaught JavaScript errors, unhandled Promise rejections, and the visitor's browser and device context. The user can also optionally take up to 10 screenshots. No back-and-forth asking what they were using or what they saw.

That's it. That's the whole tool. There's no task board, no client permission system, no forty-tool integration matrix. If your workflow needs a Kanban board and deep PM-tool syncing, BugHerd and Marker.io are the right call, I'm not going to pretend otherwise, they built for that on purpose and they're good at it.

But if you're a solo dev, a freelancer, or a small team who just wants a live feedback channel on a product that's already shipped, or a tool in test, you probably don't need any of that either. You need the report to already know what broke, so you don't have to ask.

Where SiteSay actually fits

The honest way to think about it: BugHerd and Marker.io are built for a specific kind of workflow: a client or stakeholder reviewing a site, pinning comments to exact elements, tracking dozens of them through to done across a project management tool. That's a real workflow, and if that's yours, use one of them.

SiteSay is for everything else. Whether you're gathering test feedback before launch or listening to real users after it, you get the technical details attached automatically, without setting up a review process or paying for a dozen integrations you'll never open.

I also didn't want the pricing to punish small teams for being small. SiteSay's plans start well under what most of these tools charge, and the free trial doesn't ask for a credit card because if you're the kind of person building this stuff on the side, you already know what it feels like to get asked to commit before you've even tried the thing.

If this sounds like your problem too

I built SiteSay to solve my own problem first. If "it's broken" tickets with zero context are eating your time, or you've looked at the bigger feedback tools and thought "I don't need all this," give SiteSay a try. Fourteen days, no card required.