I spent part of this week with a client trying to answer what should be a simple question: what's your first point of value with a new customer?
It wasn't simple. It never is.
We had no shortage of candidates. Maybe first value was a percentage of data loaded into the system. Maybe it was answering a question in hours instead of days. Maybe it was cost savings from reduced hours. Maybe it was just building enough internal trust that the team would keep going.
All four were real. None of them was "it."
Here's the checklist I use to pressure-test any first value candidate:
- Tangible and measurable, a number, not a feeling.
- Achievable inside 90 days.
- Narrow: one to three use cases, not "everything they bought."
- Anchored to a workflow the customer already treats as critical.
Run real candidates through that filter and most of them fall apart fast. Ours did too. And the sticking point wasn't which one to pick. It was realizing we'd been quietly mixing up two different things: first value, and the business outcome.
They're not competitors. They're sequential. First value has to live in the daily user's workflow, because that's the only place something tangible can happen in 90 days. The business outcome, that result number the exec sponsor actually bought the product for, takes longer, and it's realized through the daily user's workflow, not instead of it. First value doesn't replace the outcome. It's the down payment that earns you the right to go get it.
Confuse the two and you get one of two failure modes. Either onboarding stretches for months chasing an outcome that was never going to happen that fast, or the team hits a narrow technical milestone the exec sponsor never notices, and the customer wonders what exactly they bought.
We left the sessions with sharper questions instead of a finished statement: what's the smallest version of daily value we can prove in weeks? And what does proving that need to visibly lead to, six months out, for the person who signed the check?
That's the actual work of defining first value. Not picking the most impressive outcome. Not picking the easiest box to check.
Find the narrow, fast win that's specific enough to measure now and connected enough to matter later.