$1.8M
ARR · 9 months from $0
Replicado shipped a developer-facing AI assistant for test-data generation. They had a working product, a Y Combinator alumni network and a launch that produced 187 sign-ups across three weeks. After that, sign-ups went flat. Twelve paying customers in month two. Eight in month three.
The team had been positioning Replicado as "AI for developers." Every other AI-native SaaS launching that quarter used the same phrase. The category was loud. The positioning didn't differentiate.
When we ran the audit we found a sharper hook. Replicado's actual job was solving the test-data problem. Developers don't want AI. They want fewer broken staging environments. Most of the launch content had buried that.
"We were too close to the product. TG3 watched ten of our demos and told us what we should have been saying. We changed the website in week two."
Three interventions. Repositioning. Intent-led paid. A 24-piece content arc that ran top-of-funnel for the new category framing.
"AI for developers" out. "Test-data automation for distributed teams" in. Homepage rewritten in week two. Landing pages restructured around the test-data problem, not the AI capability.
LinkedIn killed in week one. Meta never started. We ran Google search on "synthetic test data," "staging environment fixtures," and 40 developer-intent queries. Reddit ads on r/devops, r/backend and three programming-language subreddits.
24 pieces over six months. Half technical comparisons. Quarter editorial pillars on the test-data problem. Quarter integration guides for popular frameworks. All by writers who had shipped backend code.
The original 6-step onboarding moved the user away from the value moment. We collapsed it to two steps. First commit landed in 90 seconds. Free-to-paid conversion doubled.
Three co-founder interviews on the test-data problem. Hosted by alumni newsletters with developer readership. Each one drove ~140 sign-ups and backlinks from category-relevant sites.
Sign-ups crossed 300/month by month three. By month six they were converting at 9.4% to paid. Month nine ARR hit $1.8M. Replicado closed a Series A on the back of the numbers.
| Lever | Before | After | What moved it |
|---|---|---|---|
| ARR | $0 | $1.8M | Category positioning rebuild + 9 months of execution |
| Pipeline · weekly | $0 | $340K | Intent-led paid + value-led content |
| LinkedIn CTR | 0.4% | 2.1% | Renamed the category in the ad headline |
| Demo-to-paid | n/a | 38% | Value-led demo flow + qualifying questions |
| AI citation share | 0% | 18% | Original positioning content + AEO structure |
| CPM blended | $84 | $41 | Cut Meta and Twitter, kept LinkedIn and Google |
A clean engagement still leaves notes. Three things we'd do earlier next time.
An AI SaaS launch is not the same as a B2B SaaS launch. The category itself is moving every quarter. Buyers don't know what to compare to. Most launches fail because the founder builds a great product, ships it into a noisy category and assumes the AI gold rush will carry it. The AI gold rush does not carry anyone. The AI SaaS launch case study below is what happens when you stop assuming and start naming the category yourself.
Three differences shaped this engagement. First, the AI SaaS buyer does not have a clear category yet. They will compare you to anything that vaguely sounds similar. The launch fix was to rename the category before the buyer named it for us. Second, AI-native paid acquisition behaves differently. The audience overlaps across platforms, the keywords trend weekly and CPMs move with each model launch. We rebuilt the paid strategy around intent signals, not awareness. Third, AI SaaS content has to be technical enough that engineers respect it but accessible enough that economic buyers can defend it. Value-led content (built around outcomes, not features) outperformed feature comparison content by 4x.
Category positioning, intent-led paid, value-led content. The three-part AI SaaS launch model that works when the AI gold rush does not. See the SaaS paid acquisition methodology →
The client built an AI-native SaaS product, launched publicly and watched three sales weeks pass with no pipeline. The product worked. The waiting list had been strong. The launch landed in a category so noisy that nothing stood out. Founder was three months from running out of runway when the audit started.
Nine months from kickoff to $1.8M ARR. First closed-won at week 5 after category repositioning. First six-figure deal at month 4. $1M ARR milestone at month 7. The compound effect of category ownership took roughly four months to land.
This engagement ran the full SaaS marketing retainer at $7,500/month plus ad spend of $32,000 monthly across LinkedIn and Google. Total client spend across 9 months was approximately $355,000 inclusive of ad spend. ARR generated in the same period was $1.8M, so payback was inside the first six months.
Five of the seven services. SaaS paid acquisition (LinkedIn and Google, intent-led after category rebuild). SaaS content marketing (value-led pieces, two per week). SaaS positioning work (renaming the category, a discovery-stage product). SaaS CRO (trial flow and pricing page tests). SaaS analytics (warehouse attribution from week 4).
Sometimes. The result depended on a working product, a defined ICP, and a founder willing to be told the category they thought they were in was the wrong one. Without those three preconditions the playbook does not apply. The audit call is built to tell you before any commitment.
Yes in three ways. Category positioning matters more because AI buyers don't have stable category labels yet. Paid acquisition behaves differently because CPMs and keywords move with each model launch. Content has to clear both the engineer's skepticism and the economic buyer's defensibility test.
Three calls we'd make sooner. First, run the positioning audit before the launch, not after the three flat weeks. Second, start paid in week 1 after positioning, not week 4. Third, pre-record the value-led content library in month 1 instead of writing in real-time. The corrections shave 6 to 8 weeks off the timeline.