One practice. Four ways to apply it.

Scope and data-security posture are covered explicitly in the session before any work begins. The short version: the architecture determines what data touches which system, and that is a design decision made with you, not imposed on you.

For retrieval-augmented systems, your documents can be indexed and queried entirely within infrastructure you control -- nothing needs to leave your environment to a third-party service. For inference, the tradeoffs between on-premises models and hosted API calls are real, and the right answer depends on your data classification and regulatory requirements. I have built both. The session's "Guardrails and reality check" segment covers this directly.

The governance approach I apply comes from building Verbatim -- a production Medicare/Medicaid system where citation provenance and source integrity are compliance requirements. That is a higher data-integrity bar than most industrial pilots will need, and it shapes how I approach every system by default.

No -- and anyone who quotes you a specific ROI number before seeing your operation and your data is inventing it. The evidence does not support that kind of upfront claim.

What I can say: the value AI delivers in industrial and quality-critical operations is typically in capability, not in a single measurable line item. Retrieval over your own documents means your team gets accurate answers from your own material instead of searching manually or guessing. Automated document generation means repetitive, high-stakes paperwork is produced correctly and fast. Monitoring agents mean a change in a critical source gets flagged without a person watching the feed. These are real capabilities, and experienced operators recognize their value.

Every engagement is scoped with acceptance criteria agreed upfront. A system either meets them or it does not. The PMP discipline I bring to project management means a pilot has a finish line and an accountable owner -- which is the single most common reason AI pilots stall.

Two things that are hard to find together. First: I have shipped production AI inside a real, regulated, technical business -- not as a project for a client, but as my own product with paying customers who depend on its accuracy. Verbatim is a live RAG SaaS for Medicare/Medicaid billing with citation provenance, source hashing, and an SME evaluation loop. That is not a demo. It is a working system I am responsible for keeping accurate.

Second: I have 20+ years engineering in environments that do not forgive errors -- food processing, pharmaceutical manufacturing, hospital operating rooms, lithium-battery dry rooms -- across 100+ facilities. I speak the operational language of the buyers I work with from the inside, not from a slide deck about their industry.

Most AI consultants have one of those. Almost nobody has both.

No. This is explicit by design. The AI Opportunity Assessment snapshot and roadmap are yours. You can build with me, hand the roadmap to your internal team, or take it to another developer. No proprietary framework, no license, no dependency on me to act on it.

The reason to say this out loud: a buyer in a regulated or industrial environment who has been burned by vendor lock-in before should not have to guess. The deliverable is a document you own. What you do with it is your decision.

Regulated environments are the primary setting for this practice, not an edge case. The governance architecture I use -- citation provenance, source versioning, defined review gates, human checkpoints before controlled documents -- was developed because Verbatim required it. Medicare billing is a regulated domain where a wrong answer that cannot be traced to a source is a compliance failure.

For GMP, FDA 21 CFR Part 11, or similar environments: the conversation starts with where AI outputs enter your quality system and what review and approval structure those outputs need to carry. The session's readiness scorecard includes a risk/compliance dimension specifically for this. Systems that touch controlled documents are architected with traceability first, not retrofitted later.

It depends on the engagement type. An Assessment runs 2-3 weeks: intake, the session itself, scorecard analysis, and the written deliverable. A Build Sprint runs on a scoped project timeline with defined milestones and a clear acceptance test -- you know what done looks like before we start. A Fractional Advisor retainer has a defined monthly cadence: roadmap review, active build oversight, and evaluation runs on live systems.

What does not vary: every engagement starts with a written scope, defined acceptance criteria, and a named finish line. That is the PMP discipline applied to AI adoption, and it is why the engagements that go sideways at other firms do not here.

The practice is strongest in regulated, quality-critical, and documentation-intensive environments -- manufacturing, food processing, pharma, professional services, and similar. These are the settings where the governance architecture is most directly relevant and the credibility from 20+ years of industrial engineering carries the most weight.

That said, the method -- scope it, build it traceable, evaluate it, manage it to a finish line -- applies anywhere a pilot needs to reach production and not die in a conference room. If you are unsure whether there is a fit, the free 15-minute fit check is exactly the right place to find out.