Case Study: AI SaaS · Conversational Support | Tacticalism
Case Study AI SaaS Conversational Support
Finding the right buyer is the product.

How ICP validation replaced guesswork and built a $30k pipeline — before scaling a single outbound campaign.

When you don't know who your buyer is, volume isn't the answer. Structured testing is. Here's how we found the two ICPs that actually converted — out of five.

Vertical AI SaaS
Category Conversational Support
Timeline 6 months
Approach ICP shortlisting + signal qualification
Results at a glance
Metric Before After
ICP Clarity None 2 qualified ICPs from 5 tested
Leads Generated 0 ~10/month Consistent pipeline
Pipeline $0 $30k 6 months
Buying Intent Unknown Validated Signal-confirmed
01 — The Problem

The technology worked. The question was who would pay for it.

Our client had built a genuinely capable product — an AI platform combining real-time conversation management, automated responses, context-aware guidance, and 24/7 availability through a unified interface. The technology worked. The question no one had answered yet: who would actually pay for it?

Two uncertainties were stacking on top of each other:

1
No defined ICP
The platform could plausibly serve many segments — e-commerce, SaaS, service businesses, internal teams. Without focus, every segment looked equally valid and equally risky.
2
No validated demand
Even if an ICP existed on paper, there was no evidence that segment felt the pain acutely enough to open a budget and buy.

Trying to generate leads before answering these questions would have meant spending time and money talking to the wrong people. The real problem wasn't lead volume — it was lead direction.

02 — The Insight

Assumptions made at a whiteboard don't survive contact with real buyers.

Most early-stage GTM motions treat ICP definition as a one-time desk exercise — build a persona, pick a vertical, start outbounding. The problem is that the assumptions made without buyer signals are almost always wrong in ways that only become visible after months of wasted outreach.

The only reliable way to know if an ICP will pay is to put a real offer in front of them and read the signals. We didn't need to close all five segments. We needed to find which two would lean in.

03 — The Approach

Five hypotheses. One structured test. Two winners.

We shortlisted five plausible ICPs based on use-case fit, platform pain points, and willingness-to-pay signals in the market. Each was treated as a hypothesis to be tested — not a strategy to be committed to.

E-Commerce
After-hours drop-off & cart abandonment ✓ Qualified
B2B SaaS
Support costs & agent overload at scale ✓ Qualified
Services
Response time & client communication Eliminated
Internal Teams
Internal knowledge & HR query automation Eliminated
Marketplace
Multi-vendor support & buyer queries Eliminated

Built targeted outreach per segment

Messaging anchored to segment-specific pain — response time, support costs, agent overload, after-hours drop-off. No generic pitch applied across all five.

Tracked engagement signals across all five

Reply rate, question depth, objection type, and speed of response — all tracked as data points, not impressions.

Used signals — not gut feel — to qualify or eliminate

Two ICPs showed consistently stronger signals. The other three weren't bad fits — they just weren't ready buyers. Eliminating them early saved months of wasted outreach.

What we tracked to qualify each segment
Reply Rate First indicator of segment resonance
Question Depth Active evaluation vs. passive curiosity
Objection Type Budget objections vs. timing objections
Response Speed Fast replies signal active urgency
2 Qualified ICPs — Behaviour that converted
  • Higher reply rates from the first touch
  • Substantive questions indicating active evaluation
  • Faster movement through early conversations
  • Questions indicating genuine budget consideration
3 Eliminated ICPs — Not bad fits, just not ready
  • Low reply rates despite relevant messaging
  • Surface-level curiosity without follow-through
  • Objections rooted in timing, not fit
  • Eliminated early — saving months of wasted effort
04 — What Changed

From untested hypotheses to validated, repeatable pipeline.

B4
Before The starting point

Five untested hypotheses. No outbound motion. No pipeline. No clarity on who the product was really for. Every segment felt possible — which meant none were prioritised.

1–2
Months 1–2 — Hypothesis Building Structured testing begins

Five ICP segments identified and prioritised. Targeted outreach built per segment. Signal tracking framework put in place to ensure every reply, every objection, every question was captured as data.

3–4
Months 3–4 — Signal Analysis Two ICPs emerge clearly

Signals analysed. Two ICPs qualified based on engagement depth and buying behaviour. Outreach focused entirely on the two confirmed segments — the other three retired without regret.

M6
Month 6 — Results Consistent, validated pipeline

~10 leads per month. $30k in pipeline. A repeatable outbound motion built on validated demand — not assumptions. Every conversation happening with a segment proven to lean in.

05 — The Lesson

You don't need to know your ICP before you start. You need a process to find out.

Hypothesis → Outreach → Signals → Qualification → Pipeline

Hypothesis Outreach Signals Qualification Pipeline

The mistake most early-stage teams make is either waiting too long to start (perfecting the ICP in theory) or starting too broad (blasting everyone and hoping for replies). Neither works.

The right move is structured testing: make your best five bets, go talk to real buyers, and let the market tell you which two to double down on.

ICP clarity wasn't a prerequisite to generating leads. It was the outcome of generating the right conversations first.

Work with Tacticalism

Don't guess your ICP. Test it.

We help early-stage B2B founders run structured ICP validation — so you stop burning outbound on the wrong segments and start building pipeline with the right ones.

50+ B2B companies India · US · UK No long-term contracts