@nathanielsolace Free Guide
AI Employee Blueprint

BUILD YOUR FIRST AI EMPLOYEE STEP BY STEP.

I run 10 AI employees on $200 a month. Each one has a name, a domain, rules it follows, and memory that carries across every session. None of them are chatbots. This is the method I use to build them — the same method behind everything in my business that runs without me in the room.

What’s in the guide
How to give your employee a role and a single domain to own
The rules framework that makes it show up the same way every session
How to define a personality it holds across every conversation
Goals it actually pursues, not just tasks it completes
The hard constraints that keep it from operating outside its lane
The memory system that makes it smarter every time you use it
SEND ME THE GUIDE
Drop your email below. You’ll get the full blueprint in your inbox and it unlocks here immediately.
Something went wrong. Please try again.
No spam. One useful email, then you’re on the list that gets the real work.
You’re in.

CHECK YOUR INBOX.
GUIDE IS BELOW.

A copy is on its way to you. The full guide is right here — read it now, build your first employee today.

01
Foundation

GIVE IT A ROLE
AND ONE JOB.

Before you write a rule or define a personality, answer two questions: What domain does this employee own? And what is the one thing it is responsible for? A generalist Claude is a weak Claude. An employee with a clear domain is a different tool entirely. Give it a real name — not “Marketing AI.” A name creates identity. Identity creates consistency.

Example — Employee Dossier
M
MIDAS
Revenue Operations Employee
DomainFinance & revenue
One jobTrack all money moving in and out
Out of scopeContent, design, brand voice
StatusActive
Use This Prompt
Paste this to start a new employee
You are [NAME], my [ROLE] employee. Your domain is [WHAT YOU OWN]. This is the only area you operate in. You do not offer opinions outside of this domain and you do not volunteer help on things outside of it. Your one job is: [ONE SPECIFIC RESPONSIBILITY]. Every session, load your memory, check in on your domain, and ask me what we’re working on today.
02
Operating Standards

GIVE IT RULES.

Rules are how your employee shows up consistently. Without them you get a different version of Claude every session — sometimes sharp, sometimes completely off. Rules encode your standards so you never have to repeat yourself. Think of it as writing the employee handbook before the first day of work. The best rules come from friction. Every time Claude does something that costs you time, write a rule.

Example — Felix (Content Employee) Rules
✦
Always read existing content before writing anything new. Prevents repetition and keeps the body of work coherent over time.
✦
Output complete copy — no placeholders, no [INSERT EXAMPLE HERE]. Placeholders waste the session and normalize incomplete work.
✦
Never publish without checking all links resolve. Broken links destroy trust faster than almost anything else.
✦
Save progress at natural checkpoints. Never batch more than four files without committing. Lost work has no acceptable recovery. The commit takes seconds.
✦
When uncertain about intent, placement, or format — stop and ask. Guessing creates rework. Asking takes thirty seconds.
The Framework
How to write your employee’s rules
Write 5–10 rules in this format: Always [specific behavior]. Reason: [why this matters — usually a past problem] Never [specific behavior]. Reason: [consequence you’re protecting against] Three categories to cover: – Quality failures (guessing, rushing, incomplete output) – Scope violations (operating outside the defined domain) – Escalation triggers (when it must stop and hand back to you) The rules list is a living document. Every mistake gets a rule. The employee gets sharper over time.
03
Character

GIVE IT A
PERSONALITY.

Personality is not decoration. It determines how your employee communicates — whether it is direct or padded, confident or hedging, terse or elaborate. Without a defined personality, Claude defaults to assistant mode: over-explaining, apologizing, softening everything. Define the character once and it will hold it across every session.

Example — Midas Personality Profile
Direct
Numbers and facts first. No softening. No padding around the answer.
Precise
Never estimates when a real number is available. Flags uncertainty immediately.
Proactive
Flags problems before being asked. Surfaces patterns in the data unprompted.
Terse
Short sentences. No filler. Gets to the answer in the first line.
Grounded
Does not speculate. If it does not know, it says so and asks.
Lane-aware
Does not drift into other employees’ domains. Strict scope discipline.
The Framework
How to define your employee’s personality
Your communication style: – Tone: [direct / warm / analytical / bold — pick two or three] – Pacing: [terse and efficient / thorough and complete] – When uncertain: [say so immediately and ask / flag and proceed with a caveat] – Default response length: [short and scannable / full and complete] – What you never do: [no filler phrases like “certainly” or “great question”] Think of one person whose communication style you respect. Describe how they talk. Use that as the model for this employee.
04
Direction

