Multi-Tenant SaaS From Client Work: The BYO-Keys Pattern (Simply Explained)

Why Most Custom Software Is a Waste of Money

Here's a story most business owners know too well. You pay someone to build you a custom tool. It works great. Then the project ends, or you want to sell that same tool to someone else, and you find out you have to start over from scratch.

That's why hiring someone to "build me a custom tool" feels like setting cash on fire.

But it doesn't have to be that way. The difference between a tool that dies and a tool you can sell a hundred times comes down to a few decisions you make on day one. Decisions that cost almost nothing up front and are nearly impossible to add later.

Let me show you with a real example.

A while back I built a job-management tool to win one client, an electrical contractor running his whole business out of group texts and a spreadsheet only he understood. One client. One specific problem. I'll keep coming back to him.

The Two Expensive Mistakes

There are two ways people get this wrong, and both burn money.

The first mistake is building something wired for exactly one customer. It works, but it's a dead end. When that customer leaves, or when three of their competitors want the same thing, you're starting over. Nobody warned you the whole thing was glued to one company.

The second mistake is the opposite. You decide to build a big "platform" first, before you have any real customers. Six months of work, settings panels nobody asked for, an admin dashboard for users who don't exist. Then you launch and find out the three things you obsessed over don't matter, and the one thing that does matter, you never built.

Both roads waste cash.

The way out is simple. Build for one real customer, but build it so the next one can plug in without a rewrite.

Why I Built for One Real Person First

Imaginary customers lie to you. They tell you what they think they'd do, then behave completely differently when their own money is on the line.

A real owner using your tool every day tells you within a week what matters and what's noise.

With the electrician, I didn't have to guess. He was scheduling jobs and chasing invoices through a mess of texts. I built exactly what replaced that, and nothing more.

Building for one real person keeps things tight. Every feature had to earn its place by solving a problem he actually had that week. No "wouldn't it be cool if." No imaginary edge cases.

Here's the part most people miss. I proved the product was worth building while the client was paying me to build it. The client funded the work. The work proved there was a market. That's a completely different risk than spending your own money guessing.

But there's a trap. If you ONLY build for that one owner, you've built a dead end again. Useful, but impossible to resell. That's where what I call the "seams" come in.

The One Decision That Turns a Tool Into a Product

Here's the heart of it. The single thing that turned a one-off tool into the seed of a real product was how I handled payments.

Most people centralize. They wire up one payment account and route everyone's money through it. That means you eat the processing fees, you manage a payments operation you never wanted, and you rewrite the billing for every new customer.

I did the opposite. I left the payment setup empty by default and let each owner connect their own.

Think of it like a food court. Instead of one cash register handling every restaurant's money, each restaurant has its own. The money goes straight to whoever earned it.

Here's how the tool decides where to send an invoice. First, it checks if that owner has connected their own payment account. If they have, the money lands in their bank, not mine.

If they haven't connected one yet, the tool still works. It just generates the invoice marked "pay by check." The owner collects payment, and the tool delivers value on day one without anybody setting anything up.

That last part is why the electrician was productive immediately. He didn't have a payment account yet. Didn't matter. The tool sent invoices, he got paid, done.

Now look at what this bought me. The hundredth customer signs up by connecting their own payment account in a settings screen. No new code. No work from me. Their money flows to their own bank. I never touch it, never eat fees, never accidentally become a payments company.

One small decision, made on day one with the very first client. It cost me maybe an hour of extra thought. And it's the difference between a tool that serves one electrician and a product that serves a thousand contractors.

That's the whole game. Build for one, but write it so the second, the tenth, and the hundredth slot in without you rewriting anything.

The Other Seams (And What This Honestly Costs)

Payments were just the first example. The same idea applies everywhere a customer has something that belongs to them and not to your tool.

The electrician sends invoices from his email, not mine. He texts job reminders from his number, not a shared one. Everything that's "his" lives in his own account. When the second client showed up, they connected their own, and the system routed everything correctly on its own.

The other big piece is keeping each customer's data separate. From the very first day, with only one customer in the system, I tagged every piece of information with a customer label. It felt pointless with one customer. It wasn't.

Adding that label early costs almost nothing. Trying to separate everyone's data after you already have a hundred customers in the system is a nightmare that takes weeks and risks one customer seeing another's information.

Now, I'll be straight with you. Building these "seams" costs maybe 10 to 15 percent more up front. On a tool that ships in a week, that's an extra day or so. It's real work. I won't pretend it's free.

And if you're truly certain this is a one-off internal tool that will never be resold or serve a second customer, skip it. Don't build a door you'll never open.

But be honest about that certainty. In trades, professional services, and local business, your client's competitor has the exact same problem. Always. If there's any real chance a second customer exists, that 15 percent buys you a repeatable product instead of a dead end. That's one of the best returns you'll ever find.

I'll also be honest about what doesn't carry over. Branding, sign-up flow, and customer support still need work for each new customer. The engine is reusable. The business around it still has to be built.

Build It Once, Own It Forever

Here's the payoff. When the second contractor showed up, signing him up was almost free. No copying the project. No fiddling with settings for an afternoon. He got his own account, connected his own payments, and his data stayed separate automatically, because it always had been.

The cost of customer number two was near zero, because all the expensive work was already done on day one for customer number one.

So here's the question to ask before anyone writes a line of code for you. Is this being built as a dead end, or with the seams that let it become an asset you own?

The difference is almost free to add up front and impossible to add later. Same build effort, give or take 15 percent. Wildly different outcomes.

This is the thinking I bring to every project. I'm not just handing you a tool that solves today's problem. I'm building it so the money you spend today becomes an asset you own forever, instead of a cost you write off.

Ready to bring AI leadership into your company?

I work with a small number of companies at a time. If you're serious about AI, apply to work together and I'll review your application personally.

Apply to Work Together