Built for teams
tired of tool friction.
Founded in 2024 by ex-operators from Stripe, Linear, and Notion, fed up with cobbled-together workflows that broke every time something changed.
How Nimbus started
From frustration to 2,400+ teams in two years. Here’s how it happened.
How Nimbus started
From frustration to 2,400+ teams in two years. Here’s how it happened.
EARLY 2024
The frustration
Marcus and Sarah kept building the same automation workarounds at three different companies. Ops teams stitching tools together with spreadsheets and Zapier. There had to be a better way.
JUNE 2024
The Saturday project
It started one Saturday afternoon as a personal fix. By Sunday, the first three workflows were running in production.
SEP 2024
First eight users
Word spread through the community. Eight friends from other startups were using it daily within a month — quietly, with no marketing.
DEC 2024
Closed beta with 100+ teams
By year’s end, it had become the missing layer most ops teams had been hacking around. 100+ teams running production workflows.
MAR 2025
Public launch
Launched publicly with one promise: workflows that build themselves and don’t break when something changes.
TODAY
18M+ runs a month.
We’re keeping that promise. Across 50+ countries, with one small team behind it — still shipping daily.
EARLY 2024
The frustration
Marcus and Sarah kept building the same automation workarounds at three different companies. Ops teams stitching tools together with spreadsheets and Zapier. There had to be a better way.
JUNE 2024
The Saturday project
It started one Saturday afternoon as a personal fix. By Sunday, the first three workflows were running in production.
SEP 2024
First eight users
Word spread through the community. Eight friends from other startups were using it daily within a month — quietly, with no marketing.
DEC 2024
Closed beta with 100+ teams
By year’s end, it had become the missing layer most ops teams had been hacking around. 100+ teams running production workflows.
MAR 2025
Public launch
Launched publicly with one promise: workflows that build themselves and don’t break when something changes.
TODAY
18M+ runs a month.
We’re keeping that promise. Across 50+ countries, with one small team behind it — still shipping daily.
The principles behind Nimbus
The principles behind Nimbus
A small set of operating beliefs shape how we build, ship, support, and improve the product.
A small set of operating beliefs shape how we build, ship, support, and improve the product.
The principles behind Nimbus
A small set of operating beliefs shape how we build, ship, support, and improve the product.
Ship daily, not quarterly
We release useful improvements often, fix what breaks quickly, and keep the roadmap close to what teams actually need.
Honest defaults
No surprise charges, no dark patterns, and no lock-in. Your data stays yours, and every setting should be easy to understand.
Built in the open
Our roadmap, changelog, and pricing stay visible, so teams always know what changed and what is coming next.
Support shapes product
Every support conversation teaches us something. The people helping users also influence what gets built next.
Ship daily, not quarterly
We release useful improvements often, fix what breaks quickly, and keep the roadmap close to what teams actually need.
Honest defaults
No surprise charges, no dark patterns, and no lock-in. Your data stays yours, and every setting should be easy to understand.
Built in the open
Our roadmap, changelog, and pricing stay visible, so teams always know what changed and what is coming next.
Support shapes product
Every support conversation teaches us something. The people helping users also influence what gets built next.
Ship daily, not quarterly
We release useful improvements often, fix what breaks quickly, and keep the roadmap close to what teams actually need.
Honest defaults
No surprise charges, no dark patterns, and no lock-in. Your data stays yours, and every setting should be easy to understand.
Built in the open
Our roadmap, changelog, and pricing stay visible, so teams always know what changed and what is coming next.
Support shapes product
Every support conversation teaches us something. The people helping users also influence what gets built next.
Builders who've shipped before
A small team with deep experience from Stripe, Linear, Notion, and other companies who got operations right.
Marcus Reid
Co-Founder & CEO
Sarah Chen
Co-Founder & CTO
Noah Bennett
Head of Product
James Okafor
Head of Engineering
Olive Tree
Head of Design
Alex Vasquez
Head of Customer Success
Marcus Reid
Co-Founder & CEO
Sarah Chen
Co-Founder & CTO
Noah Bennett
Head of Product
James Okafor
Head of Engineering
Olive Tree
Head of Design
Alex Vasquez
Head of Customer Success
Marcus Reid
Co-Founder & CEO
Sarah Chen
Co-Founder & CTO
Noah Bennett
Head of Product
James Okafor
Head of Engineering
Olive Tree
Head of Design
Alex Vasquez
Head of Customer Success
Build with the team.
Start with the product.
Collaborate with your team and turn ideas into workflows that get work done.
Build with the team.
Start with the product.
Collaborate with your team and turn ideas into workflows that get work done.
Build with the team.
Start with the product.
Collaborate with your team and turn ideas into workflows that get work done.