How to Scope an 'Automate Everything' AI Assistant: 7 Steps

Posted on Nov 5 • Originally published at soloagentflow.com

A business owner asked his IT-savvy friend to automate everything across three companies and his personal life. Here's how to turn that kind of request into a scoped, deliverable, and safe automation project.

h/t the IT professional who shared this request on r/automation.

A post on Reddit's r/automation captures a request many tech-savvy people are starting to get. An IT professional explained that a friend who owns several businesses asked him to build an "AI Assistant," an environment where "basically his whole life is automated," covering both personal and business matters.

One caveat up front: the source is a request for guidance, not a success story. There are no revenue figures, timelines, or results in the post. What it offers is a detailed look at what a real client wants.

The friend runs two building/insurance repair businesses and an events business. The wish list includes "literally everything": emails, flights, scheduling, calendar management, jobs, finances, profit margins, research, content creation, "and much more."

Then comes the part that makes this an engineering project rather than a chatbot setup:

That last line is the key insight: this is a multi-user system with role-based permissions sitting on top of sensitive business and financial data.

Access control isn't a feature you bolt on later. If the worker can ask the AI a question and the AI has access to the owner's finances, a clever prompt might pull that data out. Permissions need to live in the data layer and the tool connections, not just in instructions to the AI.

Narrow the first win. Pick one or two high-frequency pains, usually email and calendar. They show value quickly and carry less risk than money or travel bookings.

Separate businesses and users from the start. Three businesses plus a personal life means keeping data, documents, and connected accounts logically separate, then layering user roles on top: what the owner sees, what the worker sees, and what's shared.

Keep humans in the loop for irreversible actions. Customer emails, flight bookings, and anything involving payments should start as "AI drafts, human approves."

Assemble before you build. You probably don't need everything from scratch. Many builders combine workflow automation platforms, AI model APIs, and the apps the client already uses. Check each vendor's docs for data handling and multi-user permission features, since they directly affect whether you can enforce access restrictions.

Document security decisions. Write down where data is stored, who can access what, and how permissions are enforced.

This isn't a weekend project: the security, multi-user, and integration work make it hard. But a phased, permission-first approach gives you the best shot at delivering something the client keeps using.

Try this today: write a one-page access matrix for a business owner you know: their main tasks, the systems involved, and who should see what.