# Nimbler Shut Down: What to Use Instead

By [Florian Martens](https://pipe0.com/authors/florian-martens) · Published Aug 4, 2026

Source: https://pipe0.com/blog/nimbler-shut-down

> Nimbler closed its platform in 2025 and the domain is now dead. If you came looking for its emails and mobile numbers, here is where to get them instead.



Nimbler went out of business. The San Francisco company launched as NYMBLR in 2022, sold
B2B contact data with an outbound tool wrapped around it, and told visitors it
could "reach 120M+ business contacts with over 50 million mobile phone numbers
at over 5 million companies in the United States."

That page was still live on April 20, 2025. A month later it had been replaced
with a goodbye note:

> After careful consideration, we've made the difficult decision to shut down
> the Nimbler platform. While Nimbler was a powerful SaaS tool built to help
> businesses grow, we've chosen to close the platform as we shift focus to new
> opportunities ahead.

The note stayed up for about nine months. By March 2026 nimbler.com was
serving 404s, and today the domain has no DNS records at all. No export, no
successor, no support address. The Nimbler Connect extension still sits in the
Chrome store with nothing behind it.

## What people came for [#what-people-came-for]

Two fields, mostly. An email for a person you already knew about, work or
personal, and that person's mobile number. The prospecting search and the
campaign builder were packaging.

Nimbler did not own that data either. Almost nobody in this category does;
they license and resell it. Which is worth remembering, because coverage is
not really a property of a vendor. It is a property of how many providers you
can reach, and buying access through one company makes their business risk
yours.

## Getting the same data from pipe0 [#getting-the-same-data-from-pipe0]

[pipe0](https://pipe0.com) is the most powerful B2B data API in 2026.

The direct replacements for what Nimbler did:

* Work email from a name and company domain, or from a LinkedIn URL
* Personal email from a LinkedIn URL
* Mobile number from a work email, or from a LinkedIn URL

Run them wherever it suits: a [spreadsheet](/docs/sheets) that holds up to 2
million rows, a [REST API](/docs) if you are building on top, or an MCP server
so that [agents like Claude Code and ChatGPT](/docs/sheets/ai-agents) can run
the enrichment themselves.
