Skip to content
New: Replays now compare against the last 90 days. Read the changelog

Agents that do the busywork.

Describe a job in plain words. Capstan drafts the steps, connects your tools, tests the agent on last month's work and runs it, with a person approving the steps that matter.

NewReplays look back 90 days
Start freeTalk to salesFree for 1 builder · no card
Northgate BikesAgents Weekly churn digest

Weekly churn digest

run #418 · Mon 09:00

Step 4 of 5

  1. Done: Read last week's cancelled subscriptions from Stripe

    stripe.subscriptions.list · 214 rows · 1.2 s

  2. Done: Matched 31 accounts in HubSpot and read their last notes

    hubspot.companies.search · 31 of 31 · 3.4 s

  3. Done: Grouped the reasons: price 12 · missing SSO 8 · moved to a competitor 6 · other 5

    model · 2,140 tokens · $0.004

  4. Waiting for approval: post the summary to #revenue

    31 accounts churned last week ($18.4k MRR). Price came up 12 times, mostly on the Team plan after the March change. 8 left for missing SSO.

    Asked Maya Okafor in Slack

  5. Next: Created follow-up tasks in HubSpot for the 8 SSO accounts

Sample agents

New agent

N
  • Stripe
  • HubSpot
  • Slack

FIG 0.1 — what Capstan is for

Most busywork isn’t hard. It’s just every week.

The refunds under fifty dollars, the Monday churn report, the invoices nobody chased. Capstan takes the weekly part, shows you every step it took, and stops where a person should decide.

How a job becomes a running agent

01 · Describe

Write the job like you'd brief a colleague.

Capstan turns a paragraph into steps you can read and edit like a doc: which tools it reads, what it decides, and where it must ask first.

How building works

The job

“Every Monday, find last week's churned accounts and post the reasons to #revenue”

  1. 1

    Read cancelled subscriptions from Stripe

    Reads
  2. 2

    Find each account in HubSpot and read its last notes

    Reads
  3. 3

    Group the reasons and total the lost MRR

    Decides
  4. 4

    Post the summary to #revenue

    Asks first

schedule · Mondays at 09:00

02 · Connect

Only the access the job needs.

Each agent gets its own keys and its own limits. Reading is allowed; anything that spends money, emails a customer or changes a record waits for a yes.

See all 120 integrations

  • Stripe

    Read subscriptions, invoices

    Read only

  • HubSpot

    Read companies · create tasks

    Asks first

  • Slack

    Post to #revenue

    Asks first

  • Budget

    Stops at $5.00 a week

    $0.31 used

03 · Replay

Test it on last month's work.

Replays run a new agent on real cases from the last 30 days and show what it would have done next to what your team did. Approve it topic by topic.

How Replays work

Refund requests · last month

replay #12 · Oct 1 – Oct 31

What the agent would have done, compared with what the team did
TopicCasesSameBetterWorse
Duplicate charge646310
Refund under $50585260
Order not arrived413722
Change of address231922

186 cases · replay cost $0.92

04 · Run

Every run, step by step.

Each run keeps a trace: what it read, what it sent, how long it took and what it cost. Failures retry once, then go to the agent's owner.

Monitoring and alerts

Weekly churn digest

Last 4 runs

Recent runs with their result, time and cost
RunStartedResultTimeCost
#418Mon 09:00Done41 s$0.011
#417Mon 09:00Done38 s$0.010
#416Mon 09:00Retried once1 m 12 s$0.019
#415Mon 09:00Done44 s$0.012
  1. 01Describe
  2. 02Connect
  3. 03Replay
  4. 04Run

The job

“Every Monday, find last week's churned accounts and post the reasons to #revenue”

  1. 1

    Read cancelled subscriptions from Stripe

    Reads
  2. 2

    Find each account in HubSpot and read its last notes

    Reads
  3. 3

    Group the reasons and total the lost MRR

    Decides
  4. 4

    Post the summary to #revenue

    Asks first

schedule · Mondays at 09:00

FIG 01 — describe

Built to be trusted with real work.

How Control works

Nothing ships without a yes.

Pick the steps that need a person. Capstan asks in Slack, Teams or email with the draft attached, and waits. Approve, edit or say no; the run carries on from there.

A budget it can't overspend.

Each agent has a weekly limit. At the limit it stops and tells its owner, mid-run if it has to.

120 tools, your keys.

Connect Stripe, HubSpot, Zendesk, Notion and the rest with scoped keys. Any REST API or MCP server works too.

Every step on the record.

What it read, what it sent, how long it took and what it cost, kept for 400 days and exportable.

Run it from anywhere.

Start an agent from the command bar, Slack, the API, or from Claude and Cursor through the MCP server.

One way of working, every team’s weekly jobs.

All use cases

  • FIG 2.1 — support

    Refunds under $50, done before the queue opens.

    1. Step: Read new tickets tagged billing in Zendesk
    2. Step: Find the order and the charges in Stripe
    3. Asks first: Refund within the limit, reply with the policy cited

    63%

    of billing tickets closed without a person (sample)

    Support use case

  • FIG 2.2 — sales

    Account research on every new demo request.

    1. Step: Read the demo request from HubSpot
    2. Step: Look up the company, its size and its tools
    3. Asks first: Write a one-page brief to the account owner

    25 min

    saved per demo, by reps' own estimate (sample)

    Sales use case

  • FIG 2.3 — operations

    Overdue invoices chased, disputes left alone.

    1. Step: List invoices more than 14 days overdue
    2. Step: Skip customers with an open dispute
    3. Asks first: Send a reminder after a person approves

    9 days

    less, on average, to get paid (sample)

    Operations use case

  • FIG 2.4 — research

    A competitor brief on your desk every Friday.

    1. Step: Read competitors' pricing pages and changelogs
    2. Step: Note what changed since last week
    3. Asks first: Post a sourced summary to #product

    14

    sources read every week, each one linked (sample)

    Research use case

What teams say (sample)

“We gave it the jobs nobody wanted on a Monday. Six weeks later the queue opens empty, and every refund it made is one click away if I want to check it.”

Priya NairSupport lead, Northgate Bikessample

Teams running their weekly jobs on Capstan (sample companies)

  • Northgate Bikes
  • Pallet & Pine
  • Tandem Travel
  • Quayside Money
  • Fernway Pet
  • Halden Studio

Call an agent from your own code.

Run agents from your backend, stream their steps, and approve from your own UI. Or let Claude, Cursor and other AI tools call them through the MCP server.

Read the docsAPI changelog
import { Capstan } from "@capstan/sdk";

const capstan = new Capstan(process.env.CAPSTAN_KEY);

const run = await capstan.agents.run("churn-digest", {
  input: { week: "2026-W44" },
});

for await (const step of run.steps()) {
  console.log(step.status, step.text);
}

Shipped lately.

Full changelog

  1. Replays now compare against the last 90 days

    Pick 30, 60 or 90 days of past cases, and filter a replay to one topic before you approve it.

    Replays

  2. Approve steps from Microsoft Teams

    Approval requests arrive as Teams cards with the draft attached. Edit in place, then approve.

    ApprovalsIntegrations

  3. Python SDK 1.0

    Run agents, stream steps and answer approvals from Python 3.10 and up. Async client included.

    API