🦦

Meet OttoBot

Your sales reps' AI research assistant.

OttoBot sits inside Slack, Teams, Discord, or Email. It knows each rep's accounts, tools, and selling style. Ask it anything and it does the legwork.

Reps Are Already Using It

These are real Slack conversations from sales reps. One message, and OttoBot pulls the research, builds the deliverable, and hands it back.

Partner Sales Playbook

Building data-driven sales plays for a partner

Slack

Matt

I'm working with the head of BD at Blee. We need a library of use cases & key sales plays that HG data can support through our partnership. Adobe Workfront in key accounts is a great example — it means they're investing heavily in content management. What else you got?

🦦

OttoBot

⚡company_technographic⚡get_vendor_information⚡search_companies

I did some digging on Blee. They're an AI-powered marketing compliance review platform — customers include Rocket Mortgage, NerdWallet, Marqeta. All heavily regulated fintech.

🦦

OttoBot

Here are 6 sales plays: **Play 1: Content Factory Signal** — Adobe Workfront, Sprinklr, Bynder = high content volume, high compliance burden. **Play 2: Compliance Maturity** — OneTrust, ServiceNow GRC = already investing in compliance infra, marketing compliance is their last gap. **Play 3: Regulated Industry** — Financial services, mortgage, healthcare companies where compliance is legally mandated. **Play 4: Marketing Automation Stack** — Marketo, HubSpot = high campaign velocity that strains review processes. Each play includes technographic signals, conversation starters, and ideal account profiles.

Matt

Can you write these out in detail? I want to paste them into a Word doc to present to my contact.

🦦

OttoBot

Here you go — full 6-play playbook with executive summary, ideal account profiles for each play, conversation starters, and HG search queries you can run directly. Ready to paste into Word.

Real conversation from a sales rep using OttoBot

What Changes When the Data Is One Message Away

Reps shouldn't need to leave Slack to pull technographics, SEC filings, or competitive intel. When they don't have to, here's what shifts.

Hours → Seconds

Account research that used to mean 30 tabs and an hour of copy-pasting now takes one Slack message.

Better Signal, Less Noise

Outreach built on real technographic data and intent signals instead of gut feel. Reps stop guessing which accounts to prioritize.

Raises the Whole Team

Your newest rep produces the same quality research as your best. Playbooks and org knowledge are baked into every agent.

How OttoBot Works

Each rep gets their own agent. Agents remember context, spin up subagents for complex tasks, and call 30+ tools through MCP. Admins manage everything from Phoenix.

💬

Slack

🎮

Discord

👥

MS Teams

📧

Sales Rep Channels ↓

Deployment & Isolation

Each customer gets its own Kubernetes namespace with its own process, secrets, and network policy. We didn't build multi-tenant code. We just gave each customer their own box.

Hosted (Primary)

Runs in our VPC on EKS. We manage the infrastructure.
One namespace per customer. Network policies block cross-tenant traffic.
We push upgrades centrally. You get new features without redeploying.
Secrets synced from AWS Secrets Manager via ESO, scoped per namespace.

On-Prem (Enterprise)

Runs in the customer's VPC. They control network egress and audit logs.
Works with their existing Vault, SIEM, and IdP for SSO.
Built for regulated industries where data can't leave the customer's network.
Identical product, just deployed inside the customer's perimeter.

Key Capabilities

Multi-Channel

Works in Slack, Discord, MS Teams, and Email. No new app to install.

Per-Rep AI Agents

Every rep gets their own agent with its own memory, writing style, and account context.

Subagent Orchestration

Kicks off separate agents for research, QA, and multi-step tasks. Not just tool calls.

30+ MCP Tools

Salesforce, Confluence, HG Insights, TrustRadius, SEC filings. Connected via Model Context Protocol.

Persistent Memory

Remembers past conversations, org playbooks, and each rep's preferences between sessions.

Progressive Automation

Shadow mode first, then delegated, then full auto. You control when to hand off more.

Enterprise Security

SSO/OIDC, SOC2 compliance, encrypted credentials, full audit trails.

K8s Isolation

One instance per customer in its own Kubernetes namespace. Your data stays in your namespace.

Get Started in 3 Steps

Connect

An admin hooks up Salesforce, Confluence, and HG Insights through the Phoenix admin panel.

Personalize

Each rep links their own accounts. The agent learns their style and preferences over time.

Go

Ask OttoBot for account research, email drafts, or meeting prep. It spins up subagents for the heavy lifting.

Data Sources

OttoBot pulls from these systems through the Model Context Protocol. No custom integrations to build.

Salesforce

Pull account details, contacts, opportunity history, and activity logs.

HG Insights

Technographics, firmographics, IT spend, operating signals, and intent data.

TrustRadius

Product reviews, competitive positioning, and buyer intent signals.

SEC Filings

10-K, 10-Q, and 8-K filings. Earnings data, risk factors, executive changes.

Confluence

Internal playbooks, battle cards, and product documentation.

Google Workspace

Email, calendar, and docs for meeting prep and follow-up drafting.

Channels

Reps talk to OttoBot wherever they already work.

Slack

DM or channel — reps ask OttoBot directly in their workspace.

MS Teams

Same experience for Teams-first orgs.

Discord

For teams that run on Discord.

Email

Forward an email, get a research brief back.

Put an OttoBot on your team

We're rolling this out with design partners now. Let's talk about what it looks like for your org.