Skip to content

How we build

Build around real work. Test before wider use.

A useful agent needs more than a successful demo. We make the inputs, permissions, failure paths, and acceptance criteria part of the implementation.

  1. 01

    Understand the job

    Map the current work with its owner. Review representative inputs, existing software, access permissions, and the cost of getting it wrong.

    DELIVERABLE

    Workflow map + system inventory

    DECISION TO MOVE FORWARD

    Agree the outcome, exclusions, owner, and native-versus-custom recommendation.

  2. 02

    Design the boundaries

    Specify tools, source access, actions, approval gates, and the path for incomplete or hostile inputs. Decide how to test behavior before building broadly.

    DELIVERABLE

    Permission matrix + evaluation cases

    DECISION TO MOVE FORWARD

    Approve the behavior, stopping rules, and acceptance tests.

  3. 03

    Build and connect

    Implement the agent and its interface. Validate tool arguments, handle duplicate triggers, and test failed calls and partial completion in an isolated environment.

    DELIVERABLE

    Integrated system + test evidence

    DECISION TO MOVE FORWARD

    Demonstrate the agreed cases, including actions that must not happen.

  4. 04

    Release with an owner

    Begin in a sandbox or read-only mode, then reviewed actions. Broader permissions require a separate decision backed by results.

    DELIVERABLE

    Release checklist + operating runbook

    DECISION TO MOVE FORWARD

    Confirm ownership of alerts, pause controls, exceptions, and rollback where possible.

  5. 05

    Improve with evidence

    Review accepted outputs, errors, costs, and team feedback. Re-run evaluations when prompts, models, sources, or connectors change.

    DELIVERABLE

    Regression results + change record

    DECISION TO MOVE FORWARD

    Expand scope only when the evidence and responsible owner support it.

Handoff, not dependency

Know what runs.
Know who owns it.

Agree on customer-controlled accounts and infrastructure where feasible. The contract sets rights to custom work, reusable components, and third-party software. Underlying models and platforms remain licensed.

Explore agent design

The handoff inventory

  • Architecture, configuration, and deployment instructions
  • Repository access and agreed custom deliverables
  • Tests, known limitations, and evaluation examples
  • Access inventory, retention decisions, and secret ownership
  • Operating instructions, exception owner, and exit process

A useful next step

What would you put an agent to work on?

Discuss a project

Tell us what should happen, which tools are involved, and where the work gets stuck.