The Problem

Tim Denning and business partner Todd Brison serve solopreneurs, coaches, and small digital businesses. After years of operating online, their automations had evolved organically, layering new tools on top of old ones, adding Zaps to solve immediate problems, and inheriting integrations from platforms they no longer used.

They had no single view of what was actually running, what was broken, and what was costing them money without delivering value.

They needed someone to open the hood, map everything, and tell them what was real.

What We Did

SSLab conducted a full audit of their Zapier automation ecosystem, covering every Zap that ran during a one-month window. The deliverable was an interactive spreadsheet with built-in macros and filters, not a static report, but a diagnostic tool Tim and Todd could use to sort by trigger, expected output, and operational status.

Working

Over 70% of runs successful and operating as intended. The automations doing what they were designed to do.

Partial

Runs succeed but fail at key steps worth noting. Close to working, but with gaps that could lose data or skip actions.

Halted

Does not run or stops midway due to errors. Dead weight in the system, consuming plan capacity without producing results.

Filtered

Always filtered out. May run some actions but never fully completes. Often the hardest to spot because they look active.

Key Findings

18 out of 100

Only 18 Zaps worked end to end. 6 partially worked. The rest were either filtered out or contained errors. Over 80% of the automation layer was not delivering value.

Stale Integrations

Automations built for courses no longer in use were still active, triggering downstream Zaps that ultimately filtered themselves out, wasting runs and task credits.

Undocumented Workflows

Zaps existed outside of Zapier's own records, likely managed by a third-party tool. These contained sales data from multiple payment providers with no single source of truth.

Cascading Chains

Some Zaps triggered other Zaps that then filtered themselves out, creating unnecessary complexity and run costs with no output. Automation for the sake of automation.

For many businesses, just knowing what you have is the first step toward modernization.

This audit gave Tim and Todd a clear, filterable picture of their entire automation layer. What was working, what was wasting money, and where leads or data were falling through the cracks. The audit surfaced pipeline gaps that weren't visible from inside the business: stale integrations burning task credits, multi-provider sales data with no reconciliation, and automations that looked active but produced nothing.

These are the kinds of findings that save real money and prevent real problems. But only if someone takes the time to look.

Scope

Zapier Calendly Typeform Notion Teachable Payment Integrations

The audit covered every automation that touched their operational stack, from lead intake forms through payment processing, course enrollment, and internal logging. One month of activity, every Zap, every integration.

Running on stacked automations?

If your business runs on Zapier, Make, or other no-code platforms and you're not sure what's actually working, an automation audit can give you clarity before you invest in modernization.

Get started