Demand-gen agencies sell to VP marketing and CMO buyers who speak in pipeline metrics, not generic awareness goals. A prospect lands and wants to confirm three things in under a minute: do you run the channels we need (LinkedIn, webinars, lifecycle, intent), have you done it for our industry and ACV, and what does a typical pipeline outcome look like. SleekAI reads your service pages, your case studies with their channel mix and pipeline outcomes, and your team bios, then answers those three questions in the same conversation.

Case studies are usually a custom post type with ACF fields for channel mix, ACV range, sales motion, and reported outcomes (pipeline, SQLs, opportunities, CAC payback). The data-source wizard maps those fields into context at retrieval time, so the bot quotes "3.1x pipeline in two quarters at $40k ACV" instead of generic adjectives. Outcomes that haven't been published stay out of the index by default, so the bot only quotes verifiable numbers.

Routing handles the post-qualifier step. Enterprise pipeline inquiries above a certain ACV get sent to the senior partner who runs that segment, mid-market goes to the demand-gen director, and self-serve audits route to a hosted form. The logs in wp_posts become a quiet feedback loop: every week the agency sees which channel combinations prospects keep asking about, including the ones where the case study library is thin.

Demand-gen buyers are some of the hardest inbound prospects to convert on a generalist agency site, because their evaluation criteria sit at a very specific intersection: channel mix, ACV band, sales motion, geo, and reported pipeline outcomes. A VP marketing at a $40k ACV B2B SaaS doesn't need a brand-story homepage; she needs to confirm in under sixty seconds that the agency has done LinkedIn plus webinars for a similar profile and produced a credible pipeline number. Most agency sites flunk that test by accident.

The case studies are organized by client logo or vertical, not by channel mix and ACV, and the homepage talks about "full-funnel growth" because that's the breadth pitch. A semantic chatbot fixes the gap without rewriting the site, because it reads the structured fields on the case study CPT and answers a pipeline-shaped question with a pipeline-shaped reply. Routing is the second lever and it compounds the first.

Demand-gen agencies usually have three or four intake flows hiding behind one contact form: enterprise pipeline retainers, mid-market diagnostic engagements, partner-channel referrals, and audits. A bot that asks two qualifying questions and sends each prospect to the right partner converts a meaningfully higher share of the same traffic, because the right human reads the right brief on the right day. Conversation logs add a quiet third benefit.

They become a structured feed of what prospects expected the agency to cover but couldn't easily confirm. Every channel combination that shows up three times in a month is a case study the agency should publish next quarter, or a service page that needs sharper positioning. The chatbot pays for itself in the first month it routes one enterprise inquiry to the right partner instead of into the wrong inbox.