Field notes
Practical writing for web agencies: bug reporting, client communication, tool choices, and the small workflow details that keep projects moving.
The retainer overrun you find out about at month-end is the expensive one. Here's how agencies track hours against client bug work so they see the burn building mid-month — while there's still time to do something about it.
Estimating bugs is harder than estimating features — you can't size what you haven't reproduced yet. Here's a practical way to estimate bug fixes for client work, and when to use story points versus hours.
"When will it be done?" is the question every retainer client asks and most agencies answer with a guess. Here's how to forecast delivery from work you're already tracking — and give clients a date you can actually stand behind.
Client bugs don't respect your sprint boundaries — they arrive whenever a client hits one. Here's how agencies fit a steady stream of client-reported bugs into a sprint rhythm without the plan falling apart.
Asana is one of the best project management tools available. But agencies that use it for client-facing bug tracking run into the same problems every time. Here's why, and what to use instead.
Basecamp is one of the few project management tools clients actually use — it's designed for them. But using it for bug tracking reveals a structural problem: client collaboration and bug triage are different jobs, and Basecamp only solves one of them.
Umbraco Cloud adds deployment environments, git-based workflows, and hosted infrastructure to the mix. Here's how Umbraco Cloud agencies track and fix client bugs without the context getting lost between environments.
Umbraco agencies deal with bugs in the backoffice, the front end, and the grey area between them. Lantern is the only bug tracking tool with a native Umbraco NuGet package — here's what that means in practice.
Web design agencies face a specific challenge: clients use 'bug' to mean anything from a broken layout to a colour they've changed their mind about. Here's how to handle real bugs professionally without design feedback getting mixed in.
Website maintenance agencies live and die by retainer efficiency. Here's how to handle client bug reports at scale — with flat-rate pricing that grows with you, not against you.
WooCommerce bugs aren't just inconvenient — a broken checkout means lost orders. Here's how WooCommerce agencies track and fix client store issues without the email chaos.
WordPress development agencies face a specific bug problem: the post-launch phase, when clients start using the site and find everything you missed in testing. Here's how to handle it without your inbox becoming the bug tracker.
WordPress maintenance agencies deal with a constant stream of bugs across multiple client sites. Here's how to handle the volume without drowning in email threads — and why flat-rate bug tracking fits the retainer model perfectly.
ClickUp markets itself as one app to replace them all — and for internal teams, it often delivers. But the client-facing bug reporting experience is a different story. Here's where ClickUp falls short for agencies, and what to use instead.
Tired of 'it's broken' emails with no context? Here are copy-paste templates to send clients, real before/after examples of good vs bad bug reports, and a faster way to skip the whole process.
Notion is flexible enough to hold a bug database — but flexible isn't the same as built for it. Here's where Notion breaks down for client-facing bug tracking, and what agencies use instead.
Notion, Trello, ClickUp, Asana, Basecamp — agencies default to what they already know. They're not wrong to try. But project management tools and bug trackers solve fundamentally different problems, and that mismatch shows up every time a client is involved.
The 'Reported / In Progress / Fixed' Trello board is a rite of passage for web agencies. It works — until clients stop using it, bugs fall through the cracks, and you're back to chasing email. Here's why Trello isn't the answer for client-facing bug tracking.
Comparing Atarim and Lantern for agency bug tracking. Atarim excels at visual design feedback on WordPress — but if you need structured bug tracking across multiple clients, here's why Lantern takes a different approach.
Umbraco agencies have specific needs that generic bug trackers don't address — non-technical clients, CMS-level issues, and backoffice-aware reporting. Here's what's actually worth using.
Feedbucket is a solid embeddable widget for visual bug reporting — but per-site pricing and limited issue tracking make it a tough fit for multi-client agencies. Here's how it compares to Lantern.
Monday.com is a powerful project management platform — but using it for client-facing bug tracking means asking non-technical clients to learn a complex tool they didn't ask for. Here's how it compares to Lantern.
Pastel makes visual feedback on live websites effortless — no installation, clean UI, perfect for one-off reviews. But for agencies managing ongoing bug tracking across multiple clients, here's where it stops being enough.
Stop chasing vague bug emails from clients. The Lantern Umbraco package adds a floating bug report button to your site — visible only to logged-in backoffice users, invisible to everyone else.
Stop chasing bug reports through email. Here's how to add a proper WordPress bug tracker to every client site — no plugin required, just one script tag.
Comparing BugHerd and Lantern for agency bug tracking. Features, pricing, pros/cons, and which tool is right for your web development team in 2026.
Comparing Marker.io and Lantern for agency bug tracking. Features, pricing, integrations, and which tool fits your team's workflow in 2026.
Comparing Usersnap and Lantern for agency bug tracking. Features, pricing, workflows, and which tool fits your team in 2026.
Managing bug reports across 20+ WordPress client sites is chaos. Here's the workflow that actually works for WordPress agencies.