There is a specific email that every software team has received a hundred times, and it goes like this: "Hey, the thing isn't working." No page. No browser. No screenshot. Sometimes a photo of a monitor taken with a phone, at an angle, slightly blurred. A developer reads it, sighs, and begins the interrogation - which page, which button, what were you doing, what browser are you on. By the time the actual bug is understood, an afternoon is gone. Marker.io was built to delete that email.
The Brussels-based company makes a website feedback and bug reporting tool. In plain terms: you add a small widget to a website, and anyone looking at it - a client, a tester, a colleague, a boss - can point at what is wrong, draw a circle around it, type a sentence, and hit submit. What lands in the development team's tracker is not a vague complaint. It is a screenshot with the annotation still on it, plus the browser, the operating system, the screen size, the console logs, and a recording of what the person clicked in the minute before things broke.
The originA tool built to fix its own makers' bad days
Marker.io did not start as a startup. It started as a web design agency run by Gary Gaspar, Olivier Kaisin and Emile-Victor Portenart, who spent their days building websites for clients and their evenings drowning in feedback about them. Clients would email lists of changes. Changes would arrive as annotated PDFs, or spreadsheets, or a wall of text in a thread that nobody could find later. Testing a site before launch meant copying all of it, by hand, into whatever the developers actually used.
So the founders built an internal fix, and then noticed the fix was more interesting than the agency. Around 2014 they turned it into a product. The pivot from services to software is a well-worn path, and most agencies that try it fail because they treat the product like a side hustle. Marker.io committed to it, kept the team small, and never took venture money.
That history shows up in the product's manners. Because the founders once sat on the receiving end of bad feedback, the tool is opinionated about small things - the guest who reports a bug should not have to make an account, the developer should not have to hunt for the browser version, and the client should never see the internal ticket where an engineer vents about the CSS. The people who built it had lived every one of those moments, and the design reflects a grudge worked out in code.
"Capture website feedback, bug reports, and visual feedback faster - without endless emails, PDFs, or screenshots."Marker.io, on what the whole thing is for
The problemThe reporter and the fixer speak different languages
The core insight is quiet but sharp: the person who finds a bug and the person who fixes it are almost never the same person, and they do not speak the same language. A client sees "the price looks weird on my phone." A developer needs "the currency component overflows its container below 380px on iOS Safari." Traditionally, someone has to translate between the two, and that someone is usually a project manager burning hours as a human relay.
Marker.io removes the translator by capturing the technical context automatically, at the moment of the complaint. The non-technical person does the easy part - point and describe. The tool quietly attaches everything the technical person would otherwise have to ask for.
The productOne widget, a lot going on underneath
On the surface, Marker.io is a button. Underneath, it is a set of features aimed at the two people the tool serves. For reporters, there is the annotation widget and a guest portal, which lets outside clients submit and follow feedback without needing a paid seat in the team's project management tool - a small detail that agencies love, because it keeps clients out of their backlog while still keeping them in the loop.
For developers, there is the part that matters: session replay, which records what the user did before the bug appeared, so nobody has to reconstruct it from memory; the full console log and technical metadata attached to every report; and two-way integrations that keep the ticket in Marker.io and the ticket in Jira in sync, so no one is copying statuses back and forth. More recently the company added data masking, so sensitive information can be hidden in screenshots and replays, and a layer of AI that translates, rewrites and titles feedback to make raw client comments legible.
The tool's job is to make the easy person's job easier - and let the hard person's job get easier as a side effect.
The customersAgencies first, enterprises quietly after
Marker.io's natural home is the web and digital agency, where client feedback is a daily tax. That is where it started and where much of its base still lives. But the same problem exists inside large product organizations, and the customer list has grown to include names like L'Oreal, Fujitsu, Patreon, Amgen and FantasyPros. Across roughly 3,000 active teams, more than two million feedback reports have moved through the widget.
The users inside those teams are a specific crowd: QA testers running user acceptance testing before a launch, product managers collecting stakeholder sign-off, support staff turning a customer complaint into a reproducible ticket, and developers who just want the console log without asking for it.
User acceptance testing is where the tool earns its keep most visibly. UAT is the phase before a website goes live, when a group of people click through everything and flag what is broken. Done the old way, it produces a spreadsheet with columns nobody agrees on and a hundred rows that need translating into tickets. Done through Marker.io, each flag is already a ticket, already routed, already carrying its evidence. The spreadsheet disappears. For an agency signing off a client project, that is the difference between a launch week and a launch month.
The differentiatorWhere it sits, and why teams stay
The visual feedback category is not empty. BugHerd, Usersnap, Userback, Ruttl and Pastel all live nearby, and plenty of teams try to fake the workflow with a screen recorder and a manual issue tracker. Marker.io's edge is depth on the developer side of the report and breadth on the integration side. Session replay and full technical metadata put more in the developer's hands than a simple annotation tool does, and the two-way sync means the project management tool - not Marker.io - stays the single source of truth. That last point matters more than it sounds. Teams distrust tools that try to replace their tracker. Marker.io is happy to feed it instead.
| What lands in the ticket | A plain email | Marker.io report |
|---|---|---|
| Annotated screenshot | Maybe, blurry | Yes |
| Browser, OS, screen size | You ask | Auto |
| Console logs & errors | No | Auto |
| Session replay | No | Yes |
| Two-way tracker sync | No | Yes |
The businessSmall on purpose, profitable on purpose
Marker.io sells the way most durable software businesses do: tiered per-seat subscriptions, starting around $39 a month, with the features developers care about - Jira sync, session replay, the developer console - sitting on the Team plan near $149 a month billed annually. Every plan opens with a 15-day free trial. Higher business tiers add invoice billing for companies that need it.
What is unusual is the shape of the company behind that pricing. Marker.io is bootstrapped. It raised no institutional venture money, reached roughly $492,000 in annual recurring revenue in 2024 - up about 61% from the year before - and did it with a team of around six people working remotely. In a market where the reflex is to raise a round and hire, Marker.io's answer was to stay small and keep the margins.
The marketA boring problem that never goes away
Bug reporting is not glamorous, which is exactly why it is a good business to be in. Every organization that ships a website has the feedback problem, forever, and the pain is concrete enough that people will pay to remove it. Marker.io fits into that market as the specialist that made one workflow - visual feedback that turns into a real ticket - genuinely good, rather than the platform that tries to own everything. For a six-person team, being the sharpest knife in a specific drawer is a defensible place to stand.
It is also a reminder embedded in a product: most of the friction in software is not the code. It is the conversation about the code. Marker.io took the most repetitive part of that conversation and turned it into a button.