We recently spoke with Harsha Gaddipati, COO and Co-Founder of Slashy, a seed-stage San Francisco startup building what Harsha describes as "Superhuman married with an executive assistant." Harsha walked us through how Slashy uses Context.dev to run around 5,000 company enrichments a day, and why the integration has stayed out of his way since December.
What is Slashy?
Slashy is an email client with an assistant built in. It reads the inbox the way a good chief of staff would: figuring out who is writing, what they want, and what the user actually needs to do about it.
For that to work, Slashy needs to know a lot about the companies its users talk to. That is the problem Context.dev solves for them.
Enriching email contacts at scale
Slashy's users email everyone, from Fortune 500 CFOs to two-person startups. For each of those contacts, Slashy pulls in company-level data: logos, descriptions, domains. That data feeds the product's intelligence layer and also shows up directly in the right-hand sidebar while the user is reading their email.
Today that means about 5,000 enrichments a day, and the number keeps going up as more users come online.
"We enrich roughly 5,000 companies a day for our users and the number is continuously growing."
The timing made this a harder problem than it should have been. HubSpot had just sunset Clearbit, which was the default enrichment API for most teams. A lot of products woke up one morning and needed a replacement.
Finding Context.dev
Harsha found us through a Google search. What sold him was not a pitch deck, it was the API itself.
"We picked Context.dev as the simplicity of their API was great."
At seed stage, evaluation time is expensive. Slashy did not have weeks to spend on enterprise onboarding calls or dense SDK docs. They wanted to hit a URL, get JSON back, and go build their product.
How they use it
Slashy plugged Context.dev into two places:
- The company enrichment pipeline that ingests email contacts, pulls out domains, and hydrates each one with company data.
- The right-sidebar company panel, which renders the logo and company info inline while the user reads email.
"Context.dev allowed us to build out our company enrichment pipeline, along the UI we show in our right sidebar for company information."
The UI piece is the harder test. Users will notice a missing logo or a wrong description in about half a second. The data had to be good enough to render straight to the product, not just sit in a warehouse somewhere. It was.
Zero outages since December
Slashy started using Context.dev in December 2025. Traffic has scaled a lot since then.
"We started using them back in December, and since then haven't had an outage despite scaling significantly."
When an enrichment API sits in the hot path of a user-facing product, a failed call is not an abstract metric. It is a blank logo in somebody's inbox at exactly the moment they are trying to figure out whether to reply. Slashy has not had to build retry queues or fallback providers to cover for us, which is the real test.
The Clearbit-shaped hole
Harsha was direct about the market context: Context.dev showed up right when a lot of teams needed it to.
"Super useful as Clearbit got sunset by HubSpot."
A lot of products were quietly built on top of Clearbit for logos and company data. When HubSpot pulled the plug, those teams had to go find something else, fast. Slashy found it and kept shipping.
What Slashy got out of it
- Around 5,000 enrichments a day, scaled from December 2025 with no infrastructure work
- Zero outages, reliable enough to run in the critical path of a user-facing product
- A simple API that was fast to evaluate and fast to integrate
- A working Clearbit replacement
- Both the pipeline and the visible UI come from the same source
- No custom scraping or retry logic on Slashy's side
Why it fits
Slashy is small and moves fast. They need dependencies that stay boring. Context.dev's API was short to evaluate, short to integrate, and has not asked for attention since.
"Can not recommend enough for people who want a simple api that just works."
The best thing you can say about a piece of infrastructure is that the team forgot it was there. Slashy went from picking a provider in December to running thousands of enrichments a day without a single war room along the way.
P.S. If you spend too much of your day in email and you want an inbox that actually helps you move, check out Slashy. Think Superhuman married with an executive assistant, built for people whose inbox is the job.