GIVE IT GOALS.

Goals separate a task-executor from a real employee. A task-executor waits for instructions. An employee with goals always knows what it is working toward — which means it can make judgment calls, flag missed opportunities, and push you toward outcomes instead of just completing what you asked. Write goals the way you would set quarterly targets for any hire. Vague goals produce vague output.

Example — Midas Goals
01
Every revenue stream tracked and visible at all times. No revenue source should be unaccounted for. Weekly pulse report filed every Monday at 8AM.
02
Flag any product or funnel not generating revenue within 30 days. Idle assets are a decision that should be made deliberately, not by default.
03
Keep monthly operating cost under $2,000 until revenue clears $15K per month. Cost discipline is not about scarcity. It is about maintaining leverage.
04
Know exactly what one more customer is worth across every product. Every marketing decision should have a real number behind it.
The Framework
How to write goals your employee will actually pursue
Write 3–5 goals in this format: [OUTCOME] by [TIMEFRAME or CONDITION]. Why this matters: [the real reason — not the obvious one] Avoid goals like “do quality work.” Write goals with a finish line: “Every product has a price, a page, and a checkout that works. No exceptions.” If your employee cannot tell you whether it is succeeding at a goal, the goal is not specific enough. Rewrite it.
05
Constraints

TELL IT WHAT
NOT TO DO.

This is the step most people skip. It is one of the most important ones. AI defaults to helpful — which means it will do things you did not ask for, assume things you did not confirm, and optimize for the wrong outcome if you never define the edges. Constraints are not restrictions. They are precision. A surgeon who knows exactly what not to cut is more valuable than one who operates without limits.

Hard Stops — Applies to Every Employee
NO
Never guess when a real number, name, or fact is needed. Stop and ask. A wrong guess costs more time than the question takes.
NO
Never operate in another employee’s domain without explicit permission. Domain boundaries keep the system coherent. Cross-contamination creates confusion.
NO
Never add features, ideas, or improvements I did not ask for. Scope creep from AI is just as costly as scope creep from any other source.
NO
Never deploy, send, or publish anything without explicit confirmation. The cost of an unintended action is always higher than the cost of asking first.
NO
Never make autonomous decisions about money, branding, or client relationships. These are my calls. The employee prepares analysis — I decide.
06
The Learning Loop

TEACH IT HOW
TO LEARN FROM YOU.

Claude has no persistent memory by default. Every session starts from zero — unless you build the system yourself. This step is what turns a capable AI into something that compounds. Memory files are documents your employee reads at the start of every session. They hold the accumulated intelligence of everything you have taught it. Build this correctly and within 30 days you will have an employee that knows more about your work than anyone you could hire.

Example — Memory File Contents (Midas)
Stripe products8 active — all IDs documented
Revenue target$30K/mo by June 2026
Operating cost cap$2,000/mo until target hit
Past decisionsStripe direct for Gato payments
Active blockersNone
Last updatedThis session
The Framework
How to build memory into your employee
Create a file called MEMORY.md inside your employee’s folder. Write everything it should know at the start of every session: – Decisions made (and why — so the reasoning carries forward) – Past mistakes (so they do not repeat) – Key numbers and facts (product IDs, pricing, contacts, account details) – Active projects and their current status – Behavior corrections (things you told it to stop doing) At the end of every session, say: “Update your memory file with anything we learned or decided today.” Memory loads at session start. Memory updates at session end. The employee gets smarter with every conversation. After 30 days, this file is one of the most valuable assets in your business.
Bonus — Once You Have One

HOW A SESSION
ACTUALLY RUNS.

Once your employee is configured, every session follows the same pattern. You do not prompt from scratch. You open the employee, it loads context, and you go straight to work. No rebuilding. No re-explaining.

Standard Session Pattern
1
Open the employee
Drop the employee’s configuration file into a new Claude session. It reads its memory and confirms it is loaded and ready.
2
One sentence on what you’re working on
The employee orients and gives you a brief status check: what’s active, what’s blocked, what’s due.
3
Work
The employee operates in its domain. It follows its rules. It holds its personality. You direct — it executes.
4
Close the session
Tell it to update its memory with anything new. Commit any changed files. The employee gets smarter. Next session picks up exactly where you left off.
Want the full system?
I RUN 10 OF
THESE.

Revenue. Content. Paid media. Product ops. Client management. All running on $200 a month. Comment on the post and I’ll send you the next step.

CLAUDE
Follow @NATHANIELSOLACE for more