Demos that never graduate
The pilot impresses, then stalls without an owner, an architecture or a business case.
01 // ARCHITECTConsulting & Architecture
Know where Claude pays off. Before you scale it.
Before you roll out Claude, Claude Code or the Claude API, find out whether your data, use case, platform, security, evaluations and team can carry it. We assess 6 areas and give you a prioritized fix list.
45 minutes. No pitch deck, no sales script.
- 01
45 minutes to a discovery call
Scope the Claude use cases and systems in play. No pitch deck, no sales script.
- 02
1 week to a readout
Where the gaps are and which practice will move the needle fastest.
- 03
6 areas scored on one rubric
Every score comes with the evidence behind it, not an opinion.
The problem: the scaling gap
Starting is easy. Scaling is where AI programs stall.
A Claude pilot is quick to start. Knowing what comes next is harder. 4 patterns that stall AI programs.
Seats without lift
Licenses roll out, but usage clusters in a few power users. No playbooks, no champions, no measured outcomes.
Security says not yet
Data classification, access scopes and audit needs surface late, after teams have built on assumptions.
A shadow stack
Every team wires up its own prompts, keys and connectors. Spend climbs, quality varies, nothing is reusable.
Why you need a partner
Claude is 5 layers of decisions. Each one depends on the others.
A wrong call in one layer forces rework in the rest. We assess all 5 together and hand you one plan.
01
Claude apps
Team and Enterprise plansProjectsConnectorsSSO and provisioningAdmin and usage controls
Risk without a plan
Over-broad connector permissions. Rollout with no role-based playbooks.
02
Claude Code
Terminal, IDE and webCI/CD and GitHubSubagentsHooks and skillsMCP serversManaged settings
Risk without a plan
Unsafe dev-machine permissions. No repo standards. Unmanaged spend.
03
Claude API and Agent SDK
Tool useMCPPrompt cachingBatchFiles and citationsExtended thinking
Risk without a plan
No evals. Runaway token costs. Agents with more autonomy than controls.
04
Cloud and procurement
Anthropic APIAmazon BedrockGoogle Cloud Vertex AIMicrosoft Foundry
Risk without a plan
Region, residency and commit-spend decisions made after the build.
05
Governance and people
Data handling and DLPAudit and loggingModel risk reviewTraining and championsSuccess metrics
Risk without a plan
Policy written after the pilot. Adoption never measured.
Strategy firms hand you a plan. Dev shops write the code. Mach carries one plan across all 5 layers.
What we do
Scope of the work.
6 areas, scored on one rubric, with the evidence behind every score.
01
Data readiness
Where the data lives, who owns it, how clean it is, and whether Claude can reach it safely through approved connectors and MCP servers.
02
Use case clarity
Whether each Claude use case has a measurable outcome, a real user and a named owner.
03
Platform review
Your cloud path, Claude Code environments, CI/CD and integration capacity measured against what your roadmap needs.
04
Security and governance
Access controls, data handling, permissions, model risk and policy gaps, reviewed with your team.
05
Evaluation maturity
Whether you can measure Claude output quality and token spend before and after every change.
06
Team and skills
Who can build and run Claude today, and where you need champions, training or partners.
Interactive
Take the self-check.
6 questions, 1 per area. Score yourself and see where you stand before we talk.
Data
Can Claude reach clean, owned data through approved connectors?
Use case
Does each Claude use case have a measurable outcome and a named owner?
Platform
Can you deploy and monitor Claude workloads, including Claude Code, in your environments?
Security
Has security reviewed how Claude touches customer data and source code?
Evals
Do you score Claude output quality and track token spend on every change?
Team
Do you have champions and training to take adoption past the first team?
Example answers shown. Change them to score yourself. Nothing is stored or sent.
Deliverables
What you walk away with.
Everything is yours to keep, whether you build with us or on your own.
01PDF
Readiness scorecard
A score for each of the 6 areas with the evidence behind it.
02List
Prioritized fix list
The gaps to close, ordered by impact on your first Claude use case.
03Workshop
Readout session
A walkthrough with leadership and the teams who will do the work.
04Diagram
Current-state architecture
How data, systems and Claude surfaces connect today, drawn on one page.
05Checklist
Claude Code and security baseline
Permissions, managed settings and repo standards your security team can review.
06Plan
First-90-days plan
What to do next, whether you build with us or on your own.
How it works
4 steps, one team.
Senior operators work alongside your team, so every score is backed by evidence, not opinion.
01
Scope
Pick the Claude use cases and systems in scope and line up interviews.
02
Assess
Interviews, system walkthroughs and data sampling across all 6 areas, with small hands-on Claude Code and API tests where they help.
03
Score
Score each area against a consistent rubric and document the evidence.
04
Read out
Present the scorecard and fix list, then agree on next steps.
Powered by our platform CloudTeams™
Context stays on one record, not in a deck
The Claude readiness assessment runs on the CloudTeams™ Platform, the AI-powered platform we built for firms that sell expertise. Mach is its first customer.
- Contacts, notes and tasks from discovery stay on one record
- A read-only AI assistant answers questions across it, so nothing is re-explained
- One team carries the work from readout to roadmap
FAQ
Questions about the Claude readiness assessment
Straight answers. Still curious? Ask us on a free call.
Do we need to be a Claude customer already?
No. The assessment works whether you are evaluating Claude, running a pilot or already rolling it out. We start from where you are.
Which parts of Claude are in scope?
Claude apps, Claude Code, and the Claude API and Agent SDK, plus the cloud path you buy through: the Anthropic API, Amazon Bedrock, Google Cloud Vertex AI or Microsoft Foundry.
How long does the assessment take?
Most assessments run a few weeks depending on the number of systems and use cases in scope. We confirm the exact timeline on the first call.
Is this a vendor evaluation?
No. We assess your organization, data and platforms against what your Claude plans require. This assessment does not compare vendors.
Who owns what you produce?
You do. Everything is yours to keep, whether you build with us or on your own.
Claude and Claude Code are products of Anthropic, PBC. The Anthropic logo is a trademark of Anthropic, PBC. Mach Advisory™ is an independent firm. Product capabilities and availability change frequently, so we confirm current details with you at scoping. The scorecard shown is illustrative and is not client data.
Project inquiry
Tell us about your project.
Tell us where you are and what you need. We will tell you honestly whether a Claude readiness assessment is the right next step.
- 01Tell us where you are headedA two-minute form. Share the outcome you want and any constraints.
- 0245-minute discovery callWe listen first. No pitch deck, no sales script.
- 03Your readout within one weekWhere the gaps are and which practice will move the needle fastest.
First conversation freeSenior team, not a sales repMutual NDA on request
Ready to choose a time? Schedule your free consultation →
Project inquiry // 2 minutes
Tell us about a Claude readiness assessment
Sending this form requests a follow-up; it does not reserve a meeting time. Prefer a new tab? Open the inquiry form