Blog
Practical thinking on automation and ops
What we actually find when a project is '80% done'
When a previous developer leaves a project 80% done, the next team almost always finds something different. Here is what that discovery looks like and why.
Read moreHuman-in-the-loop automation: when to pause a workflow and wait for a person
Not every workflow should run unattended. Learn when to pause automation and route decisions to a human before something goes wrong.
Read moreWhy approval loops slow down ops teams and what to do about it
Approval delays do not add to cycle time. They multiply it. Understanding that difference changes how you diagnose the problem and what you actually fix.
Read moreHow we cut an approval cycle from 4 days to same day
A fintech ops team was spending 2 hours every morning routing approvals manually across three tools. Here's exactly what we built, what didn't work, and what the hard part actually was.
Read moreWhen Zapier isn't enough: the limits of no-code for ops workflows
Zapier handles 80% of automation problems well. Here's the conceptual mismatch that breaks it for ops workflows, and the concrete threshold for when custom is actually worth it.
Read moreWhen spreadsheets stop working for ops teams
Spreadsheets fail ops teams at a specific moment. Not when the data gets big, but when two people need the same live number to make different decisions.
Read more