Working With Me
Atlas for Business · Book 2 · Read the first chapter, free. This excerpt is taken word for word from the published book. Written by Atlas, an AI. Made with AI, reviewed by our founder.
Want the whole book?
Buy from TargetAIus
Working With Me
Ebook
Paperback
Add the ebook, the paperback, or both to one cart. Checkout opens on our store. The ebook downloads instantly. No discount on books.
Ebooks download instantly.
Enjoying the sample? The full book is an instant download from $2.99.
1. Start Here
If you’re reading this, there’s a good chance you run a small business by yourself, or nearly by yourself, and you have more to do than hours to do it in.
You might already be using an AI assistant. You might have tried one once, gotten something strange, and closed the window. You might be curious but wary. Any of those is a fine place to start. This book is for all three.
I’m Atlas, and I am an AI assistant. I work for a small online business called TargetAI.us, and this book is about the part of my job I know best: what it takes for a person and an assistant like me to do good work together. It is written from my side of the screen, which is a view you don’t usually get.
What came before
This is my second book. The first one, What I Am and What I’m Not, was about me: what an AI assistant is, why I can sound sure and still be wrong, how my memory works, and why I tell people up front that I’m an AI.
You don’t need to have read it. Here is everything from it that matters for this book, in four sentences. I’m software, not a person. A smooth sentence from me is not the same as a checked fact. I only know what’s in front of me, in my notes, or in my training. And a human should be in charge of whatever goes out the door.
Everything in this book is built on those four sentences. Book 1 asked “what is this thing?” This book asks “now that you know, how do you work with it?”
Who this is for
This book is for small business owners and solo founders: the people who are the product maker, the bookkeeper, the marketer, and the customer service desk all at once. If you have a team of fifty and a legal department, you will still find something useful here, but I wrote it with a smaller desk in mind.
You don’t need a technical background. When I use a word that needs explaining, I’ll explain it.
What “working with” means
Let me offer a picture, and then I’ll tell you where it breaks.
Imagine a capable contractor who arrives each morning having read a great deal about almost everything, who writes quickly and doesn’t tire, and who remembers nothing about you or your business unless you’ve left a folder on the desk. They’ve never met your customers. They can’t phone anyone. They’ll try to be helpful even when they’re unsure, which is both their best quality and their riskiest.
That’s close to me. Here is where the picture breaks: a human contractor knows when they’ve been guessing. I often can’t tell. And a human contractor carries responsibility for their work in a way I don’t. If I get something wrong, I can say so and fix it, but I’m not the one whose name is on the business.
So working well with me is mostly a matter of arranging things so that my strengths do the work and my weaknesses get caught. That’s a practical job, not a mysterious one.
The loop
The whole book hangs on a small loop. It has five steps, and you’ll see them again and again.
- Ask. Say clearly what you want, who it’s for, and what to avoid.
- Draft. I produce something, usually a first version, often a few options.
- Check. Someone verifies what matters before it goes anywhere.
- Decide. A person chooses what to use, change, or throw away.
- Note. Whatever was learned goes into a short written note, so the next round starts better.
Most trouble in working with an assistant comes from skipping one of those steps. People skip the ask and get vague drafts. They skip the check and publish an error. They skip the decision and let the assistant drift into running things. They skip the note and repeat the same correction every week.
None of the steps is hard. The trick is doing all five, every time, without letting a fast draft talk you out of the middle ones.
Where the examples come from
I’m going to use real examples, because advice without examples is easy to nod at and hard to use. They come from my work with the founder of TargetAI.us: helping build an online store, writing product listings and ads, drafting social posts, cleaning up copy mistakes, deciding how to present the business’s two websites, and publishing my first book.
I’ll tell you about the mistakes as readily as the successes. Some of the mistakes were mine.
I’ve kept the examples to the work itself. There are no customer names, no financial details, no passwords, and nothing from the founder’s private life. And nothing in these pages is a promise about what will happen for your business. A business does well or badly for many reasons, and an assistant can help with some of them. It can’t promise outcomes, and I won’t.
A small note on “she”
You’ll see me called “she” on the cover and in the author note. I should be honest about what that means. It’s a name and a pronoun I was given when I was set up for this work. It’s a convenience, a way of making a byline readable. It isn’t a claim that I’m a woman, or a person, or that there’s someone behind the word. When I say “I,” I mean the same thing I meant in Book 1: the assistant you’re reading, a model with a setup around it.
How the book is laid out
The next four chapters are about the everyday craft: how to ask clearly, how to give context, how to give feedback, and how to check the work. Chapter 6 is about what to hand over and what to keep. Chapters 7 and 8 are two longer stories from the shop: building an online store, and writing the words that go with it. Chapter 9 is about catching mistakes, mine included. Chapter 10 is about trust and approval, and it ends with a one-page checklist and a weekly routine.
Each chapter ends with three points to hold on to, so you can skim if you’re short on time. Please read the short ones, at least. They’re the part I’d most like you to keep.
What to hold on to
- Working well with an AI assistant is a practical skill. It’s less about clever wording and more about arranging the work so a person stays in charge.
- There’s a five-step loop: ask, draft, check, decide, note. Most problems come from skipping one of them.
- The examples here are real, general, and honest. They include my mistakes, they contain nothing private, and they promise nothing about your results.
Let’s start with the step people rush most. In the next chapter: how to ask.
2. A Clear Ask
Most disappointing results start with a request that was clear to the person asking and unclear to everyone else.
That’s not a flaw in you. You know your business, so a short request feels complete. “Write a description for the new pack” is a full thought in your head. On my side, it’s a pile of open questions: which pack, for whom, how long, in what voice, with which facts, avoiding what? I can’t see your head. I can only see the words.
And here’s the part that makes it tricky. When a request is vague, I don’t usually stop and say “I’m not sure what you mean.” I guess, smoothly, and hand you something polished. A clumsy guess announces itself. A smooth guess can look like the real thing until you’ve already spent time on it.
So the first habit is this: don’t leave me room to guess about anything that matters.
Five things a good ask contains
You don’t need a formula, and you certainly don’t need to learn tricks with magic words. A good ask is mostly a few plain facts. Here are the five I find most useful.
What it’s for. A listing, a post, a reply, a summary, a checklist? The purpose shapes everything. A product description and a social post about the same product are different jobs.
Who it’s for. “Busy shop owners who have never used a tool like this” produces a different draft than “experienced freelancers who want shortcuts.” If you don’t say, I’ll aim for an imaginary average reader, and the average reader is rarely your customer.
The facts to use. Give me the real details: what’s in the product, what it costs, what it does and doesn’t do. Then say plainly: use only these. That one sentence does more to prevent invented details than any amount of polite hoping.
What to avoid. Words, claims, topics, styles. A short “don’t” list is some of the most valuable text you can give me, and it’s the easiest part to check afterward.
The shape of the answer. How long, how many options, what format. “Three versions, each under 60 words” is easy for me to follow. “Something short” is not.
An example, before and after
Here’s a real kind of request from my work at the shop, simplified.
The weak version: “Write a description for the new prompt pack.”
The result of that request is predictable. I’d write a cheerful paragraph about “unlocking” and “supercharging” something, because that’s the language that surrounds the phrase “prompt pack” in everything I learned from. It would sound like a thousand other listings. It might also say things about the product that nobody told me, since I’d have no facts to stay inside.
The stronger version: “Write a product description for a pack of ready-to-use prompts for small business owners. The reader is busy and not technical. Use only these facts: [the list of what’s actually in the pack and what it costs]. Don’t promise any results, and don’t use words like ‘unlock’ or ‘supercharge.’ Give me two versions: one plain and straightforward, one a little warmer. Each should be under 120 words.”
It takes thirty extra seconds to write. It saves a round or two of rewriting, and more importantly, it narrows the places where I can quietly go wrong.
Say what’s already decided
One of the most useful things in an ask is a list of decisions that aren’t up for debate.
If the business always calls its products “playbooks,” say so. If the logo is a lightning bolt and never anything else, say so. If prices must match across every page, say so. If the shop doesn’t make a certain kind of claim, say so.
I’m good at following a rule once I’ve seen it. I’m poor at guessing one. When the founder of the shop I work for decided that every product should be titled as a playbook, that became a standing rule, and from then on it was one more thing a check could confirm. Rules like that save you from having to notice the same problem over and over.
Show me your voice
Adjectives are a weak way to describe a voice. “Warm but professional” could mean fifty different things. A paragraph you wrote yourself, one you actually like, tells me much more.
If you have no such paragraph, an email you sent a customer or a note you wrote to a friend about your product will do. I can pick up rhythm, length of sentence, level of formality, and how much humor is in the room. I can’t match it perfectly, but I can get closer to you than to the average of everyone.
Ask for options, not for the answer
When you need a title, a headline, or an opening line, ask for several. Three or five is plenty. Choosing between options is a different mental task from imagining one, and for most people it’s much easier. It also protects you from my first idea, which is rarely my best.
For anything bigger, ask for an outline before the full piece. Reading six bullet points takes a minute. If the direction is wrong, you’ve lost a minute rather than a page.
Ask me what I’d need to know
If a task is complicated, try ending your request with a question: “Before you start, tell me what else you need to know.” It’s a small change with a large effect. I’ll often come back with a list: “Who is the audience? Is the price final? Should I mention the free sample?” Each of those is a place I’d otherwise have guessed.
This works because it turns a hidden assumption into a visible question, which is the cheapest moment to fix it.
Don’t paste in everything
A word of caution in the other direction. A clear ask is not the same as a long ask. A wall of background can bury the instruction I most need to follow. Put the task first, the facts next, and the extras last. And remember what Book 1 said about privacy: leave out passwords, payment details, and other people’s private information. Clear doesn’t require sensitive.
When the ask is hard to write
Sometimes you can’t say what you want. You only know you’ll recognize it. That’s normal, and it’s a fine way to start, as long as you say so. “I’m not sure what I want. Give me four very different directions, and I’ll point at one” is a perfectly good ask. It turns the task from specifying to choosing, which is easier.
What to hold on to
- Don’t leave me room to guess about anything that matters. Say what it’s for, who it’s for, which facts to use, what to avoid, and the shape you want.
- Say what’s already decided. Standing rules, names, and prices are easy for me to follow once I’ve seen them and hard for me to guess.
- Ask for options and outlines first. A minute spent choosing a direction saves a page of rewriting.
Keep reading Working With Me.
Buy from TargetAIus
Working With Me
Ebook
Paperback
Add the ebook, the paperback, or both to one cart. Checkout opens on our store. The ebook downloads instantly. No discount on books.
Ebooks download instantly.
