Most AI tools give you a quick, confident answer to the question you asked. That is fine for a quick question. It is not what a consultant needs the week before a client meeting, when the question is whether the client’s own plan holds up.
Revan the Strategist is built for that week. You bring a decision, tell Revan what you know and add the client’s files. Then you ask the way you would ask a sharp colleague, push back when you see it differently, and follow up with the next question. Revan pushes back on you too.
Here is what that looks like across one engagement. This is an illustrative example. The client and all figures are fictional.
The setup
A management consultant is working with a distributor of industrial supplies. The CEO wants to open a second distribution center to fix late deliveries. The consultant has loaded two years of order history, delivery performance and the customer complaint log into the Ops Review folder of the client’s Data Room, and meets the CEO on Thursday.
Question 1: Is the client right?
Consultant: The CEO is convinced a second distribution center in Charlotte will fix late deliveries. Everything is in the Ops Review folder. I meet him Thursday. Is he right?
Revan: Not based on what’s in these files. Late deliveries rose from 6% to 14% of orders over the two years, but distance doesn’t explain most of it. About two-thirds of late orders had stock on hand and still shipped late, because they waited three days or more between order entry and picking. Transit times to the Carolinas are in line with every other region. One caveat: the complaint log only covers the last eight months, so I can’t tell whether this is seasonal. It’s worth walking the order-to-pick process with the warehouse manager before Thursday.
Revan answers the question it was asked, even when the answer is “not based on these files.” The call comes first, the evidence follows, the caveat says what the files can’t show, and the next step is something the consultant can do before Thursday.
Question 2: Push back
Consultant: Their biggest account is in the Carolinas, and it’s the one complaining loudest. Doesn’t that point to distance?
Revan: It’s the right thing to push on, because losing that account is the real risk here. But their late orders look different from everyone else’s. Most are split shipments caused by backorders, not slow transit. A building closer to them would ship the same backorders, just from a shorter distance. If distance were the problem, you’d see long transit times on complete orders, and you don’t.
A good push deserves a real answer, not a retreat. Revan takes the concern seriously, names the risk behind it and then says what the evidence would look like if the consultant were right. That last sentence is the useful one: it tells you what would change the answer.
Question 3: Go deeper
Consultant: So why does that one account have so many backorders?
Revan: Their volume roughly doubled over the two years, and most of the growth is in about 40 items. My best explanation is that reorder points on those items were never raised to match. I’m inferring that from the pattern, though, because inventory settings aren’t in the folder. If you add the item master export, I can check it item by item instead of guessing.
Revan says plainly when it is inferring, and asks for the file that would let it check. A general AI assistant is more likely to state the explanation as fact.
Question 4: Pressure-test the recommendation
Consultant: The item master is in the folder now. Here’s where I’m leaning: fix reorder points and the order-to-pick process first, and revisit the distribution center in six months. Pressure-test that.
Revan: The item master confirms it: 31 of those 40 items have reorder points below current monthly demand. Your recommendation holds, with two changes. First, the strongest objection: the CEO may want Charlotte to grow into new accounts, and that reason wouldn’t show up in this data. Ask him directly before you present, or you’ll be arguing against a plan you haven’t fully understood. Second, give the six months a trigger. If on-time delivery hasn’t recovered to an agreed level in 90 days, the distribution center case reopens. That turns “not now” into a plan he can say yes to.
This is where the ten perspectives earn their place. The operational case was already strong. The strategic question and the stakeholder question, what the CEO really wants the building for and how he will hear “not now,” are what would have sunk the meeting. Revan raises both, and the 90-day trigger turns a no into a plan.
Question 5: Then deliver
Consultant: Good. Build the board summary in our template, and a one-page action plan for the warehouse manager.
Revan: Both are ready: a six-slide board summary in your firm’s template, and a one-page action plan with owners and 30-, 60- and 90-day checkpoints. I flagged two figures in the summary to confirm with the controller before it goes out. They come from the order history export, which may not match the books exactly.
The deliverables come out in the firm’s own template, and the open questions travel with them.
Five questions, each sharper than the last. The consultant’s judgment drove every turn. Revan did the digging, checked the logic and said plainly what it didn’t know.
I found that the board debate is stronger, it’s better informed and that as a board we are operating at a different level thanks to what Revan is able to bring in a relatively short space of time.
Tom, Chairman, Montpellier Legal & Risk Advisory Group
Built for how a practice works
The conversation is only part of it. Client work runs by client and by engagement, your team needs the same files, and your clients expect polished work back. Revan gives your practice that structure:
- A project and Data Room for every client, or for every engagement, with folders and subfolders so every file has a home. Point Revan at one folder, like the financials or the interview notes, and it works from exactly those files.
- Clients stay separate. Access is set per project and per Data Room, so someone working on Client A never sees Client B.
- Your team shares the work. Projects, Data Rooms, files and finished work are shared across the team. Each person’s conversations with Revan stay private.
- Your methods built in. Load your frameworks, templates and methods once for the whole firm, or for each project. They stay private to your firm.
- Your brand on the work. Word, PowerPoint, Excel, charts and dashboards come out in your firm’s look.
- Your clients, under your brand. With white labeling, available at an additional charge, your clients sign in to a platform that carries your name and collect your work in their own Data Room.
The decision stays yours
Revan sharpens your judgment. It doesn’t replace it. Your clients hire you for your expertise and your name goes on the work, so you make the call and you decide what reaches your client.
Try it on a live engagement
The free 7-day trial is the full version. Set up a client project, ask us for a Data Room, upload the files from an engagement you are working on now, and ask the question you are working on. Then push it until you are happy with the answer.
See how Revan the Strategist works
What’s the client question you’d bring to Revan first?



