Three guardrails. First, show conservative and aggressive bands with the coefficients visible, so the buyer can choose the band. Second, refuse to compute when inputs are obviously off (negative spend, impossible team size). Third, never quote a single hero number without the math. Together these make the bot defensible in a finance review rather than a marketing fantasy.

From a custom table or ACF fields you maintain. Most teams seed with public analyst data (e.g. McKinsey, Gartner, or category-specific studies), then tighten with their own case-study outcomes. The bot reads from WordPress on every conversation, so updates take effect immediately. Conversation logs help refine the ranges over time.

Yes. If the visitor mentions a tool they would retire, the bot can ask for its annualised cost and add it to the savings line. Be careful: counting retired-tool spend as 'savings' while also charging full license is the most common audit failure. The bot should show the gross and the net so the buyer can choose how to present it.

Yes. Productivity savings, error-reduction value, and risk-mitigation value all have established frameworks. The formula can convert them to dollars using stored coefficients (cost per FTE, cost per error event, etc.). Be honest about which line items are direct and which are derived, and the buyer's CFO will respect the analysis.

Yes. Add a horizon input (1, 3, or 5 years) and the formula multiplies annualised savings, optionally with a discount rate. Most savings calculators stop at year 1 because compounded savings claims age badly. If you do go multi-year, show the per-year breakdown rather than a single total, so buyers can sanity-check.

ROI is savings minus cost divided by cost. Savings is the absolute number. Many buyers want both. A common pattern is to run the savings bot first (lower friction, fewer inputs) and offer to switch into a ROI mode if the visitor wants to see net return. Multibot makes this a config change rather than a custom build.

Yes. The lead-capture hook pushes inputs, computed bands, formula version, page URL, and transcript to your CRM. The SDR opens a record that already includes 'Acme, $24M spend, 8-person team, $939k aggressive band' and writes a relevant first email instead of guessing from a form submission.

If you sell into healthcare, financial services, or other regulated verticals, scope claims carefully. The system prompt can disclaim that estimates are directional and that actual savings depend on implementation. Log retention and PII handling are configurable. SleekAI does not ship default analytics that send conversation content to third parties.