The Best Collaborations Start With a Deliverable, Not a Vibe

A lot of founder conversations sound promising in the room and useless in real life. You leave the call with good energy, broad alignment, and absolutely nothing you can execute. I’ve learned to treat that feeling as a warning sign, not a win.

I recently had one of those exploratory intro calls after Amrish discovered Notis on Instagram. We talked about where Notis came from, the traction we’re seeing, where I want to take the product, how I think about the competitive landscape, and whether there could be a collaboration down the line. It was a good conversation. But good conversations are not a business model.

Why I care more about clarity than chemistry

When you are building a product in public, you meet a lot of smart people who can open doors, share ideas, and paint attractive possibilities. That can be valuable. It can also become a very expensive distraction if you confuse intellectual stimulation with actual progress.

At this stage, I care a lot less about abstract strategic help and a lot more about concrete outputs. If someone wants to collaborate, I need to understand what gets built, shipped, tested, or unlocked. Not eventually. Not in theory. In practice.

The trap of strategy without a surface area

Founders are especially vulnerable to this trap because strategy feels productive. You can spend an hour discussing markets, positioning, partnerships, and category design and feel like something meaningful happened. Sometimes it did. Most of the time, it didn’t.

If there is no clear deliverable attached to the conversation, the next step becomes fuzzy by default. Fuzzy next steps create polite follow-ups, delayed replies, and the kind of optional collaboration that dies quietly in everyone’s inbox.

That is why I was explicit on the call. I said that any collaboration would need to be tied to something concrete. A specific proposal. A defined contribution. A surface area where value can actually be measured.

What an actually useful proposal looks like

The bar is not perfection. The bar is specificity. I do not need someone to arrive with a ten-page deck and a polished grand strategy. I need them to answer a simpler question: what exactly are we doing together, and how would we know if it worked?

A useful proposal creates a timeline. It creates an output. It creates a reason to say yes, no, or not now. It can be evaluated today, in six months, or in twelve months because it is grounded in reality instead of enthusiasm.

That was the conclusion of this conversation. No agreement. No artificial urgency. Just a clear invitation to come back with something specific enough to assess against timing, priorities, and expected upside.

What this says about how I’m building Notis

Notis exists because I am obsessed with turning intention into execution. That principle applies to the product, but it also applies to how I make decisions around the company. I do not want a business built on vague potential. I want a business built on compounding proof.

That means choosing collaborations the same way I choose features: based on whether they create a concrete outcome for the user, the product, or the business. If the value is real, it should survive contact with specificity.

There is a broader lesson here for founders. You do not need to say yes to every intelligent person who wants to explore something. You need to protect focus hard enough that only real opportunities make it through. A clear proposal is not friction. It is respect.

The simplest filter I keep coming back to

Whenever a conversation drifts into possibility mode, I return to the same filter: what is the deliverable? If nobody can answer that clearly, the opportunity is probably not mature enough yet. That does not make it bad. It just means it belongs in the maybe later pile, not on this week’s roadmap.

For me, that is what this call clarified. There may be something worth doing in the future. But until there is a concrete proposal on the table, the right answer is patience.