What a Claude Code setup includes: what to expect

This article walks through what a done-for-you Claude Code setup includes, from the first call to the handover. You will learn what happens in the discovery week, what the rules are, how the person-approves step works, what training covers, and what you own at the end.

Claude and Claude Code are Anthropic's products. I am an independent consultant, and I am not affiliated with Anthropic.

I do not list prices here. I share them on the first call.

It is a setup, not a course

A setup is not a class, and it is not a subscription to a tool. I build it for your business, on your computers. Your team uses it every day, and you own what I build.

If you want to know what Claude Code can do first, read What Claude Code can do for a small business in the Philippines. This article is about what you get and in what order.

The steps, in order

1. Apply.
2. A short fit call.
3. The discovery week.
4. The setup: rules, the person-approves step, training and handover.
5. Monthly care, only if you want it.

Steps 1 and 2: Apply, then a short call

You fill in a short form. I read every one. If it looks like a fit, we have a 20-minute call about the work that takes your team the most time. We talk about what you do every week and which computers and tools are involved. You can ask me anything, including about prices.

Step 3: The discovery week

The discovery week is paid. The fee is deducted from the setup if you continue. I share the amount on the first call.

An NDA is signed before I see your data. Then, during the week, I:

• Map the work your team repeats.
• Measure how long each task takes now.
• Write a plan: what to automate first, what access it needs, and the hours it could save.

You get the plan in writing. If the numbers do not work, you stop there, and you have a clear picture of your own work either way. I make no promise about hours saved before this week, because measuring is what the week is for.

What the setup includes

If you continue, the setup has five parts.

1. Rules

The rules are a written list of how your business works and what the AI may and may not touch. They cover your tone for customer replies, your report layouts, your file names and your limits.

Claude Code works from these rules every time. That is why it behaves like it knows your business instead of starting fresh each day. The list is in plain words, so you and your team can read it and ask for changes.

2. The person-approves step

My rule is simple: the AI drafts, and a person approves.

Anything that sends, pays or deletes waits for a person. A customer reply is drafted, and your staff press send. An invoice entry is prepared, and a person confirms before money moves. A clean-up is suggested, and a person decides what is deleted.

This step is built in during the setup, so it does not depend on anyone remembering.

3. Least access, and testing on a copy

The AI gets only the access the task needs, starting with read-only. I test it on a copy of your data, not the live files, so a mistake during testing cannot reach your real records.

This matters under the Data Privacy Act of 2012 (RA 10173) when personal information is involved. I am not a lawyer, so ask a lawyer about your own case. I cover the full picture in Is my data safe with AI?.

4. Training for your team

A setup only works if the people who use it trust it and know how to use it. I train your team on their own tasks, using their own files. They learn how to run it, how to check a draft, how to approve or reject, and how to ask for changes to the rules.

5. The handover

At the end, you get a full handover. You own everything I build, and you should not depend on me to keep it running. The handover covers what was set up, where it lives, how to run it, and the rules in plain words.

A short example: a small accounting office

This is an illustration, not a client story.

Picture a small accounting office in Davao. The team enters supplier invoices by hand and builds the same month-end summary every month.

• Discovery week: I sign an NDA, then map how the invoices arrive and how the summary is built. I measure the time and write the plan.
• Rules: The office's file names, invoice fields and layout go into written rules.
• Person-approves step: The AI enters invoices into a sheet and drafts the summary. The accountant checks any line it marked as unclear and approves the summary.
• Training: The staff learn to run it and check drafts on their own invoices.
• Handover: The office owns the setup and the rules.

The accountant still does the accounting. The typing and the first draft are what move.

Who it is not for

A setup is a poor fit if:

• You want a quick trick or a short video course. That is not what I sell.
• The work is rare or changes every time. Repeat work is where this pays off.
• You want the AI to send, pay or delete with no person in between. I will not set that up.

If the discovery week shows the numbers do not work, I will say so.

How setup is priced

Setup is priced per computer, meaning each laptop or desktop I set up. I share the amounts on the first call. The discovery week fee is deducted from the setup if you continue.

What to do next

1. List the work your team repeats most. See 5 repeat tasks every Davao business can automate for ideas.
2. Count the computers where that work happens.
3. Apply for a discovery week. It starts with a short call, and I sign the NDA before I see anything.