Skip to content
ExoHuman

Use cases

The agents each department runs.

Start with one department, prove it, then add the next. Every agent has a role, an owner, the compute it needs and a clear line for what it may do alone and what waits for a person.

Sales

A pipeline that never goes cold.

Agents research accounts, score inbound leads, draft follow-ups in your voice and keep the CRM clean. Reps spend their time on conversations, not admin.

Every lead answered the same day, with reasoning attached.

Connects to

CRME-mailCalendarSlack

Agents

  • sdrStandardon new lead

    Researches and scores every inbound lead, drafts the first reply

  • account-managerStandarddaily 08:00

    Watches renewals, prepares offers within approved discount bands

  • deal-deskStandard

    Builds proposals and pricing from the canon and past deals

Waits for a person

  • ⏸ Any outbound e-mail to a new contact
  • ⏸ Discounts above the approved band
  • ⏸ Contract terms

Marketing

From brief to published, with your brand intact.

Agents draft campaigns, repurpose content across channels, watch competitors and render visuals on GPU profiles, all against one shared positioning document.

A weekly content calendar shipped by two people instead of six.

Connects to

CMSSocial schedulersAnalyticsDrive

Agents

  • contentStandard

    Drafts articles, newsletters and social posts from the canon

  • creative-studioGPU · L4

    Generates and edits product imagery and short video

  • market-researchStandardMon 08:00

    Tracks competitors and summarises what changed this week

Waits for a person

  • ⏸ Publishing anything public
  • ⏸ Paid media spend
  • ⏸ Changes to positioning

Customer support

First answers in minutes, escalations with context.

A support agent triages tickets, answers from the knowledge base, reproduces issues and hands anything sensitive to a person with the full history attached.

Most tickets resolved on first touch; people handle the hard ones.

Connects to

Help deskWhatsAppTelegramVoice

Agents

  • supportStandardon new ticket

    Triages and answers tickets, drafts macros from resolved cases

  • qa-reproPerformance

    Reproduces reported bugs in a sandbox and files them

Waits for a person

  • ⏸ Refunds and credits
  • ⏸ Account deletions
  • ⏸ Replies to flagged customers

Operations & finance

The back office, on autopilot with receipts.

Agents reconcile invoices, chase payments, keep records tidy and prepare month-end. Every payment waits for the person who owns it.

Month-end closes days earlier, with an audit trail auditors can read.

Connects to

AccountingBanking exportsSpreadsheetsE-mail

Agents

  • back-officePerformancedaily

    Invoice runs, CRM hygiene, vendor follow-ups

  • financeStandard1st of month

    Reconciles transactions, drafts month-end pack and variances

Waits for a person

  • ⏸ Every payment
  • ⏸ Vendor changes
  • ⏸ Anything touching payroll

Leadership

A chief of staff that reads everything.

A chief-of-staff agent assembles the morning brief, chases owners for objectives and drafts the board pack from what every department recorded.

The company's state, in one page, every morning.

Connects to

CalendarE-mailDocsEvery department

Agents

  • chief-of-staffStandarddaily 07:00

    Morning brief, objective tracking, board-pack drafts

  • brainHigh memory

    Consolidates decisions and facts into shared company knowledge

Waits for a person

  • ⏸ Anything sent to the board or investors
  • ⏸ Changes to objectives

Engineering

Coding agents with real machines.

Claude Code, Codex and Gemini CLI agents work in their own containers with the resources builds need: they triage issues, open pull requests and keep dependencies current.

A backlog that moves overnight, reviewed in the morning.

Connects to

GitHubCIIssue trackerMCP

Agents

  • devPerformance

    Implements scoped issues and opens pull requests

  • opsStandardevery 15 min

    Watches health, rotates logs, proposes fixes

  • docsStandard

    Keeps documentation in step with merged changes

Waits for a person

  • ⏸ Merges to protected branches
  • ⏸ Production deploys
  • ⏸ Infrastructure changes

By industry

Patterns our customers run.

Agencies: one agent team per client

Give each client isolated agents with their own credentials, data and channels on one instance. Bill compute per client and add GPU studios only for the accounts that need them.

Cloud · Scale

Professional services

Research, drafting and review agents that work from your precedent library, with partner sign-off on anything that leaves the firm.

Cloud · Scale or Enterprise

E-commerce and retail

Catalogue enrichment, product imagery on GPU, customer service over WhatsApp and daily margin reports, scaling up for peak season and back to zero after.

Cloud · Launch → Scale

Software companies

Coding, QA and documentation agents on Performance profiles, plus support and success agents that read the same product knowledge.

Cloud · Scale

Media and data science

Transcription, embeddings, fine-tuning and video pipelines on L4, A100 or H100 profiles, billed only while the job runs.

Cloud · Scale

Regulated industries

Healthcare, finance and public-sector teams connect their own servers and GPUs as worker nodes, keeping data on their infrastructure while ExoHuman schedules agents onto them.

Cloud · your nodes

Start with one department.

Set up your instance today; add departments as each one proves itself.

Use cases · ExoHuman