How long does a TPA take?
Typically four to eight weeks, depending on the size of the business and how many of the 20 domains are in scope. The first week is selection and access, then we run the analysis, then we write up the roadmap.
A complete map of how work actually flows across your organization, scored for AI opportunity, data readiness, and sequence dependency. The signature diagnostic inside our AI Implementation Programme, run before any AI tool is recommended.
20
H / M / L
1
Before
A Total Process Analysis is a complete map of how work actually flows across your organization. We score every relevant domain for AI opportunity, measure data readiness per function, and surface the dependencies between functions so implementation is sequenced safely. The deliverable is a roadmap, not a slide deck.
The technology is rarely the problem. The problem is choosing a function without checking whether the data is ready, whether the process is stable, or whether another function has to change first. A TPA answers three questions before a tool is bought: where to start, what to skip for now, and what will block adoption.
The framework covers twenty business domains. Each domain is selectable per engagement, because a small startup does not need the same scope as a vertically integrated manufacturer.
Decision rights, reporting, and oversight of execution.
Market fit, pricing, and launch preparedness.
Signals on competitors, customers, and pipeline movement.
Demand generation and the path to first contact.
Pipeline, forecasting, and the discipline of the sales motion.
Onboarding, adoption, and expansion inside the installed base.
Supplier relations, qualifications, and inbound material flow.
Scheduling, capacity, and the flow from order to output.
Day-to-day output against the measurements that matter.
In-line checks, release decisions, and non-conformance handling.
Systems, documentation, and audit readiness.
Risk management, incidents, and environmental compliance.
Submissions, market approvals, and post-market obligations.
Project pipeline, stage gates, and technical risk.
Warehousing, distribution, and customer delivery.
Planning, reporting, and the numbers the board reviews.
Hiring, capability, and the people side of execution.
Systems, integrations, and the data foundation AI depends on.
Patents, trademarks, and protection of commercial position.
Strategy execution, cross-functional coordination, priorities.
Not every engagement covers all 20. Selection depends on company type, industry, and the maturity of each function.
The programme is grounded in Lean, Six Sigma, Theory of Constraints, and field experience with AI adoption. It keeps the analysis honest when the temptation is to jump to tools.
Most of the outcome is decided in a few places. Optimizing anything else is motion without progress.
A busy function is not a productive one. The baseline is what came out the other end, not what was scheduled.
The documented process is a theory. We work from what actually happens on a Tuesday night.
Automating a broken process just makes it fail faster. The process gets stable first, then AI goes on top.
Every relevant domain mapped as it actually runs, with AI opportunity rated High, Medium, or Low.
A per-function view of what data exists, where it lives, and whether it is fit to feed AI.
Where changes in one function will block or unlock changes in another. The sequence matters.
A prioritized plan with measurable milestones. What starts first, what waits, and why.
A clear read on where AI fits, and the functions where it is premature or a distraction today.
Small to medium life science and medtech companies in commercialization phase, where leadership has decided AI belongs somewhere in the business but has not yet settled where. It is not the right engagement for teams wanting a quick AI demo.
Practical answers to what gets asked before a TPA engagement is scoped.
Typically four to eight weeks, depending on the size of the business and how many of the 20 domains are in scope. The first week is selection and access, then we run the analysis, then we write up the roadmap.
When the question is already scoped to a single process, or when leadership wants a fast AI demo rather than a diagnosis. A narrower engagement is a better fit. A TPA is the right choice when the decision is where AI belongs across the business, not whether one specific tool is worth trying.
TPA is the whole-business diagnostic. AI Process Mapping is a narrower engagement that picks one process and implements AI inside it. Both sit inside the AI Implementation Programme. Many teams start with a TPA and then commission an AI Process Mapping engagement for the first priority it surfaces.
No. Which domains are in scope depends on company type, industry, and the maturity of each function. A small startup in early commercialization is scoped differently than a vertically integrated manufacturer. The selection is part of the first week.
Thirty minutes. You describe where you stand. We say directly whether a TPA is the right engagement for you, or whether a narrower one fits better.