Know what to automate before you pay anyone to build it.

John maps one team's recurring work with the person who runs it, then writes down which tasks to automate, which keep a human reviewer and which should stay manual, and names the one workflow worth building first.

AI opportunity report$750Fixed price, one team
SheetO-01
ForOwners and operations leads
TimelineOne call, then the report within five working days
You getA written map of one team's work and the first workflow to build.

A report is the right first step for some teams, and a detour for others.

It fits if

  • A team spends real hours each week on repeating work: entering, checking, chasing or re-typing.
  • You suspect some of it could be automated, and nobody has had the time to work out which part.
  • You want something written that you can hand to a partner, a board or a builder.
  • You would rather spend a little to choose the right first project than a lot on the wrong one.

It does not fit if

  • You already know the workflow you want built. Go straight to a pilot.
  • You want the work done, and a recommendation would only delay it.
  • Nobody who knows the work day to day can spare an hour for the call.

How the report gets written.

  1. A short note before the call

    You say which team the report is about and send whatever you are comfortable sharing: a job description, a process note, a sample form. Nothing confidential is needed.

  2. One working call

    John walks through the team's week with the person who runs it: what comes in, what gets typed, checked or chased, how often, and what goes wrong.

  3. Each task gets a mark

    Every recurring task is marked automate, keep a reviewer or leave manual, with the reasoning written beside it. Rare cases and costly mistakes are marked to keep a person.

  4. The first workflow is named

    One workflow is chosen as the place to start, with what it would take to build, what would need review, and an illustrative estimate of the hours involved with the inputs shown.

  5. A read-through

    John goes through the report with you, answers questions, and changes anything that is wrong about how your team works.

What you receive.

Deliverable schedule: AI opportunity report
DeliverableWhat it is
The work mapThe team's recurring tasks in one table, each marked automate, keep a reviewer or leave manual, with the reason.
The first workflowThe one worth building first, the steps it covers, and what a person still checks.
An illustrative estimateHours a week the first workflow touches, calculated from the numbers you gave, with every input shown so you can change it.
What a build would needThe systems, access and example records a builder would ask for, so the next step has no surprises.

One price, agreed before work starts.

$750Fixed price, one team

One price for one team's work. It is agreed in writing before the call, and it does not change with what the report finds.

Included

  • One working call of up to an hour with the person who runs the team
  • The written report, delivered within five working days of that call
  • A thirty-minute read-through of the report with John

Not included

  • Building or installing anything. The report tells you what to build and what to leave alone
  • More than one team or department. A second team is a second report
  • Choosing or buying software on your behalf

Boundaries.

  • Outcomes

    The report is a recommendation. Nothing about savings or results is promised, and the estimate is illustrative.

  • Your data

    The report is written from the call and from what you choose to send. No access to your systems is needed.

  • No obligation

    The report is yours to use with any builder, including your own staff. Soxoa building it is one option, not a condition.

  • Honest result

    If the right answer is to change nothing yet, the report says so and explains why.

Questions people ask first.

Who needs to be on the call?

The person who runs the team day to day. An owner alone often cannot describe the steps closely enough, so bring whoever knows where the hours go.

How long is the report?

A few pages. It is written to be read in one sitting and acted on, with the table of tasks first.

Is the price credited if we go on to a build?

No. The report stands on its own, and a build is scoped and priced separately.

What if we already use AI tools?

Say which ones on the call. The report works with the tools your organization has already approved.

Start with the map.

Thirty minutes with John. Say which team you have in mind, and you will hear whether a report would help or whether you already know enough to build.