Requirements in.
Configuration out.
Preciq® takes weeks out of configuring a business system. Your consultants' notes, documents and workshop transcripts go in. A configured system comes out, with the decisions, the evidence and a record you can prove.
Every match carries its evidence.
Each requirement maps to a real setting, with the client's own words beside it, the file and line it came from and, where captured, who said it. Nothing invented.
Where the weeks go, and where they don’t any more.
Preciq reads every transcript, note and document, and pulls out what the client actually asked for.
Each requirement is matched to the real setting in the system, with the client’s own words beside it.
When two meetings disagree, Preciq puts both quotes side by side for the consultant to settle, not three weeks later in testing.
Generate builds the configuration package, ready to load through the system’s own tooling, and Read Back confirms what is in place.
Your best people, too busy in the settings to consult.
Requirements are gathered in workshops and typed into spreadsheets. Configuration is keyed in by hand, field by field. When the deadline closes in, the features the client actually bought get parked as "phase two", and when the project ends the knowledge walks out the door. It was never the software and it was never your consultants. It is the manual distance between what the client said and what the system was told. Preciq closes it.
| Without Preciq | With Preciq |
|---|---|
| Weeks spent trawling notes and hunting settings | Minutes: Preciq finds the setting and reads the client's words onto it |
| Features quietly parked as "phase two" | Every requirement delivered, or a named, signed decision that it is not |
| Hundreds of setup questions, worked through by hand | Captured once, in whatever form it arrives, never typed twice |
| Configuration keyed in, field by field | Matched to real fields, with a confidence score and a reason |
| A late change means starting the affected section again | A late change re-matches and re-designs in seconds |
| Sign-off by email chain, hard to trace | Named sign-off, role by role, fully auditable |
One engine, seen at two stages.
Discovery sharpens the sale and is free to partners. Project carries the same engine through delivery.
Preciq Discovery
Walk into the next discovery better prepared and walk out knowing what you captured and what you missed. Run the conversation with your own must-have questions, Preciq proposes the scope and flags the gaps.
Learn more →Preciq Project
Take the same engine from discovery to delivery. Run the workshops from a ready-made questionnaire, generate the configuration and load it through the target system's own tooling. Then read the live system back.
Learn more →One flow, start to sign-off.
The same engine reads your client's own words at every stage. What changes is how much of the job it does.
Preciq produces the Workshop Questionnaire, the exhaustive list of what is still to decide across the surface. It is not a stage, it is the output that prepares the workshops, and the workshops are where the number lifts. Stages 1 and 2 are free to partners in Preciq Discovery. Stages 3 to 5 are Preciq Project.
Fast, and still yours to check.
The argument you take into the room.
Preciq makes your engagement faster and cleaner. These are the wins your client keeps.
Live sooner
They pay for the system from the day the contract is signed. Every week earlier live is value recovered, not just cost saved.
Sign-off they can defend
Who agreed what, when and why, answerable in minutes when the auditors ask, not days of email archaeology.
Answers that outlast the team
Why a setting is the way it is stays in the record, not in the head of someone who has left.
Requirements in. Configuration out.
Bring a real discovery brief and watch Preciq match it, live.