Your docs have answers. Your pricing has tiers. Your form asks for an email. Wengrow does the job none of them do: qualifies the buyer and routes to your AE.

The classic B2B SaaS funnel problem

Your marketing site pulls in 50,000 visitors a month. 1% fill out the "Request a demo" form. The other 99% either:

1. Try your free / trial product (great for you, if you're PLG).
2. Leave (bad for you in all models).
3. Email support with a sales question (medium-bad — your support team now has to triage).

The demo form captures anyone who clicks the button — including tire-kickers, students, competitors doing research, and champions without buying authority. Your AEs spend hours a week on non-deals.

Wengrow replaces the form with a conversation that qualifies by ICP fit, intent, and champion authority before the demo gets booked.

What the agent actually asks

For a mid-market B2B SaaS prospect:

• "What's the primary problem you're trying to solve right now?" (intent depth)
• "What company are you at?" (firmographic — we can enrich via Clearbit webhook)
• "What's your role?" (champion vs. decision-maker)
• "How many people would be using it?" (SMB / mid-market / enterprise tier)
• "When are you evaluating?" (urgency)
• "Do you have a current solution, or is this a net-new evaluation?" (replacement vs greenfield)

Based on the answers, route:

• High intent + right ICP + decision-maker → route to an AE workflow today; productized calendar scheduling integrations, starting with Calendly, are planned soon.
• High intent + wrong role → route to a PLG trial link; email the decision-maker separately.
• Low intent + right ICP → drop into a nurture sequence; revisit in 30 days.
• Out of ICP → polite decline + pointer to competitor (yes, really — builds goodwill and doesn't waste AE time).

Champion vs decision-maker — the key B2B signal

Forms ask for an email. They can't tell you if the filler is the buyer. Wengrow's agent asks about role, team size, and budget authority directly.

A PM at a prospect account is a different lead than a VP of Engineering at the same account. Both are valuable — but your AE should know which they're talking to before the call.

Per-segment deployments

Run different agents for different segments:

• One on the marketing homepage tuned for top-of-funnel.
• One on your pricing page tuned for higher intent ("you're clearly evaluating — let me get you to the right conversation").
• One on the docs / changelog tuned for existing users with upsell potential.
• One on ABM-targeted landing pages with custom-field questions specific to that account list.

Each with its own KB namespace, its own qualification flow, its own analytics. Teams already evaluating Drift or Intercom — see those comparisons for head-to-head context.

Integrations that matter for B2B SaaS

• Salesforce for the SLG motion — leads sync with account enrichment, opportunity creation, and a signed deep-link back to the conversation.
• HubSpot for marketing automation — leads drop into sequences, lifecycle stages update automatically.
• Calendar scheduling: planned soon, starting with Calendly. Today, use CRM sync, email alerts, or signed webhooks to route high-intent leads into your existing booking workflow.
• Slack for high-intent lead alerts to the sales channel in real time.
• Clearbit / Apollo / ZoomInfo for enrichment via webhook (when the prospect gives their email, enrich with firmographic data before the lead lands in Salesforce).
• Segment / Rudderstack for customer data platform integration — conversation events flow into your CDP alongside product usage.

A recommended configuration

• Tier: Pro ($1,499/mo, includes SSO) for mid-market SaaS with up to 10 deployments; Business ($2,499/mo) for higher-volume with custom AI system prompts per segment.
• Personality preset: Consultative Sales.
• Qualification fields: company size, role, use case, timeline, current solution, team size, budget authority.
• Knowledge base: marketing site, docs site (public parts), pricing page, changelog, blog posts. Avoid uploading internal sales enablement documents or customer-specific information.
• Integrations: Salesforce plus Slack/email alerts today. Calendar scheduling, starting with Calendly, is planned soon; use signed webhooks for custom routing in the meantime.