The forty-page proposal was theatre. Here is what we do in the first meeting instead, and why you see your idea as software within the hour.
We stopped sending proposals. Not as a stunt, but because the proposal had quietly become the least honest document in the process.
You know the artefact. Forty pages. Mockups that cannot be clicked. A wall of assumptions. An estimate engineered to look more certain than anyone in the room actually was. It took us a week to produce, it cost the client nothing visible, and it taught neither side anything real. It existed to win the deal, not to build the product.
So we replaced it. Now the first serious meeting produces working software, in the room, while you watch.
What does a first meeting look like now?
You describe what you need. We build a real, clickable version of it on the screen in front of you, using Lovable inside Ariane, our internal AI delivery layer. Not a slide. Not a static mockup. Screens you can click, flows you can follow, something that behaves like the thing you are trying to buy.
When you say the booking step should come before the login, not after, we change it, and a minute later you are looking at the new version. The conversation stops being about a document that describes a product and becomes about the product.
Two things keep this honest rather than a magic trick.
First, you watch the whole time. There is no pre-built demo we are pretending to improvise. The screen is shared, the work happens live, and when something turns out to be awkward to build, that tells us something worth knowing this early.
Second, the prototype is disposable on purpose. It is not the product, and it is not the foundation of the product. It exists to make a shared, concrete decision about what we are actually building, which is the single most expensive thing to get wrong later. We throw it away and build the real thing properly. What survives the meeting is the agreement, not the code.
Why is a prototype better than a proposal?
Because it moves the risk to the right place and exposes the truth earlier.
A proposal pushes risk onto you. You approve a document and hope the finished product matches the picture. The gap between the two is where projects quietly die. A working prototype puts the uncertainty on the table while it is still cheap to resolve. If the idea has a flaw, you find it in week one for the price of a meeting, not in month three for the price of a rebuild.
It also changes the honesty of the room. It is hard to hide behind a prototype. Either the flow works and feels right, or it does not, and we both find out at the same moment. That is uncomfortable for a vendor who would rather sell certainty. It is exactly what a serious buyer should want.
And it is faster. The week we used to spend writing a document that looked like a plan, we now spend building something that is much closer to the actual answer.
Does building this fast mean building it carelessly?
No, and this is the distinction that matters most. The speed is in the prototype, not in the product.
The live prototype is throwaway, so it is allowed to be fast and rough at the edges. The production build that follows runs through the full discipline: Claude scaffolds inside Ariane, a second model validates the work against the spec, and a senior engineer is accountable for every line that ships. We have written elsewhere about why that pipeline lets us hold a fixed price and a fixed date. The point here is that the prototype is a thinking tool, not a shortcut around the engineering.
Treating the two as the same thing is the mistake. We keep them separate on purpose.
What this means if you are choosing a partner
If an agency needs a week to send you a proposal, ask what that week is for. It is not for you. A proposal is a sales document wearing the costume of a plan, and the longer it takes to produce, the more it is about looking certain rather than being right.
The studios worth hiring in 2026 can show you, not tell you, in the first conversation. The tooling to do that exists now and we use it every day. The ones still mailing PDFs are protecting a process, not serving a client.
Where to start
The formal version of this is an HDL Discovery Sprint. Two weeks, fixed price. You leave with a working prototype, a real architecture and a real price. No proposal theatre, no estimate inflation, no hourly games.
It is the cheapest, fastest way to find out two things at once: whether we are the right partner, and whether the thing you want to build is the thing you should build. Most of our projects start there, and the ones that do tend to be the ones that ship on time.
The proposal was never the deliverable. The clarity was. We just skip to the clarity now.