SpotDraft scales high-signal code review with Baz

Key results with Baz

• Faster, more predictable delivery. Initial measurement showed a 20–30% reduction in merge time and time-to-first-comment as Baz offloaded routine review work and increased reviewer engagement. (SpotDraft trial data)
• Production issues caught earlier. Baz surfaced multiple production-impacting bugs (security, networking, business logic) that were remediated directly in PRs during the pilot.
• Stronger developer trust and adoption. Engineers reported more actionable, higher-quality comments from Baz versus the incumbent, accelerating team-wide buy-in.
• Seamless migration from CodeRabbit. Baz converted existing configs into reviewers and ran parity checks to preserve reviewer intent and ensure consistent results post-switch.

The Challenge

The SpotDraft engineering team was looking to increase delivery velocity without compromising on production quality. SpotDraft’s leadership needed to accelerate product delivery without increasing risk. Their incumbent tool provided useful static analysis, but it lacked the ability to reason about real-world behavior and impact. SpotDraft needed a solution that would:

• Surface only high-signal, production-relevant issues, not noise
• Reduce reviewer cognitive load while maintaining engineering rigor
• Enable a low-friction migration, preserving existing review intent and workflows

The Baz approach

To meet SpotDraft’s requirement, Baz focused on four complementary capabilities: code review automation, seamless migration, focus on production impact, and rapid time to value.

1) Code review automation
Baz reviewers reason about code behavior and production impact, not just syntax.

At SpotDraft, this translated into multiple production-impacting issues being caught and resolved directly within PRs during the pilot.

2) Seamless migration
Baz treated existing CodeRabbit configurations as inputs, converting them into Baz reviewers and running parity checks to ensure continuity and trust post-migrations.

3) Focus on production impact
Baz prioritized high-severity logic and behavior issues over low-value noise, aligning code reviews with what actually affects SpotDraft’s products and users.

4) Rapid time to value
SpotDraft observed measurable improvements during the pilot phase itself, without requiring workflow changes or retraining.

Impact for the business

For SpotDraft, Baz translated into three key outcomes:

• Lower production risk. Logic and behavior regressions were identified earlier, reducing the likelihood of high-impact incidents.
• More predictable delivery cycles. A 20–30% drop in merge time and faster reviews improved planning reliability.
• Higher developer leverage. Engineers spent less time parsing low-value comments and more time building product.

Value > noise

Leaders should prioritize tools that reason about production impact, not only syntactic correctness. The business value comes from preventing regressions and reducing cognitive load, not from generating more signals.

Conclusion

SpotDraft successfully transitioned  from CodeRabbit to Baz, using the migration as an opportunity to raise the bar on code review quality across teams.. With strong early results and a clear operational playbook, SpotDraft scaled Baz confidently—continuing to expand automation coverage, improve review quality, and integrate more deeply into its engineering workflows.

‍