Blar Success Case: Finnecto

Introduction

The first time we met Vicente, Finnecto’s CTO, he had just resolved a bug that caused a three-hour partial outage in one of their modules. Exhausted but relieved, he shared his frustration—his story perfectly aligned with what Blar was built to solve: preventing bugs from reaching production.

When we introduced Blar and explained how it could prevent bugs, optimize code, and identify vulnerabilities before deployment, Vicente was intrigued but skeptical. He challenged us:

"If your product can catch the bug that caused this outage, I’ll give it a shot."

He set up Blar and ran it on the problematic pull request (PR). Within seconds, Blar started commenting on the PR—and there it was: the exact bug that had caused the outage. Vicente smiled, laughed, and said:

"Okay, guys. Let’s give it a shot."

The Problem

Finnecto is a SaaS company specializing in automating spend procurement for enterprises across Latin America. Working with enterprises means adapting to highly specific requirements, which forces the engineering team to move at an extremely fast pace while maintaining high-quality standards.

New features and integrations are built at lightning speed, making it easy for small but critical mistakes to slip through the cracks. A single undetected issue can:

❌ Break functionality
❌ Disrupt services
❌ Erode customer trust

Vicente and his team needed a safety net—a way to catch issues early without slowing development.

First Week with Blar

During the first week of trying out Blar, Vicente still had to manually and thoroughly review each pull request (PR). It wasn’t just about catching bugs—Vicente also wanted to enforce code consistency and maintainability.

At Finnecto, code must be:

🔹 Homogeneous – Ensuring a uniform structure across the entire codebase.
🔹 Predictable – Making it easy for engineers to understand and extend any part of the code.
🔹 Standardized – Reducing onboarding time and preventing technical debt.

To address this, we developed the Blar Styleguide Wiki, allowing users to define custom coding patterns. Blar also assists in writing this Wiki by extrapolating common patterns found in the existing codebase and providing concrete examples.

The Result

With this feature in place, Finnecto:

✅ Reduced PR review time by 40%
✅ Maintained a bug-free, standardized codebase
✅ Enabled engineers to work faster and with more confidence

The Solution

Blar became Finnecto’s safety net, helping their team catch issues early and enforce coding best practices—without slowing down development.

Blar’s technology includes four specialized AI agents:

✅ Bug Detection Agent – Identifies potential bugs before deployment.
✅ Optimization Agent – Recommends performance improvements.
✅ Security Agent – Detects cybersecurity vulnerabilities and exploits.
✅ Code Quality Agent – Ensures compliance with style guides and design patterns defined by the user.

By integrating Blar into their development pipeline, Finnecto significantly reduced post-deployment issues, improved code reliability, and allowed their engineers to focus on building new features at top speed—instead of firefighting production bugs.

The Impact: First Month with Blar

In just the first month of using Blar, the results were undeniable:

🚀 Blar caught 21 bugs—14 of them critical, saving Finnecto over 60 hours of debugging time.

🚀 Reduced Pull Request review time by 40%

🚀 Identified and fixed 12 N+1 query issues, optimizing database performance.

One of the most significant optimizations came from Django Rest Framework (DRF), where Finnecto’s API was unknowingly making hundreds of redundant queries per request. Due to missing .select_related() and .prefetch_related() calls in DRF serializers, certain endpoints were making over 505 queries, when they should have been executing just 5—a 99% reduction in unnecessary database calls.

By catching these issues early, Blar helped Finnecto:

✅ Reduce API response times, making their service smoother for users
✅ Optimize database performance, reducing costs
✅ Improve overall system efficiency

Conclusion

With Blar, Finnecto no longer has to sacrifice speed for stability. Bugs are caught early, security risks are mitigated, and the team can scale development faster and with confidence.

For Vicente and his team, Blar wasn’t just a tool—it became an essential part of their workflow. 🚀

"Blar has become an integral part of our development process. Not only does it prevent issues before they reach production, but it also helps us better align our coding practices and avoid technical debt. It has changed the way we build software."

– Vicente Espinosa, CTO of Finnecto

Get Started now

Are you ready to experience the power of Blar for yourself? Join companies like Finnecto that are optimizing their development process and catching critical issues before they reach production.

✅ Enhance code quality
✅ Reduce debugging time
✅ Prevent security vulnerabilities

Start your journey today! Get Started with Blar 🚀