AI teammates for sales and customer success.
Scan accounts approaching renewal, surface usage and sentiment changes, and recommend next steps.
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 sourceConnect your data
Pick the systems it can read. Lobu turns those updates into live customer memory.
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.”
Lobu works autonomously
It scans memory on schedule, spots the account at risk, and keeps the evidence attached.
You review and approve
You can edit the draft, send it, or leave it.
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.
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],
});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.
Tracks account health, rollout progress, and renewal signals across the customer base.
Reviews incoming contracts, summarizes risk, and surfaces missing protections before sign-off.
Reconciles data across systems, explains variance, and prepares recurring reporting runs.
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.
Run in your cloud.
Docker, a cloud VM, or Kubernetes when data and controls need to stay with you.
Let lobu run it.
The same project with managed isolation, secrets, and upgrades — nothing to operate.
Latest blog posts
The Agent Loop Is the New SaaS
The business logic SaaS sold you is now an agent loop that watches your data and acts. Here is how to build and own one with Lobu.
Read post →Shopify's Aquifer, in the Open
Shopify treats an agent's corpus as the compounding asset. Lobu keeps the signal—not the chat—and makes that architecture work across companies.
Read post →Filesystem vs Database for Agent Memory
Agents need a workspace to think in and a warehouse to remember in. The filesystem is for ephemeral work. The memory layer is for durable organizational knowledge.
Read post →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.