# How to Run a One-Person Business With an AI Assistant Run a solo-business assistant pilot with recurring preparation, clear permissions, dependable references, and a realistic review of usefulness. By Righthand Team · 2026-10-07 Source: https://www.righthand.ai/blog/how-to-run-a-one-person-business-with-an-ai-assistant Running a one-person business means the same person sells the work, delivers it, answers messages, and remembers every next step. An AI assistant can take on bounded preparation and coordination tasks, but the business still needs your judgment and authority. The best starting point is a recurring burden you can describe and review clearly. ## Quick answer Delegate research, draft preparation, scheduling coordination, and follow-up tracking one workflow at a time. Give the assistant a dependable source, explicit account access, permission limits, and a definition of completion. Keep pricing, spending, sensitive decisions, and relationship exceptions under your control. Righthand's [executive assistant role](/roles/executive-assistant) and [task delegation](/features/task-delegation) are relevant for a solo owner. Available actions depend on the accounts and capabilities configured for your business. ## Start with the work that repeats List the tasks you perform every week: preparing client calls, drafting updates, checking missing materials, organizing inquiries, and tracking commitments. Choose one that has stable inputs and an output you can inspect quickly. Avoid delegating a vague responsibility such as “grow the business” first. It requires strategic choices and gives you little basis for judging a result. “Prepare tomorrow's client brief from these sources” is a practical assignment. Separate preparation from execution. An assistant may produce a useful draft without having permission to send it. That lets you learn whether the context and tone are right before expanding authority. ## Build a small operating reference Give the assistant approved service descriptions, business hours, communication preferences, relevant contacts, and recurring workflow instructions. Mark information that is internal only. Keep personal and business account context clear. Do not rely on one long conversation as the only place important rules exist. Use an accepted reference for the current scope, prices you allow it to quote, and actions that require approval. Define completion for each task. A meeting time proposed is different from a confirmed calendar event. A reminder sent is different from receiving the missing material. Useful status reporting should preserve those distinctions. ## An illustrative solo-business week A freelance consultant starts by delegating client-call preparation and weekly update drafts. The assistant uses approved notes and project records to identify completed work, open questions, and the next decision. One client requests an extra workshop. The assistant records it as a proposed addition and drafts a response for the consultant. It does not accept the work or quote a fee. The consultant reviews the drafts, approves specific messages, and keeps scope decisions personal. The assistant tracks which updates were sent and which questions remain open. At the end of the week, the consultant checks whether preparation was easier and whether corrections were manageable. This example illustrates a workflow; it is not a customer result or a promise that the same setup will save a fixed amount of time. ## A first-week delegation brief > Prepare my client-call briefs and weekly update drafts using the approved project records and current correspondence. Link consequential facts and flag missing information. Keep business and personal requests separate. Do not accept extra scope, quote custom fees, spend money, or send messages without approval. For each task, report prepared, awaiting review, authorized action completed, or unresolved, with the evidence that supports the status. Show me the next decisions requiring my attention. Add specific accounts, client names, and deadlines. The brief should let the assistant act on known work rather than search broadly for things to do. ## Expand based on review burden After a week or two, assess the work prepared, the corrections needed, and the decisions that still consumed your attention. Expand the workflow that was useful and accurate. Fix unclear sources or boundaries before adding more tasks. A solo business benefits from simplicity. Keep one accepted task list and one clear owner for external messages. Multiple automations with overlapping authority can create more coordination work than they remove. If the assistant cannot access a source or complete an authorized action, require a prompt status report and a usable fallback. You need to know what remains yours to handle. ## FAQ ### Can an assistant run the business for me? It can support defined tasks, but business judgment, accountability, and consequential authority remain with you. Expand specific workflows rather than handing over an undefined role. ### What should I delegate first? Choose recurring preparation with trustworthy inputs, such as client briefs or status drafts. Those outputs are easy to review before external action. ### How do I know it is helping? Compare preparation, review, correction, and follow-up effort with the usefulness of the completed work. Output volume alone does not establish saved time. ## Related resources Explore [follow-up management](/use-cases/follow-up-management) and [calendar management](/use-cases/calendar-management) for bounded coordination.