Your Stack: One Assistant, One Brain, a Handful of Skills

The word "system" makes people reach for their wallet. Before this course asks you to build anything, it should tell you what you need to buy: nothing. The stack that runs an AI-operated small business fits on an index card, and most of it is already on your desk.

The full stack

• One AI assistant. The Claude, ChatGPT, or Gemini subscription you already pay for. One, not three. Every tool you add doubles the places your context lives and halves the chance any of them is current.
• One Business Brain. A single document holding your prices, voice, policies, and current facts. Every skill reads it first. You will write it in the next chapter, and it is the piece most owners are missing.
• A handful of skills. One per workflow from your audit, either installed from the Vexlo toolbox and customized, or built with the five-section template from AI Skills for Small Business. Five workflows means roughly five skills. Not twenty.
• A calendar with two recurring blocks. Monday morning and Friday afternoon. Chapter 4 fills them.
• One folder. Where the Brain, the skill files, and the runbooks live. Name it something your future employee can find.

That is the whole stack. If your list is longer, something on it is decoration.

What is deliberately not on the list

Automation platforms. Tools that watch your inbox and fire actions without you have a real place in the world, but not at this stage. Every trigger you automate is a checkpoint you gave up, and Chapter 5 will show why checkpoints are where your quality control lives. Master the human-in-the-loop version first; automate individual steps later, once a workflow has run clean for months.

Custom AI builds. The honest ladder from the skills course still holds: one-off prompt, master prompt, skill, custom build. A custom build costs thousands and earns its keep at a scale most small businesses have not reached. Everything in this course lives on the skill rung, at $0 beyond your existing subscription.

A second brain app, a new note system, a project manager. If you have one you love, keep it. The system in this course needs a folder and a calendar, and adopting new tools mid-build is how builds stall.

Why small stacks win

Every component you add is something that can be stale, lost, or unknown to the person covering for you. The two-truck HVAC company runs its four workflows on one Claude subscription, one Brain document, five skill files, and a shared folder. When their office manager took a week off, the owner ran the whole system from the runbooks, because there was nothing to learn except where the folder was.

Compare that with the owner who has three AI subscriptions, each holding a different half-remembered version of the price list. More stack, less system.

Set up the folder today

Create the folder now and give it four subfolders:

The archive folder matters more than it looks. When you update a price in the Brain, the old version gets dated and archived, and a mystery about "why did the assistant quote the March rate" takes thirty seconds to solve instead of an afternoon.

Try it now

Build the folder structure above, then write your stack on an actual index card: assistant name, the five workflows from your audit, and which skill will serve each (a toolbox install, a customization, or a from-scratch build). If any workflow needs a tool you do not currently pay for, challenge it. In our experience the card survives the challenge and the extra tool does not. You now have the target the next five chapters will build toward.