Automation Sprint

One day in your office. On Monday, the job runs itself.

For a team of up to 6 with one recurring job that costs real hours every week.

Three hours go into the press review every Monday. Then the same job returns next week, and every week after that.

This is the in-person format. We spend a full day with your team, in your building, on your real work. No slides, no generic exercises, no hypothetical use cases.

By the end of the afternoon one job you currently do by hand is running on its own, built with your tools and your data, and your team has watched it being built. Seeing it made is half the value: it is the moment people stop thinking of AI as a chat window.

The day is the service and the obligation at the same time. While we work, the AI literacy register the Act asks you to keep gets filled in, with names and dates.

How it runs

Morning: we look at the real work
We open your editorial calendar, your inbox and your drive. We list the recurring jobs and measure them: how often, how many minutes, who does them. Then we pick the two with the worst boredom-times-frequency score.
Afternoon: we build, in the room
The first of the two gets built live, in front of you, with your data and your tools. Not a prototype: the real thing, still running after we leave.
Last half hour: the boring part that pays
What can be uploaded and what cannot. What has to be disclosed when it goes out. Who approves. We fill the register in there and then, while everyone is still in the room.
Two weeks after: delivery
We finish the documentation, specify and price the second automation, and hand over the mini-policy. You can call us while you settle in.

What you leave with

One working automation, yours, with the documentation to change it without calling us.
A second automation specified and priced, ready to switch on when you want it, for example a press review or a monitoring digest on the files you follow.
A reusable prompt and skill set your team runs again without rebuilding the method.
An AI literacy register, filled in by name and date.
A two-page operational policy: what is allowed, what is not, who approves.
Playbook Team Edition, three months of access for the whole team.

Questions

Why is this in person rather than online?

Because the morning depends on opening the actual work, and the afternoon depends on your team watching the thing get built. Both lose most of their value over a video call. This day is what we mean when we say workshop; there is no separate workshop product.

What if we do not know which job to automate?

That is the morning. We measure the recurring jobs with you and pick on frequency and tedium, not on what sounds impressive. Small teams almost always already know the answer; the measuring makes it defensible.

Does the automation keep working after you leave?

It runs on your tools, and it comes with a documented manual route so a person can always complete the job by hand. If you want someone to own it as your work changes, that is Partner Light.

One day in your office. On Monday, the job runs itself.

How it runs

What you leave with

What does that job cost you today?

Questions