Build for the business you have, not the one on your roadmap

Every scoping call reaches a moment where someone says, *we might also want to handle X down the road.* Sometimes X is real. More often it's a hypothetical business that doesn't exist yet. And the pull to build for it anyway is strong.

Don't.

The shopping problem

When teams evaluate SaaS platforms, they usually shop for the business they hope to become in three years. That's how you end up paying for a tool where you use 15% of the features and your team quietly builds spreadsheets around it. UDig calls this the bloated SaaS era — vendors add features to justify pricing tiers, and buyers pay for surface area they'll never touch. The pitch deck promises fit. The daily reality is friction.

The same failure mode shows up in custom builds. Someone sees the demo, gets excited, and starts asking whether the new tool can also handle the acquisition they might do, the product line they're considering, and the reporting the board *may* want next year. By the time scope closes, you're building a platform for a business that doesn't exist, paid for by a business that does.

What changed about custom

The old rule was simple: buy off-the-shelf until you couldn't. Custom cost too much to justify for anything narrow. AI-assisted development has moved that line. White Beard Strategies walks through the updated math and the direction is clear — narrow, well-scoped tools that used to be economically absurd now pencil out.

And "custom" doesn't mean what it used to. Watson Lake makes the point that custom software in 2026 is rarely a ground-up build. It's more often a thin bespoke layer over the SaaS you already run — the piece that reads your CRM, watches an inbox, and posts the right thing to the right Slack channel at the right time. That kind of layer is cheap to build and cheap to throw away when the business changes.

Which is exactly why building for a hypothetical future is the wrong move. If the tool is cheap and narrow, you don't need it to survive five years of pivots. You need it to work now.

Build for Tuesday

When we scope, we ask what happened last Tuesday afternoon. Which invoice got sent late. Which handoff dropped. Which report someone printed and marked up by hand. That's the business you actually have. It's boring, it's specific, and it's where the biggest wins are.

If your business changes — and it will — a narrow tool that fits today is easier to replace than a platform that never quite fit anything. The instinct to future-proof usually costs you the present.

Scope for the workflow you ran this week. Ship it. Ship the next one after the business tells you what it needs, not before.