Question 1

When do the 30 days start, and what counts as done?

Accepted Answer

The clock starts the day we are given access, not the day you sign. Inside it: a mapping call where we write down how the work happens now and what it takes out of your week, an agreement on what gets built and what it will never do without a person, the price read off a fixed catalog, the build and the install on your own accounts, then a rollout where your people put their real work through it with us in the room. Done means one job running on your real work, not a demo of it. If access takes three weeks to arrange, the 30 days start when it arrives.

Question 2

Where does ten hours a week come from?

Accepted Answer

Anthropic’s Economic Index (2025) found AI power users save 10+ hours a week, and it is the one figure on this site with a source under it. It is a finding about AI power users, not a promise about your business, because nobody has measured your business yet. The number the guarantee is measured against is the one we write down with you at the mapping call: the work in scope, and what it takes out of your week today. Source: Anthropic Economic Index, 2025.

Question 3

What do I tell the people who do this work today?

Accepted Answer

Tell them it is about capacity. It takes the work nobody is measured on: chasing the same document, retyping the same reply, raising the same invoice on the same day every month. Your people stay on the parts that need judgement, and the same people carry more of the week without adding headcount. We map the work with the people who do it, and they put their real work through it with us in the room. If it is still being worked around after that, it is the wrong build.

Question 4

Why not give the job to someone on the team?

Accepted Answer

Often you should. If a person has room for it and it is genuinely their work, do that first and keep your money. The jobs worth building are the ones that come back to you whoever you hand them to, because they need your prices, your rules or your sign-off. Handing those over moves the queue instead of clearing it. If the honest answer on your call is a person with room, you will hear that instead of a proposal.

Question 5

Who is accountable when it gets something wrong?

Accepted Answer

A person you name, and the line is agreed in writing before we build. Anything that reaches a client, moves money or cannot be undone is drafted by it and sent by a person, and that step moves only if you move it yourself, in writing, once you have watched it work. Your AI agent is built to stop and say it does not know instead of guessing, and a correction is written down once and stays. The name we give it moves no responsibility off a person.

Question 6

What if that work still takes the same hours in 30 days?

Accepted Answer

You get the build fee back. At the mapping call we write down the work in scope and the hours it takes out of your week today. If that work is not taking less of your week 30 days after install, you tell us by email and the build fee is refunded. No forms and no argument. It assumes you took part: the access we agreed, and a real run on your own work. Delivered support hours are not covered and hourly consulting carries no guarantee.

Ten hours a week back.You decide. It does the work.

Your business already uses AI.It still waits to be asked.

The part you don’t have.The layer that makes it run.

Owners and operators.In their own words.

We do the setup.You run the business.

Mapping

Plan

Build

Rollout

Worth doing, or not yet.Here is how to tell.

What small businesses ask before the call.

A 30-minute audit call.No pitch.