Make a clear, safer operating decision.
You will be able to quote a project without hiding usage costs, underpricing monitoring, or pretending that a living agent workflow needs no maintenance.
Good agent work is useful before it is impressive.
An agent implementation is not finished when it first replies. Policies change, sources go stale, integrations fail, conversations reveal edge cases, and channels charge for usage. Pricing has to make room for responsible operation.
Make the relationship visible.
The language that keeps the work clear.
Work through the decision in order.
Estimate the delivery work
List discovery, build, QA, client approvals, training, and launch tasks before assigning a fee.
Separate fixed from variable
Keep implementation and recurring operations distinct from provider usage or pass-through channel fees.
Define the operating cadence
Say what is reviewed, how often, who responds to issues, and what happens outside the included service.
Write the change path
Set a simple process for requests: describe, assess risk and effort, approve, then release with a record.
A realistic, bounded implementation.
An agency sells a lead-qualification workflow for a regional contractor. It quotes a setup phase for discovery, CRM configuration, conversation testing, and pilot launch.
The recurring service covers weekly exception review, monthly outcome reporting, and approved prompt or policy maintenance. Voice and message usage are shown separately with an agreed cap and notice threshold.
When the client later asks to add a new franchise, the request is scoped as a change because it adds data, users, and new rules. The agency stays honest about the responsibility it is taking on.
Use this copyable working template.
Adapt it to the client’s evidence, policy, people, and tools. Do not treat placeholders as approved instructions.
Put the operating system around the agent.
Use workspace access, reporting, tasks, and client communication records to make the managed-service work visible rather than treating it as invisible overhead.
Before you move on
- List every task required after a workflow first goes live.
- Separate fixed delivery, recurring service, and usage costs.
- Write one clear sentence for a client about overages or scope changes.
- The price includes ongoing responsibility.
- Usage is visible and capped or monitored.
- Support and review are defined.
- Changes are not silently absorbed into the original scope.
Build the operating layer around your agent.
Use the free Spacebrain workspace to keep contact context, handoffs, tasks, automation, and reporting together.