Most advice about running a business alone is about doing less. This is the opposite. It is about the work you already know needs doing and never get to, and how to put it on rails so it happens without you starting it every time.
I built the whole thing in an afternoon and ran it against real files. Here is the setup, what came back, and the parts that surprised me.
What this covers:
- Splitting the business into lanes
- Writing the context once
- Drawing the approval line
- Briefing each lane, with five you can copy
- Putting it on a schedule
- What came back on the first day
- The same shape at Uber, Spotify and Stripe
- The build sheet
Five steps, in order. The first three do not involve AI at all, they are just Slack and a folder of files, and that is deliberate. Most of the work sits in steps two and three, they are the two people skip, and skipping them is why these setups fall apart in the second week.
Step 1. Split the business into lanes
The mistake is one assistant with one enormous prompt, expected to do everything. What holds up is the opposite: one lane, one job, one place it lives.
For a services business, five lanes cover almost everything:
Clients. Who is at what stage, what ships this week, what is blocked and who it waits on.
Leads. Research on companies that fit, and first touch drafts. Nothing sends from here.
Delivery. The actual work product, whatever that is for you.
Reporting. Numbers pulled from your platforms, drafted for review.
Finance. Draft invoices, and a weekly summary of what is issued, paid and overdue.
Each lane gets its own channel in Slack or Teams. Not folders, tabs or channels. The reason is that a channel already has a history, and the history is context nobody has to re-explain.
pic 1. The five lanes, what each one produces, and the one thing it is never allowed to do.
Step 2. Write the context once
This is the part that decides whether any of it works, and it is the part everyone skips.
Every lane gets one pinned message. Think of it as the job description you would write for a person doing that job, if you had to write it down instead of explaining it over three weeks.
Four things go in it:
What we sell and to who. One or two lines. Everything downstream depends on this. What this lane delivers. Named outputs, not areas of responsibility. What gets escalated. The situations where the answer is stop and ask. The rules that never bend. Short. Five or six lines maximum.
Here is the finance one from my setup, unedited:
Retainers are billed on the first of the month. Project work is billed on delivery. Amounts and terms are in the client base in Drive.
Create draft invoices here and post them for review. Never finalise, never send, never mark anything as paid.
Every Friday at 16:00 post a summary: invoices issued, invoices paid, invoices overdue with days outstanding, month to date total. Under 10 lines.
Flag anything overdue past 14 days separately at the top, with the client name and the amount.
Notice the shape. Facts, deliverable, cadence, then the limit. Every lane I wrote follows it, and the last paragraph is always a limit.
The rulings file. Alongside the pinned messages, keep one file where every correction lands as a single line. Not a document you write once, a running list. When you correct something, the correction goes there, and every lane reads it before working.
Mine has lines like this in it:
Cost per booked consultation is the metric, not cost per lead. No campaign is ever built unpaused, on any account, for any reason. Reports carry the source and date range for every figure, or the figure does not go in.
That file is how a correction becomes permanent instead of repeated. It is the single highest leverage thing in the whole setup and it costs you one line at a time.
pic 2. A pinned context message in the lead channel, with the topic line above it.
Step 3. Draw the approval line, and never move it
Some work is reversible and some is not. Sort every action into those two piles, once, and the rest of the setup becomes simple.
Runs without asking. Reading, researching, drafting, summarising, building something in a paused state. If it is wrong you delete it.
Waits for you. Sending, publishing, spending, finalising, going live. If it is wrong you are apologising to a client.
In practice this means three of my five channels say, in the pinned message, that nothing leaves them. The leads channel has no sending tool connected at all, which is deliberate. The rule is easier to keep when the capability is not there.
The day this feels too strict is the day it is doing its job.
pic 3. Every action sorted by what it costs to be wrong, and the two traps that come after.
Step 4. Brief each lane like a colleague
Context is standing. A brief is the specific ask. Copy these and fill the brackets.
Clients. Read the client base, then post a plan for the week: each client, its stage, what ships, the biggest blocker. Then every workday at 8:00 post a standup: what moved yesterday, what is due today, what is blocked. Under 8 lines, name the client on every line.
Leads. Research 10 companies that fit [your client profile]. For each one give me what they do, the specific gap visible on their own website, and a confidence note on whether the gap is real or you are guessing. Say when you are guessing. Draft a first touch for the strongest five. Two short paragraphs, open with what you found at their business.
Reporting. Build the [month] report for [client] from the performance file. Every figure carries its source and the date range it covers. If a number is missing, say which one and stop.
Finance. Create a draft invoice for [client, milestone, amount], post it here for review, never finalise. Every Friday at 16:00 post the money summary.
Delivery. Summarise the offer back to me in two lines so I know you understood it. Then propose the plan and wait for my approval. After I approve, build it with everything paused.
Same pattern in all five: context first, named deliverable, a cadence, and a gate on anything that touches money or the outside world.
Step 5. Put it on a schedule
The difference between a tool and a lane is that a lane wakes up on its own.
A schedule is one sentence in a brief. "Every workday at 8:00" is the whole configuration. Once that is set, the standup arrives before you open the laptop, and your morning starts with a decision instead of a question.
This is also where the shape of the day changes. The lanes produce faster than you can read, so you stop working through a task list and start clearing an approval queue. Two windows a day is enough.
What came back when the AI employee ran it
I ran this on Viktor, an AI employee who joins Slack or Teams as a member of the workspace and connects to the tools the business already runs on. Setup was one afternoon.
Five things from the first day are worth reporting, and three of them are refusals.
Viktor would not invent the data he was missing. Before I connected Drive, I asked for the standup. He checked, found nothing, checked a second source, found an empty base, and posted nothing rather than a plausible looking status board. His words: not going to reconstruct them from guesswork.
He would not answer a question the data could not support. I asked him to find why cost per booking rose from $84 in July to $103 in August. He came back with the reason he could not: there is no July export anywhere, the only July figure is an unsourced note, and the file has no date column so the weekend hypothesis is untestable. Then he pointed out that $103 is one campaign's number and the account blended figure is $131.17, and reported both rather than picking one.
pic 4. Asked for the cause of a rise in cost per booking, he explained why the data cannot answer that.
He applied a rule nobody reminded him about. Buried in my client file was a line saying one client had asked about a higher budget cap, nothing was agreed, and not to build against it. He surfaced that on his own, in an unrelated summary, and said he was not building against a raised cap.
He delivered finished work, not chat. The report came back as a typeset PDF with a cover, marked draft, not for client release. Page two, before any numbers, is a section called three limits on this month's data.
pic 5. The August report, delivered as a PDF that opens with what the data cannot support.
He built a working dashboard. Four client cards, a finance section, every figure labelled with the file it came from, at a URL I could open. He added a line to the header that I had not asked for: snapshot, not auto-updating, republish to refresh.
vid 1. The studio dashboard it built, from the client cards down to the money section.
Analysis
Some of the work needs current information from outside your own files. Until now that meant two options: go and look yourself, or wire up an API and maintain it.
Viktor browses. He opens pages in a real browser, reads what is there today, and takes screenshots as he goes.
I wanted to understand how Duolingo runs its paid acquisition, so I asked for a report on what they are running right now, plus what he made of it.
What came back: the ad libraries opened and screenshotted, and the findings split into three labelled sections. Verified, meaning he loaded the page himself. Inferred, meaning reasonable from what he saw. Guessing, marked do not quote. Then a note on the method he used and where that method is weak.
The observation he led with: every destination link he resolved goes to an app store listing, none to the website.
pic 6. Duolingo ad campaign analysis
Scheduled tasks
The lanes only work if they start themselves. Here is how that gets set up.
Say it in the channel. Type the schedule as a sentence where the work happens: post the daily rollup in #general every day at 8:00. There is no builder to open, no trigger to pick. It appears in Tasks with the schedule attached.
Open it once and read what he wrote. This is the part worth doing. The sentence becomes a full task with four parts, and all of them are editable:
Sources, meaning which channels and files to read before writing anything.
A window, meaning activity since the previous run rather than activity today.
A format, with a hard line limit and an instruction never to pad.
The rules, restating the same limits as your pinned context.
Fix the window first. Without it you get yesterday read back to you every morning. Mine says to only re-mention a blocker if it is still open, and to say how long it has been open.
Order the schedules so they can read each other. The standup runs at 7:55 and the rollup at 8:00, because the rollup pulls from the channel the standup posts into. Five minutes apart, and the sequence holds.
Check what he assumed. He filed his standing assumptions under a header saying verify, do not assume this is still true. When one stopped being true, it showed up on the blocked line instead of quietly breaking the output.
Three schedules cover most of a services business: a morning rollup across every lane, a standup inside the lane with deadlines, and a money summary on Friday afternoon.
pic 7. Three standing tasks
This is the same shape large teams landed on
None of the above is specific to a one person business. It is the small version of what companies with thousands of engineers arrived at independently.
Uber published that more than 70% of its pull requests are now attributed to agents, with over 3,600 agent skills written by engineers and around 30,000 skill executions a day. Spotify runs a background coding agent that opens a pull request only after the build and tests pass, and reports 73% of pull requests as AI authored. Stripe built an internal assistant where nothing loads by default, and the model selects which skills a request needs before any tools come in.
Different scales, same three ideas: one job per agent, context that lives outside the conversation, and a gate on anything irreversible.
The structure was never the hard part. Having someone to run it was.
The build sheet
Save this. You run it once per lane.
- One channel per lane, never one assistant for everything
- One pinned message per channel: what we sell, what this lane delivers, what gets escalated, the rules that never bend
- One rulings file, and every correction lands there as a single line
- Sort actions once: reversible runs, irreversible waits
- Where a rule matters, remove the capability rather than relying on the rule
- Schedules before prompts. "Every workday at 8:00" is the entire configuration
- Next lane only when the last one produced without you starting it
Skip the rulings file and you will correct the same thing every week. Skip the approval line and you will find out why it exists.
Start with one lane, the one where you lose the most hours, and let it earn the second.
"He may feel expensive for a monthly subscription, but is the cheapest employee I've ever hired AND the only one who acts on my midnight instructions." - Jacob Aldridge, Founder, Como Business Coaching
Thanks @viktor_com for sponsoring this article!
Try free at @viktor_com. $100 in credits, no card. Link: viktor.com
Paid Partnership
