The bug came in on a Tuesday. Subject line: "Website issue." Body: "Hi, there's something wrong with the homepage."
No URL. No browser. No steps to reproduce. No screenshot.
You copy the email into your Notion database, add a status of "To Do," and reply asking for more information. Three days later the client replies with "still not working." Two more back-and-forths later, you figure out it only happens in Safari on mobile. You fix it. The client emails again to say thanks. You manually update the status to "Done."
Repeat for every client. Every bug. Every month.
That's not a Notion problem — Notion is a genuinely excellent tool. That's a Notion-for-client-bug-tracking problem. There's a difference.
Why Agencies Start in Notion
It makes sense. You already use Notion. It's free (or nearly so), it's flexible enough to model almost anything, and setting up a basic bug database takes about fifteen minutes. A few columns — client name, status, description, priority — and you have something that looks like a bug tracker.
For internal work, it's fine. Your team can log bugs, assign them, update statuses. It beats a shared spreadsheet.
The trouble starts when clients enter the picture. Because Notion wasn't built for client-facing workflows, and every workaround you add to make it work creates new friction somewhere else.
Where Notion Breaks Down
1. Clients don't log into Notion
Sharing a Notion page with a client requires them to create a Notion account, accept an invite, learn to navigate the interface, and remember to go there instead of emailing you. Most won't. They'll send an email, a Slack message, or a WhatsApp — and your Notion database becomes a log of bugs your team heard about, not a place clients actually use.
2. No embedded widget
When a client notices a bug on their website, they're in their WordPress admin or Umbraco backoffice. To report it in Notion, they have to stop what they're doing, open a different tab, find the Notion link you shared six months ago, and fill in the form — if you built one. That context switch is too much friction. Most clients don't make it. The bug gets emailed instead.
3. Text descriptions only — no video
Notion supports file attachments, so a client could theoretically record a video and attach it. But there's no built-in prompting, no Loom integration, no one-click recording. In practice, clients write text. And written descriptions of interactive bugs — "the button doesn't work," "the form is broken," "something looks off on mobile" — are almost never enough to reproduce the issue without follow-up questions.
Every vague description adds a round-trip of clarification emails before a developer can even look at the bug. Multiply that across ten clients and twenty bugs a month.
4. No per-client scoping
One Notion database for all clients sounds manageable at first. Then you have eight clients, forty open bugs, and a database that requires a PhD in filters to navigate. Worse, if you give clients view access, they can see each other's issues. If you create separate databases per client, you've tripled your admin overhead and given up any cross-client visibility.
There's no clean answer inside Notion because the data model wasn't designed for this.
5. Clients don't know what's happening
Once a client submits a bug (or emails you one and you log it yourself), they have no visibility into what happens next. Did you see it? Is someone working on it? Was it fixed? They don't know, so they email to ask. You reply. They email again. The bug tracker becomes an inbox problem you're running in parallel.
6. No structure means no consistency
Notion forms help, but they're optional and easy to bypass. Without enforced fields, bug reports look different every time — some have priority set, most don't; some have browser info, most don't. You can add instructions and required fields, but you're building and maintaining tooling that a purpose-built tracker gives you out of the box.
What Purpose-Built Bug Tracking Looks Like
A tool built for client-facing agency bug tracking does a few specific things that Notion doesn't:
- Clients can submit bugs without creating an account
- The reporting button lives inside the client's CMS, not in a separate tool they have to remember
- Video walkthroughs replace written descriptions — clients show you the bug, not describe it
- Each client has an isolated view of their own issues
- Clients can see status updates without emailing you
These aren't advanced features. They're the baseline for a tool designed around how agencies and clients actually work.
How Lantern Solves It
Lantern is built specifically for this workflow.
No account needed for clients. Each client gets a portal at a unique URL. They click the link, click "Report Bug," and submit. No sign-up, no onboarding, no explaining where to go. The barrier is low enough that clients actually use it.
Widget inside their CMS. The bug report button embeds directly into the client's WordPress admin or Umbraco backoffice — visible only to logged-in users, invisible to visitors. Clients report bugs from exactly where they found them, without switching tools.
Loom video built in. When a client hits "Report Bug," they can record a 30-second Loom walkthrough. You see their browser, the URL, exactly what they did, and exactly what broke. No follow-up questions. Fix it on the first pass.
Per-client portals. Each client has their own scoped view. They see their issues only. You see all clients in one dashboard, with filters to cut across clients when you need to. The data model is built for multi-client agency work from the ground up.
Status visibility. Clients can see the status of their bug reports in their portal — no need to email you asking for an update. That alone cuts a significant chunk of inbound noise.
Lantern's Team plan is £30/month flat for unlimited clients. No per-seat charges for clients, no cost increase as your agency grows.
The Honest Summary
Notion is one of the best tools available for knowledge management and internal workflows. It's not a bug tracker — at least not in the way agencies need one when clients are involved.
If you're running client websites on support retainers and managing bugs via email, Notion, or a shared spreadsheet, you're spending more time on the process than the process saves you.
Try Lantern free for 14 days →
No credit card required on the Individual plan.
Already using Notion internally and want to keep it? Lantern works alongside your existing tools — bug reports flow in from clients, your team triages them in Lantern, and you can integrate with Jira if bugs need to move into your dev workflow.
Simple bug tracking for agencies. No credit card required.