MITIGON

Integrations, automations, dashboards and internal tools, built for pharma work. Start with one workflow - fixed scope, fixed price, working software.

Discuss a workflow See example scopes

Illustrative cutaway of a QC laboratory and adjoining office: a QC analyst uses LIMS at a laboratory bench, a planner works at a separate ERP desk for orders and material data, and a quality reviewer checks records at a separate review desk.

What we build

Three places pharma teams usually start

We use AI for the drafting and searching. Your team reviews and approves everything before it becomes a record.

Records

A recurring document gets retyped into a record.

We build the workflow that drafts it from the source system.

First project: one input type, one destination, your team reviews every draft.

Knowledge

Answers are buried in manuals, handover notes and resolved cases.

We build search that finds them, with references back to the source.

First project: one team, one document set.

Tools

A process runs on email and spreadsheets, or two systems that don't talk.

We build the tool or integration around it.

First project: one workflow, fixed scope.

Don't see yours? If it's pharma work that runs on documents and systems, it's worth a conversation.

Discuss a workflow

Example scopes

One workflow. A clear first scope.

These are illustrative project scopes, not completed client projects.

From an incoming request to a reviewed record

Extract agreed fields from one recurring request format. Flag missing information and let a person check the draft before it reaches the destination system.

We assess handling time, corrections and exceptions against the current process.

Timing: Agreed after reviewing scope and access
Handover: Drafting workflow, field mapping and handover notes
Price: Fixed price agreed before start

SourceEmail

Material request

Please prepare material MAT-042 for the next run.

Draft record

Material reference: MAT-042Source: incoming request
Required date: Not providedReviewer input needed

From a technical question to the relevant previous case

Search an agreed collection of technical documents and resolved cases. Show source passages and the equipment or version they relate to, where recorded.

We test real questions with an experienced team member to see whether the results help them find the right information.

Timing: Agreed after reviewing scope and access
Handover: Search tool, agreed source collection and handover notes
Price: Fixed price agreed before start

QuestionTeam member

Equipment restart

Where is the restart procedure?

Source-linked result

Restart checks

Example equipment manual · Section 4.2

“Before a restart, confirm the equipment identifier and use the procedure for the recorded revision.”

Illustrative source passage. Check the equipment and revision.

From an email chain to a shared request tracker

Build a focused tool for one request workflow. Capture the agreed fields, show who owns each request and make missing information visible.

We test the workflow with your team, from a new request to handover, including missing information and changes of owner.

Timing: Agreed after reviewing scope and access
Handover: Request tracker, agreed data export and handover notes
Price: Fixed price agreed before start

SourceEmail

Support request

Could someone pick up this equipment support request?

Request overview

Received
Triage
Assigned

Owner: Not assignedTeam input needed
Next step: Assign an owner and confirm the required information.

The systems in your workflow

Work with what you already use.

Every project starts by assessing interfaces and access around your systems, with a defined source and destination.

ERP

Orders and material data

LIMS

Samples and test results

eQMS

Deviations and quality records

Process historians

Equipment and process data

Document control

Procedures and revisions

Plus whatever else your workflow runs on.

Designed around your requirements

Keep quality in the design.

We agree the intended use, review steps and evidence with your quality team. These references inform the scope where applicable.

EU GMP Annex 11

Define system responsibilities, data checks and evidence for the intended use.

Computerised systems

21 CFR Part 11

Assess electronic record and signature requirements before choosing the workflow.

Electronic records and signatures

GAMP 5

Use risk to guide specification, testing and handover across the system lifecycle.

Risk-based lifecycle guidance

How a pilot works

A defined scope, a fixed price and a clear handover.

Scope
Check the workflow, system access and who will review the result. Agree the deliverable, price, data handling and how to judge the work.
You getAn agreed scope and acceptance criteria
Build and test
Build the agreed workflow. Test it with representative examples and your team’s feedback, including missing information and exceptions.
You getA working tool to review against the scope
Review and hand over
Work through agreed corrections. Hand over the tool, documentation and any support arrangements agreed before starting.
You getThe deliverable and its handover documentation

Not sure what to build yet? A scoped assessment can identify what to test first, or why the work should not proceed.

Bartek Baran

Founder, Mitigon

Who you’ll work with

Mitigon is a founder-led software consultancy for pharmaceutical teams.

Bartek Baran leads the work. He has built web products, robotics systems and embedded software. As co-founder and CTO of Blynksolve, he developed a web-app digital twin used in pharma manufacturing pilots.

ISPE member

Start with
one workflow.

Tell us what happens today and where it gets stuck. We’ll discuss a focused first project.