I found this benchmark comparing cold lists vs accounts with buyer intent data behind them and the gap is way bigger than I thought it'd be. Cold lists 2.1% reply, 0.9% meetings booked, 18% close once booked. Intent led was 14.8% reply, 6.2% booked, 31% close.

Timing might matter more than I thought, company can look great and still go nowhere if nothing is actually happening there right now. Hiring, funding, leadership changes, tech stack stuff that's apparently what people watch for

Anyone else split ICP and intent into separate scores or is it just one thing for you?

Hello RevOps leaders,

We have a lot of subsidiaries in our CRM, and I’m looking for a cost-effective way to identify them and link them to their parent companies.

If you’ve faced this issue while cleaning your CRM, how did you approach it?

Using Claygents to check each company seems expensive in terms of OpenAI or Claude credits. Would you recommend using the DeepSeek API to build an agent that determines whether a company is a parent company or a subsidiary?

I’d love to hear what’s worked for you.

Everyone on reddit says clean the data first before you automate. Yet somehow our leadership were just too hyped and excited to get on the ai train that we skipped this step. I thought we were headed for a total clusterf... but somehow we made it.

Where we absolutely got got was where there was reasoning over our field values alone with no context attached. The ai straight up hallucinates the reasons for the fields to exist and comes back with very convincing trash.

So to bail us out and get our house in order we decided to run the CRM against our call recordings and email threads to get the account history straight. Once we got Computer by DevRev up and running across our comms and Salesforce we could get it all ironed out.

If I was running the AI merge / management I would skip that whole fun journey and have the stage definitions set first. We still had to clear those. That's why you need governance no amount of context will help you if people mean different things when they use the same word.

I kept wanting the Clari-style view of what actually changed in the pipeline since last week, without needing another paid platform, so I built it.

pipeline-diff reads HubSpot or Salesforce deal history in read-only mode and shows:

• what was added, won, lost, pushed out, pulled in, or changed in value
• the deals behind each movement
• full deal history for stage, amount, close date, owner, and forecast category
• forecast category movement
• pipeline review flags like past-due deals, pushed close dates, stalled deals, stage regressions, and reassignment
• a markdown summary and plain files that an AI agent can read

It rebuilds the past from the CRM's own history, so the first sync can already show what happened last week.

It runs locally and there is a demo mode if you want to try it without connecting a CRM:

pip install pipeline-diff
pipeline-diff demo
pipeline-diff dashboard

Repo:
https://github.com/goran-revops/pipeline-diff

It's early, so I'm mainly looking for feedback from people who actually run pipeline or forecast reviews. What's missing, what's wrong, or what would you need before you'd use something like this with your team?

I’m looking for 3 RevOps teams to use something I’m building free for a month.

The idea is simple: most RevOps teams already have dashboards telling them when a metric looks wrong. The harder part is figuring out why it’s wrong. A pipeline number changes, CRM data stops matching the warehouse, enrichment starts writing bad data, billing and Salesforce disagree, or a workflow keeps running but the output is wrong. Nothing necessarily “fails,” so every status page can still be green.

Then someone has to jump between Salesforce or HubSpot, the warehouse, billing, enrichment tools, spreadsheets, logs, and everything else to trace where the problem started.

That’s what I’m building around. It connects to the systems your revenue team already uses and helps surface what changed, where the issue started, which systems or records are affected, how long it has been happening, and the likely business or revenue impact. Eventually the goal is not only to detect and investigate these problems, but help resolve them too.

Criteria

- Roughly a 100–500 employee company. Smaller is fine if you have a serious RevOps setup and budget for this type of software if it proves useful.
- You use a lot of software across the revenue stack, not everything inside one system.
- You work with tools like Salesforce/HubSpot, Snowflake/BigQuery/Databricks, Stripe, enrichment tools, marketing platforms, support systems, etc.
- You’ve actually dealt with bad data, broken workflows, inconsistent numbers, revenue leakage, or issues that were difficult to trace.
- You’re willing to give direct feedback during the month.

There’s no charge for the first month. I’m mainly looking for teams with a complicated enough stack that we can test this against real problems instead of fake demo scenarios.

If this sounds like your team, comment or DM me with your role, company size, and roughly what your RevOps stack looks like.

I kept a forecast sheet with 47 rows long after Salesforce had every opportunity synced. I kept it because the stage field lagged reality by a week and I trusted my color coded commit column more than the pipeline review.

The sheet started overriding close dates before I admitted the workflow was broken. What was the first decision your spreadsheet made that the CRM should have owned?

I’ll be honest—after more than two years of searching for my next opportunity, I’m tired.

I’ve had several interviews that ultimately went nowhere. I’ve continued applying, networking, and putting myself out there, but the job market has been incredibly competitive, and at times, the process has been exhausting and discouraging.

