Evidence before budget
Building got cheap. Being wrong did not. ValueGraph turns a product idea into a case built on customer evidence, so you know whether to build it, revise it or stop it before the money is committed.
8
Steps from a vague idea to a case that survives the room.
1
Graph every finding lands on, so the inconvenient evidence cannot go missing.
3
Honest endings: build, revise, or stop. Any of them beats finding out in year two.
Why we built this
We started ImpactML after years of watching the same failure. A project lands exactly as specified, on time, and nothing about the business is better. The gap was never effort or budget. It was the distance between what the business needed and what got built.
It happens two ways. Someone with influence falls for an idea and pushes it through, having misread the need. Or a team builds the technically interesting thing first and goes looking for someone who wants it afterwards. Both get funded, because the case for them is opinion dressed as strategy. The evidence, if it ever arrives, arrives after the build, when the only decision left is how to present it.
ValueGraph reverses that order. You get the case first: what customers are actually trying to get done, where the idea is thin, and whether this is what your next chunk of budget should buy.
Business impact
Stop it early
The assumptions that would sink it surface while they are still cheap to test: an outcome nobody wants, a problem the market has already solved, a claim the evidence will never carry. You end up with a decision you can explain, not a wasted quarter.
Build what gets used
Every capability attaches to a real problem or opportunity, not a feature wish list. When a planned build serves nothing a customer is trying to get done, the graph makes that obvious long before it reaches a sprint.
Defend the call
You leave with a pitch: customer quotes, market signals, the weak points in your own argument, and a clear recommendation. People argue with the case, not with you.
The journey
Five phases, eight steps. Not a one-way pipeline: when the evidence moves, you loop back. It all stays in one case, so nothing has to be rebuilt from scratch in a new deck.
Frame
Name the idea, the customer, and the outcome you think you enable. That outcome is the lens for everything that follows.
Assess
A first pass on demand and competition, so you are not learning the category live in front of a customer.
Surface what the idea is standing on. Catch the assumption that sinks the whole thing before you spend a week on interviews.
Discover
Short, focused conversations about the outcome, not your product. Nobody is shown the solution first, so the answers can still surprise you.
The same jobs and frustrations start clustering across conversations. You curate what is real. How often something came up stays visible, and so do the answers you did not want to hear.
Decide
Capabilities are proposed against the needs the evidence found, then you keep the ones you would stand behind. This is the hinge from research to a build.
Where your original idea and the evidence part company: needs you never addressed, capabilities you did not expect, a claim resting on a risky assumption. It advises. You decide.
Deck
A pitch deck that quotes the evidence and gives a straight recommendation: build it, revise it, or stop it. The thing you take to the board, the investor, or Monday's planning session.
The artefact
Under the journey is a Jobs-to-be-Done value graph. The idea, the market signals, the assumptions, the customer jobs and the things you would build are all connected to each other. A capability that solves no real problem is visible. An assumption with no evidence behind it is visible. A need customers keep raising that your idea never answered is visible.
That is the point of it: not a prettier interview tool, and not another canvas. A living case for what to build that updates as the evidence does.
The spine
Evidence (market signals, assumptions, customer conversations) sits on top of the spine. When it moves, the case moves.
If you already have access, the platform is ready. If you want a seat, a walkthrough, or a conversation about using ValueGraph with your team, talk to us.