Implementation

Business implementation, case by case.

We take on a small number of projects each year, chosen case by case and scheduled around our own work. The work is remote and in writing, and if it isn't a fit or the timing won't work, we say so plainly.

The job
Draft the Monday report from the team's shared documents
Works from
The Reports folder, read only
Done when
The draft is in your inbox by 8:00, every figure linked to its source
Asks first
Before anything goes to someone outside the team
Not included
Changing the documents it reads
Tested on
The last eight weeks of your real reports
Price
Fixed, and agreed before work starts
Illustrative: every project starts with one page like this.Agreed ✓

What it can look like

Pick a job and see how it runs.

One real job, done the same way every time. Here is what goes in and what comes back.

Forms summarized into your records, with anything missing or inconsistent flagged.

Illustrative example.

Something else? If it's a repeatable piece of work, describe it and you'll hear plainly whether Claude fits. Describe it

How it works

Five steps, all in writing.

Step 1 of 5

Describe the job

Five questions, about five minutes.

  1. 1What does your team do, and how many people?
  2. 2What should Claude take on?
  3. 3Which tools does it touch?
  4. 4When do you want it working?
  5. 5Anything else we should know?

Guardrails

Try to make it misbehave.

The Monday-report job from the top of the page, given a few requests. The scope decides ahead of time what it may do, what waits for a person and what it refuses.

Pick a request to see what the agent does with it.

Remote by default

Everything happens over email, shared documents and your own tools. No discovery calls; if you want a call, ask. On-site work is rarely possible.

Projects are taken on as the schedule allows. If the timing doesn't work, you'll hear that in the first reply.

Describe a project