How to start a one-person business with an AI employee

agencies rarely lose accounts over the quality of the work. the accounts go to the admin around the work. a promise made on a call and never written down. a revision round nobody counted. an invoice that went out eleven days late. a proposal that has been sitting in a prospect's inbox for a fortnight because the third touch never happened

i run a b2b agency. two people work with me on contract, a designer and a media buyer, and the client side has always been the part that scales worst, because every improvement there is a person's memory, and memory does not hold a business together past a certain size

this year i put an ai employee on the client side of it. his name is Viktor, he works inside slack or microsoft teams, and everything he does comes out of nine messages i typed into a channel in one sitting

what follows is the setup itself: nine messages as they sit in my workspace, with the specifics of this trade written into them

nine messages, one job description

they read as a job description and a rulebook, and they run before every task

two describe the business and set the limits. four run the daily and weekly work on accounts. three cover money and the team. none of them are clever, and none of them mention ai. they read like the onboarding note you would hand a new account manager, which is the highest compliment i can pay them

they live in a single message at the top of the channel, and the file is the system. when a task goes out without that file, it goes out carrying half the rules

one. the client file

this is the file that everything else leans on

1you work for a b2b agency. we run paid search, landing pages and content for b2b saas and industrial clients. three people: me, [designer], [media buyer].
2retainers are monthly, projects are fixed fee, and both are agreed before work starts.
3never quote a price, never promise a date, never contact a client directly.
4anything you produce comes back to me as a draft, and any number in it names the file it came from.
5read this before every task. reply with three lines on what you think your job is.

the reply matters. if his three lines come back with a different idea of the job, the file is thin, and you will spend the week fixing tone when you meant to be reviewing work. mine described his job as reading account history and surfacing what needs a decision, and said he treats the rest as noise. that is the job

two. the morning read

1read the last 12 hours across the inbox and the client channels. return, in this order: anything from an active client, anything with a deadline this week, anything from a proposal sent in the last 14 days, anything unpaid past its due date.
2
3skip newsletters, receipts, cold outreach, and anything i was only copied on. one line each: who, what they want, what it needs from me.

the order carries the weight. without it you get a digest of everything, you read all of it, and the job you tried to hand over is back on your desk

three. the qa pass before a deliverable ships

this is the message that has saved me the most money, because in an agency the expensive mistakes are the ones the client finds first

1run the qa list against [deliverable] before it goes out. every claim traceable to a source we can show the client. every number matching the dashboard it came from. terminology matching the brand terms in the client file.
2one clear ask of the client, in a single line. nothing promising a date we have not agreed.
3
4return pass or the list, with the file behind every check. do not edit the deliverable.

an extra reader holds the same list at seven in the evening with the same attention as at nine in the morning. it catches the client name spelled wrong, the metric pulled from the wrong column, the line promising a date nobody agreed to

four. the revision log

revision rounds are where margins quietly disappear on fixed fee work. someone says "just one more tweak" four times and the project stops being profitable

1from [thread], build the revision log: round number, what the client asked, who owns it, what has shipped, what is still open and for how many days.
2
3if a request falls outside the agreed scope, flag it separately and keep it out of the queue. i decide whether it becomes a change order.

two revision rounds are priced into every fixed fee project. the log is what makes the third one visible while there is still margin left in the job

five. the status draft

clients do not leave because of one bad week. they leave after a month of wondering what is happening.

1draft the friday status for [client]: what shipped this week, what is in progress, what we are waiting on from them, the next date we owe.
2
3six lines maximum. plain sentences, dates where dates belong.
4
5if the retainer is past three quarters used, add one line with the position and the options.

that last line turns a budget surprise into a conversation a fortnight early.

six. the proposal follow-up ladder

proposals do not lose themselves. they get lost

1for [proposal] sent on [date]: day 3, a short note with one new relevant fact from their industry. day 7, a different angle, for example a comparable piece of work or a question about their review process. day 14, a clear close: yes or no, and a date.
2
3hold these dates and remind me on the morning. drafts only, i send.

the rule that keeps this tolerable sits in the same file: every touch carries something new, an example, a fact from their market, or a question. on a day with nothing to add, we skip the touch

proposals rarely die from a no. they die from a maybe, and the ladder is the only part of this that treats silence as a stage in the sale

seven. the invoice chase

cash is the constraint in a small agency, not profit

1invoices are net 7. day 8, a short reminder with the invoice attached. day 15, a firmer note that names the pause in work. day 22, tell me and draft nothing further.
2keep the list: who, amount, days outstanding, and what has been delivered against it.

he drafts and keeps the record. i press send, which is why the relationship stays mine

the pause at day 15 is written into the retainer agreement on the first page, which means naming it later reads as a term of the contract and stays out of the relationship

eight. the scope-change reply

the request arrives by email and always arrives sounding small

1[client] asked for [request], which is not in the statement of work. draft a reply: confirm we heard it, call it a change, and attach a change order with the scope, a price placeholder [number] and a delivery placeholder [date].
2
3no discount, no free sample, no apology for charging. i will set the numbers before it sends.

charging for out of scope work comes down to wording, and this message handles the wording while everyone is still friendly

nine. the gate

the last message is the one that makes the other eight safe to run

1before anything that sends, spends, or reaches a client: post the plan, the tool, the credit cost, and the exact text. wait for my yes.
2
3if a number appears in anything a client will read, name the source file.
4
5escalate to me every time: pricing, scope, deadlines, apologies, anything legal.

that is the working relationship. he proposes, i approve, and approval is a click. the nine messages above only run unattended because this one stops at the door of anything that leaves the building

the team uses the same employee

access follows channel membership. the designer is in the project channels, the media buyer is in the performance channels, i am in all of them. the room decides what is visible, so access looks after itself

their instruction blocks sit in the same file:

1[designer] is the designer on [project]. when she asks for a brief, return the client's objective in one line, the deliverable, the constraints, the examples the client liked, and the one thing to avoid. under 200 words.

her first request came back as a finished brief inside two minutes, with nothing added to my calendar. the second person using the same employee is the moment this stops being a personal tool

the file grows with the business

the file at the top of the channel is the part of this setup that compounds, and it grows a few lines at a time

a new client adds a block: their goals, their brand terms, the examples they liked, the one thing to avoid, and the date we owe them next

a new offer adds a rule: how it is priced, what it includes, and where it lands in the weekly runs

a new person adds their instruction block, so the employee works with them from their first day

fridays i spend five minutes reading that file and adding whatever came up during the week. one line is usually enough, and the next request in the channel comes back closer to done because of it

1every line added to this file applies to every run after it. keep it under one screen.

that is the whole maintenance. the nine messages carry the setup, the file carries the memory, and between them the work gets lighter every month

what stays with me

pricing and scope. the call with the client. the last review of anything published under my name. the hard conversation when something went wrong

everything else has an owner. most days the trade is clear: an evening of admin against twenty minutes of decisions, and the reason the agency can carry more accounts without another contract

the setup, in order

1. write the client file. one screen, badly, today
2. connect three tools, not thirty. email, calendar, the drive where proposals and contracts live
3. type the nine messages into one channel, in the order above
4. run week one by hand. read everything he produces
5. write down every correction as a line at the top of the channel
6. add the team's instruction blocks once your own drafts stop needing edits

a one-person agency does not scale on effort. it scales on the parts of the work that happen without a person remembering them, and the nine messages are where that starts

try free at viktor.com. $100 in credits, no card. @viktor_com

paid partnership.