Find your next customer.
Keep the ones you have.

Connect public signals with customer conversations and activity. Your agents find opportunities, spot churn risks early, and show who needs attention and why.

Create your workspace

Open sourceSelf-hostuse Lobu Cloud

SlackAcme Co.
customer-health
MC

Maya Chen

@Lobu Which customers need our attention, and why?

LobuAPP

Meridian needs attention: usage fell 40%, SEC-142 is open, and renewal is September 30. Ask Maya to review the account; churn is not confirmed.

Data — Lobu
app.lobu.ai
Your workspace schema. Select a type to explore its records and relationships.
claude — acme

Illustrative example

60+ connectors. Bring an MCP server or let your agent build a tool with the Connector SDK.

  • Slack
  • Gmail
  • GitHub
  • Jira
  • Notion
  • ChatGPT
  • Claude
  • Codex
  • Gemini
  • Grok
  • Your next connector

Spot customer risks early.

An illustrative account review: a renewal date alone does not tell the whole story.

ChatGPT

Partial context
Which customers need our attention, and why?

Checked the renewal agreement

Called Gmail search tool
Gmail · search

Meridian renews September 30.

The renewal is scheduled. Usage and open support issues have not been checked.

What about usage and open issues?
Called Jira search tool
Jira · search

SEC-142 · SSO access issue open · Alex Rivera · Due Sep 24

The SSO issue needs attention. Check product activity before completing the account review.

ChatGPT+Lobu

Install
Which customers need our attention, and why?

Found Meridian’s account context

Called Lobu search tool
Lobu · search
Entity type
Customers
Entity
Meridian Labs
Events
  • Gmail · Meridian renews on September 30.
  • PostgreSQL · Weekly active seats fell 40%.
  • Jira · The SSO access issue is still open.

Meridian needs attention: usage fell 40%, SEC-142 is open, and renewal is September 30. Ask Maya to review the account; churn is not confirmed.

Connect your customer context.

Bring public research, conversations and customer activity together.

LobuAcme Co. / Connectors

What your agents can reach — data, tools, models, and runtimes.

Add connector
SlackChatAudience

1 connection · #customer-health · OAuth

Connected
GmailDataActions

1 connection · Customer success inbox · OAuth

JiraDataActions

1 connection · Jira projects · MCP / OAuth

Connected
1–3 of 6 connectors
LobuAcme Co. / Gmail / Feeds

Gmail

● active

Runs on Gmail v1.0.4

What it brings in 1 source

Threads: Customer contracts & renewalssynced + live
WhenStatusItems
28 min agocompleted3
58 min agocompleted2
1 hour agocompleted8

Connect with OAuth or API keys, and scope access per connection.

Explore connectors

See the signals behind customer risk.

Renewal dates, usage changes and unresolved issues, with evidence for each.

LobuAcme Co. / ActivityIllustrative example

All activity

Meridian renewal

3 entries

Select an entry to inspect its source. Open a linked record to see what connects it.

  1. Gmail·Maya ChenMeridian renews on September 30.

    The renewal date and account owner come from the customer agreement.

    Illustrative source excerpt

    Meridian Labs · Analytics Cloud · $84,000/year · Renewal: September 30 · Account owner: Maya Chen.

    Gmail · Maya Chen · 2026-09-18

  2. PostgreSQL·Product activity feedWeekly active seats fell 40%.

    The two recorded weekly periods show lower usage. The cause is not established.

    Illustrative source excerpt

    Meridian Labs · Weekly active seats fell from 50 to 30 between September 7–13 and September 14–20, a 40% decrease.

    PostgreSQL · Product activity feed · 2026-09-21

  3. Jira·Alex RiveraThe SSO access issue is still open.

    Alex owns SEC-142, due September 24. Whether it explains the usage decline needs checking.

    Illustrative source excerpt

    SEC-142 · Meridian SSO access issue · Owner: Alex Rivera · Status: open · Due: September 24.

    Jira · Alex Rivera · 2026-09-22

