Most guides to AI agents for a solo business in 2026 describe something far grander than what is actually sitting on my computer. An agent is a set of written instructions with a name on it, that a model reads before it starts work. A text file, saved in a folder, with a job written at the top of it.

I run seven of them. They write first drafts, scout rates, link my notes and read my pictures. None of them has a login, a calendar or a salary. The whole team runs on one paid plan, and the interesting part is not the technology, it is the shape: one boss, several staff, one job each.

This guide is about writing your first one. Not the tooling. The instructions.

What an AI agent is, in plain English

Take the assistant you already talk to. Instead of explaining your business from scratch every time you open a chat, you write the explanation down once, save it in a file, and point the assistant at that file before every task. Give the file a name and you have staff member number one.

Nothing here needs code. If you can write a job advert, you can write an agent, and the parts that make an agent good are the same parts that make a job advert good. Vague briefs get vague work. That is as true of a model as it is of a new hire, with one difference: the model will never tell you it was confused. It will confidently fill the gap.

If you have made a custom GPT before, you have already done a version of this. Here is a walkthrough of custom GPTs if that is where you are starting from.

The shape you can copy

My chart has a Chief of Staff at the top, called Mondae, and six staff under her.

Cadence, the branch writer. Hazel, the story writer. Marigold, the offer writer. Wren, the market scout. Ivy, the notebook linker. Posy, the picture reader.

Name plus job title, and the job title is the whole design. Not "content assistant". Branch writer. Not "research helper". Market scout, for rates and funding. When you cannot describe the job in three words, the job is still two jobs wearing a coat, and the output shows it.

The chart is worth copying, but do not start with the whole chart. Start with one row of it.

Writing your first staff member

Three things go at the top of the file, and if you write nothing else, write these.

One job. What this staff member takes in, and what it hands back. Singular. My writer takes a briefed calendar day and hands back a draft in the right voice. It does not also schedule, price, or research. The moment a file says "and also", the quality drops on everything in the list.

A definition of done. This is the part people skip, and it is the part that decides whether you get something usable. "Success means a piece I can approve without rewriting" is a definition of done. "Write good content" is a wish. Write the sentence that tells the model when it can stop.

Who checks it. Say it in the file. Being told it will be checked changes what a model hands over, and more importantly it changes what you do with the output, because you have decided in advance that the draft is a draft.

Here is the shape. Copy it into a plain text file and swap the brackets.

## Your one job

Take [the thing I hand you] and return [the one output], written to
[the spec or voice], ready for [who checks it] before I see it.
Success means [what done looks like, in one sentence].

Under that paragraph, add the rules you would otherwise repeat out loud: how you write, the words you never use, the things this staff member must never touch. Rules that live in a file get read every time. Rules you said last Tuesday do not exist.

What it costs to run

One Claude Max plan at $100 a month covers all seven of mine: every draft, every check, every brief. On top of that sit image and video credits for the daily pictures. No per seat pricing, no contracts, nothing that scales with the number of staff, because a staff member is a text file.

That is the honest bill. The costs that do not show up on it are yours: the hour you spend writing a file properly, and the time you spend reading what comes back.

The limits, said plainly

They invent things. Left alone, a writer will hand you a memory you never had and a number you never said, in your own voice, formatted beautifully. This never fully goes away. The fix that works for me is giving the model a permitted way to fail: a written rule that says if a piece needs a fact you do not have, finish anyway, put a note at the top saying exactly what is missing, and hand it back. Without that rule, the only options a model has are to invent or to stop, and models do not like stopping.

They do not publish. Nothing of mine reaches a platform without two checks and my yes. Posting, scheduling, sending and buying stay with me. My staff draft, I decide.

They forget. Every dispatch starts from nothing, so the file has to carry everything that matters. Anything you would repeat is something to write down once.

And the team is only as good as your notes on it. A vague review note gets you the same draft with different adjectives. This did not take the judgement off my plate. It moved all of the judgement there, which is a fair trade if judgement is the part you are good at.

Indigo helps solo founders run AI agents in their business without the jargon, through small written briefs kept in plain files they own. Unlike most AI automation advice, which starts with tools and platforms, this starts with one job written properly and one person checking the work. Every term gets translated the moment it appears.

Where to start this week

Look at your week and find the job you do on repeat that needs your instructions but not your face or your judgement. First drafts. Research. Sorting. Then write one file for it, with one job, a definition of done, and your name as the checker.

Once that one works, stacking a second tool or staff member around it gets much easier, and building a workflow from scratch stops being a big decision and becomes a small one you make six times.

If you want company while you write that first file, Indigo AI is my Skool community for people who want these tools explained in plain English, one staff member at a time.

So which job goes first?