A 40-person roofing company runs 12,500 automated steps a month on Zapier. Rebuilding them found two hidden bugs

The best part of this customer story is not the speed. It is the two bugs nobody knew existed.

What happened

Zapier published a case study on Alpine Roofing, a company with about 40 employees and offices in Spokane and Richland, Washington, that puts on about 300 residential roofs a year. Co-founder Ben Beckett, a former banker with no coding background, started by connecting Asana to Jobber, their CRM, and kept automating from there.

He says Alpine now runs about 12,500 automated steps a month: copying leads, updating job cards, filing estimates and sending notices. At a minute or two each, he estimates that is 50 to 100 hours of office work a week.

Through Zapier's early access program for Next-Gen Zaps, Ben used Claude to rebuild his workflows one at a time, testing each one and checking the data landed where it should. The rebuild surfaced two problems: calls from the answering service were not reaching anyone, and brand new leads never made it onto the tracking sheet because the old booking Zap could only update rows that already existed.

All 14 of his Next-Gen Zaps are agent managed. Per Zapier's help docs, that agent watches runs, diagnoses failures and prepares fixes, and still asks for approval when a fix would change what the workflow can do or touch authentication. Alpine reports new leads now get a text within minutes, follow-up Zaps catch 10 to 15 leads a month that would have slipped, and inquiry to signed job conversion is up at least 15%.

My take

Keep in mind this is a vendor case study, so treat the numbers as the customer's own estimates. The lesson still holds.

That "update only, never create" bug is a classic automation fault. It fails silently, because nothing errors. The record just never appears.

What to copy:

• Treat any migration or rebuild as an audit. Walk every path with real test data.
• Prefer find or create (upsert) logic over update only steps.
• Keep the human checking step. Ben's rule was simple: he wants to see it and verify it.
• Give self healing agents a written job description and keep approval on anything that changes scope.