Skip to content

See the process you actually run

From the documents you already have — in our cloud, or as an appliance on yours.

  • Improve or reimagine
  • Evidence for compliance
  • Map before you automate
SOP

order-fulfillment-sop.pdf

1. Receive customer order
2. Verify inventory availability
3. Route to fulfillment queue
Transcript

steerco-interview-transcript.txt

Process owner: Credit checks happen after pick-and-pack…

Consultant: Who approves exceptions over $50k?

Recording

process-owner-interview-01.m4a

47:12 · stakeholder interview

Policy

credit-approval-policy.docx

§§4.2 Approval thresholds
§§4.3 Escalation path
Limit missing above $50k
Workshop

discovery-workshop-notes.docx

Day 1 — Intake walkthrough
Day 2 — Exception paths
Process deck

as-is-walkthrough.pptx

order-management.thinkprior
INTAKEFULFILLFINANCESHIPReceive customer orderPick & pack itemsCredit OK?GAPApproval limit missingShip orderNo policyApproved
The problem

You can't transform a process you haven't seen.

40–60%

Of engagement time spent mapping current-state — before transformation starts.

20–100+

Sources in a typical corpus — SOPs, policies, org charts, notes, manuals.

1–2 wks

Senior time on manual mapping, billed at $200–500/hr.

Missed

Gaps and contradictions — operational and compliance risk, routinely overlooked.

Hours to a defendable current-state, not weeks of reading.

Process mining needs event logs. Most clients only have documents — and agents need the same visual as-is.

Maps in the formats leadership already expects.

Visio, Word, PDF, Miro, HTML — evidence of how work actually runs, ready for steer co and audit. No days redrawing swimlanes.

Expected deliverable formats

  • VSD (Visio)
  • Word
  • PDF
  • Miro
  • HTML
  • MD
How it works

Three steps to a current-state you can stand behind

  1. 01

    Upload the corpus

    SOPs, transcripts, policies, scans — the pile you already have.

    SOP

    order-fulfillment-sop.pdf

    Transcript

    steerco-interview-transcript.txt

    Policy

    credit-approval-policy.docx

    Drop corpus here
  2. 02

    AI produces a ~70% map

    Structured process map with Gaps flagged for analyst review — not hidden, not invented.

    order-management.thinkprior
    INTAKEFULFILLFINANCESHIPReceive customer orderPick & pack itemsCredit OK?GAPApproval limit missingShip orderNo policyApproved
  3. 03

    Analyst-in-the-Loop finishes Gaps

    Confirm the charter, fill seams, export to tools you already use.

    Analyst review queue

    Credit threshold above $50kGap
    Exception escalation pathConfirmed
On-premise

ThinkPrior, on your machine.

Same loop. The corpus stays on local volumes — never ThinkPrior cloud.

  • Docker Desktop
  • 16 GB RAM
  • 50 GB disk
  • No phone home

Your machine

Browser

Appliance

Local volumes

Your models

Request the appliance

Bring your own keys — model calls go only where you point them.

Supported doc types

The files you already have.

EN · ES · DE · FR · JA

Ingest

  • PDF
  • Word
  • Excel
  • PowerPoint
  • Images
  • Audio / transcripts
  • HTML
  • CSV / JSON

Export

  • VSD (Visio)
  • Word
  • PDF
  • Miro
  • HTML
  • MD
Free trial

Request a free trial

Request a free trial. We'll provision access. Tell us what you're trying to map — we'll follow up at your work email.

~70%

Defendable current-state from your corpus — jumpstart, not black box.

  • Jumpstart a defendable ~70% current-state map
  • You finish the last 30% with Analyst-in-the-Loop
  • No credit card. Limited seats while we gather feedback
What do you need?
Security

Client data stays yours — in our cloud or on your machine.

Built for consulting engagements where trust is the product. Run an isolated cloud engagement, or keep the corpus on a machine you control.

  • Cloud engagements

    Every cloud engagement runs in an isolated environment within Google Cloud. Client data is encrypted at rest and in transit, never shared across accounts, and never used to train models. You can permanently delete engagement data at any time.

  • On-premise appliance

    The appliance keeps the engagement corpus and blobs on local Docker volumes. ThinkPrior does not receive those documents. The process does not construct GCP clients or probe cloud metadata. You operate the machine.

  • Your models, your keys

    Bring your own keys (BYOK). On-premise does not phone home for models. You bring five endpoints — fast, reasoning, embeddings, vision, and speech. Secrets stay on the appliance disk. Routing never logs keys, prompts, or corpus.

FAQ

Common questions

Straight answers on discovery scope, corpus formats, exports, where data lives, and how we differ from prompt tools and process mining.

Bring the corpus you already have.

To our cloud, or to a machine you control. Get a visual current-state. Finish Gaps with your team — then decide what to improve.