Questions, answered plainly.
If something isn't here, write to us. We'd rather tell you "we don't know yet" than guess.
Every enterprise deal creates promises: "Roadmap Q2", "coming soon", "can be customized". Provaniq records who promised what, to whom and when, and shows whether Product actually stands behind it.
Feedback tools collect what customers ask for. Provaniq covers the step after: what your company promised in response, and whether Product approved it. The two can live side by side.
RFP-heavy B2B software companies of roughly 50 to 500 people, such as ERP, HRMS, procurement, FinTech, compliance and healthcare IT. Presales and Product use it together; commercial leaders, Customer Success and founders use it before deals and renewals.
No. RFPs and tenders are the best starting point, but requirement sheets, RFQs, customer workbooks and compliance documents work too. Deals without an RFP are linked through your CRM export.
No. Provaniq reads exports from those tools and connects them. Deals stay in your CRM, the roadmap stays in Jira, Linear, ClickUp or a spreadsheet, and Provaniq doesn't write RFP responses.
Three files: past RFPs or requirement sheets (XLSX, CSV, DOCX or PDF), a CRM export, and a roadmap or backlog export. A simple spreadsheet with capability, status and target release is enough for the roadmap. Optionally, add call or meeting transcripts your tools already produce.
We start upload-first, so there is no integration project. Design partners can upload call or meeting transcripts their own tools already produce, such as Maqsam, Google Meet or Microsoft Teams. Provaniq never records or transcribes calls itself, and only reads the transcript text. Live connectors and AI-agent access come later, once the core proves useful.
Mixed Arabic and English documents are common across MENA, so they are a core design goal. We are validating Arabic handling with design partners before making any claims.
Design partners start with anonymised files. How files are processed, including any AI processing, training and regional data residency, is agreed in writing before anything is shared. If it isn't agreed, it doesn't happen.
No. AI flags possible promises and suggests matches; a person confirms each one, and Product makes the decisions. Provaniq will never tell you to "build feature X".
We say so. Missing evidence shows as "We don't know yet", with what it means, for example that demand by industry may be understated. No made-up confidence scores.
They are pipeline linked to a requirement or promise: useful context, not proof that a gap caused a loss. We keep the two clearly separate.
We're opening a small design-partner programme across MENA, starting in Egypt, Saudi Arabia and the UAE. Fill in the short form on the Apply page and press Send. It reaches our team at hello@provaniq.com, and we reply to your work email.
You give three anonymised files, a few hours of review time over four weeks and honest feedback. You get your own Commitment Exposure Map and Requirement Registry, review sessions with us, and a say in what we build next.
There is no public price yet. Design-partner terms are agreed individually, and pricing will be shaped with the first teams who use it.
If the results changed a real decision, we agree how to keep your map updated. If they didn't, we part ways and you keep what you learned.
You only share transcripts of calls where participants agreed to recording under your local rules. We agree with each design partner what is shared and how it is anonymised before anything is uploaded. We never receive audio.
