From scattered files to promises you can stand behind.

Six steps turn the files you already have into one view of what was asked, promised and approved. Every row keeps its source.

1

Extract requirements

Every requirement row is read from your XLSX, CSV, DOCX and PDF files, together with its file, sheet, row or page.

Kept with every row
XLSXDOCXPDFCSV
Payroll file in WPS formatRFP-0417 · R214
Multi-level approvalsRFP-0388 · R97
2

Normalise answers

Different ways of answering become one consistent set of statuses.

Answer → status
"Comply"→Supported today
"Partial compliance"→Partly supported
"Requires custom work"→Needs custom work
"Planned Q3"→On the roadmap
"No"→Not supported
3

Group similar requirements

AI suggests when different wording means the same need. People merge, split, rename or correct. The original wording is always kept.

Suggested as one requirement
Approval hierarchyMulti-level approvalThree-stage approval workflowApproval by transaction value

→ Advanced Approval Workflow

4

Link commercial context

Requirements connect to accounts, opportunities, pipeline, won and lost deals, country, industry, stage and renewal dates from your CRM export.

Linked from your CRM export
Customer A · won · renews Q1 2027Linked
Prospect B · open · LogisticsLinked
Prospect F · industry missingUnknown
5

Detect commitments

Language like "Roadmap Q2", "coming soon" or "we will support it" is flagged as a possible promise. A person confirms it before it counts. Ambiguous wording never silently becomes an official promise.

Possible promise · needs a person to confirm"Planned for Q2 release."
Presales comment · Customer A · 12 Mar 2026
ConfirmNot a promise
6

Reconcile against Product

The heart of Provaniq. For every confirmed promise: is there a matching Product-approved item on your roadmap?

Matched against your roadmap export
Product approvedNo Product approval yetProduct is reviewingDeliveredPromised date passedWe don't know yet

Examples use sample data

The recurring loop

Not a quarterly report. A living memory.

Every change updates what everyone sees next. That's what keeps Presales and Product working from the same truth.

  • A new RFP changes the picture
  • A Product status change changes the next answer Presales gives
  • A commitment deadline changes the risk
How we build it with you

Four weeks from your files to a real decision.

We start small, with your real but anonymised files. Early processing may be partly manual. What matters is whether the result changes something you do.

Week 1

Share three files

We agree how files are handled, then you share an anonymised snapshot.

  • Historical RFPs or requirement sheets
  • A CRM export
  • A roadmap or backlog export
  • Optional: call transcripts from Maqsam, Google Meet or Teams
Week 2

We map your promises

Your Requirement Registry and Commitment Exposure Map, built from your own rows.

  • Every number keeps its source
  • Unknowns stay visible
Week 3

Review it together

We walk through what surprised you, what you'd ignore and what's missing.

  • Presales and Product in one room
  • Possible promises confirmed by you
Week 4

Decide what happens next

If it changed a decision, we keep it updated. If not, you've lost very little.

  • One real action is the bar
  • "Keep this updated?" is the question
A 20-second tour

Watch one promise get backed.

Files in, promise found, Product decides, next RFP answered. Hover to pause.

XLSXTender-2026.xlsx ✓CRM export ✓Roadmap ✓
WPS payroll integrationNo approval yet
Advanced approvalsProduct approved
Data residencyProduct is reviewing
Employee loansWe don't know yet
WPS payroll integration
No Product approval yetProduct approved · Q1
Approve
Known supported184
Partly supported24
Known gaps11
Need Product4

Sample data