Requirements in.
Configuration out.

Deliver more implementations with less senior time. Preciq takes what your client has already given you - workshop recordings, notes, emails, documents - and turns it into the design, the documentation and the import package. Your consultants make the judgement calls. The re-keying, the write-ups and the chasing of sign-off go.

Now live on Microsoft Dynamics 365 Business Central, Finance & Operations, Dynamics 365 Sales and HubSpot (more systems coming soon), configured from plain discovery notes and written straight into the live system.

New: Preciq now reads Dynamics 365 Finance & Operations (FSCM) and Dynamics 365 Sales, live and working, alongside Business Central.
0Dynamics 365 Finance & Operations settings Preciq reads, extracted from a live environment, so your design starts from what's real, not what's remembered
0F&O modules mapped, area by area, so your team doesn't have to carry the system in their heads
90%confidence before a match auto-accepts, everything else waits for your decision, with the reason shown
Zeroerrors importing the generated package, and it's the package your client goes live on

Pre-sales promised the earth. Delivery got "phase two".

Requirements are gathered in workshops and typed into spreadsheets. Configuration is keyed in by hand, field by field. And when the deadline closes in, the features the client actually bought get parked as "phase two". When the project ends, the knowledge walks out the door.

It was never the software, and it was never your consultants - brilliant people, too busy in the settings to consult. It is the manual distance between what the client said and what the system was told. Preciq closes it: it reads what was captured, matches it to the target system's real configuration and holds anything it isn't sure about for a human to decide.

Without PreciqWith Preciq
Features quietly parked as "phase two"Every requirement delivered, or a named, signed decision that it isn't
Hundreds of setup questions, worked through by handRequirements captured once, in whatever form they arrive - never typed twice
Configuration keyed in, field by fieldMatched to real fields, with a confidence score and a reason
A late change means starting the affected section againA late change re-matches and re-designs in seconds
Sign-off by email chain, hard to traceNamed sign-off, role by role, fully auditable

Four things your team stops doing by hand.

One flow, from a captured requirement to an applied configuration.

1. Capture without the grind

Requirements in, any form: a workshop transcript, a note, a document, a whiteboard. No trawling through hundreds of setup questions.

2. Matched to the real system

AI maps each requirement to a real configuration field in the target system, with a confidence score and a plain reason. Confident where it should be, and it flags what a human must decide.

3. Governed by design

Low-confidence matches are held for sign-off. Roles review what they own. The whole design is auditable. Governance is the default, not an add-on.

4. Configuration out

Where the target system supports it, Preciq generates the package that applies the design. Live on Microsoft Dynamics 365 Business Central, Finance & Operations, Dynamics 365 Sales and HubSpot (more systems coming soon), the package imports through each system's native tooling, no raw database writes. Where a system doesn't support Build yet, you still hand over Blueprint: the governed design, agreed, signed and traceable.

Talk. Don't type.

Let an AI note-taker capture the meeting. Drop the transcript into Preciq, and your requirements read themselves.

In discovery calls and design workshops the real work is listening, not scribbling. Use an AI note-taker like Plaud (or any recorder that gives you a clean transcript) to capture every word of the conversation. Then upload that transcript straight into Preciq. Preciq reads it, pulls out the requirements and the configuration decisions, and tells you what is standard, what is a config choice and what is genuinely bespoke. No forms, no re-keying, no requirement lost between the call and the document.

Nothing gets missed

Every point raised in the room is captured and read, not just what someone remembered to write down afterwards.

Faster to value

Walk out of the workshop and have a coverage read the same day, not a fortnight later.

One source of truth

The transcript is the record and Preciq is the analysis, so every decision is traceable back to the moment it was said.

Bring your own note-taker

Plaud, Otter, Fireflies, Teams, Zoom, whatever you already use. If it produces a transcript, Preciq can read it.

1. Record

Record the meeting with your AI note-taker.

2. Upload

Upload the transcript into Preciq.

3. Read

Read your requirements back, mapped to standard, config or custom, ready to act on.

Stop taking notes. Start capturing requirements.

Preciq works with any AI note-taker that exports a transcript. We are a Plaud affiliate partner, and we like their kit, but the choice is always yours.

One flow, start to sign-off.

1
Capture
Transcript, document, whiteboard
>
2
AI Match
Confidence-scored, reasoned
>
3
Solution Design
By role, senior first
>
4
Roles & Users
Security by function
>
5
Generate
Docs and config package
>
6
Approve & Commit
Named sign-off

Once a project closes, Preciq keeps the record live. See Continuous Improvement for what happens after go-live.

Built to match the real system, not a checklist.

Multi-source capture

A transcript, a document, an email, a live workshop board. Preciq reads what's given - no forms to fill in first, nothing typed up twice.

Confidence-scored matching

Every requirement maps to a real field with a score and the reason it was matched, not a black box.

Function by function

Focus one area at a time, the way a stream workshop runs, with its own matches and its own outstanding items.

Approve, edit or reject

Every line can be actioned individually. An edit or a reject captures the reason and stamps who and when - your audit trail writes itself.

Instant re-match

Change a requirement and the match and the design move with it - a late change costs you seconds, not a lost weekend.

Roles & Users

Security modelled as part of the configuration. Pull existing roles and users or import from a sheet, down to read, edit, post or approve.

Generate & white label

A governed Solution and Configuration Map, a sign-off certificate, role User Manuals, and a real configuration package. Add your logo and ship it as your own - your brand on every deliverable your client keeps.

Named approval

Each owner gets their own link and approves their own area. Nobody signs on someone else's behalf.

Drift, flagged

A year on, Preciq compares the live system against what was approved and flags what changed - so nothing drifts unnoticed, and you have a reason to be back in front of the client a year on.

What your clients get out of it.

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.