Build it with your team, in one day.
John and the people who do the work pick one real workflow, mark up what should change, and build a working automation on approved examples of your own work before the day ends.
This day works for some teams and wastes a day for others.
It fits if
- Your team already has at least one AI tool the organization has approved them to use.
- Someone in the room can approve a change to how the work is done, that day.
- There is a real, repeating workflow with real volume behind it, and you can bring approved examples of it.
- The people who do the work will be at the table, not only the people who manage it.
It does not fit if
- Nothing is approved and nobody is allowed to decide. The day turns into a policy discussion.
- You want a talk or an awareness session for a large audience. This is a working day at a table.
- No example of the work can be used in any form.
- You are expecting the backlog cleared in a day. It is one workflow, built properly.
What happens on the day.
A short preparation call, first
Before anything is booked, we pick the workflow, agree which examples are approved to use, and confirm the tools and access your team already has.
Map the work
Everyone who touches the workflow walks through it step by step, including the steps nobody documented.
Mark it up together
Each step is marked automate, keep as a human step, or leave manual, with the reasoning written beside the mark.
Build the one worth building
Your team builds it, with John at the table, on approved examples of your own work.
Break it on the hard cases
The team feeds it the messy examples. Where it fails, we fix it, put a person in front of it, or mark that path to stay manual.
Write it down and name an owner
The day ends with operating notes, a named owner on your side, and a ranked list of what is worth building next.
What leaves the room with you.
| Deliverable | What it is |
|---|---|
| The working build | The automation from the day, running on your approved examples, in the tools you already have. |
| Operating notes | How it runs, what to check, what to do when it fails, and how to change it. |
| The marked-up map | The workflow as drawn, marked automate, keep or leave manual, with the reasoning. |
| What to build next | A ranked list of the remaining candidates and what each would take. |
One price, agreed before work starts.
$3,500Fixed price for the day
One price for the day, agreed in writing before the date is booked. It covers the preparation call and the day itself, remote or on site in Northern California.
Included
- A preparation call to pick the workflow and agree the approved examples
- One working day with John and the people who do the work
- The working build, the operating notes, the marked-up workflow map and a ranked list of what to build next
Not included
- Travel outside Northern California, which is quoted separately when the day is on site
- Software licenses. The build runs on tools your organization has already approved
- Support after the day, which is a separate conversation and never assumed
Boundaries.
- Outcomes
Nothing about results is promised. The day ends with either a working build or a written reason it was the wrong thing to build.
- Your data
Data handling is agreed before any real records are shared. Bring approved examples only.
- Your tools
The build runs on software your organization has already approved. Soxoa does not resell tools.
- After the day
The build is yours to run. Support afterwards is a separate conversation.
Questions people ask first.
Who should be in the room?
The people who do the work, plus someone who can approve a change to it. If the person who can decide cannot attend, move the date.
On site or remote?
Either. On site in Northern California is included in the price. Remote works well when the team is already distributed.
Do we need to buy software first?
No, but your team needs at least one AI tool the organization has already approved them to use.
What if the build does not work by the end of the day?
Then you leave with a written reason and the marked-up map, which is usually what stops the wrong project from being funded.
Bring one workflow. We will build it.
Thirty minutes with John. Describe the workflow that eats the most time, and you will hear whether a day would fix it and what he would leave alone.