The company profile below is composited to preserve anonymity while preserving the strategic and numeric truth of the engagement.
Composite Company Profile
Series B embedded-finance API platform. Roughly 90 employees, ARR in the low eight figures, ACV between $60K and $180K depending on transaction volume. Their customers are fintech operators, vertical SaaS platforms, and marketplaces embedding payments, KYC, and ledger primitives into their own products. Highly technical audience: staff engineers, VPs of platform, and CTOs evaluate the product, and legal or compliance signs off before contracts close.
The Problem
The company had strong bottom-of-funnel conversion when developers landed on the docs, but the top of the funnel had gone flat. Organic traffic had plateaued for four consecutive quarters at around 42,000 monthly visits, and non-branded impressions were declining month over month against a backdrop of well-funded competitors publishing aggressively. Paid CAC had crept from $18K to $27K over the same window, and the CFO had capped further paid expansion until organic could carry more of the pipeline load.
Two prior efforts had failed. A freelance content agency had shipped 60 marketing-flavored blog posts over 18 months that ranked for terms no engineer searches. A separate in-house attempt to publish developer tutorials stalled after four posts because engineering did not have bandwidth to review, and marketing did not have the technical literacy to ship without review.
What Our Team Diagnosed
Our SEO and content team ran a full topical audit, a SERP intent breakdown across 380 target terms, and a technical crawl of the docs subdomain. Three root causes surfaced that the client had not seen.
First, the domain was competing against itself. The docs subdomain and the marketing root domain were both trying to rank for the same integration-oriented queries, and Google was oscillating between them, suppressing both. Second, the taxonomy of the developer content was written from the platform’s perspective (product names, internal module names) rather than the language engineers actually type into search. Third, the site had no programmatic layer at all. Competitors were publishing hundreds of thin but well-structured pages targeting the long tail of “use case + industry + primitive” queries, and this client had zero coverage there.
Strategy MV3 Shipped
Engagement was our Growth AI tier plus a scoped programmatic SEO build-out. Three parallel workstreams.
The consolidation workstream mapped every URL on the docs subdomain and the marketing root to a single canonical intent, added 301s where duplication existed, and rewrote the internal linking model so that top-of-funnel content flowed authority into a single canonical set of solution pages. This alone recaptured rankings that had been split.
The content workstream shipped a 90-day editorial calendar of engineer-authored deep dives on integration patterns, ledger design decisions, KYC flow trade-offs, and reconciliation architecture. Each post ran through a technical reviewer inside the client’s engineering org for accuracy, but our team owned the drafting, outline, SEO structure, schema markup, and publishing. That unblocked the bottleneck that had killed the prior in-house effort.
The programmatic workstream built a data-driven page factory. We modeled a two-axis matrix (industry vertical by API primitive) and generated 340 templated pages, each hand-tuned with a distinct value proposition, three code samples, an integration checklist, and a domain-specific FAQ. Every page was schema-marked with TechArticle, HowTo, and FAQPage JSON-LD.
Implementation
Weekly cadence. Two long-form technical posts per week from our content pod, technical review turnaround under 72 hours via a shared Notion workflow, and a fortnightly programmatic page batch of roughly 30 URLs. Our analytics team stood up a GA4 property with cross-domain tracking between the marketing site and the docs subdomain, wired up Search Console for both properties, and built a Looker Studio dashboard that combined GSC impressions, GA4 signup events, and Salesforce opportunity data pulled via a nightly n8n workflow.
Rank tracking ran through Ahrefs with a custom keyword set of 620 terms tagged by intent (informational, integration, comparison, industry). Weekly reports flowed to the client’s head of marketing and VP of platform. MV3’s senior team oversaw the engagement, our SEO lead ran the content pod, and our analytics engineer owned the reporting stack.
Outcomes
Over a nine-month window measured from kickoff to the end of month nine:
- Non-branded organic traffic grew from 42,000 to 187,000 monthly visits, a 4.5x lift.
- Non-branded organic-sourced signups grew from 118 per month to 604 per month, a 5.1x lift.
- Sales-qualified opportunities attributed to organic (first-touch and last-touch blended) grew from 9 per month to 41 per month.
- Blended CAC across paid and organic dropped from $27K to $16.4K, a 39% reduction, driven by organic carrying a larger share of pipeline.
- Top-3 rankings on the priority keyword set grew from 34 terms to 218 terms.
The programmatic layer contributed roughly 44% of the traffic lift and 31% of the signup lift, validating the thesis that industry-by-primitive coverage was the largest unclaimed surface.
Timeline
Nine months from kickoff to the outcomes above. Consolidation work closed in month two. First traffic inflection landed in month four. The programmatic layer began contributing meaningfully in month six once Google finished indexing and re-crawling the templated URLs.
Composite Testimonial
“They understood our stack well enough that our engineers stopped resisting content review. That was the unlock. The programmatic build shouldn’t have worked as well as it did, but they modeled the intent correctly and the numbers followed.” – Priya, VP of Growth
How this profile is built
This profile is a composite, built from patterns and outcomes across multiple engagements rather than one client account, so there is no individual client identity behind it to protect and no further non-public data being withheld. If you want to see how a similar diagnostic maps to your own numbers, book a discovery call.
Ready to run the same playbook?
If your API or developer-first platform has plateaued and paid CAC is climbing, our team can diagnose whether the same three-part strategy applies. Book a discovery call or review our AI SEO agency and Growth AI service pages.
