Article · Field notes
The Calendar Does Not
16 Feb 2026 6 min read
I have heard “this is very interesting” often enough to become suspicious of it.
It sounds positive. It can produce a friendly follow-up, an LOI, even talk of a pilot. Then nobody introduces procurement, nobody asks for the security documents, and the next meeting remains politely unscheduled.
The words say the deal is alive. The calendar does not.
I reach this point in the least efficient way possible: build first, then discover distribution waiting with a knife. My default move is still to ship B2C because it lets me hear the raw customer voice. Catalin Fetean describes the founder-led version here. If real people use the app, I may have an engine worth reusing.
B2C growth follows a cruel curve, though. You hit a distribution wall where organic spikes stop and paid growth gets prohibitively expensive.
For most bootstrapped B2C products with zero ad spend, the organic ceiling sits between 1,000 and 5,000 total users.
The first users can come from a good product and the right launch threads. Then the curve flattens and every new user becomes harder to find.
So I strip the UI, package the engine underneath, and take it to partners who already have the users I want. In my head the move from B2C to B2B2C takes one sentence. In a company it passes through a buyer, a champion, security, legal, procurement, and several calendars I can’t control.
An LOI is a mood
I used to count an LOI as progress. Now I treat it as a description of the mood on the day it was signed. A contract changes the business. An LOI can disappear into a folder without inconveniencing anybody.
The part I keep relearning
Until there’s a signed contract, nothing has actually happened. LOIs and warm pilots are mostly just people being polite.
My planning assumptions
I use these numbers to stop myself from declaring a deal late when it is merely behaving like a B2B deal:
- Sales cycle: 3 to 6 months for mid-market or enterprise.
- Pilot: usually 30 to 90 days. If it’s longer, the deal is dying.
- Conversion: 20% to 30% of “warm” intros make it to a signed pilot.
Reality check: the “rule of 10”
In the first 6 to 12 months of a B2B pivot, the goal isn’t scale. It’s 10 referenceable customers.
One contract per month is a big win for a founder-led team in the beginning. Each one is a separate set of technical hurdles cleared and legal walls moved. Revenue is only part of it.
| Milestone | Target Timeline | Metric for Success |
|---|---|---|
| Foundation | Months 1-3 | 50 discovery calls, 0-1 contracts |
| Validation | Months 4-8 | 3-5 active pilots |
| Consistency | Months 9-12 | 1 new contract signed per month |
The feature that turns me into a consultant
Early on, a big partner will ask for “just one custom feature” to sign the deal. If that feature only ever serves them, you’ve quietly stopped being a SaaS founder and become an underpaid consultant.
I’ve learned to say no to customisations that don’t improve the core engine for everyone. If you can’t sell the engine as-is, the engine is the problem, not the missing feature.
Silence has a price of zero
A flat no is fine. It’s the maybes that bleed you out slowly. The moment a prospect stops responding, deal value drops to zero. Silence usually means a lack of internal urgency. If they aren’t talking to you, they aren’t talking about you internally either. Close the file and move on to the next 100 emails.
Procurement is more flattering than praise
You can feel the difference between a prospect being polite and a prospect trying to get the deal through their own building. The words often sound similar. The calendar does not.
I stopped scoring the adjective and started scoring the inconvenience a buyer accepts on my behalf:
| Strong signals (the “pull”) | Weak signals (the “push”) |
|---|---|
| Asking for security documentation | ”This is very interesting” |
| Introducing the procurement team | ”Let’s touch base next quarter” |
| Negotiating specific pricing terms | Signing a non-binding LOI |
| Asking for a technical rollout timeline | Asking for more case studies |
Automating a message nobody wants
There’s a huge temptation to buy a stack of AI-powered GTM tools and blast thousands of leads. For a product without traction, if your message doesn’t resonate manually, AI just helps you fail at scale.
In the early stages, the founder is the one sending emails. You can pivot the value prop mid-conversation. You feel the ouch of a rejection. Real owners respond better to a founding engineer than a BDR.
The week-three problem
Cold outreach is a clarifier. Selling to SMB or mid-market partners, the numbers are a reality check. A healthy campaign realistically yields a 1% to 3% positive reply rate.
Send 100 targeted emails, get 2 or 3 people on calls, and the value prop is working. For a lean team, the sweet spot for founder-led sales is 50 to 100 high-intent, manual outreaches per week.
My planning math is deliberately joyless: 100 emails → 3 replies → 1 discovery call → 0.2 closed deals.
That’s roughly 5 weeks of consistent outreach for a single high-quality partner. The product usually isn’t the problem. Founders just quit around week three, before a single contract has had time to land.
The modular approach is still the cleanest way I know to build: prove the engine with users, then sell it through somebody who already has distribution. I just no longer draw the arrow between those two stages as a straight line.
On the next call, if somebody says “very interesting,” I’ll be pleased. Then I’ll look for the procurement meeting.