Contrasting Before and After Workflows

Your demo shows a 14-step manual troubleshooting process finishing in two clicks. The buyer says, “Impressive, but we do not do it that way.” Either the before looked like a straw man, or the after looked like a magic trick. The comparison did not land because it was not theirs.

Make the before theirs

Use the prospect’s actual process, gathered in discovery: their steps, their tools, their elapsed time. Count steps and minutes using their own numbers. A workflow contrast only persuades when the audience recognizes the before as honest.

Show the after at equal scope

Run the after path on the same task, with the same data and the same starting condition. Do not skip setup. If automation needs a one-time configuration, show it or state it plainly. Hidden prerequisites are exactly what skeptical engineers hunt for, and finding one retroactively spoils the whole comparison.

Mechanics of the side-by-side

• Use a visible step counter, either split-screen or in sequence.
• Time both paths honestly, including waiting and handoffs.
• Name what the after path does not do, so the claim stays credible.
• Point to the step where an error used to occur and show it no longer can.

Tie it to a number the buyer owns

Convert the gap into something they track: minutes saved per incident multiplied by incidents per month. Present it as an estimate to validate with them, not as a promise. Letting the buyer correct the inputs turns your slide into their business case.

Adapt to the room

For an executive audience, collapse the 14 steps into three named phases and keep the counter. For engineers, show every step and expect questions. In a competitive evaluation, run the contrast on a scenario you chose with the buyer beforehand so no one suspects a staged case.

Decision and check

Decision: for each core demo scenario, write the before with the customer’s own step count and the after at identical scope. Check: the buyer confirms the before is accurate (“yes, that is what we do”) before you show the after, and nobody finds a hidden prerequisite. A workflow contrast that passes both tests is ready for the room; one that fails either goes back to discovery.

This micro-skill belongs to the free SE Ignite curriculum and the Mastering the 80% philosophy: universal mechanics, not product tricks.