I opened my calendar that morning, saw "9:12 A.M. Training Session," and knew before the call ended what it meant.
The client was paying Asenda for a one-day workshop on how our AI pipeline surfaces bottlenecks in a logistics operation. Four hours, a shared screen, and a walkthrough of the exact workflow my unfinished product was supposed to automate. They were happy. They booked a second session. And I sat there doing the arithmetic every founder with a runway clock does: six months left, and the thing I had been building toward for nine of them was being delivered by hand, in a workshop, by people who were not me and not the product.
The product lost to the workshop because the workshop was real. The product was a promise.
What the workshop actually sold
The client did not buy a tool. They bought the outcome of the tool: a process for catching exceptions before they became delays. The workshop delivered that process in four hours. No onboarding, no integration risk, no "we will have that in the next sprint." They paid for certainty, and certainty wears a human face better than a roadmap.
Here is the uncomfortable part. The workshop solved their problem. It automated nothing, but it answered their question, which is what they showed up with. I had built a demo that could answer a similar question in thirty seconds, but they could not see the demo working on their data, with their staff asking it their questions. So they chose the version they could see.
I am writing this because I think the failure was mine, and it was a specific kind of founder failure. I had been treating the product as the answer and the distribution as an afterthought.
The lesson was the medium
The thing that made the workshop win was not the content. It was the delivery. The client saw a named person, with a real screen, making a real decision in front of them. They could interrupt. They could ask "but what about our Accra warehouse?" and get an answer in the room.
That is the shape of the gap between a product and its market. The product is a possibility. The workshop is a proof. And until your product can be a proof, it will keep losing to the workshop.
There is a documented version of this exact dynamic, in a different field. In the early years of what became the personal computer, the people selling the machines kept losing to the people who would come in, set up a demonstration, and run your actual problem in front of you. The machine was faster. The machine could scale. But the demonstration could be touched and questioned, and the machine could not, so the machine kept losing until the software and the demos caught up with the questions. The gap was never raw capability. It was the moment of proof. That is the part I keep thinking about: the product that wins is the one that can answer a question it did not prepare for.
My workshop could answer questions I did not prepare for. My product could not. So the client chose the workshop.
What I would build first now
If I were starting over with six months of runway, I would not build the full product first. I would build the narrowest thing that could sit in front of a real client and answer their real question, on their real data, within the first hour of a session. I would make the product the thing that makes the workshop unnecessary, one question at a time.
That means picking the single question the client asked most often in that four-hour session, and making the product answer it so well that the workshop becomes a demo of the product instead of a delivery of the process.
The second training session is scheduled. I am not cancelling it. But I am changing what happens in it. The next workshop will have the unfinished product in the room, answering one question, live. If it stumbles, I learn where the proof still lives in the human. If it holds, I have found where the product starts.
The product did not lose to the workshop because the workshop was better. It lost because the workshop was closer to the proof. I am going to close the gap.
Comments
No comments yet.