Sales · Self-hostable

AI teammates for sales and customer success.

Scan accounts approaching renewal, surface usage and sentiment changes, and recommend next steps.

Connects to
ChannelDiscordGitHubGmailGoogle CalendarGoogle ChatHacker NewsLinearMicrosoft TeamsPostgreSQLProduct HuntRedditRepositoryRSS / AtomSlackTelegramWhatsApp CloudX (Twitter)YouTube+3 more
Why Lobu

Catch what you'd miss.

Most stacks make agents call MCP every turn to reconstruct state. Lobu ingests connectors and webhooks into one append-only log first — so agents resume where the org left off.

See source
1

Connect your data

Pick the systems it can read. Lobu turns those updates into live customer memory.

HubSpotStripeZendeskGmailGoogle DriveGitHubNotionSnowflakePostgreSQL50+ more
Use existing connectors, or let your agent write code to connect any data.
Watching changes across every sourceConnector SDK
2

Define the goal

Tell it what to watch for and when to ask before acting.

“Watch every account for churn risk. If renewal is within 30 days and health drops, draft a CSM check-in for approval.”

Runs every weekday · 9:00Watchers
3

Lobu works autonomously

It scans memory on schedule, spots the account at risk, and keeps the evidence attached.

Acme Corp
Jordan Lee, VP Eng
at risk
plan Enterprise · 120 seatsrenewal Jun 30 · 21 days
Derived from recent events:
"API latency on /sync" ticket opened
2d ago · Zendesk
Logins fell 38% over 14 days
5d ago · Product
Renewal date set to Jun 30
9d ago · CRM
Globex Inchealthy
+ 17 more customersMemory & entities
4

You review and approve

You can edit the draft, send it, or leave it.

R
Revenue agent
online
Heads up: Acme Corp is trending toward churn. Logins are down 38% over 14 days and their renewal is in 21 days. Want me to draft a check-in for their CSM?12:01
Yes, and include the usage drop.12:01
Drafted. Saved it to the Acme account and pinged @dana.12:01
Replies in your team's chat, or your own app over the API:
For engineers

The whole agent, in code.

One project defines it end to end: the agent, its connectors, the memory schema, watchers, and skills. Write it yourself, or let your coding agent generate it. Pick a piece to read the code.

lobu.config.tslobu.config.ts
import {
  connectorFromFile,
  defineAgent,
  defineConfig,
  defineEntityType,
  defineRelationshipType,
  defineWatcher,
  reactionFromFile,
  secret,
} from "@lobu/cli/config";
import type SalesforcePipelineConnector from "./salesforce-pipeline.connector.ts";
import type accountHealthMonitorReaction from "./account-health-monitor.reaction.ts";

const sales = defineAgent({
  id: "sales",
  name: "sales",
  description:
    "Help revenue teams track account health, rollout progress, and renewal signals",
  dir: ".",
  providers: [
    {
      id: "anthropic",
      model: "claude/sonnet-4-5",
      key: secret("ANTHROPIC_API_KEY"),
    },
  ],
  network: {
    allowed: [
      "github.com",
      ".github.com",
      ".githubusercontent.com",
      "registry.npmjs.org",
      ".npmjs.org",
    ],
  },
});

// entity types and relationships defined here…

const accountHealthMonitor = defineWatcher({
  agent: sales,
  slug: "account-health-monitor",
  name: "Account health monitor",
  schedule: "0 */12 * * *",
  notification: { priority: "high", channel: "both" },
  tags: ["sales", "health", "renewals"],
  minCooldownSeconds: 1800,
  reaction: reactionFromFile<typeof accountHealthMonitorReaction>(
    "./account-health-monitor.reaction.ts"
  ),
  prompt:
    "Poll CRM data for tracked accounts. Track expansion progress, risk level changes, and renewal timeline.\n",
});

export default defineConfig({
  connectors: [
    connectorFromFile<typeof SalesforcePipelineConnector>(
      "./salesforce-pipeline.connector.ts"
    ),
  ],
  org: "sales",
  orgName: "Sales",
  orgDescription:
    "Help revenue teams track account health, rollout progress, and renewal signals",
  agents: [sales],
  entities: [organization, product, region, renewalRisk, team],
  relationships: [affects, expandedInto, runs],
  watchers: [accountHealthMonitor],
});
04/EXAMPLES ]

Explore agent workflows.

Each example shows the sources, the memory, and the action for one AI teammate. Same loop — connect, watch, act — pointed at a different job.

01Sales

Tracks account health, rollout progress, and renewal signals across the customer base.

Sources
HubSpotStripeZendesk
Draftsa CSM check-in when a renewal nears and health drops.
Fork this agent →
02Legal

Reviews incoming contracts, summarizes risk, and surfaces missing protections before sign-off.

Sources
DriveGmailDocuSign
Flagsmissing clauses and routes them for review.
Fork this agent →
03Finance

Reconciles data across systems, explains variance, and prepares recurring reporting runs.

Sources
StripeSnowflakePostgres
Preparesa variance summary ahead of the monthly close.
Fork this agent →
07/RUN ANYWHERE ]

Local, self-hosted, or managed.

The same project runs on your laptop, in your cloud, or fully managed by lobu — your data and controls stay wherever you need them.

Local

Run on your laptop.

One command boots the gateway, workers, memory, and embeddings.

Self-host

Run in your cloud.

Docker, a cloud VM, or Kubernetes when data and controls need to stay with you.

lobu Cloud

Let lobu run it.

The same project with managed isolation, secrets, and upgrades — nothing to operate.

09/FROM THE BLOG ]

Latest blog posts

Give every teammate a colleague.

Paste the setup prompt into Claude Code — lobu.config.ts, role files, and channels land in your repo. Ship it today.

Start building
Status:// provisioning…