$2.7M in Pipeline Built, More Than the Team Had Produced Before

An agency managing 50 or more WordPress sites migrates a portfolio, not a website. One conversation moves dozens of properties and carries renewal weight for years. In a raw lead count that agency looks identical to someone launching a personal blog, so any team optimizing for volume drifts toward the cheapest lead and away from the only accounts that change the revenue line.

The incumbents had the budget to saturate the biggest metros. Every agency in New York, London, and San Francisco was already receiving outreach from better-funded competitors weekly. Competing there meant paying the highest acquisition cost for the least attentive buyer.

The person deciding where a portfolio of sites lives is not a marketer. It is a DevOps lead, an engineer, or a senior WordPress developer who has already survived a bad migration and evaluates every infrastructure claim on merit. Send that buyer marketing language and the pitch is dead on the first line—not because the product is wrong, but because the sender clearly does not do the job. Speaking the language fluently was a prerequisite for the motion, not a polish step at the end.

The account universe was split into Tier 1, Tier 2, and Tier 3 cities, then deliberately weighted toward Tiers 2 and 3. Agencies in those markets run the same size portfolios and carry the same infrastructure pain, but almost nobody was selling to them. Reply rates reflected that immediately—this was an arbitrage play on attention, not a discount play on price.

By hand, then verified. Search Google for web development agencies in a given city, open each agency site, and pull the details that mattered: portfolio size, client type, decision maker, contact path. BuiltWith and SimilarTech confirmed the part that decided everything—whether the sites in that portfolio actually ran WordPress, and what host and plugin footprint sat underneath. Outreach could then reference the real stack instead of guessing at it. This predated scraping bots, Clay, and the enrichment layer teams now take for granted; tech-stack lookups were the closest thing available, and they were enough to make every email specific.

Kinsta and WP Engine publish their agency and partner directories. Every name in those catalogs was an agency already paying for managed WordPress hosting at volume—qualified, budgeted, and running the exact portfolio profile the ICP called for. A dedicated competitive email campaign worked that list with switch-and-consider messaging built on self-healing and autoscaling infrastructure rather than price, giving the motion a second account universe that required no discovery to identify.

The messaging was sourced where the buyers actually talk. Active participation in agency, DevOps, and WordPress developer communities on Facebook and LinkedIn surfaced what this audience complained about in their own words: traffic spikes taking sites down, plugin conflicts, migration risk, the cost of babysitting uptime, and what self-healing and autoscaling would have to prove before anyone trusted them. That language went straight into product marketing copy, email sequences, and social touches. Campaigns accelerated because the copy read like it came from someone inside the work rather than someone selling into it.

Email sequences, LinkedIn and Facebook social touches, and affiliate partnerships were wired to reinforce each other against the same named accounts, with the MarTech stack automating MQL and SQL tracking, CTR, opportunities, demos, and trials. Automation carried repetition; the manual effort stayed where judgment mattered—research, messaging, and discovery.

Fit before engagement. Sites under management, client profile, technical requirements, and market tier were weighted above clicks and opens. Engagement tells you when someone is paying attention; fit tells you whether attention is worth a Sales Engineer's hour. With one closer, that distinction decided the number.

$2.7M in potential customer lifetime value across nine months, concentrated in large agencies and high-value accounts. Set against a business doing roughly $2.6M in 2023 and $3.2M in 2024 by third-party estimate, that single seat generated more pipeline opportunity than the team had produced before it.

The monthly lead KPI was exceeded by 25%, consistently rather than in one spike, because the tiered-city model kept producing fresh accounts instead of recycling the same saturated list. Messaging pulled from the developer and agency communities kept response rates from decaying the way generic sequences do—each new cohort heard language they recognized.

Closing conversions rose 20%. Nothing about the pitch changed. The Sales Engineer simply stopped spending time on accounts that were never going to migrate a portfolio, and started every call with research already attached.