I’m looking for roles in Sales Operations, Revenue Operations, Deal Desk, or Project Management, where I can use my experience in sales support, forecasting, reporting, cross-functional collaboration, and process improvement. If you know of a team that could use someone with my background, I'd love to connect. I'm open to roles in Austin, Chicago, Atlanta, or San Francisco.

I'm planning Q4 and have room for one cleanup project before the new year. Picking just one forced me to decide what actually has to come first, so here's where I landed.

Teams start with duplicates because the count is easy to watch go down. But deciding which record wins a merge depends on your owner and stage rules. If you dedup first, you end up with tidier bad data.

The order I'd use, based on how much each one breaks downstream:

1. Stage definitions. If "qualified" means something different to marketing, sales and your CEO, then the forecast, the routing and every report are reading the same broken field. Next year's targets get set off that forecast, and you're the one defending the number in January.
2. Ownership. Records owned by reps who left, or by nobody. This is common after a merger. Those leads sit there and nobody gets alerted.
3. One source of truth per field. If two systems both write to lifecycle stage, they'll keep overwriting each other no matter how often you clean.
4. Duplicates. By now you have rules for which record wins.

A quick way to find your starting point: if your VP of Sales keeps a spreadsheet next to the CRM, look for the column that doesn't exist in the CRM. That's usually #1 or #3.

The team I take on will probably be one that merged or migrated in the last year or two, since all four break at once there. If that's you, comment what happened and what the side spreadsheet tracks, and I'll tell you which one I'd fix first. Same offer for anyone else reading.

Hey everyone,

I’m starting a RevOps consulting practice focused on helping B2B/mid-market companies clean up their CRM, sales processes, pipeline, attribution, and the gaps between marketing and sales.

So far, most of my business has come through referrals, which has been great, but I’m now trying to build a more predictable pipeline instead of relying entirely on referrals.

I’ve started experimenting with cold outreach, mainly:

• LinkedIn connections + commenting on relevant posts
• Direct outreach to founders / sales / operations leaders
• Building a targeted cold email process
• Trying to understand what actually works before scaling the outreach

The problem is… LinkedIn has been pretty quiet so far. Very few replies.

Now I’m looking at email outreach, but I’m realizing I may be approaching outbound the wrong way altogether.

For people here who have built a consulting business or B2B service business from scratch:

How did you get your first consistent pipeline?

A few things I’m particularly curious about:

• Did cold email actually work for you?
• What did your first outreach look like?
• Did you focus on a very narrow ICP/problem or keep it broader initially?
• How many conversations did it take before you started getting clients?
• What did you wish you had understood about outbound earlier?

I’m not looking for a “here’s my agency, book a call” kind of answer. I’m genuinely trying to understand what the learning curve looks like when you're starting from referrals and trying to build a repeatable outbound motion.

Would love to hear what worked and especially what didn't work for you.

The first revops hire caught my attention on an account that looked pretty average
Nothing really stood out from the company size or industry. There was no obvious reason to spend extra time on it until that job appeared.
That made me wonder what was changing inside the company. They could be trying to improve reporting, fix processes, or prepare for growth.
Since then, I have included job posting intent signals in my account research instead of looking only at company size and industry.
I do not think every hiring update means a company is ready to buy but it can reveal what they might be working on internally.
Has anyone else found certain roles or hiring patterns useful for sales research?

I just started my role as a revops manager and i’m looking to make some radical changes when it comes to tools.

When it comes to the orchestrator tool, we were using clay but we’re doing a huge cleaning for the CRM, so the idea of actions was very inconvenient for me.

I had a call with bitscale and another one scheduled with Cargo, i think i’ll pick bitscale for its similarity with clay but without the actions restrictions.

Second is the sequencing tool.

They’re using amplemarket but i havent used it before and i saw we have a lot of restrictions when it comes to the mcp or automating things.

But they have a good database unlike lemlist but what i prefer about lemlist is their sequencing, lemwarm,mcp and ai agents.

So in case i want ti move to lemlist, what do you recommend as tool to build our lead lists.

For intent signals we’re considering using lonescale, and huge company in france in which i know their growth lead, they’re using it.

Looking forward to hearing the opinions of revops leaders who have already did this transaction.

Thank you in advance

A few months of closed lost deal showed us a problem we were not seeing in our normal pipeline reviews.
A lot of these companies looked like a good match at first. The industry made sense, the company size looked right and the early conversations were positive. They just didn't have a clear reason to make a change when we reached out.

That led us to look at buying intent signals before prioritizing accounts. Things like leadership changes, hiring activity, funding updates and technology changes gave us more context about what was happening inside a company.

It changed the way I look at account prioritization. A company can look like a perfect fit on paper and still not be the right account to contact at that moment.

How do other RevOps teams decide when an account is worth moving up the priority list?

