Most companies have no idea what their AI is actually doing to them. The AI Architecture Audit measures it across seven dimensions, scores the integrity of every deployment against the load it carries, and produces the decision document and the 12-month plan.
The Execution domain reads against Bain's decision-effectiveness research. The Financial domain loads AI ROI net of supervision and rework against McKinsey's State of AI findings. The Talent domain applies Smart's Topgrading discipline. The compliance read carries the EU AI Act Article 4 obligation that did not move when the May 2026 Digital Omnibus deferred the high-risk timeline. Every methodology reference is named and verifiable.
Four situations most leadership teams recognize. The pattern beneath them is the same: AI gets adopted tool by tool, and no one holds the cross-cutting view of what it's doing to the business.
A $30M company's board asks the CEO for an AI strategy at the next meeting. The CEO has six tools across four departments and no single view of what any of them is doing to the business. The audit produces the scored diagnostic, the per-deployment decision document, and the board-ready language — so the CEO walks in with an architecture, not a list of subscriptions.
A $12M services firm reports AI-driven savings to its lenders. The CFO has never loaded the supervision time, the rework, or the per-seat price trajectory against the claimed gain. The audit runs that accounting deployment by deployment and separates the net-positive initiatives from the ones that are net-negative once senior review time is counted.
A $60M company expects to run a sale process within eighteen months. Its most valuable workflows depend on AI, but the vendor contracts have never been reviewed for assignability, the prompts and tuned models have unclear IP ownership, and the data rights may not convey to a buyer. The audit surfaces the transfer gaps a Quality-of-Earnings team will probe — before the buyer's diligence does.
A founder-led $8M company runs faster than ever on AI, and the founder is the prompt engineer, the quality-control gate, and the only person who knows which outputs to trust. The audit names the bus-factor-of-one workflows and the verification load that has migrated onto the founder, and sequences the work to convert trapped value into owned, transferable capability.
The firm that sold the tool measures adoption. The firm that implemented it measures uptime. Neither measures the questions a CFO, a board, a lender, or an acquirer asks. The AI Architecture Audit exists to answer them.
No AI vendor relationships, no implementation revenue, no platform referral compensation. The findings are not steered toward any tool — independent in the structural sense, not the marketing-language sense.
Fulcrum measures; it does not deploy. The audit tells you what your AI architecture is doing and what to do about it. Building, integrating, and operating the tools is the company's work or its chosen vendors'.
The audit does not tell you which products to buy. It evaluates the deployments you already run against leverage, fragility, dependency, ROI reality, compliance posture, and transferability — and recommends continue, restructure, sunset, or expand per deployment.
The audit produces the diagnostic, the decision document, and the roadmap. Execution is the company's work.
The audit is not a substitute for legal, accounting, or regulatory counsel; it informs decisions that specific filings and transactions still require the appropriate professional advisors to execute.
Every domain anchors to named research, a named framework, or an observable behavior — not a vague best practice. Every rubric level describes an observable state, not a positive adjective: a 1, a 3, and a 5 are different things you'd see if you watched the company for a week.
Specificity is the standard. Vagueness is the failure mode.
The score measures one thing precisely: the integrity of AI deployment relative to the load it carries — not how much AI the company uses. Three deployments running cleanly, with documented prompts, defined ownership, and bounded vendor exposure, score higher than twelve deployments accumulating bus-factor risk, governance gaps, and unsupervised output drift. Adoption-percentage benchmarks measure surface usage. This measures whether the architecture holds — defensible to the CFO, the board, the attorney, the lender, and the acquirer's Quality-of-Earnings team when they read the work product.
The audit is not a ninth Fulcrum instrument. It's a transverse lens: it takes the seven dimensions Fulcrum already measures and asks what AI is doing to each one. Each domain is scored on a five-level behavioral rubric, native to the audit — never averaged across the EQI or CAM scales.
AI accelerates drafts while quietly slowing the decisions they feed — each output carries a verification loop that migrates onto senior people. Predicts whether decision throughput keeps pace or hits a verification ceiling.
Loads supervision, integration, rework, and vendor price trajectory against claimed return — exposing the "saving" that's net-negative once senior review time is counted. Predicts margin exposure from unmodeled AI cost escalation.
Tests the opposite of the usual assumption: AI deepening founder dependency, with the founder as prompt engineer and quality-control gate. The signal is a critical workflow with a bus factor of one.
The time AI was expected to give back gets absorbed into more work, with verification load concentrated on the few trusted to check output. An organizational-continuity measure — not an assessment of any individual's wellbeing.
Measures the gap between sanctioned AI policy and actual usage — shadow AI — and quantifies the share of the organization running company and customer data through tools with no contract, DPA, or audit trail.
Distinguishes AI-native judgment from AI-dependent habit and locates high-value workflows living in one or two people's undocumented prompt habits. Predicts a capability cliff when a key person leaves.
Examines whether the AI architecture can transfer in a transaction — vendor-contract assignability, IP ownership of prompts and tuned models, data rights, and the governance documentation a buyer's Q-of-E team will probe.
Within those domains, the audit inventories every deployment — sanctioned or shadow — across the same taxonomy the Capability Map and Decision Matrix use end to end:
High exposure with matching maturity: workflows documented and owned by more than one person, AI's financial contribution measured net of overhead, dependency reduced rather than deepened — an architecture that reads as enterprise-value-accretive in diligence.
AI produces the appearance of capability while concealing a weakness underneath. The apparent output is high, but it doesn't survive honest accounting — supervision and rework consume the claimed gains, or the AI substitutes for a capability the company should own.
Every engagement produces the same six deliverables. Depth is consistent at the single-tier price; companies that move into a Fulcrum tier engagement see this architecture scale.
The diagnostic. Executive summary; archetype identification with structural implications; the scored five-level rubric across all seven domains; the findings narrative; a 12-month integrity roadmap summary; and a reference into the remediation library. The document the CEO walks the board through.
A side-by-side scorecard of every current deployment, each rated on six dimensions: leverage vs. fragility, dependency concentration, vendor risk, ROI reality, compliance posture, and successor risk. Each carries a recommended action — continue, restructure, sunset, or expand.
A 12-month sequenced action plan: the specific gaps to close, the order to close them, the owner assigned to each, the success metric, and 30/60/90-day milestones. Not just what's wrong, but what to do first, who does it, and how you'll know it worked.
A structured inventory of every deployment — what it is, where it runs, who owns it, what's documented, what depends on it downstream, vendor-concentration risk, and governance posture. Also the structured data source for the AI Strategic Mirror's setup.
The operational package: a prompt-library starter, governance-framework templates, a vendor-evaluation rubric, a board AI-update template, a Topgrading-grade hiring scorecard, a usage-policy template, an EU AI Act compliance checklist, sector-specific items where they apply, customer-disclosure language, and an incident-response framework. Working documents — the compliance items are templates a company adopts with its own counsel, not legal opinions.
Kickoff, Mid-Engagement Findings Review, and Executive Readout with a Fulcrum partner.
The AI Architecture Audit comes from Fulcrum & Co. — the diagnostic practice of Ryan Erickson, who built and exited two companies, ran a 275-person organization through a revenue doubling, and has worked with 20+ founder-CEOs from pre-revenue through $800M+. It's the same practice whose leadership diagnostic took a SaaS company stalled at $50M for three years to $800M — and a trajectory toward $1.7B this year — by finding the constraint its revenue chart was hiding. The audit applies that discipline to a narrower question: whether a company's AI is creating leverage or fragility.
The audit runs 30–45 days from signed contract to Report delivery. Three 90-minute working sessions anchor it: Kickoff frames the engagement and reviews the intake; Mid-Engagement Findings Review calibrates first-pass findings against the company's reality; Executive Readout walks the bound Report and works the Decision Matrix deployment by deployment, so the team leaves with decisions rather than findings.
It runs on a structured intake of roughly 85 fields plus a defined document review — completed before Kickoff. A small set of fields is answered by both the CEO and the AI-decision owner; where their answers diverge, the gap itself is a Cultural Coherence × AI signal.
Companies whose findings warrant deeper, integrated work move into a Fulcrum tier engagement (Growth Diagnostic and above), where the AI lens runs alongside the seven leadership-diagnostic domains. The audit is the entry point; the tiers are where the work scales.
The firm that sold you a tool measures adoption; the firm that implemented it measures uptime. Neither measures what the deployment is doing to your decision velocity, margin, founder dependency, senior-team load, data exposure, talent concentration, or transferability. The audit is independent — no vendor relationships, no implementation revenue — so its recommendations aren't steered toward any product.
Structural conflict of interest. An implementer's revenue depends on the deployment continuing and expanding; the "sunset" and "restructure" calls are precisely the ones it's least able to make. Independence is the reason the recommendations can run in whichever direction the evidence points.
The leadership diagnostic measures the company's operational and leadership architecture across seven domains and eight public instruments. The audit is a transverse lens over those same domains, measuring what AI specifically is doing to each. Companies whose findings warrant deeper work move into a tier engagement, where the AI lens runs alongside the full diagnostic.
No — by design. The audit applies Fulcrum's existing methodology to AI context rather than introducing a new instrument. The maturity score is native to the audit and scored 1–5; it's never averaged with the EQI or CAM scales.
Different product, different measurement, different deliverables. CAM measures capital readiness and produces a capital architecture and execution kit. The AI Architecture Audit measures what AI is doing across seven operating domains and produces the diagnostic, decision document, and roadmap. A company can engage both.
30–45 days from signed contract to Report. It runs on a ~85-field intake plus a document review, completed before the first session. Participation centers on the CEO and the executive who owns AI decisions — CFO, COO, or a designated technology or operations lead, depending on the company. Three 90-minute working sessions anchor the engagement.
Yes. Every engagement operates under a Mutual NDA executed at signing, and the work product belongs to you. The one defined data use is the AI Strategic Mirror: if you activate it, the Capability Map populates your Mirror and nothing else — not benchmarking, not model training, not any other client's Mirror.
The audit still applies. With nothing to inventory, it shifts to governance posture, the hiring scorecards that decide whether your next hires can govern AI, a vendor-evaluation framework, and the policy and compliance scaffolding — including the EU AI Act Article 4 obligation, enforceable in August 2026 regardless of how much AI you run. Mapping where AI would create real leverage, governed from the start, is less expensive than retrofitting governance later.
Start with the free mini-scan for a fast read, or open a discovery conversation. Either way, the work product that informs those decisions is not the place to economize. Fulcrum & Co. — we measure what no one else measures.
