Last month I watched a business owner spend three weekends building an inventory reconciliation workflow in Make. Beautiful architecture. Conditional logic. Error handling. API integrations to Square, QuickBooks, and Google Sheets. He showed me the flow diagram like a trophy.

Then I asked what his time was worth.

“Around $150 an hour.”

I pulled up a Chrome tab. There was a SaaS tool that did exactly what he’d built, better tested, with support, for $49 monthly. His 30 hours of building (closer to 40 when we counted debugging) cost him $6,000 in opportunity cost to avoid a $588 annual subscription.

He bought the software that afternoon.

You’re Asking the Wrong Question

When people discover workflow automation tools, Zapier, Make, n8n, they ask: “Can I build this?”

If you’re technical enough to be reading this, the answer is almost always yes. Modern automation platforms are powerful. AI makes them more so. You can build almost anything.

Wrong question.

The right question: “Should I build this?”

That’s an economic question. It requires knowing your hourly value, estimating build time honestly (then doubling it), calculating payback period, and checking whether someone has already solved your problem better than you will in a weekend.

Most automation projects fail this test. They fail quietly, consuming weekends and delivering negative ROI that nobody calculates because the cost was “just time.”

Your time is not free. Your time is the most expensive resource you have.

Four Questions Before You Touch a Workflow Canvas

Does a purchased solution already exist? Not “could I find one if I looked harder.” Have you actually searched? Spent 20 minutes? Read comparison articles? Most problems you face are not unique. Someone has productized the solution.

What would building actually cost? Estimate the hours. Double that number. You will hit problems you didn’t anticipate. Multiply by your true hourly value, not your salary divided by 2,000, your actual opportunity cost. What else could you do with those hours that would create value? That’s the real cost.

What’s the payback period? If building takes 40 hours and saves 2 hours weekly, that’s a 20-week payback before you see net positive returns. Can you afford to wait five months? Will the system still matter then? Will you maintain it when it breaks?

What’s the ongoing maintenance tax? Every custom system you build is a system you own forever. APIs change. Integrations break. Requirements drift. That weekend project becomes permanent overhead. Purchased solutions push that burden to vendors who maintain it as their core business.

The Math Has to Work on Paper

In AI Strategy for Business Leaders, I walk through automation systems worth building and share the 20-some workflows that run my operations. But I spend more time on what NOT to automate, because that’s where most people waste hundreds of hours.

Before you build your next automation, write down the economic case. Literally write it. Estimated build hours (doubled). Your hourly value. Weekly time saved. Payback period in weeks. Purchased alternatives with pricing.

If the math doesn’t work on paper, it won’t work in practice.

And if the math shows buying beats building, congratulations. You just saved yourself a weekend and learned the most important lesson in operational automation: thinking beats building. Every time.

The full framework for deciding what to automate, how to architect systems that deliver ROI, and patterns that work across industries is in the book. I also maintain free companion resources including workflow templates and decision frameworks.

But start with the economics. Build less. Buy more. Automate strategically.

Your weekends will thank you.