The future of GTM is here. nRev is a GTM wizard, trained on 10,000+ deployed marketing and sales engines. It consults based on what's working, builds and deploys automations, simply by having a conversation with it.
EOL Dataset by HeroDevs — Find every EOL dependency in your stack. Free. In 5 minutes.
Find every EOL dependency in your stack. Free. In 5 minutes.
Promoted
Maker
📌
Hi everyone, Sayanta here, co-founder of nRev.
We started building nRev when we couldn't find a single $1-50M B2B company running GTM on fewer than 10 tools.
Clay + HeyReach + Trigify + n8n + 15 more, patched together. Every new experiment meant adding another in the line and sticking to them for the entire year.
Rajat, Nikhil and I (ex-Mindtickle) kept walking into this same mess at every team we worked with. So we started fixing it. 10,000+ workflows later, today we're shipping 3 things:
1. A brainstorming agent trained on every one of those 10,000 workflows. What worked in staffing. What broke in SaaS. Which motions compound for which ICP. Brainstorm strategy with it before you build anything. 2. A CLI that turns Claude into a GTM engineer. 70+ data providers, skills, MCPs, the full stack. 3. An AI builder that strips the technical tax. Describe a workflow in plain English. Agents build it, connect the tools, run it.
The bigger bet underneath all three: most "GTM Saas" is prescriptive. The workflows are built to suit majority teams, but today AI allows us to design our motions that work best in our context and teams. We're closing that gap.
Free to try, no credit card. I'd love your honest feedback on which of the three you'd actually use first, and what's missing for your stack.
Massive thanks to our 100+ design partners who broke nRev in every possible way over the last year, and to Kevin for hunting us today. Rajat, Nikhil, Jay, Aradhya and I are all in the comments answering everything.
Report
@sayanta_ghosh Wow, the Avengers are gathered. Congratulations on the launch.
Report
Maker
@myheldwords Thank you for the support :) Would love to hear what you think about the brainstorming agent on the platform
Report
Maker
Hey PH, Jay here, founding growth marketer at nRev.
Quick context: I'm the only non-engineer in this comment thread.
Before nRev, I was the marketer at every previous company who personally bought Clay, HeyReach, Smartlead, n8n, Make, and a dozen more. I have worked with more spread sheets than any growth marketer should. I have apologized to more founders about tool sprawl than I'd like to admit.
So when Sayanta and Rajat showed me the early AI builder, I genuinely tried to break it.
Built a multi-step LinkedIn warm-up sequence with intent triggers, dedupe logic, and a fallback for when our enrichment provider returned junk. The kind of workflow that usually takes me 3 days in n8n and another day debugging.
For any marketer or SDR leader scrolling this, I would be deeply thankful if you could give the brainstorming agent a spin and let me know your thoughts
or
Drop your hardest GTM problem in the replies. I will personally walk you through how I'd attack it on nRev.
Report
Maker
Hi PH, Aradhya here. I head Product at nRev and have been on the founding team since day one.
When "AI builds it" enters any pitch, every product person quietly worries about the same thing. The magic demo problem. Looks beautiful in a 60 second video. Falls apart at workflow building.
We have spent the last year obsessing over the unglamorous half. What happens when an integration breaks at midnight. What happens when a user describes a workflow that's actually 3 workflows tangled together. What happens when the same prompt produces slightly different results across two runs.
The product decision I'm proudest of is putting the brainstorming agent in front of the AI builder, not after it. Most teams come to nRev wanting to build a workflow they already had in mind. Half the time, after 10 minutes of conversation with the agent, they realize the workflow they wanted to build wasn't the one that would actually move their numbers. They change the plan before writing a single workflow.
That moment, watching someone rethink their motion before touching the builder, is what convinced me we shipped the right thing. Honest ask for anyone trying nRev today. Start with the brainstorming agent.
Even if you never build a workflow on us, tell me where the agent fell short of what you'd expect from a great operator sitting next to you. That feedback shapes the next 6 months of our roadmap.
Report
Can I set this up to watch executive job changes in my target accounts and trigger a warm outreach the day they update LinkedIn?
Report
Maker
@athsara absolutely, and this can be completely outbound - the entire sequence of steps and a notification to let you know about it in the way you want.
Report
Maker
@athsara Indeed. We have live linkedin monitoring that you can run on a cadence of your choice. We further have Rocketreach as a partner that can help you directly search people who've recently switched jobs or used to work with your past customers.
You can even monitor and warm up prospects by automatically engaging with their linkedin.
Congrats on the launch @aradhya_shandilya@sayanta_ghosh@nikhil_ojha2@rajat_jain5 !! I'd love to know from where are you pulling in signals from? I'd like to keep a tab of updates from some products I follow - what are they building, their communications, etc. What are your sources? They post across reddit, insta, linkedin too. Do you cover those too?
Report
Maker
@avirup_mukherjee social listening is the way to go and yes it's all in ;)
You can monitor mentions, releases, posts and even more like hiring patterns. Brainstorm with our nrev agent. You'll be surprised.
What happens if something breaks midway? Can users' see what broke? this has been a major problem with some of the AI integration-type tools I've tried till date
Report
Maker
@dipanjan_dey I love this question, this is probably one of the things that make workflows stand far apart from agents. Workflows are defined by the exact steps that they need to do. In fact, even the AI steps have guardrails which ensure 100% times that they structure their output in the way that is desired.
This ensures that the sacrosanct GTM systems of record are not messed up even over millions of executions and every time the output or actions are exactly same.
Agents in nRev however are used to experiment on data sets, build the workflows but not execute workflows because of this exact same problem
Report
Maker
@dipanjan_dey Absolutely. Every execution stays logged. Every credit attributed. You can even set up notifications directly on slack, gmail and more if anything goes off.
Report
Maker
Hi PH, adding the technical side Sayanta skipped.
I'm Nikhil, co-founder of nRev
We started building nRev a year ago in the midst of AI transforming the world. Our first big question was agents vs workflows, which empowers GTM the most?
Workflows are predictable, follows the exact steps in the same way, and auditable. That was the foundation of nRev because of the certainty one needs in their GTM motions and the way they interact with the systems of record (sacrosanct to the teams)
Also most workflow builders didn't care about bulk executions, rate limits of vendors, fallbacks, etc. nRev takes the entire responsibility on itself so that outcomes get done everytime.
However over time, the problem that our design partners pointed out was the learning curve and technical knowledge required to build workflows.
This launch, where we come out to the world, is where nRev completely eliminates such complexity and transforms designing and building GTM experiments to conversations and instructions in plain english.
We are hungry for feedback and look forward to transform your entire distribution engine with nRev
Hi everyone, Sayanta here, co-founder of nRev.
We started building nRev when we couldn't find a single $1-50M B2B company running GTM on fewer than 10 tools.
Clay + HeyReach + Trigify + n8n + 15 more, patched together. Every new experiment meant adding another in the line and sticking to them for the entire year.
Rajat, Nikhil and I (ex-Mindtickle) kept walking into this same mess at every team we worked with. So we started fixing it. 10,000+ workflows later, today we're shipping 3 things:
1. A brainstorming agent trained on every one of those 10,000 workflows. What worked in staffing. What broke in SaaS. Which motions compound for which ICP. Brainstorm strategy with it before you build anything.
2. A CLI that turns Claude into a GTM engineer. 70+ data providers, skills, MCPs, the full stack.
3. An AI builder that strips the technical tax. Describe a workflow in plain English. Agents build it, connect the tools, run it.
The bigger bet underneath all three: most "GTM Saas" is prescriptive. The workflows are built to suit majority teams, but today AI allows us to design our motions that work best in our context and teams. We're closing that gap.
Free to try, no credit card. I'd love your honest feedback on which of the three you'd actually use first, and what's missing for your stack.
Massive thanks to our 100+ design partners who broke nRev in every possible way over the last year, and to Kevin for hunting us today. Rajat, Nikhil, Jay, Aradhya and I are all in the comments answering everything.
@sayanta_ghosh Wow, the Avengers are gathered. Congratulations on the launch.
@myheldwords Thank you for the support :) Would love to hear what you think about the brainstorming agent on the platform
Hey PH, Jay here, founding growth marketer at nRev.
Quick context: I'm the only non-engineer in this comment thread.
Before nRev, I was the marketer at every previous company who personally bought Clay, HeyReach, Smartlead, n8n, Make, and a dozen more. I have worked with more spread sheets than any growth marketer should. I have apologized to more founders about tool sprawl than I'd like to admit.
So when Sayanta and Rajat showed me the early AI builder, I genuinely tried to break it.
Built a multi-step LinkedIn warm-up sequence with intent triggers, dedupe logic, and a fallback for when our enrichment provider returned junk. The kind of workflow that usually takes me 3 days in n8n and another day debugging.
For any marketer or SDR leader scrolling this, I would be deeply thankful if you could give the brainstorming agent a spin and let me know your thoughts
or
Drop your hardest GTM problem in the replies. I will personally walk you through how I'd attack it on nRev.
Hi PH, Aradhya here. I head Product at nRev and have been on the founding team since day one.
When "AI builds it" enters any pitch, every product person quietly worries about the same thing. The magic demo problem. Looks beautiful in a 60 second video. Falls apart at workflow building.
We have spent the last year obsessing over the unglamorous half. What happens when an integration breaks at midnight. What happens when a user describes a workflow that's actually 3 workflows tangled together. What happens when the same prompt produces slightly different results across two runs.
The product decision I'm proudest of is putting the brainstorming agent in front of the AI builder, not after it. Most teams come to nRev wanting to build a workflow they already had in mind. Half the time, after 10 minutes of conversation with the agent, they realize the workflow they wanted to build wasn't the one that would actually move their numbers. They change the plan before writing a single workflow.
That moment, watching someone rethink their motion before touching the builder, is what convinced me we shipped the right thing.
Honest ask for anyone trying nRev today. Start with the brainstorming agent.
Even if you never build a workflow on us, tell me where the agent fell short of what you'd expect from a great operator sitting next to you. That feedback shapes the next 6 months of our roadmap.
Can I set this up to watch executive job changes in my target accounts and trigger a warm outreach the day they update LinkedIn?
@athsara absolutely, and this can be completely outbound - the entire sequence of steps and a notification to let you know about it in the way you want.
@athsara Indeed. We have live linkedin monitoring that you can run on a cadence of your choice.
We further have Rocketreach as a partner that can help you directly search people who've recently switched jobs or used to work with your past customers.
You can even monitor and warm up prospects by automatically engaging with their linkedin.
Kombai
Congrats on the launch @aradhya_shandilya @sayanta_ghosh @nikhil_ojha2 @rajat_jain5 !! I'd love to know from where are you pulling in signals from? I'd like to keep a tab of updates from some products I follow - what are they building, their communications, etc. What are your sources? They post across reddit, insta, linkedin too. Do you cover those too?
@avirup_mukherjee social listening is the way to go and yes it's all in ;)
You can monitor mentions, releases, posts and even more like hiring patterns.
Brainstorm with our nrev agent. You'll be surprised.
Kombai
What happens if something breaks midway? Can users' see what broke? this has been a major problem with some of the AI integration-type tools I've tried till date
@dipanjan_dey I love this question, this is probably one of the things that make workflows stand far apart from agents. Workflows are defined by the exact steps that they need to do. In fact, even the AI steps have guardrails which ensure 100% times that they structure their output in the way that is desired.
This ensures that the sacrosanct GTM systems of record are not messed up even over millions of executions and every time the output or actions are exactly same.
Agents in nRev however are used to experiment on data sets, build the workflows but not execute workflows because of this exact same problem
@dipanjan_dey Absolutely. Every execution stays logged. Every credit attributed. You can even set up notifications directly on slack, gmail and more if anything goes off.
Hi PH, adding the technical side Sayanta skipped.
I'm Nikhil, co-founder of nRev
We started building nRev a year ago in the midst of AI transforming the world. Our first big question was agents vs workflows, which empowers GTM the most?
Workflows are predictable, follows the exact steps in the same way, and auditable. That was the foundation of nRev because of the certainty one needs in their GTM motions and the way they interact with the systems of record (sacrosanct to the teams)
Also most workflow builders didn't care about bulk executions, rate limits of vendors, fallbacks, etc. nRev takes the entire responsibility on itself so that outcomes get done everytime.
However over time, the problem that our design partners pointed out was the learning curve and technical knowledge required to build workflows.
This launch, where we come out to the world, is where nRev completely eliminates such complexity and transforms designing and building GTM experiments to conversations and instructions in plain english.
We are hungry for feedback and look forward to transform your entire distribution engine with nRev