Preciq™ Project takes the won work from what the client said to a governed, applied configuration. Preciq is built around the way configuration engagements actually work: capture what the client needs, match it to the real system, govern the decisions, then generate what applies them. Your team makes the judgement calls; the re-keying, the write-ups and the chasing go. Here's each step.
Sizing a bid rather than delivering one? See Preciq Bid.
A workshop transcript, a document, an email, a live whiteboard. Preciq reads what's given, no forms to fill in first, and no requirement lost because it wasn't typed into the right box.
Every requirement maps to a real configuration field in the target system, with a confidence score and a plain reason. Preciq only auto-accepts above ninety percent. Everything below that is held for a human, and it tells you why.
Every line can be approved, edited or rejected, and an edit or a reject captures the reason and stamps who and when. When the client changes their mind, the match and the design re-run in seconds, not a re-do.
The three steps that turn a governed design into something the client can sign and the system can run.
The design lays out by role, senior first. Expand a role to see the functions and settings it owns. Security is part of the configuration: pull existing roles and users, or import from a sheet, down to read, edit, post or approve.
A governed Solution and Configuration Map with screen mockups, a sign-off certificate, role User Manuals, and a configuration package that imports through the target system's native tooling. Flip the toggle, add a logo, and a consultancy ships all of it as their own.
Approval is real. Each owner gets their own link and approves their own area, nobody signs on their behalf. Hard approve generates the full documentation and moves the project to closed.
ERP, CRM, planning - the flow your team learns once is the flow they run everywhere. Each system is a plug-in, not a rebuild: what changes is the fields it matches to, and whether it supports Build (an applied configuration package) or Blueprint (a governed document to hand over).
Live on Business Central, Finance & Operations and Sales, plus HubSpot (an ERP suite and a CRM). Requirements match to each system's real fields, and Preciq generates a configuration package that imports through its native tooling.
Preciq's deepest roots are in demand, inventory and sourcing configuration, developed in parallel with planning-platform partners.
The same disciplined flow applies to any system a consultancy configures for a client - a new plug-in, not a new product.
Once a project closes, Preciq keeps the configuration record live - the same audit access and governed-change story that's already part of how engagements are delivered.
A year later, a new requirement goes through as approved, and Preciq compares now against how it was. See the full Continuous Improvement page for what that means in practice.
Costing changed. A warning switched off. Extra licences in use, fewer team members than approved for. Did you mean to do that.
Every match and every edit recorded with its source and reason, timestamped from the moment it's confirmed.
Approvals by role, by name. No ambiguity about what was agreed, who agreed it, or when.
Solution and Configuration Map, sign-off certificate, and where the system allows, a configuration package, generated automatically.
Bring a real discovery brief and watch Preciq match it, live.