Skip to main content
Consulting services are offered individually based on effort. There are no standard packages, no published price tiers, and no fixed rates that apply across engagements. Every project is different, and the only accurate way to price one is to understand it first.
No pricing is published on this site. A concrete offer can only be produced after a scoping conversation — book a discovery call to get started.

​
Why there are no fixed packages

Agent builds vary too much for fixed-tier pricing to be meaningful. Two engagements with the same broad goal — say, automating an inbound support workflow — can differ significantly in complexity depending on the number of tools involved, the logic required, the state of existing integrations, and the constraints of the environment. Publishing a price list without that context would either mislead you (setting an expectation the actual scope doesn’t match) or leave money on the table by overcharging simple projects to subsidise complex ones. Neither outcome serves you. What determines effort — and therefore cost — in any engagement:
  • Scope complexity — the number of workflow branches, decision points, and edge cases the agent needs to handle
  • Tool integrations — each external system the agent reads from or writes to adds build time, testing, and ongoing maintenance surface
  • Trigger types — the number of distinct events that can start the agent and the logic needed to handle each correctly
  • Environment factors — legacy systems, undocumented APIs, compliance requirements, or constrained access can all affect what is possible and how long it takes
A narrow, well-scoped agent takes less time to build. A complex one with many moving parts takes more. The scoping conversation is how we find out which yours is.

​
How a concrete offer is produced

1

Discovery call

A focused conversation — typically 45 to 60 minutes — where we learn about your workflows, your tools, your goals, and the constraints we would need to work within. You do not need to prepare anything technical; plain-language descriptions of your processes are enough.
2

Scoping assessment

Based on what we learn, we assess the scope: what the agent would do, what it would not do, which integrations are needed, and where the edge cases are. This mirrors the approach described on the Scope & Boundaries page.
3

Written offer

We produce a written offer that specifies the scope, the deliverables, and the effort-based fee for that specific engagement. The offer is fixed to the agreed scope — costs do not change unless you approve a scope change.
There is no obligation after the discovery call. If the offer works for you, the engagement proceeds. If it does not, you leave with a clearer picture of what a build would involve — which has value in itself.

​
What is and is not included

Regardless of the specific scope agreed, every engagement includes the same core deliverables: structured discovery, a written Agent Design Document, a build and test cycle in staging, production deployment, team training, and a period of post-launch hypercare. These are described in detail on the Engagement Model page. What falls outside the engagement fee — regardless of scope — are third-party software subscriptions, ongoing maintenance beyond the hypercare window, and any changes requested after design sign-off. Those are handled as separate scoped items.

​
Ongoing support

Post-launch maintenance — monitoring, dependency updates, handling changes — is available as a separate engagement, scoped based on the complexity of the deployed agent and the level of ongoing involvement required. The terms are agreed individually, following the same effort-based model as the initial build.

​
Where to start

The right starting point is a conversation, not a price list. To get a concrete offer for your situation, book a discovery call. If you want to think through scope before that conversation, the Scope & Boundaries page explains what drives complexity and how to keep your first engagement focused.
The more clearly you can describe what the agent should do — and, just as importantly, what it should not do — the faster the scoping assessment goes and the more accurate the offer will be.