Building something, anything, as proof of intent: The prototype as co founder pitch

A screenwriter I know spent two years trying to get meetings with producers in Mumbai. She had three scripts, all polished. She sent query letters, attended industry events, cornered people at after-parties and delivered her pitch in the three minutes before they made an excuse to refill their drink. Nothing worked.

Then she took her weakest script, borrowed a friend's camera, recruited two theatre actors who owed her favours, and shot a twelve-minute short film over a weekend. The sound was uneven. One of the actors kept looking at the wrong camera.

But within a month, three producers contacted her. The same people who had ignored her scripts wanted to talk. Nothing about her talent had changed. What changed was the signal. She had moved from "someone who writes scripts" to "someone who makes films." The doing was the proof.

I keep thinking about that story when I watch non-technical founders try to recruit co-founders.

The credibility threshold

There is a moment in every non-technical founder's journey that I call the credibility threshold. It is the point at which the people you need (engineers, investors, early customers) stop evaluating your idea and start evaluating you. Not your pitch. Not your market analysis. You.

A pitch deck cannot cross the credibility threshold. I have watched dozens of founders try. The deck describes a problem, proposes a solution, shows a market size number borrowed from a research report, and ends with an ask. The person on the other side listens politely, asks a question or two, then says "interesting" and never follows up. I can almost set my watch by the pause before "interesting." It is the most diplomatic rejection in the startup vocabulary.

But a working prototype, even an ugly one, crosses the credibility threshold almost immediately. It does not answer the question "is this a good idea?" It answers a different question: "Is this person going to do the work?"

The deck says "I had an idea." The prototype says "I could not stop myself from building it."

Those are not the same sentence. They are not even the same conversation.

Six months of silence, three weeks of building

One of the founders I mentor, a woman with a decade of experience running operations for a logistics company in Chennai, spent six months trying to find a technical co-founder. She had a strong idea: a tool that helped small manufacturers track and reconcile purchase orders across multiple suppliers. She had watched her former employer struggle with this using spreadsheets for years. She understood the problem deeply.

Her deck was genuinely good. Clean, specific, grounded in real operational pain. She took it to startup meetups, WhatsApp groups, LinkedIn messages to engineers she admired. Six months. Dozens of conversations. The response was always warm and always noncommittal. "Sounds interesting, keep me posted." "Let me think about it." Nobody said no. Nobody said yes.

Then she spent three weeks using AI coding tools to build a rough prototype. The interface had default styling. Some features were half-built. But it worked. You could enter a purchase order, match it against supplier invoices, and flag discrepancies. The core workflow functioned.

Within a month, two engineers had reached out asking how they could get involved. Not because the prototype proved the product would work. But because the prototype proved she was serious. It crossed the credibility threshold that six months of polished slides could not.

A prototype does not prove your product will work. It proves you have started. That distinction is worth more than most founders realise.

The difference was not in the idea. The idea had been the same for six months. The difference was in the signal. The deck said "I need your help to make this real." The prototype said "I have already started, and I am looking for someone to build this with me." The first is a request. The second is an invitation.

What I learned at my first startup

I remember this dynamic from my own experience, years before AI tools existed. At my first startup, we spent months pitching advisors and early customers with slides. Beautiful deck. Market research. Clear problem articulation. And we got polite nods and very few commitments.

Then we built something. It was ugly. The kind of ugly that makes a designer (which I am) physically uncomfortable. But it was real. You could click through it, see data, experience what we were trying to build in a clumsy and imperfect way.

Every conversation changed after that. Advisors who had been noncommittal started giving specific feedback. Potential customers who had said "keep me posted" started saying "can you add this feature?" The questions shifted from abstract ("what is your go-to-market?") to concrete ("what happens when a user does this?"). Concrete questions mean someone is mentally using your product. Abstract questions mean someone is mentally evaluating whether to ignore you politely.

But the most important thing the prototype did was change how people treated us. We went from "people with an idea" to "people who are building something." We were no longer asking for belief. We were asking for participation.

The intent signal

I call this the intent signal, and I have come to believe it is the single most underrated asset a non-technical founder can create. The intent signal is what a prototype communicates beyond its functionality. It says: I cared enough about this problem to build something. I did not wait for permission. I did not wait for a co-founder. I did not wait for funding. I started.

That signal is disproportionately powerful because most people do not start. Most people with startup ideas talk about them. Some write decks about them. A few post about them on social media. But very few actually build something, no matter how rough, and put it in front of other people. The act of building is rare enough that it functions as a credibility signal independent of what you built.

But the intent signal has a counterintuitive quality. The prototype does not need to be good. It needs to be real. A polished deck communicates that you are good at making decks. A rough prototype with misaligned buttons communicates that you have started building the actual thing. Co-founders and investors are not looking for someone who can present well. They are looking for someone who will persist.

I have seen this with angel investors too. At the pre-seed stage, they are not evaluating your technology. They are evaluating your probability of still working on this in twelve months. A working prototype is stronger evidence of persistence than any slide about founder-market fit.

The bar has moved

The interesting thing about AI coding tools in this context is not that they make prototypes better. It is that they make prototypes possible for people who could never build them before. The intent signal used to be accessible only to technical founders or those with enough money to hire a developer. That gate has opened.

But the signal still works for the same reason it always worked. It is not about the code. It is about what the act of building communicates about the person who built it.

The founders I mentor who arrive with a working prototype, even a terrible one, have better conversations and attract better collaborators than those who arrive with a deck. Every time. The prototype does not close the deal. But it opens a door that no amount of slides can open.

Building something is not proof that your product will succeed. It is proof that you are the kind of person who builds. And in the earliest stages, that is the only proof that matters.