Pricing
Scoped work, agreed in writing.
Every engagement starts with one workflow and a written scope. These tiers are implementation starting points — exact scope and fees are agreed before work begins.
Focused Workflow Pilot
starting price · implementation project
One bounded workflow with agreed success metrics — a practical first step, measured honestly.
- One bounded workflow with agreed success metrics
- Limited set of approved integrations
- Permission planning and human-review checkpoints
- Supervised rollout with your team
- Documentation and training
- 30 days of stabilization after go-live
Operational Deployment
starting price · implementation project
A connected process across approved systems — with exception handling and a clear team handoff.
- A connected process spanning approved systems
- Exception handling for cases the workflow cannot resolve
- Monitored permissions and access reviews
- Team handoff and training
- Agreed acceptance tests before sign-off
- Scope confirmed in writing before work begins
Custom AI Program
starting price · implementation project
A phased, scoped multi-workflow implementation for businesses ready to expand carefully.
- Phased, scoped multi-workflow implementation
- Each phase separately defined with acceptance criteria
- Scope and fees agreed in writing for each phase
- Baseline security and least-privilege planning in every phase
- Human-review gates designed per workflow
- Documentation and team training per phase
Exact scope and fees are agreed in writing before work begins.
Safety in every tier
Every tier includes baseline security, least-privilege permission planning, and human-review design — safety is not a premium add-on.
Pilots aren't double-charged
If a pilot continues into a larger agreed implementation, the pilot fee is credited within the total agreed in the written proposal — it is not an extra charge stacked on top.
What prices don't include
Prices are implementation starting points, not a full operating-cost bundle. Third-party model, API, hosting, and messaging costs are separate unless a written allowance explicitly includes them.
How the work actually runs
Concrete workflows, with people in the loop.
Synthetic examples — not client results. Each shows where a person reviews before anything happens.
Inquiry triage & draft follow-up
- 1New inquiry arrives in the shared inbox
- 2Relevant details extracted and summarized
- 3Draft reply prepared for review
- 4A person approves or edits before sending
Meeting preparation
- 1Upcoming meeting identified in the calendar
- 2Summary drawn from approved sources only
- 3Briefing document prepared
- 4A person reviews before it is shared
Records kept current
- 1Approved details identified in a document
- 2Suggested record updates prepared
- 3A person approves the changes
- 4Updates applied to the business system
AI can make mistakes, and providers have limitations. What is automatic — and what a person must approve — is defined per workflow before rollout.
Optional Monthly Care
Ongoing care, capped and agreed.
Both plans are optional. Scope, caps, and response expectations are set in your written agreement — no unlimited work and no guaranteed outcomes.
Managed Care
optional · billed monthly
- Capped, agreed maintenance and monitoring
- Integration care within the agreed scope
- Business-hours support
- Scope and response expectations set in your written agreement
Continuous Improvement
optional · billed monthly
- Everything in Managed Care
- Scoped improvement work and reviews within a capped monthly plan
- Larger changes separately scoped and quoted
- Third-party model, hosting, and messaging fees remain separate
Care plans are optional — not required. Third-party model, API, hosting, and messaging costs are separate unless a written allowance explicitly includes them. Exact scope and response expectations are defined in your written agreement.
Discuss your first workflow
Start with one workflow. Measure the result. Expand when it earns its place.