Claude Adoption · Anti-consulting
Install Claude into your team. Not a workshop — an environment.
CLAUDE.md, custom Skills, sub-agents, MCP servers, hooks, slash commands — set up and committed to your repos. The team uses Claude by default, not by intention.
Anti-consulting
Other firms run workshops. We commit code to your repo.
Workshops change behaviour for two weeks. Environments change it permanently. The deliverable is the difference.
"Here is how to use Claude."
2-day workshop, slide deck, recording. Team is excited for a week, slowly drifts back. ROI measured in goodwill, not in PRs shipped.
"Here is your team using Claude — already."
CLAUDE.md committed. Skills installed. MCP servers connected to Slack / GitHub / DB. PR review semi-automated. Onboarding for a new engineer: 2 weeks → 3 days.
Common situations
"We use Claude. We are not sure it is making us faster."
Adoption is for teams that have already paid the licence and have nothing structural to show for it.
Only some engineers use Claude. Most stop at "it's faster to write it myself."
The friction is not the model — it is the missing CLAUDE.md, the missing MCP connections, the missing Skills.You have heard about Skills, sub-agents, MCP. You do not have time to figure out which apply to your codebase.
2–4 weeks, we install the ones that fit and explain why the others do not.Slack / GitHub / DB are not connected to Claude. Every prompt re-explains the project context.
MCP servers solve this in days, not quarters.Before → After
What changes in 2–4 weeks.
Adoption is measured at the team level, not the individual. The change shows in onboarding time, PR review time, and weekly Claude usage rate.
- Only some engineers use AI; the rest are unconvinced.
- Stuck at "meh, faster to write it myself."
- CLAUDE.md / Skills / MCP — heard of, not understood.
- Slack / GitHub / DB unconnected — every prompt is from scratch.
- ROI is unmeasurable. No internal evangelist exists.
- Whole team uses Claude Code daily (90%+ weekly usage).
- Custom CLAUDE.md, Skills, sub-agents running.
- Slack / GitHub / DB connected via MCP — Claude has context.
- PR reviews / tests / research semi-automated.
- Onboarding for new engineers: 2 weeks → 3 days.
Deliverables
Six artefacts. Committed to your repo, yours to evolve.
The Adoption Sprint ships these — not as a binder, but as files in your repository. After we leave, your team modifies them like any other code.
CLAUDE.md
Project overview, tech stack, directory map, command list, conventions, do-nots, recommended workflows. The brain Claude reads before every task.
Skills
Custom-built shortcuts for your team's recurring tasks — PR review, test generation, doc generation, schema migration drafts, etc. Versioned in your repo.
Sub-agents
Specialised Claude instances with focused prompts for specific roles — reviewer, test-writer, doc-writer, researcher. Called via slash commands.
MCP servers
Connectors to Slack, GitHub, your database, your error tracking, your project management. Claude stops making things up — it asks the source.
Hooks
Automated triggers — pre-commit checks, post-PR comments, scheduled audits. Claude shows up in your workflow without anyone summoning it.
Slash Commands
Team-shared shortcuts for common operations. `/review`, `/test`, `/migrate`, `/onboard` — whatever your team needs, made consistent.
4 tiers
Free at the entry. Most teams jump straight to Sprint.
Adoption Score is the entry. Workshop is for teams that need buy-in first. Sprint is the main product. Lite is for single-repo teams.
Adoption Score
2-min form → AI maturity score (0–100) + quick wins + recommended plan + ROI estimate. Email-delivered.
Workshop
2-hour lecture + 2-hour pair programming. For teams that need internal buy-in before installation.
Adoption Lite
1 repository, 1 team. CLAUDE.md + Skills + 1 MCP server + Slack support during install.
Adoption Sprint
Full installation: CLAUDE.md, Skills, Sub-agents, MCP servers, Hooks, Slash Commands. 2–4 weeks. The main product.
Why this works
The numbers behind 10× productivity.
We are not theorising about adoption. We design, build, and run our own products AI-natively — this is how we work, not just what we sell.
Tsunagu, Dr. Unco, and L-career — live products we operate ourselves. Fortress, our next one, is in active development.
Teams that reach Mature on our Adoption Score report 2.5× ROI on engineering hours. Leading stage typically reports 4×+ on focused tasks.
English, Japanese, Chinese, Indonesian — at full depth, not translated slides. We work in the languages ASEAN teams actually use.
What you can rely on
Five rules for every Adoption engagement.
Operational rules — applied on every tier from the free Adoption Score upward.
Day-1 ownership
All artefacts — CLAUDE.md, Skills, sub-agents, MCP configs, hooks, slash commands — committed to your repository. Versioned, yours to evolve.
NDA before tech
NDA signed before any repository access, including the free Adoption Score if you submit code references. Prompts are confidential.
No vendor lock-in
Everything we install is standard Claude + MCP — you can swap providers or operate without us. No proprietary middleware.
Team-wide rollout
Sprint includes pair-programming with each engineer on the team, not just leadership. Adoption stalls when only some engineers buy in.
30-day support
Adoption Sprint includes 30 days of Slack support after delivery. Tuning, prompt iteration, "this thing started misbehaving" — all included.
FAQ
Five questions before you book a Sprint.
Specific case not here? Add it to the form's message field. Reply within one business day.
How is this different from a Claude workshop?
What is in CLAUDE.md and Skills?
What MCP servers do you install?
How is the free Adoption Score calculated?
Why do you deliver Adoption in four languages?
Free Adoption Score
2-minute form. AI maturity score by email.
No commitment, no payment, no sales call. We email a written score plus a recommended next step within 1 business day.
- NDA signed before any technical discussion (including the free Score).
- Everything we install is standard Claude + MCP — no vendor lock-in.
- If a workshop is enough for your team, we will say so.
- $0 entry
- 2–4 wk Sprint
- EN / JA / CN / ID
- 30-day support
Get my free Adoption Score
Required fields marked * · 2 minutes