One workflow, operating in two weeks.

Soxoa takes one repetitive back-office workflow from mapped to operating in your environment in two weeks, tested on real examples of your own work, with a person reviewing anything that needs judgment.

Two-week workflow pilot$7,500Fixed price, one workflow
SheetO-03
ForOperations and finance leaders
TimelineTwo weeks from the day access and examples are in hand
You getOne workflow in operation, with a review path and an owner.

A pilot fits one kind of work well.

It fits if

  • The workflow repeats every week and has real volume: invoices keyed, orders re-typed, forms chased, records matched.
  • You can share real examples of it, including the awkward ones.
  • One person on your side can own it after handoff.
  • A mistake in it can be caught by a reviewer before it costs anything.

It does not fit if

  • The work is different every time, or depends on judgment nobody can write down.
  • No examples can be shared in any form.
  • You want several workflows at once. Start with one and see it run.

How the two weeks run.

  1. Map and agree the bar

    The workflow is drawn step by step, and what counts as passing is written down before any building starts.

  2. Test the options on real examples

    Approaches are tried on your own examples. What fails is recorded and dropped.

  3. Build it in your environment

    The workflow is built in the tools you already use, with access agreed in advance.

  4. Put a person where judgment is needed

    Anything uncertain goes to a named reviewer. The review path is part of the build, not an afterthought.

  5. Hand it over

    Documentation, access notes and a named owner. If the evaluation does not clear the bar, you get a written stop recommendation instead of a weak build.

What you have at the end.

Deliverable schedule: Two-week workflow pilot
DeliverableWhat it is
The workflow in operationRunning in your environment on real work, tested against the bar agreed at the start.
The review pathWho checks what, when, and what happens when the system is unsure.
DocumentationHow it runs, how to change it, and what to do when it fails.
A straight resultEither the workflow passed and is operating, or a written explanation of why it should not be automated yet.

One price, agreed before work starts.

$7,500Fixed price, one workflow

One price for one workflow, agreed in writing before work starts. It does not grow during the two weeks; anything new is written down and priced separately.

Included

  • Mapping the workflow and agreeing what passing looks like before anything is built
  • The build, tested on real examples of your own work
  • A defined human review path, documentation, and handoff to a named owner on your side

Not included

  • Software licenses and usage costs for the tools the workflow runs on
  • A second workflow. Each one is its own pilot
  • Ongoing operation after handoff, which is agreed separately if you want it

Boundaries.

  • Outcomes

    No savings or results are promised. Any estimate given beforehand is illustrative, with its inputs shown.

  • People

    The pilot takes a task off a team's plate. It is not a plan to remove anyone, and a person reviews what needs judgment.

  • Your data

    Data handling and access are agreed in writing before any real records are shared.

  • A stop is a valid result

    If the workflow does not clear the bar, the pilot ends with a written stop recommendation. The price is for the work, whichever way it ends.

Questions people ask first.

Which workflow should we pick?

One with countable volume, a named owner, examples you can share, and mistakes a reviewer can catch. John will say on the call if yours is a poor first choice.

What do you need from us?

Examples of the work, access to the systems it touches, and about an hour a few times a week from the person who owns it.

What does it cost to run afterwards?

Whatever the tools it runs on charge. Those costs are yours and are estimated before the build starts.

What if it takes longer than two weeks?

The price does not change. The scope is set so that two weeks is realistic, and anything outside it is written down as a separate piece of work.

Bring the workflow that eats the week.

Thirty minutes with John. Describe the work, and you will hear whether it suits a two-week pilot, what he would leave manual, and what he would need from you.