AI Readiness Assessment

Before you invest in tools and training, find out where your team actually stands. Our assessment evaluates tooling, codebase health, workflow maturity, culture, and compliance, and produces a prioritized rollout plan you can act on.

Schedule Your Assessment See the Self-Check

What We Evaluate

Four dimensions of readiness

  1. Tooling
    Editors, permissions, integrations
  2. Codebase
    Type coverage, tests, structure
  3. Workflow
    Tickets, reviews, sprint cadence
  4. Culture
    Openness, skeptics, leadership buy-in

How We Assess

What the assessment covers

  1. Codebase Audit
    A direct review of your repository: type coverage, test health, build performance, and the architectural patterns that interact with agentic workflows. We work with read-only access; no code leaves your environment.
  2. Workflow Audit
    How tickets become code, where reviews happen, where time is lost, and which parts of your existing workflow will accelerate (or fight) agentic adoption.
  3. Tooling Survey
    A short survey of every engineer covering current tools, pain points, and openness to change. We anonymize and aggregate before reporting back.
  4. Leadership Conversations
    Confidential conversations with engineering leads, product managers, and executives to understand strategic intent, budget realities, and political constraints.
  5. Risk & Compliance Review
    A review of where code lives, what data is sensitive, and which agentic tools are compatible with your privacy, compliance, and IP requirements.
  6. Phased Rollout Plan
    A written report with a prioritized rollout sequence, scoped by impact and effort. Each phase has clear deliverables, exit criteria, and a recommendation on whether to do it solo or with our help.

Self-Check

Ten signals that predict a successful rollout

Walk through these with your engineering leads. The more you can answer yes to, the faster a rollout will compound. The full assessment covers each in depth and produces a written plan.

  1. Tooling
    Engineers can install IDE extensions and CLI tools without IT escalation.
  2. Tooling
    The team is on a modern editor (Cursor, VS Code, JetBrains), not a locked-down environment.
  3. Codebase
    TypeScript covers a meaningful share (>50%) of the codebase, or the team is open to migrating.
  4. Codebase
    The repository has a working test suite the team trusts.
  5. Workflow
    Work is tracked in tickets (Linear, Jira, GitHub Issues) with reasonably specific acceptance criteria.
  6. Workflow
    Pull requests are reviewed before merge, and there is a real review culture.
  7. Culture
    Engineers are open to changing their daily workflow if the evidence supports it.
  8. Culture
    Leadership is willing to invest in measurement and follow-through, not just a one-off pilot.
  9. Compliance
    You have a working understanding of where your code can and cannot be sent (privacy, compliance, IP).
  10. Capacity
    The team can afford 2–4 weeks of partial focus on rollout without missing a release.

The full assessment covers these signals in depth, plus the workflow audit, leadership conversations, and risk review. You walk away with a written report and a phased plan.

Tools & frameworks evaluated

  • Biome / Ultracite
  • Claude Code
  • Cursor
  • Firebase
  • GitHub
  • Linear
  • Linear Cloud Agents
  • Shadcn/ui
  • Supabase
  • TanStack
  • TypeScript
  • Vite
  • Vitest

How We Work

A typical assessment, step by step

A standard assessment runs two to four weeks and ends with a written report and a 60-minute walk-through call.

  1. Discovery & Scoping
    A 30-minute call to understand goals, scope, and constraints. We confirm fit, agree on access requirements, and lock the timeline.
  2. Codebase & Workflow Audit
    Read-only repository review and live walkthrough sessions with engineering leads. We document what we see and where the highest-leverage opportunities sit.
  3. Engineer Survey & Interviews
    Anonymous survey to every engineer plus brief 1:1 calls with key contributors. We surface what the team already believes about agentic tools and what they actually need to ship faster.
  4. Leadership Alignment
    Confidential conversations with engineering leads, product managers, and execs to align strategic intent with what the engineering team actually needs to succeed.
  5. Report & Recommendations
    A written report covering current readiness, risks, and a phased rollout plan. Includes specific tool recommendations, training priorities, and ROI projections.
  6. Walk-Through & Q&A
    A 60-minute call to walk leadership and engineering leads through the report, answer questions, and align on next steps. The report becomes the team's own document afterward.

Common questions

  1. How is this different from a workshop?
    A workshop is a one-day intro. An assessment is a multi-week diagnostic that produces a written report and rollout plan. Most teams do both: the workshop builds intuition, and the assessment produces the plan.
  2. Do you need access to our private code?
    Yes, but read-only. We sign mutual NDAs before the audit begins, and no code leaves your environment. We document patterns and signals, not snippets.
  3. Will the report tell us not to adopt agentic AI?
    If that is the right answer, yes. Our incentive is to be right, not to sell.
  4. Can we use the report internally and skip further engagement?
    Absolutely. The report is yours to execute on.
  5. How much does the assessment cost?
    Scoped after the discovery call based on team size and depth of audit.