Implementation
A gap study you can stop after
Most failed ERP projects were mispriced before they started, because nobody mapped the requirements properly. We sell the mapping first, as its own piece of work, so you can see exactly what your requirement list costs before you commit to the build.
How it runs
01 — Gap study
Two to three weeks on your floor. Every requirement mapped to configure, extend or build, with a price against each line. Delivered as a document you own, whether or not you proceed.
02 — Configure and build
Core configured, the pharma layer built, historical data migrated and reconciled against your existing system.
03 — Validate and train
IQ, OQ and PQ execution, UAT with the people who will use it daily, SOPs written, operators trained on the floor.
04 — Go-live and hypercare
Parallel run, then cutover. Our team on site through the first month-end close and the first full batch cycle.
How we hold ourselves to it
Start with one line, not the plant
We would rather prove it on a single production line and expand than spend a year in design.
The gap study is yours
You pay for it, you own it, and it is useful even if you choose another vendor.
We name our dependencies
Where a capability comes from a third-party application rather than from us, we say so before you sign.
See it on your own floor.
Two hours with your production and QA leads. We walk one product end to end and show you where it lands in the system — then you decide whether a gap study is worth it.