Pruvato runs real business work — starting with customer quotations — under rules you approve, with every outcome independently verified against your own systems and kept on a tamper-guarded record.
Get your free Quotation Health Check See how it works
From the WhatsApp message, priced from your own list, never guessing.
A quote that breaks them stops and asks you.
Confirmed in your own Zoho by a read-only account, on a permanent record.
AI can already draft your quotes, update your systems, message your customers. But when a customer, an auditor, or your own accountant asks "why did this happen?" — most AI tools can only show you what the AI said it did.
A confident message from the tool itself. Useful for debugging. Worthless when money or a customer relationship depends on it.
A separate read-only account reads your books back and compares, line by line. The AI's word is never the proof.
Thousands of technical entries showing that things ran — not whether the right thing happened, or who allowed it.
What ran, under which of your rules, approved by whom, with what result — permanent, and answerable in one lookup.
The discount below your floor is discovered in review — after the quote went out.
Your rules sit inside the execution path. A quote that breaks them isn't flagged — it stops, and asks you.
Only possible when you govern the work itself
The quote that was never registered, the follow-up never sent — no log entry, no alarm. Nothing looks wrong.
Every job runs against a declared plan — so the step that never happened shows up as unfinished, never as fine.
Only possible when you govern the work itself
The burden of proof should sit with the system — not with you.
Paste the customer's WhatsApp message. The model drafts a plan — line items, prices, terms — grounded against your real catalogue and rules.
Every field is grounded or becomes a question. Numbers come from the customer's text or your price list — never invented, never averaged into existence.
Exceptions reach you as a named decision on an exact document hash. Change one line afterward and the approval no longer covers it. "Ok 👍" is not an approval; this is.
The engine — not the model — performs the work, under the approved plan, with rules enforced in the execution path. A below-floor quote isn't flagged. It cannot be sent.
The part that checks the work reads your systems back independently, and reports Confirmed, Doesn't match — needs you, or Not confirmed yet — never assumed. Every action lands on your record, permanent and searchable by your team — and trustworthy to an auditor.
What was supposed to happen, what the system says happened, and what your books show. Most tools stop at the second. The verdict here only ever comes from the third.
Two clocks on every row — when it happened, and when it reached the record — because a slow check and a late entry are different things, and the record says which. Drawn from real sandbox runs; identifiers shortened.
Example — what your dashboard shows. Not live customer data.
Three buckets, never blended into one score — a single "98% healthy" number is exactly the kind of reassurance that hides the AED 3,927. Every figure opens to its own quotes.
Every decision is stamped with the exact rules in force at that moment. Update your rules next month and old records stay judged by the rules of their day — nothing is quietly re-graded.
Two lists, kept separate on purpose: things that need your decision, and things that couldn't be determined yet (a system didn't answer, a check is still due). Blurring those is how real problems hide in noise.
The new quantity stands as a documented exception. Your reason is required and recorded word-for-word — a ruling must say why.
Fix it in Zoho (or ask us to draft the correction), and the same read-only account re-reads your books until they match your approval again.
The same read-only account checks your books again after the fix — the case closes once they actually match your approval.Your ruling never rewrites the mismatch — it's added beside it, so the record keeps both the problem and the decision, in order, forever.
Snapshotting the rules beside an action lets violations be reviewed after the money moved. Here, the rules are what the engine executes under — violations don't need catching, because they can't run.
Watching actions can't see the action that never happened. A declared plan can: the registration that was skipped, the follow-up that never went out — surfaced as Unknown, never assumed done.
The identity that writes holds no power to verify; the identity that verifies is read-only at the provider itself — a ceiling we can prove, by attempting a write and keeping the refusal on record. The record is trustworthy because no one gets to grade their own homework.
Governance is arriving everywhere, and that's good — the question underneath it is who sits in the judging seat. Here, a read-only account reads your system of record and compares values, line by line — no second model forming an opinion about the work. That account holds no permission to write, so its findings stand on their own.
These are two different things, and the difference is written down rather than promised. What follows are the default rules for a new connection — yours are generated for your own setup and may differ. The right-hand list isn't a feature we haven't built yet — it's a set of actions this connection is structurally unable to perform in your account.
The part that checks the work holds no power to change it. Confirming that a quotation arrived correctly is done by a separate read-only user in your own Zoho — one that cannot create, edit or delete anything, enforced by Zoho itself rather than by us.
We prove it rather than assert it: that user attempts a write, Zoho refuses, and we keep the refusal on record.
Default rules shown · v1.0.0 · once these are yours, changing any line requires your approval.
Every capability claim on this page belongs to exactly one of these columns.
Not yet: invoices, payments, or anything beyond quotations. Not yet: enterprise scale. Quoting first, done properly — the rest follows the same discipline.
For trading and services businesses quoting from Zoho, Excel, and WhatsApp. Send us your quotation export — we return a findings report on your last year of quoting: money gone silent, pricing drift, expired pipeline, version chaos. Every figure carries its basis, and what your data can't support, the report says plainly.
Request your report or email partners@pruvato.com · 3–5 partner slots · English first, Arabic coming
No. Discount floors and rules are enforced in the execution path — a violating quote can't be sent, only escalated to you. Your approval is bound to the exact version you were shown; change anything and the approval no longer covers it.
Exactly what's authorised and nothing more — see the full breakdown of what it can and can't do in your account under Permissions.
The free report reads your file's structure and computes findings; our stored records keep technical fingerprints — versions, counts, hashes — never your amounts. Deletion after the agreed window is itself a recorded event.
The AI only proposes — plans, drafts, suggestions. A deterministic engine executes, humans approve the exceptions, and an independent check confirms outcomes against your systems. That division is the product.