The prototype is not the point
Building fast is no longer the achievement. It never was.
Issue #05 · June 6th 2026
I write about the things that don’t change in a world that won’t stop changing.
I believe adding real value is what gives us purpose, keeps us happy and improves our lives.
Everyone can ship now. A landing page in an afternoon. A scoring tool before the next meeting. An AI agent running on your own hardware over a weekend. The technical barrier is gone. Which means prototyping speed is no longer a differentiator — it’s the baseline.
The question that remains is the same one it always was. Does this add real value to someone’s actual problem?
Intent before interface
Earlier this year I was working with NEXMO, a mobility data space running under a European public research mandate with a fixed deadline and limited resources. The team needed a way to prioritise which use cases to activate first. There were more candidate use cases than capacity to run them, and the decision had real consequences — the wrong prioritisation meant wasted effort, missed stakeholder commitments, and a showcase event with nothing credible to show.
The Use Case Scorer I built for that problem was not technically interesting. It was a structured scoring model that weighted strategic fit, data availability, partner readiness, and time to demonstrable output. It took a few hours to build. What it took much longer to produce was the logic behind it — which dimensions actually mattered to this specific programme, in this specific political context, with these specific constraints.
The tool followed the thinking. The thinking followed the problem. That sequence — business intent first, interface second — is the only sequence that produces something worth using.
“The tool followed the thinking. The thinking followed the problem.”
A prototype built in the opposite order — interface first, problem fitted to it afterwards — is a demo. Demos are not useless. But they are not the same thing as a tool someone opens every day because it makes their work better.
The tool that runs your operation
I run a chief of staff agent on a Mac Mini at home. It connects to my real workflows — calendars, communications, project notes, ongoing ventures. It surfaces what needs attention. It drafts, it summarises, it flags. It runs while I sleep.
I did not build it to demonstrate that it was possible. I built it because I needed it. The difference sounds small. It isn’t.
A prototype that doesn’t survive contact with your own operations isn’t ready for someone else’s. The moment you depend on something yourself — when breaking it costs you something real — you start making different decisions about how it’s built. The edge cases you would have ignored become the cases you fix first. The interface you would have left rough becomes the thing you polish because you use it every morning.
This is the test I apply to everything I build now. Would I run this in production for my own work? If the answer is no, it isn’t finished. If the answer is yes, it has a chance of being useful to someone else.
The public face as proof of work
When I needed an operational website for my independent work, the deployment took an afternoon. GitHub to Vercel, domain pointed, landing page live. The tooling is that fast now. Any competent operator can do it before lunch.
What the tooling cannot do is decide what the page needs to say, to whom, and with what level of specificity. That took longer. The question was not technical — it was strategic. Who lands on this page? What do they already know? What do they need to believe by the time they leave? What does the absence of certain information signal, and is that the right signal?
Execution was free. Judgment was the asset. That pattern repeats across everything worth building.
What the agentic era actually changes
In 2020, a working prototype bought you credibility. It was proof that you could build — that the idea was not just an idea but something that could exist in the world. That signal had value because building was hard and slow and most ideas never made it to a demo.
In 2026, a working prototype buys you nothing on its own. Everyone has one. The venture landscape is full of impressive demos built over a weekend by a single person with access to the same tools you have. The demo is no longer the filter.
The new filter is whether the thing you built is grounded in a real problem, for a real person, with a real consequence if it doesn’t work. That filter is not new — it’s the same filter that always separated products from projects. What’s new is that it’s now the only filter left, because the execution excuse is gone.
You can no longer say the idea was good but the team couldn’t build it. You can no longer say the prototype would have validated the hypothesis if only there had been time. There is time. There are tools. The question is whether you understood the problem well enough to build the right thing.
“The execution excuse is gone. The question is whether you understood the problem well enough to build the right thing.”
The invariant
The prototype was never the point. It was always the cheapest way to test whether you understood the problem well enough — a forcing function that turned vague thinking into something concrete enough to be wrong about.
Now that it’s even cheaper to build, the test is purer. The signal is cleaner. A prototype that adds no real value is now just visible evidence of a thinking problem, not a building problem.
The bar hasn’t risen because the tools got better. It’s risen because the tools removed every excuse except the one that was always there: did you understand what you were building, and why it mattered to the person you were building it for?
That question has no agentic shortcut.
Fernando Martín is Managing Director of NEXMO Movement Data Hub (UC3M), Venture Builder at MOVEN, and founder of Eccocar. He writes here about venture building, AI agent operations, and the European technology landscape.
The Invariance — by Fernando Martín In a constantly evolving world, only value is the invariance that holds everything together.
Thanks for reading. If this resonated, share it with someone who needs to read it.