Sales teams have been stuck with stale databases for 15 years. Jesse changes everything.. the first internet-wide search engine built for sales & marketing. Ask in plain English: "Find newly opened soccer facilities in the Midwest needing turf solutions." Jesse scans the live web and finds the right buyers in the market today. We are an anti database company, we don’t scrape and store stale databases and sell them at premium. Every lead is found fresh from the live internet and delivered.
Forum Threads
This is the single biggest GTM mistake
Not building lookalike list.
All of us must be having some customers. Some customers came inbound, few via referrals, few via word of mouth- it does not matter.
What matters is that these customers are able to solve their pains with your product.
Hence, once they are your customers- you should be "finding more of these".
This is by far the most underrated GTM hack I have come across.
There are few lookalike tools you can try- Ocean, Jesse (my product).
While using these tools, you should be able to find out why certain new customers were surfaced- what were the logic behind these new suggestions, and then run a focussed outbound/ABM campaign on those list.
What are the BEST and WORST lead gen tools you have tried?
While building Jesse, I talked with a ton of founders, builders and asked about their experience with the best and worst lead gen tools they have used.
I am curious to know the opinion of this group on this matter.
Some common ones that many use today are:
> Apollo
> Clay
> Lusha
> Zoominfo
Feel free to name and mention any other tools that you have come across.
A Guide to Finding Your Next 100 Customers
I ve spent years working on B2B customer acquisition for products moving from early traction to real scale. We tested every channel, built lightweight systems for volume outreach and partnerships, ran hundreds of experiments, and eventually created repeatable processes that a small team could run without constant firefighting.
Distribution is the #1 bottleneck you ll hit. Features get copied. Messaging gets borrowed. What actually compounds is a clear system for identifying the right accounts, testing quickly, and turning early signals into consistent pipeline.
By the end of this you ll know:
- What each major acquisition channel actually buys you (and why most teams misuse them)
ThriveSparrow
Looks good - but for someone who already uses LinkedIn SalesNav - how's it different and what more can it add??
@its_grs
Fair question, and honestly Jesse is more complement than replacement if you already live in SalesNav.
Three real differences:
Data source: SalesNav knows what is on LinkedIn. Jesse reads the open web, news, funding, company sites, local directories, reviews, so it catches what LinkedIn underrepresents, recency signals like a fresh raise, and the local SMB long tail (salons, clinics, agents) where LinkedIn is thin.
Query model: SalesNav is structured filters bounded to LinkedIn's fields. Jesse takes a plain-English ICP and reasons over it, so you can ask for things there is no filter for, "recently raised Series B and hiring AEs," "uses Salesforce," a specific pain point, and still get matches.
Output: every result comes ranked with a rationale and a source, so the why-it-matched qualification is already done and auditable, and you can export it or pipe it into a workflow instead of working inside LinkedIn.
Where SalesNav might is mostly useful: if your ICP maps cleanly to its filters and your targets are all active there, it is excellent.
Jesse helps you when the criteria do not fit those filters, the targets live off LinkedIn, or you want a reasoned, exportable list rather than manual qualification.
Plenty of people run both.
@maulikdoshi
Thanks Maulik.
Really appreciate this, you described the exact itch we built Jesse to kill, and we are only getting sharper from here.
Does it have MCP integrations yet?
@saurav_gopal
Yes, we have an MCP server that exposes Jesse's search as tools (find companies, find people, fetch results), so any MCP client can run a search and get the results right in the flow.
It works today with the key-based clients, Claude Code, Claude Desktop, Cursor, and the API, by pasting your Jesse API key.
It is in request-only beta right now, so reply or DM and I will get you early access.
Nevertheless it will be fully public in 2 to 3 days.
Side note: if n8n is also on your radar, the template is already live in the n8n gallery (search 'Jesse'). Same API key."
So proud to see Jesse out in the world today. 🚀
I've watched the team pour everything into this, late nights, endless user calls, and a stubborn refusal to ship just another stale database when the whole industry said that's just how it works.
The live-internet search is genuinely wild, but what I'm proudest of is how obsessively we listen to users. Every piece of feedback gets read and acted on, and it shows in how fast this thing keeps getting better.
If you've ever burned an afternoon building a lead list only to find half of it was wrong — this one's for you. 🙌
@gautham_madhavan This is beautiful- huge congrats to the whole team for the launch and on building something that actually solves the stale-list pain so many of us have lived through. The live-internet search is the real delta, and the fact that you’re obsessively listening to users and shipping fast is what turns “wild concept” into “daily tool.”
I’ve burned way too many afternoons assembling lists that go half-bad before outreach, and Jesse’s approach is exactly what SDR teams need to stop that waste.
Let’s get Jesse into Top 5 of the Week.
Kula
I think the live web search can be a huge delta in tools like these. It can solve for the freshness of the data always there in the tool.
I think this is a cool concept. Looking forward to testing this out. All the best for the launch, guys.
@rohitsrivastv Exactly- freshness is the biggest delta, and live web search at query time is what keeps data from decaying the moment it hits a database. That's the core unlock for timing-sensitive outreach.
Thanks for the kind words and the launch congrats! When you test it, try prompts that encode recency (e.g., "VP of Sales who recently changed roles at Series B SaaS") to see how the signals surface. If you hit any edge cases or want help tightening your ICP criteria, I'm here.
All the best
Requestly
Cant wait to try this. Have had my own share of struggles with stale databases.
@itsshrey Thanks, Shreyas. It will be really awesome to have you use Jesse and share more detailed feedback with our product team.
Definitely interested in seeing how the results compare with more established prospecting tools.
@harshita_kaur1 That's the right bar to set- comparing results against Apollo/Clay is exactly how you'll see the difference.
The key edge is freshness and signal quality:
Apollo/Clay: scrape once and sell a pre-built database; titles change, companies pivot, signals go stale by the time you get them.
Jesse: runs live, grounded web research at query time—no snapshot lag. When you search, it goes to public sources right then and reasons over what's currently there.
Practical impact for timing-sensitive outreach:
No baked-in 30–90 day lag on job changes or funding rounds—catchable as soon as they hit the web (news, company site, LinkedIn).
Recency is encoded in the criteria (e.g., "VP of Sales who recently changed roles at Series B SaaS"), pulling on visible recency signals rather than just current title.
Built-in "changed role in the last two weeks" toggle is next, so you don't have to word recency into the prompt