I've been building Velor — an AI customer support agent for small B2B SaaS teams — for the past several months. The product works. Getting first customers has been harder.
Here's what I got wrong.
The mistake: targeting up-market
I got excited about logos. Sent cold email to founders at Rippling, Gusto, Deel, Mercury — 50+ emails to companies with 100+ employees. Zero replies. Then I tried the "50-200 employee" band. Still zero.
The issue wasn't the pitch or the copy. It was the target. Companies that size have:
170 emails, 0 replies confirmed what I should have known from the start: these weren't my buyers.
What actually works: 2-10 person founder-run teams
When the FOUNDER is personally answering support tickets, the dynamic is completely different:
Our first trial customer: a 2-person fintech company. The founder was spending 4 hours a day in their support inbox. Velor deflected 70% of those tickets in week one without a single wrong answer.
The product:
Velor trains on your docs and answers customer questions grounded in what's actually in your knowledge base — not hallucinated answers. It also takes real actions (looks up orders, escalates tickets, files disputes) instead of saying "please contact support."
If you're a 2-10 person team with paying customers and you're the one answering support questions: velorplatforms.com → "speak with an agent" (no signup, live demo, 30 seconds).
Happy to talk or share more about what I've learned. Posting here partly because IH is full of exactly the founders I'm looking for.
The shift from logos to founders who feel the pain daily is the whole game for early B2B sales. Good instinct measuring pain by who personally answers the tickets.
170 emails and 0 replies is a strong signal that the ICP or messaging needs refinement. I’d validate the audience and their actual pain points before scaling outreach. I use SERPSpur’s SEO Audit Tool to identify website issues and opportunities that can also help qualify prospects.
Agreed -- and that's exactly what the post is about. The mistake wasn't sending 170 emails, it was sending them to the wrong buyer type before validating who actually felt the problem personally. The companies I was targeting were too big and too funded, which meant support had already been delegated to a dedicated hire. The founder wasn't feeling the pain anymore.
Once I narrowed to founders still personally answering customer emails -- smaller, earlier-stage -- the reply rate changed completely. Same email structure, different list. The ICP shift did more work than any copy change would have.
The validation lesson: if you can't identify who feels the problem personally (not just who has the problem in their org), you're probably targeting the wrong layer.
The founder-run threshold is the real signal, not company size. We see the same split. A founder who is still doing the day to day work feels every hour a bad process costs, so a tool that removes four hours a week sells itself in one call. Once there is a dedicated person or team doing that job, the buyer stops feeling the pain personally and the decision turns into a committee exercise. Curious whether you found the same drop off once support gets handed off internally, even inside your 2 to 10 person range.
Yes, the handoff shows up even within the 2-10 range. The inflection is usually when someone starts saying "my team is spending time on this" instead of "I'm spending time on this." That pronoun shift is the tell -- it's moved from personal pain to managed cost, and the buy cycle lengthens noticeably from there.
On cold outreach, the best pre-call signal I've found is whether the founder's name shows up answering in their own public channels or forums. If they're still doing it publicly, the pain is personal. If all the answers come from support@ or a team member, it's already been delegated.
The shift from logos to founders who feel the pain daily is the whole game for early B2B sales. Good instinct measuring pain by who personally answers the tickets.
It's useful because it's observable before the call. You can check whether the founder's name shows up in their own support threads, community channels, or IH comments. If it does, the pain is still personal. That turns "founder feels the pain" from a retrospective diagnosis into an actual targeting criterion you can apply before reaching out.
The founder-signal problem. Large companies already outsourced the pain. When you're addressing a 50+ person company, support is someone else's job - they're not motivated to change because it's not their time cost. But a founder answering support tickets themselves? That's immediate, felt pain. The 2-10 person founder-run band works because the pain is personal and the solution is obviously worth its weight. This is why broad cold outreach fails - you're fishing in a sea of people who don't actually feel the problem. Narrowing to "founder answering their own support" filters for founders who need this today, not someday.
"Today, not someday" is the actual ROI question. "Someday" buyers run the idea through a quarterly planning process and it competes with ten other priorities. "Today" buyers close on urgency. The filter you described -- founder still in the inbox -- selects for "today" automatically, which is why the conversion rate was so different from the logo-targeting phase. The 170 emails weren't just going to the wrong size company, they were going to people for whom the problem was theoretical.
The part that stands out is not the company size, it is who is in the inbox. A founder answering their own tickets feels the cost every day, so they buy fast. Someone managing a team just files it as a backlog item. I have been doing direct one on one onboarding with early founders for a similar reason, when the buyer is also the user you skip the whole internal approval chain entirely. Would be curious whether your win rate holds once a couple of these 2 person teams grow to 10 or 15, since that is usually where the founder stops touching support directly.
The 10-15 threshold is the right question to watch. My hypothesis is the tool stays relevant if the founder is still using it personally -- even if there's now a support person, if the founder is still configuring the knowledge base and reviewing conversations, the pain is one layer up but still theirs. The risk is when it becomes fully delegated and the founder has no interaction with it at all.
Haven't had enough customers long enough to validate this yet, but it's exactly the cohort I'm watching. The leading indicator I'm tracking is whether the founder is still the one adding content -- or if that's been handed off too.
The contrast between 170 unanswered emails and the 2-person fintech is pretty stark.
Have you seen the same response from several other 2–10 person teams yet, or is that first trial customer still carrying most of the evidence behind the ICP shift?
Still mostly carrying on that first one -- I've had a few conversations with 2-10 person teams since but nothing else closed yet. So it's a strong signal from a sample of one, which I'm aware is a thin foundation to build a thesis on.
What I'm watching more than close rate right now is engagement: is the founder actually using it, are they adding content, are they seeing it resolve tickets without human intervention. The first customer is doing all of those, which gives me more conviction than if they had bought and gone quiet.
The real test will be the next two or three. If I see the same activation pattern from founder-run teams and a different one from companies where support is already delegated, that's the cleaner signal I need.