The last rule I work by is to test small and expand only what works.
A short pilot is cheaper than a rollout that doesn’t fit. It also gives the team a chance to say what is annoying before it is built into everything.
What a pilot should answer
- Did the number move, and by how much?
- Did the team use it without being chased?
- What did it get wrong, and who caught it?
- What would we drop?
How to keep it small
- One number.
- One team or one pipeline.
- A fixed length, written down before you start.
- A date to decide what to keep.
Why I keep a person on the write
A pilot is also where you learn how often the AI draft needs a fix. If people approve everything without reading it, the approval step has stopped working. That is a finding too.
The catch
A small test can mislead you. A pilot with a few deals tells you about those deals. Treat the result as a reason to try a bit more, not a proof.
If you want this built around your own pipeline, email me or see RevLathe.
I’m Seth Levanen. I find the AI shortcuts that keep the quality and drop the busywork. Email me if you want to talk about it.