Every workflow tool demos well. That is what demos are for.

The gap between a good demo and a good decision is the set of questions nobody asks, because they only become obvious six months in, when the thing is already embedded in your operation and switching costs are real.

Here are the seven worth asking while you still have leverage.

1. Can it reject an incomplete order?

This sounds small. It is the whole game.

If the system will happily accept an order missing the co-op details, the rotation or the audio, then it is a filing cabinet, not a workflow. The rework you are trying to eliminate starts with orders that arrive half-formed. Ask to see what happens when someone tries to submit a bad one.

2. Who can see status without asking a human?

Ask specifically: can traffic see whether production has finished, without sending a message? Can sales see whether the client approved, without calling the AE?

If the answer involves anyone reporting status to anyone else, you have bought a system that still needs a spreadsheet next to it. You will build that spreadsheet within a month.

3. What happens on the second market?

Most tools handle one market fine. Ask what changes at four.

Does the same order work across markets, or does someone re-key it? Do promotions carry their own rules per market? Can one person see all of them at once? Multi-market is where generic tools quietly stop being free and start costing you a coordinator.

4. Where do approvals actually live?

If approvals happen over email and then get recorded in the tool, they do not live in the tool. They live in email, and the tool is a transcript.

You want feedback attached to the version of the asset it refers to, so nobody is guessing which round of notes applies to which cut.

5. Does it integrate with what you already run?

Your automation system, your traffic system, your audio. If the new tool cannot talk to them, then "one system" means one more system, and someone re-types everything into it.

Ask for the specific integrations by name, not the word "integrations."

6. What is the record when someone complains?

A client disputes a spot. A listener disputes a contest. What can you produce, how fast, and does producing it require anyone to remember anything?

If your proof of performance is assembled by hand from inboxes after the fact, you do not have a record. You have a research project waiting to happen.

7. What does it cost when the person who understands it leaves?

The real test of a workflow system is whether it survives turnover. If status, history and rules live in the system, a new hire is productive quickly. If they live in a long-tenured person's head and their spreadsheet, that person's departure is an operational event.

This is the question that separates a tool from an operation.

How vCreative answers them

These are the questions we built around, and it is fair to hold us to them:

• vPPO handles production orders with dynamic order forms, so incomplete orders do not enter the workflow, and puts sales, production and traffic on one view with spot history and co-op tracking
• vProMedia keeps creative production and approvals in one system, on the asset, instead of in spreadsheets and email threads
• vPromotions runs promotions execution across markets with the record kept as the work happens

Ask us the seven questions. Ask the other vendors too. The answers will tell you more than any feature list.

One question worth adding to the list: what happens when you call support. Katherine Davis, radio production specialist at Cox Media Group Atlanta, admits she usually dreads it, because support is normally slow and impersonal. Her experience here was the opposite, and she frames the value in the only terms that matter to a busy team: the time she did not waste trying to work it out alone.

The bottom line

You are not buying software. You are buying what your operation looks like in eighteen months.

Pick the questions that reveal that, and the decision usually makes itself.

Bring your seven questions to a demo.

Frequently asked questions

What should we ask a vendor about integrations?

Whether the integration is certified by the traffic vendor or built independently, whether data moves in both directions, and whether an order created in traffic appears in the workflow system without manual entry. Those three answers separate a real integration from a checkbox.

How long should implementation take?

Ask for a plan with dates rather than a range. For reference, vCreative implementation runs on a roughly three week plan covering setup, customization and training, at about two hours of training per employee, with the first benefits typically showing inside 90 days.

What is the most overlooked question?

What happens when you contact support. Response quality is invisible during a demo and decisive once you are live, particularly for a small team where one unanswered question can hold up a spot.