The SOP-to-Agent Kit: turn one written process into an AI agent that does the job your way

Step 1: Pick one process to start with

Pick a job that repeats every week, follows roughly the same steps each time, and that you're tired of doing or checking yourself. Good first picks: replying to new quote requests, writing a weekly client update, turning call notes into a follow-up email, or checking an order before it ships.

Skip anything that moves money, needs legal judgment, or needs access you aren't ready to give. Start small.

Step 2: No SOP yet? Let Claude interview you

Answer the way you'd explain it to a new hire. Use voice dictation if typing is slow. Real examples are worth more than rules.

Step 3: Turn the SOP into agent instructions

This is the main prompt. Paste your SOP in at the bottom.

Answer the questions at the end, then ask Claude to update the instructions with your answers. Save the final version.

Step 4: Put it in a Claude Project

1. In Claude, create a new Project and name it after the job, like "Quote Reply Agent".
2. Paste the agent instructions into the Project instructions.
3. Add knowledge files: the SOP itself, your price or service list if the job needs it, two or three examples of great past work, and any templates.
4. In ChatGPT: create a Project or a custom GPT, paste the same instructions, and upload the same files.

Now that one job has its own agent. Open a chat in the Project, give it the inputs, and it works from your instructions every time. On a plan that lets you share Projects, or by sharing a custom GPT, anyone on your team can use it too.

Step 5: Test it on real past cases

Don't trust it yet. Give it three to five real jobs from the past where you know what the right result looked like. Remove names and private details first.

Compare each answer to what you, or your best person, would have done. Write down every gap.

Example. A small cleaning company turns its "reply to a new quote request" SOP into an agent. The Project holds the SOP, the price ranges by home size, and three of the owner's best past replies. First test: a request for a deep clean of a 3-bedroom home with a dog. The agent writes a friendly reply with the right price range and asks for the move-in date. But it offers a Saturday slot, and the owner always checks Saturdays with the team first. The SOP never said so. That's a gap in the SOP, not a bad answer.

Step 6: Fix the SOP, not the answer

When the agent gets something wrong, the easy move is to fix the answer and move on. Don't. Fix the instructions, so it never makes that mistake again.

Paste the change into the Project instructions and the SOP file, then run the same test again. In the cleaning example, the fix is one new "stop and ask me" line: weekend slots need the owner's OK. When it passes all your test cases, it's ready to use. Keep a person checking anything that goes to a customer until it's earned your trust.

Step 7: Repeat, then follow the rules

One SOP, one agent. Do that ten times and you've got a team. Each new agent goes faster, because now you know the steps.

Rules and common mistakes:

• One agent, one job. An agent that does five jobs does all of them badly.
• Always include "when to stop and ask me". That's what keeps it safe.
• Test on real past cases before any customer sees its work.
• Fix the SOP, not the answer.
• Keep a person reviewing anything that goes to a customer until you trust it.
• Never paste passwords, card numbers or private customer data into a chat.
• Update the Project the day your process changes.