The stack that turns a demo-request form into a meeting on the right rep’s calendar before the buyer closes the tab. Four layers: a router that enriches, qualifies, and books in one pass; Salesforce as the record of ownership; Slack as the alarm; and, for sites with the traffic to fund it, a live conversation agent in front of the form. The 2026 version of this stack has a fork the 2025 version didn’t — Salesforce closed its acquisition of Qualified on April 1, 2026, so the conversation layer and the CRM are now one vendor.
Speed is the entire design goal. The Oldroyd lead-response study (MIT/InsideSales, 2007, over 15,000 leads across 100+ companies) found responses inside 5 minutes were about 21x more likely to qualify the lead than responses at 30 minutes. That is vendor-platform data rather than a controlled trial, so treat the multiplier as directional — but it is why this stack is built around a sub-minute path instead of a nightly sync.
How the pieces fit
- Default is the router under roughly 15 revenue-facing seats. Form, real-time enrichment, ICP qualification, territory and ownership routing, and booking on one canvas, with assignments resolving in about 400ms and routing rules written in natural language instead of branching field logic. Growth is a ~$500/mo platform fee with 20K enrichment credits a year; seats are $45 (routing plus scheduling) or $20 (scheduling only), and admin and editor seats are free.
- Chili Piper is the router above that line, and the only one of the two with a bundled account-identification layer. Its 2026 repricing folded the old Concierge, Distro, and Handoff SKUs into two tiers: Routing & Scheduling at $1,250/mo ($15,000/yr, 15 seats, 45,000 AI credits/yr) and Experiences at $3,500/mo ($42,000/yr, 30 seats, 150,000 credits), which adds 24/7 AI qualification, live calling from the form, account identification, and ABM targeting. Annual billing only; additional seats run $45-50/mo.
- Qualified is the optional conversation layer in front of the form. Piper, its AI SDR agent, opens a chat, voice, or video conversation on high-intent pages, qualifies against live Sales Cloud data, and books in-session. Salesforce completed the acquisition on April 1, 2026; Qualified still sells standalone as Premier, Enterprise, and Ultimate, demo-gated, and its own pricing page carries no Agentforce branding as of this writing.
- Salesforce is the ownership record the router reads from and writes back to. Territory, account owner, open opportunity, and lead status are the inputs that decide the routing outcome; the booked meeting, the resolved owner, and the enrichment payload are the outputs. Sales Cloud Enterprise is $175/user/mo billed annually, Unlimited $350.
- Slack is the alarm, not a notification nicety. The owning rep gets the booked meeting with the enrichment payload attached, and — the part teams skip — any lead that fails to resolve an owner fires into a staffed fallback channel. Pro is $7.25/user/mo annual, Business+ $12.50.
The handoffs that make it a stack
Form submit → the router enriches the contact against connected providers and scores it against your ICP rules → the record matches to an account owner or a round-robin pool read from live Salesforce data → the qualified visitor sees that rep’s calendar in the same session and books. The router then writes owner, source, and enrichment payload back to Salesforce as one record, and posts to Slack twice: the meeting to the owning rep, and any unresolved lead into a fallback channel with a named human on rotation. A no-show or reschedule returns to the router for a re-offer rather than landing in somebody’s inbox.
Run the conversation layer and the front of the chain changes, not the back. A visitor hits a pricing or product page, Piper opens the conversation, reads ownership from Sales Cloud, qualifies live, and books — then the same Salesforce-write and Slack-alert tail runs unchanged.
The arrow carrying the value is the second one. Enrichment without routing produces a well-described lead nobody owns; routing without the Salesforce write produces a booked meeting the forecast cannot see.
Why this combination
The status quo it replaces is a form on a marketing site, a nightly sync, a shared inbox, and a scheduling link pasted into a reply. That loses on both axes this stack optimizes: elapsed time to the calendar, and correctness of assignment. Adding a scheduling tool alone fixes the first and not the second — the rep who books is whoever answered, not the account owner, and the territory dispute surfaces a week later in pipeline review.
The router is the spine rather than the chat agent because routing errors are the more common bottleneck. A missing owner, a territory the rules cannot resolve, or a round-robin that assigns to a rep on PTO breaks the chain no matter how good the conversation was. Buy the conversation layer when the site produces enough high-intent sessions to fund a six-figure contract; buy the router first regardless.
What it costs
Three tiers, set by which router you run and whether you add the conversation layer.
Lean (5-15 revenue-facing seats, Default spine): about $32K-$40K/year all-in. Default lands at $765/mo for five routing seats plus two scheduling-only seats, or ~$9.2K/yr. Salesforce dominates the bill — 10 Enterprise seats at $175/user/mo is $21K/yr. Slack Pro across a 25-person company adds ~$2.2K/yr. The CRM is roughly two-thirds of the total, which is the number that surprises teams shopping routers.
Mid-market (15-30 seats, Chili Piper spine): about $77K-$105K/year. Chili Piper’s floor is now $15K/yr and its qualification-and-ABM tier is $42K/yr; 25 Salesforce Enterprise seats are $52.5K/yr; Slack Business+ across 60 people is ~$9K/yr. Multi-year Chili Piper commitments discount 15% (2 years), 25% (3 years), and 40% (4 years) — real money, and the reason its sales motion pushes term length.
Conversation-first (Qualified added): about $100K-$150K/year. Public benchmarks put Qualified Premier at $40K-$68K/yr list for roughly 25 users, with negotiated deals landing closer to $40K-$50K, and it sits on top of Salesforce rather than replacing any line. Routing the same work through Agentforce instead meters at $2 per conversation or Flex Credits at $500 per 100K, about $0.10 per action.
Three hidden lines. Default’s enrichment pool on Growth is 20K credits a year, about 1,600 a month, so a site taking 1,000-plus submissions a month gets pushed to Scale or a Web Intent add-on. Chili Piper bills annually with no monthly option and no free trial, so a bad fit is a 12-month bad fit. And Salesforce seats accrue for people who only need to be routed to — every SDR added to a round-robin pool is another $175/mo.
When this stack is the right pick — and when it isn’t
Pick it when inbound demo requests run 100+ a month, Salesforce is the system of record, and you have written territory or account-ownership rules a machine can evaluate. That combination is where the sub-minute path pays back.
Skip it in three cases. Under 30 inbound requests a month, a scheduling link and a Slack alert do the same job for the price of the Slack seats, and the router’s platform fee has nothing to amortize against. If nobody owns the routing rules, the stack automates an unresolved territory argument and then gets blamed for the outcome — write the rules first, per lead routing. And if you are product-led rather than form-led, the entry point is a signup and not a demo request; the product-led sales stack is the right reference.
Common variations
- HubSpot instead of Salesforce. Both routers support it; Qualified does not survive the swap, because Sales Cloud depth is what justifies its price. Swap when your CRM is not Sales Cloud, and either drop the conversation layer or replace it with a HubSpot-native chat.
- Deeper enrichment. Point Clay at the inbound row for waterfall enrichment and AI research the router’s built-in providers do not cover — see lead enrichment with Clay and Claude. Swap when the ICP test needs more than firmographics.
- Self-built triage. Run the qualify-and-alert path on n8n instead — see inbound lead triage. Swap when volume is low enough that the router’s platform fee exceeds the ops time, and accept that you now maintain the calendar logic yourself.
- Agentforce-native. If you are already committed to Agentforce, get Salesforce to state on paper how Qualified converges into it before signing a standalone multi-year Qualified deal. Post-close, that is a pricing question, not a product question.
What this stack does NOT replace
- Demand generation. The stack converts inbound; it does not create it. A site with no high-intent traffic gets a faster path to the same zero.
- The ICP and scoring rubric that decides who qualifies — see lead scoring and MQL vs SQL, plus the ICP rubric Skill for a runnable version.
- The territory and ownership model itself. The router executes rules; it does not adjudicate them.
- CRM hygiene. Unresolvable ownership in Salesforce is the most common cause of a lead landing in the fallback channel.
- Marketing automation for the leads that do not qualify. This stack books the ones that do and hands the rest back.
- The post-booking sales motion. Call recording and coaching belong to Gong and the conversation intelligence stack.