Our engagements

Four ways to work together

Every engagement starts with understanding the process — not with choosing a technology. We don't build agents for the sake of it. We build them when the process is clear and the alternative (a person doing it manually) is a worse use of your team's time.

The shift

What changes when an agent handles the work

Before

  • Someone checks email to classify inbound requests
  • Data entry takes 20–40 minutes every morning
  • Reports built manually every Friday afternoon
  • First-line support tickets reviewed by senior staff
  • Supplier documents filed by whoever has time
  • Errors found days later during reviews

After

  • Agent classifies and routes within seconds of receipt
  • Data extraction runs automatically on a schedule
  • Reports generated and distributed without human touch
  • Known patterns resolved without escalation
  • Documents classified and filed with structured metadata
  • Errors flagged in real time with full audit trail
Engagement types

Choose the right starting point

01

Process Audit

No commitment to build

We map a specific workflow end to end, identify where an AI agent can take over without adding risk, and deliver a written assessment. You leave with a clear picture of what's possible — whether you work with us on the build or not.

What's included

  • Two structured sessions with the team members who own the process
  • A written process map identifying decision points, exceptions, and data flows
  • An honest assessment of automation fit — including where AI would not be appropriate
  • Estimated scope and timeline for a build, if relevant

Scope note: This engagement works best when at least one person on your team can describe the process step by step, including the exceptions. If the process isn't documented and opinions differ on how it works, we'll flag that in our assessment.

02

Agent Build

Core offering

We design, develop, test, and deploy a custom agent for one specific process. Integration with your existing tools is included in the build. After launch, we remain accountable for a 30-day period — responding within 24 hours to any reported failure.

What's included

  • Process audit (included in every build engagement)
  • Agent architecture and logic design reviewed with your team before build
  • Integration with your existing tools (email, CRM, database, or API)
  • Staged testing with real data before production deployment
  • Full documentation: what the agent does, what it doesn't, how to override it
  • 30-day accountability period with 24-hour response SLA

Scope note: One agent, one process. We deliberately don't scope builds that span multiple unrelated workflows — that leads to fragile systems. If you have multiple processes to automate, we sequence them.

03

Team Integration

Alongside any build

Agents fail when the team doesn't know how to work with them. This isn't generic AI literacy training — it's specific to the agent we've built and the process it handles. Your team learns what to trust, when to override, and how to give us feedback that improves the agent over time.

What's included

  • Two structured half-day sessions with the team using the agent
  • Walkthrough of the agent's decision logic in plain language
  • Practical exercises using real edge cases from your process
  • A feedback protocol your team can use to flag issues without involving us every time
04

Maintenance & Iteration

Optional ongoing

Processes evolve. An agent built for how things work today will need tuning as your tools, team, or requirements change. Our maintenance retainer covers quarterly reviews, performance monitoring, and logic updates when something in your process shifts.

What's included

  • Monthly performance report: tasks handled, escalations, errors
  • Quarterly review session to assess whether the agent still fits the process
  • Logic updates for process changes within agreed scope
  • Priority response for production issues

Scope note: The maintenance retainer covers the agent we built together. Major re-builds due to significant process changes are scoped separately.

Not sure which engagement fits?

Describe the process you want to automate. We'll tell you honestly which engagement type makes sense — or whether this is a case where we'd recommend a different approach entirely.

Describe your process