AI readiness and workflow assessment
A scoped assessment before you build anything
A fixed-scope assessment that tells you where AI fits in your document-heavy work, where it doesn’t, and what a first pilot should cost. You get a baseline you can measure against and a recommendation you can defend, including “don’t build” when that is the honest answer.
Request a Free ConsultationA fixed fee for the assessment is quoted after the consultation.
What you get
- Inventory of 1 to 3 candidate document-heavy workflows.
- Data and document source review: formats, systems, volume, quality.
- Privacy, security and data-handling constraint map.
- Fit scoring on repetitiveness, volume, text-intensity, risk and review burden.
- Baseline metric definition: time-to-answer, review time per document, error rate, escalation rate.
- A recommendation with the evidence behind it, including “don’t build” when that is the answer.
- A fixed-price pilot proposal for the highest-value workflow.
Two ways in
One assessment, two starting points. Both end in the same seven deliverables; the teardown adds a measured look at the system you already have.
Greenfield readiness
1.5 to 2 weeks
You have document-heavy work and want to know where AI fits, and where it doesn’t. You get the seven deliverables, ending in a recommendation and a fixed-price pilot proposal for the highest-value workflow.
Existing-prototype teardown
2 to 3 weeks
You already built or bought a RAG, assistant or extraction prototype your team doesn’t trust. You get the same seven deliverables plus a configuration-and-measurement sweep of the existing system: measured effect sizes and an explicit fix, rebuild or walk-away verdict.
What the written deliverable looks like
Every assessment ends in a written report with the same six sections. This is the outline, not a sample. The figures in each section come from your own workflows.
Workflow inventory
The one to three workflows examined: who does each today, what it takes in time and review, and where it breaks.
Constraint map
Privacy, security and data-handling limits any build has to respect, each traced to its source: a policy, a contract or a regulation.
Fit scores
Each workflow scored on repetitiveness, volume, text-intensity, risk and review burden, with the reasoning shown rather than a bare number.
Baseline metrics and how they will be measured
The figures a pilot would be judged against (time-to-answer, review time per document, error rate, escalation rate), where each comes from, and how it is collected before anything is built.
Recommendation
Build, don’t build, or fix what you have, with the evidence behind the verdict and the main risks named.
Pilot proposal with scope, milestones and price
A fixed-price proposal for the highest-value workflow, with a stop option after each milestone. If the recommendation is “don’t build”, this section says what to do instead.
What I’ll need from you
- Interviews with the people who do the work today.
- The documents and systems involved, or a representative sample of them.
- Current volumes and any error or turnaround figures you already track.
- An IT or security contact for the constraint map.
- For a teardown: access to the prototype, its configuration, and any evaluation data it was tested with.
Who this is for
- Administrators, compliance and operations teams at small and mid-sized US companies working through plans, policies, claims and other documents.
- Teams sitting on a RAG, assistant or extraction prototype they cannot trust and need a straight verdict on.
- Buyers who need a build-or-don’t-build decision they can defend to a board or an auditor.
Who it’s not for
- Teams looking for a rubber stamp on a decision already made.
- Anyone who needs 24/7 managed operations, or medical or clinical advice.
- Work where success metrics cannot be defined.
Start with the free consultation
Describe the workflow and what goes wrong in it through the contact form. If the assessment is not the right next step, you’ll hear that too.
Request a Free Consultation