We are not accepting clients at this time.

Book a diagnostic Book a call

Here is what you are actually hiring.

OpFlows builds the AI that handles the work your team repeats, and then runs it. That second half is the whole business, and it is why the terms look the way they do.

  • One thing, done properly
  • Terms in writing, before the work
  • Maintenance is the product

Four things that are true of every engagement. Including the ones that cost us money.

You can check whether we do these, because you will be in the room while we do them.

  1. Hours before technology

    Nothing is proposed until the repetitive work has been mapped and ranked by hours. If the ranking says the honest answer is that none of it is worth automating yet, that is the answer you get and there is no proposal behind it.

  2. A person stays in the way

    Nothing we build moves money, signs anything or speaks to your customer without a person between it and the outcome, unless you decide otherwise for a named step. A person approves what reaches a customer, and a person supplies the numbers that are judgements. Every action is logged, so what it did and why is readable rather than guessed at.

  3. We build alongside your systems, not on a copy of them

    Your data stays in the tools you already run and stays yours. Nothing of yours moves onto a platform you would later have to buy back, and no part of the engagement depends on you migrating first.

  4. Maintenance is the product

    An API gets retired, a field gets renamed, a model changes how it reads a message, and the thing routing your jobs starts routing them into nothing. Someone has to catch that before your customer does. That is why running it is part of the engagement rather than an upsell after it, and why we say so before you sign instead of in month two.

The whole commercial relationship, on one screen.

There is no version of this you have to ask for, and no term that appears later. If something below would be a problem, it is cheaper for both of us that you find out now.

The diagnostic
Free · 60 minutes
A qualification call. No document comes out of it and nothing is owed either way.
The discovery
Priced
We interview the roles you nominate, or work from your job descriptions and task lists, and come back with a ranked map and a build order. What you pay for it comes off the build.
The build
Fixed
Fixed scope, fixed price, agreed before the first day.
Running it
Monthly
Required, not optional, and you pick one of two. Maintain keeps what we built working. Continuous adds build capacity in the month, every month. If it stopped, the automation would stop.
Tooling and model usage
At cost
AI model usage and any tooling the build needs run on accounts we hold and operate, and are billed through to you at cost — quoted before we start, never marked up. Your own systems and data stay yours.
Commitment
None
No annual minimum and no exit fee. End it and the automation winds down with it. It also means we have to be worth the monthly figure every month rather than once at signing.
Your systems and data
Yours
They stay where they are, in the tools you already pay for, under your ownership. The automation layer is the part that runs on accounts we hold and operate.

The work we turn down.

A firm that will take anything has no method, only a calendar to fill. These are the jobs we say no to.

Book a diagnostic

  • Work nobody can define

    Not work that varies — agents handle variation. Work where two people in the room would disagree about what the right answer is. There is nothing to build against yet, and that is a decision to make rather than a system to buy.

  • Work worth less than the build

    Agents moved this line and it is lower than it was, so rare work is not automatically out. It has not disappeared either: if the hours back do not clear the cost, you hear it in the discovery rather than after the invoice.

  • A process that is broken, not slow

    Automating it makes the wrong thing happen faster and more often. Fix it on paper first; it is cheaper than anything we would build.

  • Work we cannot maintain

    If a build would depend on a system we cannot get proper access to, we will not take it on. Something we cannot keep running is not something we should have sold you in the first place.

  • A date before a scope

    No go-live date is committed to before the work has been scoped. Any timeline you have seen on this site is an example plan — yours gets its own dates in writing, agreed before you sign anything.

  • Cutting your headcount for you

    We are not in that business. The repeating half of a job goes to the automation; the half that needs judgment, or a relationship, or knowing why this customer is different, stays with the person who is already good at it.

  • A wall of logos we have not earned

    OpFlows is early. We have one engagement, and the next result will be reported in the same format.

A 60-minute diagnostic, then a fixed scope. Nothing owed either way.

Book a diagnostic

Free, no pitch deck. We work out whether there is anything here worth building — including when the answer is that there is not.