Claude consulting pricing, agreed upfront.
Every engagement starts with a written scope, estimated effort, and agreed rates and billing terms. You know how the work will be charged before it begins.
Talk to a senior consultant01
Rates and billing terms agreed upfront
We agree the rates, estimated effort, and billing terms in writing before work begins. Every engagement has a named senior consultant.
02
Scope and expectations in writing before you sign
Deliverables, timeline, the named consultant, and what is out of scope, on one page you can forward to procurement.
03
Change orders, not surprise invoices
When something outside the scope surfaces, we stop, quantify it, and put the options in writing. You approve, defer, or decline.
04
The first call and the written scope are free
Thirty minutes with a senior consultant, then a scope with clear rates and billing terms. Useful even if you never hire us.
Engagements
Ten engagements. One senior consultant each.
Readiness assessment Start here
Where Claude fits, what it needs to be safe, and scopes and effort estimates for the next two engagements
Timeline
2 weeksClaude Code rollout
Repo conventions, permissions, CI gates, and two weeks of paired delivery
Timeline
4 to 6 weeksEnterprise deployment & governance
Claude Enterprise or Team with SSO, roles, policy, runbook, and a rollout plan
Timeline
3 to 5 weeksCustom agent
One production agent on the Agent SDK, with evals, checkpoints, and a runbook
Timeline
6 to 10 weeksMCP integration
One scoped MCP server for a business application, knowledge source, data platform, or internal API
Timeline
2 to 4 weeksEvals, guardrails & security review
Graded evaluation harness, red-team pass, guardrails, and a review your CISO can sign
Timeline
3 to 4 weeksWorkflow design for a business team
Three workflows built as Claude projects and templates, measured before and after
Timeline
3 weeksOptional Atlassian integration
Claude wired into JSM, Confluence, and your pipeline, with your permission schemes intact
Timeline
4 to 8 weeksTraining & enablement
Role-based, hands-on session on your own repos and workflows, plus 30 days of office hours
Timeline
1 daySenior on call
Monthly senior support with the named consultant who built it. Cancel any time.
Term
MonthlyRates and billing terms are agreed in writing. Anthropic subscription and API costs are contracted directly, and we help you size them. Travel is billed at cost when you ask us on site.
What shapes the engagement
How we estimate effort.
- ↑More systems, repos, or teams in one scope
- ↑Regulated data, formal audit evidence, or a security review as a gate
- ↑On-site days, or a timeline shorter than the one we recommend
- ↓A completed readiness assessment, because priorities and constraints are already documented
- ↓An existing Avaratak Atlassian engagement, because we already know your instance
Never on the invoice
- The discovery call, the written scope, or a second opinion on either
- Junior hours, shadowing, or "knowledge transfer" between our own people
- Account management, project coordination, or status meetings you did not ask for
- Work outside the scope. It arrives as a change order you can decline.
Let's scope your engagement.
A written scope with clear rates and billing terms a couple days after a 30-minute call.
.webp)