AI Guides › Money & Business
The One-Person Business Stack: What's Actually Worth Paying For
By Nigel Guy · 2 min read
Running a business alone with AI tools tends to produce one of two stacks: the person who's subscribed to everything that looked useful in a launch post and now pays for eight overlapping tools, or the person who's stuck on free tiers everywhere and quietly hits the same limit every week without ever deciding whether upgrading would actually pay for itself. Neither is a considered stack — both are accumulation, one just cost more.
The rule: a one-person stack should have exactly one paid tool per genuine bottleneck in your business, and nothing paid for a task that happens less than weekly.
The mechanism: the Bottleneck Map
- List the actual bottlenecks in running your business alone — the specific points where you personally are the slowest part of the process. Not "marketing" in general; something concrete like "writing follow-up emails after every call" or "turning a finished piece of work into an invoice."
- Match at most one paid tool to each bottleneck. If two tools on your list solve the same bottleneck, you have a duplicate, not two separate needs.
- Rank the bottlenecks by how often they actually recur. A weekly bottleneck justifies a subscription; a monthly one usually doesn't — a free tier or a one-off use of a general assistant covers it fine.
- Cap the number of paid tools at the number of weekly bottlenecks on your list. If you've listed two, you should be paying for two, not five.
- Revisit the map when the business changes shape, not on a fixed schedule — a new service line or a new client volume creates new bottlenecks and can retire old ones.
What to skip
Skip subscribing to a tool because it solves a bottleneck you don't currently have but "might" have if the business grows — pay for the business you run now, and add the tool when the bottleneck actually arrives. And skip keeping a free tier open indefinitely for a task that's become weekly; a bottleneck that's outgrown its free tier is exactly the signal to upgrade, not a reason to keep working around the limit.
Guardrails
- "One tool per bottleneck" is a starting discipline, not a hard rule — some genuinely need two tools working together, but that should be the exception you can name, not the default.
- The bottleneck map only stays honest if you're truthful about frequency — rounding a monthly task up to "practically weekly" to justify a subscription defeats the point.
- Run the real-usage check from a subscription audit alongside this map periodically; a tool that mapped correctly to a bottleneck six months ago can still become dead weight if your workflow moved on.
- Current pricing and what's included in a given tier shifts often enough to be worth checking directly before you commit, rather than relying on what a review said last year.
All 751 AI guides · JulieMango plans from £17/mo