Check this before I send it to a client, investor or the board
Before you send it, check the three things a tough external reader hits first: the claim you cannot evidence, the number that does not reconcile with the one three pages earlier, and the sentence that reads worse from their chair than it did from yours. You will not find them on your own read, because you know what you meant — you fill the gap as you go, and the line that lands badly on a client who is already irritated looks perfectly civil at eleven at night. Proofreading will not save you either. It checks the document, not the argument.
Decidi reads it the way the recipient will, before the recipient does. You paste or upload the draft — the proposal, the deck, the client update, the board memo — and a panel including an Editor-in-Chief, a Devil's Advocate briefed to find the reason to say no, a General Counsel for the promises you are accidentally making, and the domain specialist your reader will be, argues over it across four frontier models. An impartial moderator returns one review: the attacks ranked by how much damage they do, the claims that need backing, the lines to rewrite, and the questions to have an answer ready for. An always-on Final QA audit checks that review for unsupported claims before it reaches you.
- The first things a sceptical reader will attack, named and ranked — each with the fix
- Every claim separated into evidenced and needs-backing, so you know what to source before you send
- Numbers checked against each other — the figure on page two against the figure on page six
- Tone read cold from the recipient's chair: where it reads defensive, presumptuous or evasive, with the lines rewritten
- The questions you will get back, with your weakest answers exposed while you still have time
- Several independent models, so the thing one reads straight past is caught by another
- A downloadable review you can work through line by line, not a chat thread to scroll
Part of: How Decidi works
A send-readiness review: the attacks ranked by damage, each claim marked evidenced or needs-backing, the tone lines rewritten, and the questions to have an answer for before you press send.
Common questions
What should I check before sending something to a client?
Check four things, in this order: the claims you cannot evidence, the numbers that do not reconcile with each other, the tone in the paragraphs you wrote defensively or in a hurry, and the questions the reader will send back. Spelling and formatting come last, because a spotless document with an unsupported claim in it still costs you the account. The useful test is not "does this read well" — it is "what would a reader looking for a reason to say no do with this, and can I answer it". Decidi runs that test and returns the attacks ranked.
What is the difference between proofreading and an adversarial review?
Proofreading checks the document; an adversarial review checks the argument. A proofreader fixes typos, grammar, inconsistent capitalisation and broken formatting — real work, and none of it will save you from a projection that contradicts the previous slide or a promise you cannot keep. An adversarial review asks what a reader who wants to decline would do with this, which is the only one of the two that finds the thing that loses the deal. Decidi does the second and flags the first as it goes.
What does a tough external reader attack first?
The number, then the claim, then the omission. A client or investor reading sceptically goes straight to the figure that decides whether this is worth their money, checks whether it agrees with the other figures you gave them, tests your strongest claim for evidence, and then notices what is conspicuously absent — the risk, the timeline, the cost you left out. Tone is the last thing they notice and the first thing they remember afterwards. Decidi seats readers who work in that order deliberately.
Which claims need backing before I send it?
Any claim a reader could reasonably answer with "how do you know that?", and any number not traceable to a source you could produce if asked. In practice that means performance figures, market sizes, timelines, comparisons, and anything phrased as a certainty — "will", "guarantees", "always". The dangerous ones are the claims you believe so completely that you stopped noticing they were claims. Decidi separates the evidenced from the unevidenced and tells you which of the unevidenced ones actually matter to this reader.
How do I check the tone before I send it?
Read it as the recipient would on their worst day, taking the least generous interpretation available. The lines that go wrong are rarely rude — they are defensive ("as previously discussed"), presumptuous ("as agreed"), or evasive about the thing the reader most wants addressed, and they read as neutral to you because you know your own intent. A tone risk is any sentence whose meaning changes with the reader's mood. Decidi reads from the recipient's chair and rewrites the lines that turn.
Is one AI enough to check this before I send it?
Not for something going to a client, an investor or a board. A single model tends to agree with the way you framed the work, cannot reliably audit itself, and will usually tell you the proposal is strong and then tidy the sentences. Decidi runs several independent frontier models plus a Devil's Advocate briefed to attack the document, and a Final QA audit reviews the verdict for unsupported claims before you see it. Chat is free and needs no account, so you can test it on one paragraph before you trust it with the whole thing; plans are then counted in runs, with Plus at $19/month including 16 full runs a month and Pro at $49/month including 44.
Try it on your own decision
Start in chat free, with no account. When the answer matters, put it to GPT, Claude, Gemini and Grok — they debate it, a Final QA audit reviews it, and you get one clear verdict with the open questions named.
Start free