Question 1

What is the catch with a free AI Opportunity Audit?

Accepted Answer

There is no catch, but there is a reason. The audit is the part of this work that sells the rest of it: once a leadership team can see the hours their recurring work actually costs, ranked, with their own job titles attached, the decision usually makes itself. Peter would rather spend forty-five minutes finding out whether that is true for your company than spend it persuading you of anything. If it turns out there is not enough there, he will say so, and you keep the ranking either way.

Question 2

What does the audit actually cover?

Accepted Answer

Six questions beforehand, covering what the business does, which systems it runs on and where the week goes, then forty-five minutes on the recurring work those answers reveal. You leave with the three jobs worth automating first, the hours each one currently costs you, an honest read on how much of it a machine can safely take, and what would have to be true for it to work. It is a first pass over the same audit that opens the workshop, so you are seeing a sample of the real deliverable rather than a brochure.

Question 3

How much does the workshop cost?

Accepted Answer

One fixed fee for the whole engagement, quoted on the audit call. It is fixed because the scope is fixed: the full audit before the day, the day itself, the jobs installed inside your own software, the playbook and the policy your company keeps, and thirty days of support while your team runs it. There are no tiers, no day rates that creep upwards and nothing to renew. The reason it is quoted rather than published is that the honest answer to whether it is worth it depends on what the audit finds, and neither of us knows that before the call.

Question 4

Can a single day really be enough?

Accepted Answer

The day works because it does not start from nothing. The audit that would otherwise fill the first fortnight is finished before you arrive, so every hour in the room is spent deciding and building rather than gathering. You are also not being taught a framework to apply later. The jobs are designed, built and run on real work from your own week before anybody goes home. The thirty days afterwards exist for the one part that genuinely cannot be compressed, which is your team using the system for the first time on live work.

Question 5

How much of my team's time does this take?

Accepted Answer

Forty-five minutes to find out whether it is worth doing at all, and after that one working day plus about half an hour of intake. The workshop runs from roughly half past nine to five, with a break for lunch. Then the commitment is about an hour a week each, and Peter carries the tuning work through the following month so it does not land on anyone's desk.

Question 6

Who should be in the room?

Accepted Answer

Three to six people: whoever runs the business, and whoever actually does the work we are going to automate. The second group matters more than the first. A day spent with directors alone produces a system nobody uses, because the person who does the job every day is the only one who knows the exceptions that break it.

Question 7

Will this cost people their jobs?

Accepted Answer

Not in any company we would take on, and it is a fair question to ask before you put it to your team. We deliberately choose work that is repetitive and carries no judgement: rekeying, chasing, first drafts, looking things up. That is where a machine is genuinely better, and where nobody enjoys spending their afternoon. If your plan is to cut headcount, you do not need a workshop for that and we are the wrong people to run it. Say plainly to your team what the day is for. The ones who do the job usually arrive with the best list of what to automate first.

Question 8

What happens to our data?

Accepted Answer

You decide, in writing, on the morning of the workshop, and it goes into the policy you keep. In practice we build inside the tools you already trust and already have a contract with, using the business tiers where your content is not used to train anybody's model. Anything genuinely sensitive, such as client files, personal data and the things your insurer would ask about, is either kept out of the system entirely or handled by a person. That decision is yours, we write it down, and you can hand the result to a client or an auditor who asks. The free audit needs none of it: six questions about how the week runs, and no access to anything.

Question 9

Do we need a technical person, or developers?

Accepted Answer

No. We work with the people who run the business and the people who do the work, not with developers, and there is no code for anybody to maintain afterwards. Peter does the technical part on the day. Your team needs to know how to use what has been built, which is what the afternoon and the following thirty days are for. If you do have someone technical, bring them. They usually enjoy it and they will own it well, but nothing here depends on having one.

Question 10

Do we need to buy new software?

Accepted Answer

No. We build inside the tools you already use, because software you have already paid for and already know how to open is far more likely to be used. Most companies find that what they need is sitting inside a subscription they are already paying for. We only recommend anything new when a genuine gap is blocking the work, and that is rare.

Question 11

Why is the fee prepaid and non-refundable?

Accepted Answer

Because the largest single piece of work happens before you walk into the room. The full audit of your recurring work, the read of your systems and the first ranked list of what to automate are all finished in advance, and that work cannot be unspent once it is done. Paying in full before it begins keeps the scope fixed and the fee fixed with it. Nobody is asked to commit to any of that until the free audit has shown them what is there.

Question 12

What does the support in the thirty days actually cover?

Accepted Answer

Three things. Peter reviews the output as your first real work goes through and corrects the prompts and rules himself, so the tuning does not become somebody's homework. He answers questions by text or email within a working day. Then at the end of the month there is a review call, where we look at what the system produced, adjust anything that is not working, and confirm the weekly hour is holding without him. After that there is nothing further to pay and no licence to renew.

Question 13

What happens after the thirty days?

Accepted Answer

Nothing, unless you want it to. The capability ends up with your company rather than with us: the playbook, the prompts and the policy are written in plain language and kept inside your own tools, so nothing is locked in an account you cannot reach and nobody has to call us to change a prompt. Some companies do ask Peter to keep going month by month afterwards, adding jobs as the first ones bed in. That is a conversation you have once you have seen the work, and it is never a condition of booking.

Question 14

Is this an AI automation agency?

Accepted Answer

No. The work comes first and AI provides the leverage. The AI handles what is repetitive, high volume and low judgement. A person keeps the judgement and approves anything that reaches a customer, because your reputation took years to build and a poorly judged message can undo it in an afternoon. If what you want is a bot answering your customers unsupervised, we are the wrong firm.

Question 15

Could we not just do this ourselves with ChatGPT?

Accepted Answer

You could, and a good number of companies are trying. What usually happens is that two or three enthusiasts build something impressive, it works while they maintain it, and it quietly stops the month they get busy. The difficult part was never the prompt. It is choosing the right jobs, agreeing what a person must always approve, building it where the work already happens rather than in somebody's private account, and writing it down so the company owns it rather than an individual. That is what the day is for. If the audit shows you can genuinely do it yourselves, Peter will tell you so.

Question 16

What is the wait time?

Accepted Answer

An audit call is usually available within a week. Beyond that, Peter runs every workshop personally and supports every company through the month that follows, so only a small number are ever underway at once. In practice that means two to six weeks before a date becomes available. If you have a planning cycle or a budget year approaching, it is worth having the call earlier rather than later.

Questions people ask before they book.

Still deciding?