Explore records and relationships
LobuAcme Co. / Data
Your workspace schema. Select a type to explore its records and relationships.
LobuAcme Co. / Data / Tasks
Table
NameOwnerActionStatusDue
SEC-142 · SSO accessAlex RiveraResolve Meridian's access issueOpenSep 24, 2026
1–1 of 2 tasks
Explore company context

Find prospects worth a conversation.

See who fits, why now, and how you're connected.

Give your agent a clear brief.

Set the goal, sources and outreach permissions.

LobuAcme Co. / Agents / Market researcher
Settings
Identity
You are Acme Co.’s market researcher. Find relevant prospects with public signals and authorised relationship history.
Soul
Be specific. Cite sources, separate findings from assumptions, and explain your recommendation.
User prompt
Find prospects whose public signals match our offering. Check authorised relationship history, explain relevance and uncertainty, and draft outreach for approval. Never infer buying intent or publish private notes.
Skills
1Prospect researchReview findings with source evidence
2Research briefsTurn findings into a project brief
Guardrails
Protect secretsOutput · No recent catches
Require source evidenceOutput · Custom
Permissions
EntitiesRead
Company records
Connector writesWrite
Publish an update
AgentsUpdate
Other agents

Organization policy always applies.

Models
Models
No models pinned — this agent uses the org default.
Run in sandbox
Research sandbox (Daytona)

Commands run in the connected sandbox. Device access follows the permissions you grant.

Know who to contact and why.

Public signals meet the relationships and goals you choose to connect.

SlackAcme Co.
prospect-research
MC

Maya Chen

@Market researcher Who should we reach out to next, and why now?

M

Market researcherAPP

Ari's recent post describes a problem your prototype addresses. You have a previous conversation to build on. Draft a follow-up for review; interest in buying or a pilot is unknown.

Ari Morgan / Northwind Tools · Illustrative prospect
  • Why them: Their stated handoff problem overlaps with the workflow your team is building.
  • Why now: A recent public post invites discussion of that problem.
  • Your connection: Your own note records a previous conversation and a promise to send an example.
  • What you can offer: A working prototype and help evaluating a narrow workflow together.
  • Still unknown: Whether Ari is interested in a pilot, has time, or wants another conversation.
Inspect public signals and private context

Your meeting note · Only you
Met Ari at the founder meetup. We spoke about handing research between agents. I said I would send an example after our next release.

Founder post · Public
We still repeat the same context at every handoff. I would like to hear how other small teams handle this.

Internal project brief · Your team
Find two teams that can evaluate the handoff workflow. Offer a working prototype and help setting up a small test.

Illustrative example. No outreach has been sent.

Message #prospect-research
Message it inSlackTeamsor delegate fromChatGPTClaude.

Deploy bots in Slack or WhatsApp, or work through the web and your own agents.

Create an agent guide

Catch changes worth acting on.

Track prospect signals and customer risks. Review outreach before it is sent.

LobuAcme Co. / Automations
2 Automations

Find relevant prospects

Active
When
Every Monday at 09:00
Executor
Market researcher Cloud
Instructions

Find prospects whose public signals match our offering. Check authorised relationship history, explain relevance and uncertainty, and draft outreach for approval. Never infer buying intent or publish private notes.

Completed1m 24s

Ari's recent post describes a problem your prototype addresses. You have a previous conversation to build on. Draft a follow-up for review; interest in buying or a pilot is unknown.

Output · Prospect shortlist

Make the next follow-up better.

LobuAcme Co. / FeedbackIllustrative example

Example tested instruction change

Check usage and open issues before an account review. Name an owner; don't predict churn.

Review the change against the recorded customer case before adopting it.

Before the change

The renewal date is recorded. That alone does not establish account health.

This changes only the demonstration. No preference, agent or public record is updated.

Use recorded runs and corrections to build eval cases. Compare changes to prompts, skills or models, then review the results before updating an agent.

How self-improvement worksWrite an eval
The next run builds on what changed

The work stays.
Your agents can change.

Your next conversation.
Not another fresh start.

Keep your knowledge, tools and ongoing work together. Bring the next agent into the same workspace, with the access you choose.

Create your workspace

Know an industry inside out? Partner with Lobu