Customer stories

Engineering teams that ship with fewer surprises

How three early engineering teams used DevPulsr to find semantic drift, plug test gaps, and stop API contract breaks before they reached production.

Start your free trial Talk to the team
40+
Engineering teams active
47%
Avg. cycle time reduction
2.8×
More findings per PR vs. manual
94%
Would recommend to peers

Axlepath

Payments infrastructure · 18-person engineering team · New York

Challenge

Axlepath's payments platform processes high-stakes transactions where billing logic errors are immediately user-visible. Their engineering team of 18 was shipping 30–40 PRs per week, and senior reviewers were spending 2–3 hours daily just triaging what needed deep attention versus quick approval. A logic error in their discount calculation made it to production and affected 340 invoices before being caught.

54%
Reduction in cycle time
0
Logic regressions in 5 months post-install
2.1h
Saved per reviewer per week
"DevPulsr caught a logic inversion in a billing calculation that nobody caught in three review rounds. That alone paid for the year."

— Daniel Marchetti, Engineering Manager, Axlepath

Engineering team in a payments technology company reviewing code on monitors

Kettner Labs

Developer tooling · 9-person engineering team · Remote

Challenge

As a developer tooling company, Kettner Labs holds their own code to a high bar. But with 9 engineers, everyone was both a contributor and a reviewer — review fatigue was real. Their test coverage was 82% by line count, but they had four production incidents in 2025 caused by uncovered logical branches in recently shipped code. They needed a way to find the gaps before merge, not after.

More test gaps caught pre-merge
4→1
Production incidents/quarter
89%
Reduction in post-merge test coverage issues
"Test gap detection is genuinely useful. Not 'you have 80% coverage' — but 'these three branches you just changed have zero test coverage.' That's actionable."

— Soren Rasmussen, Staff Engineer, Kettner Labs

Small developer tooling team in a modern office space, working at standing desks

LoopForm

Form automation SaaS · 6-person engineering team · Brooklyn, NY

Challenge

At LoopForm, three senior engineers handle all code review for a team of six. They were spending 40% of their time reviewing code rather than building it. DevPulsr didn't replace human review — but it dramatically changed the nature of what reviewers spend their time on. Pre-screened PRs arrive with a findings summary, letting reviewers focus immediately on the spots that need human judgment.

40%
Reduction in reviewer hours
More focused reviewer attention on findings
2→5
PRs per dev per week (velocity increase)
"DevPulsr doesn't replace our reviewers — it makes their time 3x more focused. They now only dig into the spots that need human judgment."

— Amara Kone, CTO, LoopForm

Small startup engineering team in a minimalist loft office, startup atmosphere

Ready to add your team to this list?

14-day free trial. See results on your first PR.