Exception Cost Ladder

Exception Cost Ladder ranks every candidate workflow by how often it breaks and what a break costs the client. A lead-routing flow that fails once a week and silently drops inquiries sits at the top of the ladder; a nightly report that fails and retries sits near the bottom. The framework matters because platform choice follows the rung, not the reverse: high-exception work needs monitoring, alerting, and a named owner, while low-exception work tolerates a simpler build. Agencies that skip the ranking sell identical retainers for wildly different risk profiles, then absorb the difference in unbilled firefighting. A concrete case: a client intake flow built in Make across 3,000+ integrations may touch six systems, and each hop is a failure point that needs an error path before launch. Rank first, price second, build third.