Before You Buy an AI Platform, Ask It to Complete One of Your Workflows

Six · 8 min read · October 1, 2026

Before You Buy an AI Platform, Ask It to Complete One of Your Workflows

Say you lead a revenue team and you're comparing AI platforms. One vendor's connections page shows your CRM, the drive where your contracts live and the help desk where support logs every ticket. Your approved prices sit in an internal pricing tool that isn't on anyone's list, but most of what you use is there.

That tells you the platform can reach the places where your work happens. It doesn't tell you whether it can do the work. When an account comes up for renewal, someone on your team finds the account, reads the current contract, checks the recent support history, compares the approved pricing and writes a recommendation for the account owner. A page of logos can't show you whether a platform gets through that.

So before you buy, ask each vendor to complete one of your workflows. Not the demo they've rehearsed around the tools they know best, but one job your team already does, with the inputs, permissions, handoff and finish line that make it real.

Choose a workflow with a visible finish line

Pick something your team does often enough to recognize a good result, and small enough that a failed test won't leave a mess to clean up.

The renewal brief fits. Written as an assignment, it might read:

Prepare a renewal brief for one account using the current CRM record, the latest contract, recent support notes and approved pricing. Return a recommendation and the supporting evidence to the account owner. Do not send anything to the customer.

That makes a good test because the result has an owner and a firm limit. The platform has to pull from four sources, stay inside a boundary that matters and hand back something the account owner can check line by line.

Leave out workflows that end in something you can't take back, like a sent offer, a changed price or a cancelled contract. The first test should show you where the platform is strong, where it needs setup and where a person still has to decide. If the platform gets the renewal brief wrong, your account owner reads a bad draft. If it gets a sent offer wrong, your customer reads it.

Write the audition brief

Give every vendor the same brief. If each one hears a slightly different version on a sales call, you end up comparing how they understood the conversation instead of how they handle the work.

The brief needs five parts. Here's what each one covers, and what it looks like for the renewal brief:

Brief field What it covers For the renewal brief
Outcome The decision or deliverable the workflow supports A renewal recommendation the account owner can act on
Required inputs The systems, records and documents this run depends on The CRM record, the latest signed contract, recent support notes and the approved price list
Required operations The reads, searches, updates and handoffs needed to finish Find the account by the ID your team uses, read the contract and the price list, write the brief, deliver it to the account owner
Boundaries What the platform must not do, who approves what, and which data or actions are off limits Nothing goes to the customer, and any concession is the account owner's call
Acceptance check What the owner needs to see before calling the result useful Every figure traces to its source, and the pricing matches the current approved list

The operations row is where demonstrations get honest, because "integrates with our CRM" doesn't answer it. Can the platform find the account by the ID your team uses? Can it read the renewal date and the contract value, or only the account name? Can it tell this year's pricing from an old attachment someone left in the folder? Can it put the brief in front of the account owner without somebody copying it across by hand?

Some vendors will answer with an API description, a document listing the operations a service offers. The OpenAPI Specification says a description like this allows "both humans and computers to discover and understand the capabilities of a service." That's a fair account of what the service says it can do, but it can't show whether those operations are set up for your account, allowed under your permissions or any use to the renewal brief.

Watch for the work the demo leaves with you

A vendor can show you a convincing renewal brief and still leave the hardest parts on your side of the table.

During the demo, ask someone on your team to name every manual step out loud. Is a person exporting the support notes, choosing between two records for the same account, reconnecting a tool, pasting the brief into the CRM or deciding whether an action is safe to run? Some of those steps belong with a person. Others mean the workflow didn't get done.

Don't mark any of them as a failure on the spot. Write each one down, with who did it, so you can sort them after the demo.

Whether the brief recommends a discount may rightly be left to the account owner, since it's commercial and their name goes on it. It's a different problem if someone on your team has to go and find the contract because the platform can't reach the drive. The first is a decision you want to keep. The second is a missing operation, a missing permission or a setup step, and you need to know which.

Separate four reasons a workflow can stop

When the renewal brief doesn't come back finished, ask the vendor to say why. The answer usually falls into one of four kinds:

What happened In the renewal brief The next question
The operation doesn't exist The platform has no way to read the pricing tool Is the action unsupported, or is there another supported way to reach the same result?
The operation exists but can't run The pricing tool is connected, but the platform's access doesn't cover the price list Which permission, credential or setting is missing?
The operation runs but the result is incomplete The brief quotes last year's contract Which input, step or acceptance check failed?
The operation is available but shouldn't run The platform could email the customer a renewal offer Who owns that boundary, and what review or approval does it need?

Sorting stops this way protects you from two bad buying decisions. You won't turn down a platform that can do the job because the demo needed one setup step. And you won't buy one because the word "connected" hid the fact that it can't read your price list.

Ask to see the evidence, not only the answer

The finished brief on the screen shouldn't be the only thing you judge.

Ask the vendor to show you what sits behind it: which sources the platform read, what it did with each one, where it paused for a person and what it recorded when something couldn't be done. For the renewal brief, that means seeing the contract it opened and the price list it compared against, not just a paragraph that mentions them. If it says the brief went to the account owner, check that it arrived.

Anthropic's engineers make the same point in their guide to evaluating AI agents. Their example is a flight-booking agent that ends by saying "Your flight has been booked," when what matters is whether a reservation exists in the database. When a task fails, the guide says, the transcript (the record of what the agent did along the way) tells you whether the agent made a genuine mistake.

None of this is a trick test. You're checking whether the platform shows its work clearly enough that your account owner can put their name on the recommendation.

Make the result a buying decision

After the test, write down where the renewal brief landed, in plain words:

Then ask whether what's left changes what the platform is worth to you. A platform that needs setup before it can read your pricing tool may still be the right buy. One that can't read it at all could be fine too, if checking the prices by hand is a small job your team doesn't mind keeping.

The NIST AI Risk Management Framework was written for managing AI risk, not for buying software, but one line in it fits: AI systems "should be tested before their deployment and regularly while in operation." The renewal brief is that test, run before you sign. If you buy, run it again once the platform is live.

Apply the test to Supanova too

Hold us to the same standard. Say you bring the renewal brief to Supanova.

Start with the operations row. When you connect a tool to Supanova as a Bond with your own key, you can open that Bond and see what your key can actually do with the tool, capability by capability. Reading the price list should be one of those capabilities before you count on it in the brief.

Then the boundary. Finished work comes back for your review, and nothing ships without you. So the renewal brief lands with your team first, and what the customer hears stays the account owner's call.

Nothing your workforce is working on can silently disappear. If the renewal brief stays stuck, it becomes a decision waiting for you. Ask why it stopped, the way you'd ask any vendor. Is it a missing operation, a setup step, an incomplete result or a boundary doing its job?

Your internal pricing tool may be the part that doesn't connect. If so, you should hear that during the test and count it as a gap, the same way you would with any other vendor.

We built Supanova so people could turn ideas into economic value without waiting for capital, headcount or permission. For your revenue team, the idea might be a renewal brief for every account, not only the biggest ones. That capacity is only worth buying if the work gets finished, which is why the test comes first.

Pick the workflow your team can explain best, ask every vendor to finish it in the open, us included, and let what you see make the decision. Bring yours to supanova.team.

Sources

autonomous-workforceAI workflowAI evaluationAI procurement