AI Sales Agent Example

Measure whether an AI-assisted sales workflow creates enough revenue to justify model, tool, and human review costs.

AI sales agents can research accounts, enrich leads, qualify opportunities, and prepare follow-up before a human ever touches the deal. That work has a real cost: model calls, enrichment tools, contact search, and review time. The business question is whether the agent creates enough qualified pipeline or converted revenue to justify that spend.

This example simulates a sales funnel — prospecting, qualification, and close-prep — and ties model spend, enrichment cost, and human review cost back to a converted revenue outcome. Some jobs convert; the rest complete without revenue, so the funnel economics stay visible.

For the broader outcome-measurement pattern across these examples, see the overview page.

What You'll See

When the run completes, these Revenium views populate with the demo data:

• ROI dashboard — total agent cost vs. converted revenue, with a value ratio for the sales workflow.

• Conversion Funnel — converted vs. unsuccessful jobs across the run.

• Cost Composition — split between AI model spend, enrichment tool spend, and human escalation cost.

• Tool Cost ratio — share of cost driven by Zoominfo / Apollo / SDR handoff vs. the model itself.

• Traces — per-job sequence of prospecting → qualification → close, with parent/child step linkage.

• Agent decision costs & Tool usage — role-level attribution for the sales agent and its tools.

Run It

The example scripts ship in the public SDK repo, not on PyPI. Clone the repo first, then run from inside it:

git clone https://github.com/revenium/revenium-python-sdk.git
cd revenium-python-sdk
pip install revenium-python-sdk
python examples/agentic_outcomes/sales.py --count 5

Set REVENIUM_API_KEY (a write-scope key, rev_sk_…, generated at app.revenium.ai → Integrations) before running. Use --dry-run or --plan to preview without sending data.

View The Source

The runnable scenario lives in the public SDK:

• sales.py — github.com/revenium/revenium-python-sdk/blob/main/examples/agentic_outcomes/sales.py

• Shared runtime (common.py) — github.com/revenium/revenium-python-sdk/blob/main/examples/agentic_outcomes/common.py

• Examples README — github.com/revenium/revenium-python-sdk/blob/main/examples/agentic_outcomes/README.md

Customize

The top of sales.py exposes the customization points: SUBSCRIBER, LLM_STEPS, TOOL_STEPS, the conversion rule in pick_outcome, and the metadata fields in build_metadata. Tweak these to match your sales motion (your model mix, your enrichment vendors, your conversion rate, your average deal size). For the full TUNABLES reference and recipes, see the TUNABLES section of the examples README.

Why This Matters

Sales teams rarely need another token chart. They need to know whether the agent helped create pipeline, whether expensive enrichment was worth it, and where human review changed the economics. This example connects operational evidence from the trace with the business result reported on the job.

Related Views

• ROI and unit economics

• Logs and traces

• Agent decision costs

• Tool usage

Notes

• Values are illustrative demo values, not performance or ROI guarantees.

• Use a demo team or clearly named demo data for first runs.

• Prompt details in the UI depend on your workspace prompt-capture settings.