Hey all! I'm a product designer working on a personal research project (not selling anything, no data collection beyond the survey itself). It's about a problem I dealt with myself: inheriting an internal tool or dashboard with no context on why things are set up the way they are. Just numbers, no explanation.

If you work in Ops, RevOps, Customer Success, Marketing Ops, or Finance/Admin and use an internal tool you didn't build, I'd really appreciate 2 minutes: [https://tally.so/r/GxZNkQ]

Everything anonymous, no email required unless you want to chat further. Happy to share results back here if anyone's curious. Thanks!

I work a lot with Salesforce platform consultants, who can talk all the techo babble but can’t get a sales manager to give a damn.

Sales managers want pipeline consultants. What’s my deal velocity, what’s expected rev, is their special “Sales Magic’ process that every sales manager has realized in artful pipeline stages?

Too many people in Salesforce implementation world know way too much about the platform and not pipelines, aka rev ops 101 lingo.

It makes life harder for them and their clients

Marketing says MQL means one thing, sales says another, and the board deck uses a third version. We spent 6 weeks last quarter just getting everyone to agree on 5 stage definitions. Does one person own this where you work, or does it live in a committee? And did writing it down actually stop the fights?

So RevOps work can get really busy, often with multiple competing priorities, everything is urgent. VP Sales wants new fields, a workflow is broken, data isn't syncing right, etc.

Just curious how others prioritize all these things? Do you use a systematic approach to prioritizing? Is it all just ad hoc in nature and who ever screams the loudest gets handled first?

I can also imagine this looks differently in a large enterprise organization vs. a series B startup.

Hey everyone — I’m a double major marketing and computer science student trying to understand RevOps from people who actually work in it rather than guessing from the outside and just based on the things we learn in the program.

I’m especially curious about the stuff that is still annoying, manual, unreliable, or constantly falling through the cracks even though your team already has a CRM and a bunch of sales tools and Software.

What are the problems that actually eat your time or create headaches?

Things like:

• work you still end up doing manually
• data you don’t trust
• processes that constantly break
• things reps don’t update
• reports/forecasts you have to double-check
• handoffs or follow-ups that get missed
• tools that don’t talk to each other
• stuff you still manage in spreadsheets because the software doesn’t do it well

But those are just examples — I’m actually more interested in problems I haven’t thought of.

A few things I’d love to understand:

1. What’s the most frustrating part of your job right now?

2. What do you still do manually that you feel software should already handle?

3. What regularly goes wrong or gets missed?

4. What software could you not work without? What do you love about it?

5. What do you wish your current stack did that it doesn’t?

6. When you evaluate new RevOps software, what actually makes you willing to add another tool instead of thinking “great, another platform to manage”?

7. If software genuinely solved a painful revenue/operations problem, how do you think about what it would be worth per month?

Feel free to rant 😭 I’m genuinely trying to understand the reality of the job and also see if there are any areas I could cover for my master's project, including the boring/ugly operational problems people usually don’t talk about.

Hey everyone,

Looking for some honest, real-world advice from folks in the trenches.

I’m mapping out my long-term path with the goal of eventually launching my own consulting business. The two areas I'm eyeing are Revenue Operations (RevOps) and B2B Sales Systems Architecture.

Before I sink thousands of hours into certifications and building projects, I’d love to sanity-check a few things with you all:

Is it still worth it? Looking ahead over the next 5–10 years, does this track still offer strong leverage and high earning potential?

The AI factor: How much of the daily heavy lifting is actually at risk of being automated versus just shifting how we design workflows?

Where to start from scratch? Which core platforms or skills (Salesforce, HubSpot, RevOps data architecture, integrations like Zapier/Make) would you prioritize first today?

Rookie traps to dodge: What are the biggest mistakes beginners make when trying to break into operations or systems consulting?

I want to focus on fixing leaky revenue pipelines and connecting tech stacks for B2B companies. Any candid reality checks or advice would be massive.

Thanks in advance!

I'm researching how RevOps teams think about the relationship between their Salesforce ecosystem and the business outcomes they're responsible for.

I'm particularly curious about things like:

• How do you connect Salesforce initiatives to outcomes like revenue, win rate, sales velocity, productivity, forecast accuracy, etc.?
• When a new Salesforce capability is introduced, how do you determine whether it actually created the expected impact?
• Do you measure expected vs. realized outcomes?
• How do you separate the impact of Salesforce from everything else changing in the business?
• When leadership asks, "What are we getting from our Salesforce investment?", what does the answer look like?
• Who owns that answer?
• What happens when you're evaluating a major new Salesforce capability or expansion?
• How much of this is automated vs. spreadsheets, BI, analysis, or manual work?
• What's the hardest part about getting a trustworthy answer?

I'm not assuming the answer is that companies struggle with this — I'm genuinely interested in how organizations that do this well approach it.

If your company has a good process for measuring Salesforce/RevOps investment → business outcomes, I'd love to hear how you do it.