Book a walk-through

Stop re-explaining your process to AI every single time

You do the same CMA, the same pricing rationale, the same proposal every week, and you explain it to the AI from scratch every time. Write it down once as a skill and the model loads your process automatically. Here is what goes in one, which three to build first, and the honest math on when it pays back.

Zack PetroccaOrigin, the right hand most owners never had · 4 min read
In this article
  1. What a skill actually is
  2. The three worth building first
  3. What goes in one
  4. The honest math
  5. Do this this week

Here is a habit I watched an agent repeat four times in one week.

Open ChatGPT. Paste three comparable sales. Type roughly the same paragraph they typed on Monday about how they like a CMA structured, which adjustments matter in their market, what tone the client expects. Get back a pretty good draft. Fix the two mistakes it always makes. Send it.

Four times. Same explanation, retyped from memory, slightly different each time. Four slightly different CMAs, and the quality depended on how well they happened to describe the process that morning.

That is not an AI problem. That is a process sitting in one person’s head, being re-derived on demand.

What a skill actually is

Strip the jargon and a skill is a folder with your instructions in it. You write down how you do a task once. From then on, when you start that kind of task, the model loads those instructions and follows them without being asked.

Claude supports these directly. So does Claude Code, and the same idea works in ChatGPT as a custom GPT or a project with instructions attached. The container matters less than the habit: the process lives in a file, not in your memory.

The difference in practice is not that the AI gets smarter. It is that it stops guessing what you want, and you stop paying the tax of explaining.

The three worth building first

Pick processes you repeat and that have real rules. In this business that usually means:

The CMA. Which comps qualify, how far out you will go, what adjustments you make and in what order, how you handle a subject with no true comp, what you will not put in writing. This is the single most repeated analytical task most agents have and almost nobody has it written down.

The pricing conversation. Not the number, the argument. What you show a seller who is 12% over, in what order, with which market evidence. The agents who are good at this are running a script they have never written down, which is also why it does not survive when they hire.

The proposal or scope. For anyone selling a service: what is always included, what is priced separately, what you will never agree to, the words you use for the guarantee. This one pays back fastest because the cost of getting it wrong is a bad engagement, not a bad document.

What goes in one

Five parts, and the order matters less than the fact that they are written.

  1. The steps, in the order you actually do them, not the order that sounds tidy.
  2. The rules that never break. These are the valuable part. “Never use a comp more than six months old.” “Never quote a price in the first email.” “Every number gets a source.”
  3. What good looks like. One real example of the finished work. This teaches more than a page of description.
  4. What to do at the edges. The case that always comes up and always makes you think. Write down the answer you already use.
  5. What done means. The check you run before it goes out.

The rules and the edge cases are the ones people skip and the ones that carry the value. Anyone can describe the happy path. What makes your work yours is the judgment you apply when the happy path does not hold.

The honest math

The first time you do this, it is slower. You are doing the work and writing down how you do it at the same time, and that is maybe an extra hour on a task you already knew how to do.

You get that hour back on run three or four. After that, every run is faster, and the saving compounds in a way that is easy to miss: it is not just your time, it is the review time. When the output follows a written standard, you are checking it against a rule instead of reading it fresh and deciding whether you like it.

The bigger return is the one nobody counts. A process in a file can be handed to a new hire, a virtual assistant, or a piece of software. A process in your head can only be handed to you. Every hour you spend converting the second kind into the first kind raises the ceiling on what your business can do without you in it.

We did this with our own weekly newsletter last week. The format, the research sources, the rules about what qualifies as news worth printing, the checks before it sends: all of it lived in my head and in a long conversation. Now it is a file. The next issue does not start with deciding any of that. It starts with the work.

Do this this week

Look at what you did three times last month. Not the big annual project, the repeated task.

The fourth time you do it, do it with a blank document open next to you. Write the steps as you take them, and every time you catch yourself thinking “well, except when,” write that down too, because that is a rule.

At the end you will have a rough, useful draft. Rough is fine. A written process that is 70% right beats a perfect one that only exists when you are in the room.

Then use it next week and fix the two steps that were wrong. That is the whole method.

Questions this usually raises

What is an AI skill?
Short answer

A skill is a folder with your instructions in it. You write down how you do a task once, and from then on the model loads those instructions and follows them when you start that kind of task. Claude and Claude Code support skills directly, and the same idea works in ChatGPT as a custom GPT or a project with instructions attached.

How do I stop re-explaining my process to ChatGPT or Claude?
Short answer

Write the process down once and attach it, as a skill, a custom GPT, or project instructions, instead of retyping it from memory each time. The AI does not get smarter; it stops guessing what you want, and every run follows the same standard.

What should a written process for AI include?
Short answer

Five parts: the steps in the order you actually do them, the rules that never break, one real example of the finished work, what to do at the edge cases, and the check you run before it goes out. The rules and the edge cases carry most of the value and are the parts people skip.

Which processes should I document first?
Short answer

The ones you repeat that have real rules. For real estate agents that is usually the CMA, the pricing conversation with a seller, and the proposal or scope. The proposal pays back fastest, because getting it wrong costs you a bad engagement, not just a bad document.

Is documenting a process worth the time?
Short answer

The first run is slower, maybe an extra hour, and you get it back by the third or fourth run. After that every run is faster, review gets quicker because you check against a rule, and the process can be handed to a new hire, an assistant, or software. A written process that is 70% right beats a perfect one that only exists when you are in the room.

The System Drop

One thing to put to work, every week.

A short email with one setup, the steps, and the prompt or template to do it. Plus the news that changes how you run the business.

Step 1 of 2

More in Getting the work done
When you're ready

When you'd rather we build it with you.

Most owners start here. When you want a right hand to build it with you, start with a walk-through. We walk your business with you and find the priority that will do the most for it.

“I went from an independent contractor to a business owner.”

$7.3M to ~$11M in sales

Beau P.Real Estate Team Leader