Insights
Creating business opportunities with error tracking
Spatie Team
When running production applications for your clients, it can take days until a bug is reported to your team. This reporting-delay might not be critical to the business of your client if it is a low traffic site, but it might be a direct financial loss if it’s a high-traffic application. If the site doesn’t have a high amount of traffic, it’s still a bad experience for the user, and it will have a negative impact on the business in the long-term–a negative impact that can be avoided easily.
This is the point where an error tracker comes into place. The error tracker takes care if something breaks, and you instantly get a notification. With this notification, you receive much additional information about the incident so that tracking down the issue becomes much more comfortable than relying on screenshots provided by a user who contacts the customer support of your client. With the error tracker, you stay in the loop and be aware of the problem before the client calls and raises the issue. In Flare, the notification also includes the user who got the error, other useful context information, and if it is a common issue–a solution how to fix it.
When working with clients, they usually require some service-level-agreement when an application goes live. The easiest way to handle this on a basic level is by adding a monitoring service like Flare to the application and dedicate some weekly time to handle errors. This formalizes responsibilities but also creates business opportunities along the way. While the SLA covers the costs for the error tracker multiple times, you create new touch-points with your clients. These touch-points can be used to offer new services or to stay connected with your contacts.
This is how a happy client looks like
![]()
Staying in touch via errors might sound like an odd way for a new opportunity. Still, if you can solve an issue before the client event notices the problem themselves and notify them that you’ve already handled it, they know that they are in good hands.
Being recognized as a partner that cares, usually brings in a steady stream for project requests and makes it easier for you to run your business.
With Flare, you can track unlimited projects, so if the first SLA already pays the bill, Flare is free for all other applications, and you can add your internal applications at no additional cost.
Continue reading
Why we removed AI solutions from Flare
AI generated solutions are dead, long live AI generated solutions! We removed the old one-shot fixes from a model that could only see the stack trace. It simply couldn't compete with modern agentic AI. In their place, Flare works with the agentic AI tools you already use: an MCP server that handles real triage, a CLI with an agent skill, quick Copy for AI prompts in the UI and docs served as markdown. Hosted agents are in the works too.
Alex
Flare now uses OAuth for MCP, the CLI, and API
Connect MCP clients like Claude and Cursor to Flare by logging in from your browser, no more copying API tokens. Every connection gets its own permissions, so you can give your AI read-only access to a single project. The CLI signs in the same way, and new personal access tokens with scopes and expiry cover scripts and CI.
Alex
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates