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

About

We build the agents we wanted to hire.

Capstan started with one agent, one Monday job and a list of what it was allowed to touch. Two years later, that list is still the most important thing we make.

Founded, in Stockholm
2024
People on the team
34
Offices, Stockholm and New York
2
Time zones we work across
9
Failed payments, Mondayagent #1
Every Monday at 8, read last week's failed-payment emails from Stripe. Find each customer in HubSpot and the account manager who owns them. Draft a short note to that manager with the amount, the reason it failed and the customer's plan. Ask me before you send anything.
  1. Read Stripe emails
  2. Find owner in HubSpot
  3. Draft the note
  4. Ask Tom
The first agent we wrote, February 2024. It still runs every Monday.

It started with failed payments.

In early 2024 Tom ran support operations at a payments company, and Rafael was the engineer who kept its internal tools alive. Every Monday, Tom spent the morning on the same job: read the failed-payment emails, look each customer up, and tell the right account manager before the customer noticed.

Rafael wrote an agent to do it over a weekend. It worked on the first Monday, and on the second it emailed a customer directly, which nobody had asked it to do. So they wrote down what it could touch, made it ask before sending anything, and ran it against the previous month's emails before letting it near the next one.

“We didn't need a smarter model. We needed one we could check, and stop.”
Rafael Mendes

Three things made it safe: a list of what an agent may do, a person on the steps that matter, and a test on real work. They turned out to be what every team wanted. Ten teams were using a copy by the autumn. Capstan is what that copy became.

We're 34 people now, split between Stockholm and New York and remote across nine time zones. We still build every feature the same way: someone shows us a job they do every week, and we ask what it would take for them to hand it over and sleep.

Tom and Rafael

Co-founders of Capstan, Stockholm, November 2026

How we build.

  1. 01

    Show the work

    Every run explains itself in sentences a support lead can read. If a person can't follow it, it isn't done.

  2. 02

    A person decides

    Agents draft. People approve the steps that spend money, message customers or change records. That's why approvers are free.

  3. 03

    Test on what happened

    No agent of ours ships without a replay on real cases. We hold our own changes to the same rule.

  4. 04

    Limits live outside the model

    Permissions and budgets are enforced by code. A prompt is a request, never a control.

  5. 05

    Write it down

    Policies, decisions and our own handbook. An agent can only follow a rule someone wrote, and so can a new hire.

  6. 06

    Charge for what's built

    Builders and runs, nothing else. Pricing should never make a team cut corners on safety.

Two years, so far.

  1. One agent, one Monday job

    Tom and Rafael write the failed-payments agent at the company they work for, and give it a list of what it may touch.

  2. Ten teams and a Slack button

    A private beta. Every team asks to approve steps where they already work, so approvals move into Slack.

  3. Capstan 1.0 and a free plan

    Agents described in plain words, scoped tools and approvals, free for one builder with 200 runs a month.

  4. Replays

    Test a new agent on last month's cases with every write turned off, and approve it topic by topic.

  5. SOC 2 Type II and an EU region

    An independent audit over twelve months, and workspaces that keep every run and key in Frankfurt.

  6. · Today

    34 people, and 90-day replays

    MCP server, Python SDK and approvals in Microsoft Teams this autumn. Replays now go back 90 days.

Everything we've shipped since

The people behind the runs.

Engineers, designers and people who've run support and sales teams themselves. Most of us have done the job an agent now does.

Show a team

Showing 12 of 34 people

  • Tom Lindqvist

    Co-founder, CEO

    Stockholm

  • Rafael Mendes

    Co-founder, CTO

    Stockholm

  • Hannah Brooks

    Head of operations

    New York

  • Maya Okafor

    Head of product

    New York

  • Jonas Weber

    Product designer

    Berlin

  • Elif Kaya

    Design engineer

    Istanbul

  • Ines Duarte

    Engineering lead, Replays

    Lisbon

  • Daniel Kim

    Platform engineer

    Toronto

  • Astrid Berg

    Security engineer

    Stockholm

  • Mateo Ruiz

    Integrations engineer

    Mexico City

  • Grace Mwangi

    Head of customer success

    New York

  • Owen Price

    Solutions engineer

    New York

  • And 22 more across engineering, support, sales and operations.

    See open roles

We're hiring for 5 roles.

Remote across the US and EU, or in Stockholm and New York. Every role starts with a week shadowing a customer's team.

See open roles