Tools and services

OtterFlow

We build OtterFlow, our workflow builder. Each step of a delivery workflow is assigned to a model and run against a repository, with approval, review and gate steps.

A workflow is drawn as steps on a canvas, and each step names the model that runs it. A runner executes the workflow against a git repository through coding agents. Approval steps wait for a person, and a failed review stops the run.

Ink drawing of nested rounded squares on pale paper, each holding a solid black block and joined to the next by a line

What this covers

  • Workflow design on a drag-and-drop canvas, with a model assigned to each step
  • Runs against a git repository, with each code change on its own branch
  • Approval steps that pause the run until a person decides
  • Review steps that grade output against a rubric and stop the run on a fail
  • Gate steps that ask a yes or no question before the run continues
  • Provider keys held on the runner host, never in the workflow or the repository

Typical engagements

  • A delivery workflow for a defined build, inside a solution delivery engagement
  • A review and approval workflow for changes to an existing repository
  • Handover of the workflows used on an engagement, with the output of each step

How an engagement runs

  1. 01

    Enquiry

    You describe what has to change. We reply in writing with questions.

  2. 02

    Scoping

    One conversation to agree the problem, the people affected and how the result will be accepted.

  3. 03

    Proposal

    A written scope, acceptance criteria, a price and a start date.

  4. 04

    Delivery

    We lead the work. Decisions, risks and changes are recorded as they happen.

  5. 05

    Acceptance

    The result is checked against the criteria agreed at the start.

  6. 06

    Handover

    Documents, access and records pass to your organisation.

  7. 07

    Close

    A short written close-out, and a support retainer if you want one.

Who this suits

  • Organisations that commission a build from OtterBlock and want each step of the delivery recorded and approved.

  • Technology teams that use coding agents and need approval and review points before a change is accepted.

We use OtterFlow in our own delivery work, and we offer it to clients as part of a solution delivery engagement.

Works with: Claude Code, Codex, Cursor and Grok coding agents, on any git repository.

Tell us what has to be built.

Contact