Speak it once,
the AI listens.
Here is the machine I use more than any other, and the one that has quietly made me the most money. Writing a good instruction for a bot used to take me hours. I had to remember everything, test it against the AI, and watch it ignore half of what I asked, because I did not know how to talk to it so it would listen. Some projects slipped for weeks over this. So I built a machine whose only job is to write the best, most precise instructions I can give an AI. It weighs every variable, every use case, and every pitfall. Now I grab the mic, say plainly what I want, and it hands me the exact wording in seconds instead of hours. A better instruction makes every other bot a little sharper, and that small edge compounds across my whole company.
Your bot is not broken. It just never got a clear instruction.
Most people blame the AI when a bot gives a weak result. The real problem is almost always the instruction. Write it loosely and the AI fills the gaps with guesses, ignores half your rules, and hands back something close but wrong. Writing a truly precise instruction by hand takes hours, because you have to think through every variable, every use case, and every trap that makes an AI drift. So I built a machine that does that thinking for me. I speak a loose brief, and it writes the exact prompt in seconds. Here is who it is for, what goes wrong without it, how it works, and what you get back.
Who it’s for
Anyone who runs bots or automations and is tired of fighting the AI to get a clean result. Founders, marketers, agency owners, anyone who writes instructions for an AI and wishes it just listened the first time. It works even if you have never written a good prompt in your life, because the machine does the hard thinking and you only speak plainly.
What goes wrong
Without it, you write an instruction from memory, test it, and watch the AI ignore parts of it. You tweak, retest, and lose hours per bot. Projects slip for weeks. You are not short on ideas. You are short on a fast way to turn a rough idea into wording the AI actually follows.
How the machine works
You speak what you want in plain words. The machine weighs every variable, every use case, and the pitfalls that make an AI drift, then writes the precise, complete instruction. You do none of the hard wording by hand. The machine gathers the angles, avoids the traps, and hands you the finished prompt.
What you get back
A precise prompt in seconds instead of hours. Drop it into any bot and the output gets sharper and more consistent. A better instruction makes each automation convert a few percent better, and as your stack grows, those small edges compound into real numbers.
I was losing hours to a single instruction. Then I built the thing that writes them for me.
This is the machine I use more than any other, and the one that has quietly made me the most money, because it writes the best, most precise instructions I use every day in every automation. Each one comes out more precise, more optimised, and delivers the exact output I want, in a fraction of the time. Back in the day, writing a single instruction took me hours. I had to remember everything, then test it against the AI, because some of my rules were simply ignored.
The real problem was that I did not know how to talk to the AI so it would listen. It took so much time that I had to schedule and postpone projects for weeks, all because one instruction would not behave. So I built a machine whose only job is to write the best, most precise instructions. Really precise ones, that take into account all the variables, all the use cases, and all the possible pitfalls.
And it gives me the result in seconds instead of hours, or weeks of postponing. Now all I do is grab the mic, explain what I am trying to do, and it hands me the absolute best instructions I can use in my bots and automations. The thinking that used to eat my afternoon happens quietly, in the background, while I move on to the next thing.
This has changed my whole company, directly and indirectly. I execute far faster, I execute better, the results are more consistent, the quality is higher, and it all takes a fraction of the time. The most useful thing a company can own is the ability to turn a rough idea into a working instruction in seconds, and that is exactly what this machine gives me, on tap, every single day.
The numbers here are kept deliberately modest. A better instruction simply makes each automation a little sharper than a hand-written one would. Say each bot converts a few percent better, and on client work the delivery time drops, so I can take on one or two more clients. That edge is small on one bot, but I run many, and every one of them shares the same lift. A small edge on every automation, compounding across my whole stack, quietly turns into real revenue.
Proof point: I have documented how I run my whole company on autopilot and the systems behind it on YouTube, in a day in my life and the road I am walking in the road to 10 million, so the conservative numbers on this page are checkable.
Three moves that turn a loose brief into a prompt the AI obeys
What made this work was treating a prompt as a build, not a wish. Most people type a rough request and hope the AI fills in the rest. But a good instruction is a small piece of engineering: it names every variable, covers every use case, and closes every gap where the AI could drift. The loop here takes your spoken brief, weighs those angles for you, and writes the exact wording that makes the AI listen. From a loose idea, a precise instruction writes itself, and the same instruction lifts every bot you run. That is how prompt writing stops being a fight.
Speak: say what you want in plain words
The first move is the easy one, and it is yours. You grab the mic and explain, in plain words, what you are trying to do. No jargon, no clever wording, no worrying about how to phrase it for the AI. You just describe the job the way you would tell a colleague. That is the whole input. The machine does not need you to be a prompt expert, because being a prompt expert is its job, not yours. All it needs from you is the honest, rough version of what you want, and it takes over from there. This one move is why the whole thing is fast: the hard part is handed off, and you only supply the idea.
Weigh: cover every variable, use case, and pitfall
The second move is where the hours used to go. The machine takes your loose brief and thinks through the angles you would have had to work out by hand. It names every variable the instruction depends on, walks every use case the bot might hit, and maps the pitfalls that quietly make an AI ignore you: vague wording, rules that fight each other, the missing detail that breaks the output. This is the part almost nobody does properly, because it is slow and easy to skip. The machine never skips it. It weighs the whole thing carefully, the same careful way every time, so the instruction it writes has no soft spots for the AI to slip through.
Write: hand back the prompt the AI listens to
The third move is the payoff. Out comes a precise, complete instruction, worded so the AI does exactly what you meant, the first time. No more testing, tweaking, and retesting because a rule got ignored. The wording is built to be followed, because it was engineered around how an AI actually reads. Then the real value shows up: the same instruction drops into every bot you run. One good prompt does not help one automation, it lifts all of them at once. And because a sharper instruction makes each bot convert a little better, that small edge quietly rides across your whole stack.
Once those three moves are in place, the fight is over. You speak a loose brief, the machine weighs every variable and pitfall, and it hands you the precise prompt in seconds. You stop losing hours to a single instruction, you stop watching the AI ignore your rules, and you drop the same sharp prompt into every bot you run. You get a finished instruction built by a machine that did the thinking for you, and every small lift it gives each automation compounds across the whole company.
Before the system
- Spending hours writing a single instruction from memory
- Watching the AI quietly ignore half of what I asked
- Testing, tweaking, and retesting the same prompt for a whole afternoon
- Postponing projects for weeks because one instruction would not behave
- Every bot only as good as the rough prompt I had time to write
After the system
- Speaking a loose brief and getting the precise prompt in seconds
- An instruction worded so the AI does exactly what I meant
- Every variable, use case, and pitfall handled before I ever run it
- The same sharp prompt dropped into every bot I own
- A small edge on every automation that compounds across the stack
Prompt 1: turn your rough idea into a clear brief
Before the machine can write a precise instruction, it needs a clear picture of the job. The biggest mistake is a brief so vague the AI has to guess. Use this prompt to turn your rough spoken idea into a tidy brief the maker can work from.
Brief clarifier
Act as a prompt engineering assistant. I want to turn a rough, spoken idea into a clear brief that another system can build a precise AI instruction from. About the job: [describe in plain words what you want the bot to do, who it is for, and what a good result looks like]. Tidy this up: pull out the real goal, the inputs the bot will get, the output I expect, and any rules or limits that matter. Ask me for anything important that is missing. For each part, one line on why it matters to the final instruction.
The output is a clean brief, the honest version of what you want, ready for the maker to build on. Get this right and everything the machine writes next is aimed at the exact job you had in mind.
Prompt 2: name every variable and use case the instruction must cover
A prompt fails when it misses a case you did not think of. The system works because every variable is named before the wording is written. Use this prompt to surface the variables and use cases your instruction has to handle.
Variable and use case mapper
Act as a prompt architect. I have a brief for an AI instruction and I want every variable and use case it must cover surfaced before I write it. About the brief: [paste or describe the job the bot must do and the kind of inputs it will receive]. Map it out: which variables the instruction depends on, which use cases the bot might hit, which edge cases would break a naive version, and which inputs need a clear default. For each one, one line on how the instruction should handle it.
The output is the full list of angles your instruction must cover. Settle this once and the prompt you write next has no soft spot for the AI to slip through.
The 3-minute overview of how this works
Before the build steps, watch this short overview. It’s the exact video from the Automations Made Easy page, and it walks through the mechanics behind machines like this one. 1,000+ students have used these mechanics to save two hours a day, with zero coding.
Want to learn the mechanics behind operations automations like this?
I teach the same mechanics that power this prompt maker inside Automations Made Easy. 1,000+ students have used these mechanics to save two hours a day and build little machines that quietly handle the boring work. No coding required.
Week one: your first spoken brief, your first precise prompt.
Most people put off building a prompt maker because writing prompts sounds like a skill you either have or you do not, so they keep fighting the AI by hand forever. That is exactly why this machine matters. A prompt maker is meant to start simple and run quietly, not arrive perfect. In week one you speak your first loose brief, let the machine weigh the variables and pitfalls, and watch a precise instruction come back, so you know it works before you lean on it every day.
Week one looks like this. On Monday you take a job you have been putting off and speak the rough version of what you want. Then you let the machine turn that loose brief into a clear picture and surface the variables and use cases you would have missed. By midweek you have it close the known pitfalls, the vague wording and the rules that fight each other. By the end of the week you have a finished prompt you can drop into a real bot, and it does what you meant on the first run.
The point of the first week is not the number of prompts written. The point is to confirm the machine turns your plain spoken brief into an instruction the AI actually follows. Once that is locked, every rough idea you speak comes back as a precise prompt in seconds, and the same sharp instruction lifts every bot you drop it into, while you do none of the hard wording yourself.
From there the maths is simple and conservative. A better instruction makes each automation a little sharper than a hand-written one, so each bot converts a few percent better and each client job ships faster. That edge is small on one bot, but you run many, and every one of them shares the lift. Over three to five years, those small edges stack across a growing stack of automations and quietly compound into real revenue, all from prompts you spoke in seconds.
All of this runs while you work, sleep, or build your next bot. You speak the brief, the machine weighs the variables, closes the pitfalls, and hands you the precise prompt. No more losing an afternoon to one instruction, no more watching the AI ignore your rules, no more projects slipping for weeks. Your best prompts arrive on tap, and each one makes every automation you own a little bit better.
Prompt 3: close the pitfalls that make an AI ignore you
Even a detailed instruction fails if it is worded in a way the AI drifts around. The plan only holds once the known traps are closed. Use this prompt to find and fix the pitfalls that quietly make an AI ignore parts of your instruction.
Pitfall closer
Act as an AI instruction reviewer. I have a draft instruction and I want the pitfalls that make an AI ignore or drift from it found and fixed. About the draft: [paste the instruction, or describe what it tells the bot to do]. Find the traps: vague wording the AI could read two ways, rules that fight each other, missing details that force a guess, and anything that lets the AI skip a step. For each trap, give the fixed wording and one line on why the new version holds.
The output is a hardened instruction with the traps closed. Run this once and the AI stops drifting, because there is no longer a gap in the wording for it to slip through.
Prompt 4: write the final prompt and make it reusable
The brief is the research. The finished prompt is what you run. A good final prompt is precise, complete, and easy to reuse across many bots. Use this prompt to assemble the pieces into the clean instruction you will drop into every automation.
Final prompt writer
Act as a senior prompt engineer. I have a clear brief, a full list of variables and use cases, and the pitfalls closed, and I want the final instruction written. About the use: [describe which bots this prompt will run in and how often you expect to reuse it]. Write the instruction: state the role, the goal, the inputs, the rules, and the exact output format, in wording the AI will follow the first time. Mark the parts I should swap per job, so the same prompt works across many bots. Keep it tight and plain.
The output is the finished prompt, precise and easy to reuse. Get it right and you drop the same sharp instruction into every bot you run, so each one gets a little better at once.
The exact build, step by step
Grab the mic and say what you want
Start where it is easiest for you. Instead of staring at a blank prompt box, you grab the mic and explain, in plain words, what you want the bot to do. No jargon, no clever phrasing, just the honest rough version, the way you would tell a colleague. This single move is why the whole thing is fast, because the hard part is handed off and you only supply the idea. This is the step most people never reach, because they think they have to be good at prompts first. You do not. You just have to know what you want, and say it.
Let the maker weigh every variable and use case
Instead of writing the instruction yourself, the machine does the thinking. It takes your loose brief and works through the angles you would have had to figure out by hand. It names every variable the instruction depends on and walks every use case the bot might hit, so nothing is left to a guess. This is the slow, careful work that used to eat my afternoons, and now it happens in the background in seconds. By the time you look, the machine has already mapped the whole job, and none of the important angles have been left out.
Map the pitfalls that make an AI drift
Here is the move that changes everything. The machine knows the traps that quietly make an AI ignore you, and it maps them before writing a word. Vague wording the AI could read two ways. Two rules that fight each other. The missing detail that forces a guess and breaks the output. These are the exact things that used to make me test and retest a prompt for hours. The machine writes around every one of them, the same careful way every time, so no soft spot is left for the AI to slip through. What you end up with is not a hopeful draft but an instruction built to be followed.
Get the precise instruction the AI listens to
Now the machine hands back the finished prompt. It is precise, complete, and worded so the AI does exactly what you meant, on the first run. No more testing, tweaking, and retesting because a rule got ignored. The wording was engineered around how an AI actually reads, so the AI listens instead of drifting. This is the moment that used to take me hours of back and forth, and now it arrives in seconds. You did not become a prompt expert. You spoke plainly, and the machine turned it into the exact instruction the AI follows.
Drop the same prompt into every bot you run
Now the real value shows up. A good instruction does not help one automation, it lifts all of them. You take the precise prompt the machine wrote and drop it into every bot you own, so each one gets a little sharper at once. The bot that writes your emails, the bot that sorts your inbox, the bot that drafts your posts, all of them run on better instructions. This is the quiet multiplier. One good prompt, spread across a whole stack of automations, means the same small edge rides everywhere you have work being done for you.
Watch the small edge compound across the company
Final piece. Because every bot now runs on a sharper instruction, each one converts a little better and each client job ships faster, up to a fraction of the time it used to take. These are not big single wins. They are small edges, spread across every automation you run, and that is exactly what makes them add up. A better prompt makes one bot a few percent better, and a few percent across a whole stack, month after month, quietly becomes real money. This is the part that compounds, and it is why this machine is the one I use the most.
Speak the brief
You grab the mic and say plainly what you want the bot to do, in your own words.
Weigh the angles
The machine covers every variable, use case, and pitfall your loose brief hides.
Write the prompt
It hands back a precise, complete instruction worded so the AI listens the first time.
Lift every bot
You drop the same prompt into every automation, and the small edge compounds across all of them.
Build this prompt maker inside the same playbook 1,000+ students use
Automations Made Easy teaches the mechanics behind machines like this one. Step by step, no code, plain English. Save two hours a day and own little machines that write your instructions for you, so you spend your time running the business instead of fighting the AI to listen.
The six months after I switched it on
Here is the shape of the first six months after I turned the prompt maker on. The line tracks the extra value from sharper instructions across my stack, the small edge each better-run bot earns over a hand-written prompt, which is exactly how this machine pays off in practice.
Monthly value from sharper prompts across the stack
Three things matter on this chart. The value climbs steadily as more bots run on sharper instructions and client jobs ship faster, not in a spike. The gains come from prompts the machine wrote in seconds, without me losing a single afternoon. And every one of those months happens while the machine turns my spoken briefs into precise instructions for me.
What other students built
I teach the simple skills behind machines like this in Automations Made Easy. Students who built their own version sent back what changed in their first month.
“I stopped fighting the AI. I speak what I want, the machine writes the instruction, and the bot does it right the first time. What used to take me an afternoon now takes a minute.”
“The pitfalls part was the gift. It caught the vague wording that kept making my bot drift, fixed it, and now every automation I run gives me a cleaner result than before.”
“I used to postpone projects because one instruction would not behave. Now the prompt arrives in seconds and I just get on with the work. My delivery time on client jobs dropped hard.”
“Knowing week one was just speaking one brief and getting one clean prompt kept it easy. By month two I had dropped the maker into every bot I run and the whole stack got sharper.”
What’s inside Automations Made Easy
AME isn’t a library of pre-built automations. Every business is slightly different. What’s reusable across all of them is the underlying mechanics: how to set up little machines that listen, write, and follow up while you sleep, and how to wire the pieces together without writing code.
The program walks you through six modules: The Right Tools (the cost-effective, no-code stack I actually use), Task Selection Mastery (which automations are worth building first), Design Secrets (mapping an automation before you build it), Zero to Hero (complete beginner to confident automator), Real-World Application (we build a full automation together, end to end), and Monetization Mastery (turn the skill into a side-business).
It also includes done-for-you templates you import in two clicks, over-the-shoulder training videos, and the same playbook 1,000+ students have used to save two hours a day. No coding required. If you can copy and paste, you can build this.
The high level prompt maker: common questions
Pulled from what readers and Automations Made Easy students ask most.
Do I need to be good at writing prompts to use this?
No. That is the whole point. You speak, in plain words, what you want the bot to do, and the machine does the expert part for you. It weighs the variables, covers the use cases, and closes the pitfalls, then writes the precise instruction. The skill you need is knowing your own job, which is exactly what Automations Made Easy helps you turn into working machines. The wording is handled for you.
Why does a better instruction matter so much?
Because a bot is only as good as the instruction it runs on. A loose prompt makes the AI guess and drift, so the output comes back close but wrong. A precise one makes the AI do exactly what you meant, the first time. Since the same instruction can run in many bots, one good prompt lifts your whole stack at once, and that is where the value quietly stacks up.
How does it know the pitfalls that make an AI ignore me?
The machine is built around how an AI actually reads an instruction. It looks for the known traps: vague wording the AI could take two ways, rules that fight each other, and missing details that force a guess. I keep the method light here on purpose, but the result is what matters. It writes around each trap, so the finished prompt has no gap for the AI to slip through.
How is this better than writing the prompt myself?
Writing a truly precise instruction by hand takes hours, because you have to think through every variable, use case, and pitfall, then test it against the AI. The machine does that thinking in seconds and never skips the slow parts. The numbers on this page stay modest, but a sharper instruction simply makes each automation a little better than a hand-written one, and that edge rides across every bot.
Can the same prompt really work across different bots?
Yes, and that is where the money is. A precise instruction is written with the swappable parts marked, so you drop the same core prompt into many bots and change only the job-specific bits. One good instruction does not help one automation, it lifts all of them. That is why a small edge on a single prompt turns into a real edge across a whole stack of machines.
More Money Makers like this one
Built from the same handful of mechanics. Each one captures, converts, or earns money that would have walked out the door.
Build this prompt maker yourself, or learn the mechanics inside Automations Made Easy.
If you want to learn the mechanics behind operations automations like this and build your own at home, Automations Made Easy is the playbook. Step by step, no code, plain English. If you want to talk through how to turn your spoken briefs into precise prompts that make every bot listen, I take a small number of consulting clients each month.
€497 one-time · Lifetime access · 1,000+ students
