Earn the Second Tool: A Solo Founder's Rule for Not Drowning in Subscriptions
Adding software feels like progress and is usually overhead. The decision rule I use to keep a lean stack lean — and the specific signals that tell me a tool has finally earned its place.
By Dana Okafor —
The most expensive habit I had as an early founder wasn't a bad hire or a wrong bet. It was adding tools.
Each one felt like progress. A new churn problem? There's a SaaS for that. Onboarding feels clunky? There's a tool. Every subscription was small, every signup felt responsible, and the sum of those responsible little decisions was a stack of fourteen products I was paying for, three I'd forgotten existed, and a context-switching tax that meant I touched five apps before noon just to find out what I was supposed to be doing that day.
The number that gets quoted in 2026 is real: you can run a genuinely professional one-person SaaS on something like fifty to a hundred dollars a month of software. That's true, and it's a beautiful thing. But the dollar cost was never the real problem. The real cost of a tool isn't its price. It's the attention it asks for forever — the integration you maintain, the data that now lives in one more place, the thing you have to keep in your head, the export you'll have to do the day you finally cut it. For a team of one or three, attention is the scarcest resource you own, and every tool quietly bills against it.
So I run a single rule now, and it's saved me more time than any tool ever did: *a new tool has to be earned, not adopted.* Here's what that means in practice.
Start with the most boring thing that could possibly work
When a new need shows up, the default answer is not "which tool solves this." The default is "what's the most boring thing that already works." Usually that's a spreadsheet, a Notion database, or a column in something I already pay for.
This sounds like a productivity downgrade. It isn't. A spreadsheet is infinitely flexible, costs nothing, asks for zero new attention, and — critically — it teaches you the shape of the problem before you commit to anyone's opinion of how the problem should be solved. I tracked my first two hundred customers in a Google Sheet. I ran my content pipeline out of a single Notion database for a year. The 2026 consensus that a generalist workspace can stand in for your project manager, your wiki, your CRM, and your content calendar is correct, and the reason it's correct is precisely that it delays the commitment. You consolidate first, and you only specialize when you've felt the specific pain the specialist tool is built to remove.
There's a real ladder here, and it's worth being deliberate about which rung you're on. A flat Google Sheet is the cheapest rung — zero structure, zero opinion, total flexibility. A Notion or Airtable base is the next rung up: you've now got fields, relations, and views, which is more power and also more setup and more lock-in. And a glue tool like Zapier is the rung after that, where you start wiring those things to each other. Every rung up buys capability and bills more attention. The boring-first rule is really just: don't climb a rung until the current one is visibly straining. I have watched myself (and every founder I've advised) jump straight to the Zapier-wired, three-Airtable-base contraption for a problem that a single tab in a sheet would have held for another six months.
The boring thing has a second superpower: it tells you whether the need is even real. Half the tools I almost bought were solving problems that evaporated in a month. The spreadsheet would have just sat there, harmless. A dedicated SaaS would have sat there billing me and asking to be maintained.
The three signals that a tool has actually been earned
A tool graduates from "I want this" to "this is earned" when I can point to all three of these. Not one. Three.
1. The boring thing is visibly straining. Not "could be nicer" — straining. The spreadsheet has a formula nobody can safely touch. The Notion database is slow and three people keep overwriting each other. The manual process broke something customer-facing. There's a specific, recurring pain with a name. If I can't name the pain in one sentence, I haven't earned the tool — I'm just shopping.
2. The problem is narrow and the tool is narrow. The most reliable purchases I've made are tools that do one job well. The 2026 mistake everyone warns about, and they're right, is buying the broad "does everything" platform — the all-in-one, the general-purpose agent you have to configure into usefulness. For a small team, configuration is a project, and you don't have a project's worth of attention to spare. A narrow tool that does its one thing on day one beats a powerful tool you have to assemble. If the tool needs a "setup phase," that setup is the real price, and it's almost always higher than the sticker.
3. I know what it replaces, and I actually cut that thing. This is the one people skip, and skipping it is how the stack of fourteen happens. A new tool has to retire something — a spreadsheet, a manual ritual, or another tool. If it just adds a fifteenth surface alongside the fourteen, it isn't consolidation, it's sprawl with better branding. When I adopt something, killing the thing it replaces is part of the adoption, not a someday-cleanup. If I'm not willing to cut the old thing, that's strong evidence the new thing isn't earned yet.
Where this rule bends — the honest tradeoffs
I'm not pretending boring-first is free of cost, because it isn't, and a founder who follows it blindly will get burned in two specific ways.
You can outstay your welcome in the spreadsheet. There's a real failure mode where you're so proud of running lean that you keep limping along on a manual process that's actively costing you customers or sanity, well past the point a tool would have paid for itself in a week. The rule is "earn the tool," not "never buy the tool." When all three signals are lit, buy it without flinching — the time you save is worth far more than the subscription. Frugality that costs you more than it saves isn't frugality, it's a different kind of waste.
Some things should be bought immediately, no spreadsheet phase. Anything where a mistake is expensive or irreversible — payments, auth, sending email at scale, anything touching compliance or money — you buy the boring, battle-tested, off-the-shelf thing on day one. The "most boring thing that works" for taking payments is a real payments provider like Stripe, not a clever script you wrote against a card API at midnight. The most boring thing for getting a password-reset email to actually land in an inbox is a transactional-email service like Postmark, not your own SMTP server that works in testing and silently routes to spam in production. Boring-first is about workflow and internal tooling, where flexibility is cheap and switching is easy. It is emphatically not advice to hand-roll your own billing to save nine dollars. I learned that line by standing on the wrong side of it once.
So the rule, fully stated: default to the most boring thing that works, make every new tool earn its place against three signals, and the moment those signals light up, pay without hesitation — except for the load-bearing infrastructure you should never improvise, which you buy first and never regret.
A lean stack isn't the one with the fewest tools. It's the one where every tool can explain, in a sentence, why it's still there. If a tool in your stack can't pass that test today, you've found your next thing to cut — and cutting it will feel better than the last three things you added.