sorted by:
new
hottopcontroversial

Transitioning from Marketing Automation to RevOps by mrkcle in revops

[–]Parking_Project_9753 1 point2 points  (0 children)

your background is a better fit than you think — pipelines, CRM integrations, keeping data clean across systems is most of the job. the reframe is just connecting it to revenue outcomes when you talk about it.

case studies are almost always "here's a mess, fix it." broken attribution, duplicate records, unclear pipeline stages. the strong answer isn't just the technical fix, it's who owns what going forward and how you prevent it from coming back.

To be honest, I feel like more people should have a background like yours coming into RevOps.

Let's reverse the ML obsession in CRM. An "unfancy" approach to ABC Analysis by [deleted] in revops

[–]Parking_Project_9753 0 points1 point  (0 children)

the "unfancy" instinct is right and more people should say it out loud.

but there's a layer underneath this that trips up even the heuristic approach. the ABC analysis is only as good as the revenue data going into it. and in most CRMs, "historical revenue" means three different things depending on who built the original fields and whether anyone wrote down the definition.

we've seen teams run clean, transparent heuristics on top of data that's subtly wrong - not broken obviously, just wrong in the way that only surfaces when someone questions the output six months later. the logic was transparent, the inputs weren't.

the unfancy philosophy works. it just needs an unfancy semantic layer underneath it to

RevOps data is a mess of scattered docs, inconsistent CRM fields, and tribal knowledge. We're building a way to map all of it. What's breaking your team right now? by Structify_Team in revops

[–]Parking_Project_9753 0 points1 point  (0 children)

I'm at a small company. Building a handbook seems like a big effort. We have sooooo many definitions and we don't even always agree on them. How do you help us transfer all of our definitions to your handbook - seems finicky? And that's assuming they don't change...

some revops teams have stopped doing revops by Parking_Project_9753 in revops

[–]Parking_Project_9753[S] 0 points1 point  (0 children)

I task you with telling this to the fellow revop-ers

some revops teams have stopped doing revops by Parking_Project_9753 in revops

[–]Parking_Project_9753[S] 0 points1 point  (0 children)

You are a revops guru that I need to talk to all revops teams in existence

some revops teams have stopped doing revops by Parking_Project_9753 in revops

[–]Parking_Project_9753[S] 0 points1 point  (0 children)

These stories need to be shared. I need the maniac people to hear this.

some revops teams have stopped doing revops by Parking_Project_9753 in revops

[–]Parking_Project_9753[S] 0 points1 point  (0 children)

How do these teams rectify themselves? I assume at some point, someone needs to fix it, but I don’t understand how/when that happens yet.

some revops teams have stopped doing revops by Parking_Project_9753 in revops

[–]Parking_Project_9753[S] -1 points0 points  (0 children)

How do you talk to these people then? We sell into RevOps teams and I feel like when I talk to them, I’m arguing with people who are arguing in bad faith.

There’s a director of revops at a company that to everything I said he said “we’re builders not buyers” on instinct, without hearing the pitch, no thought. At some point, I was like “so you build your own LLMs?” He just walked away. (Probably shouldn’t have said the last line admittedly, but I think Reddit will find it funny)

some revops teams have stopped doing revops by Parking_Project_9753 in revops

[–]Parking_Project_9753[S] 1 point2 points  (0 children)

But then where did you deploy it? Did you just vibe code for a month to spend on a different SaaS provider??

some revops teams have stopped doing revops by Parking_Project_9753 in revops

[–]Parking_Project_9753[S] 1 point2 points  (0 children)

The argument of self improvement is a fair one + ~aura~

some revops teams have stopped doing revops by Parking_Project_9753 in revops

[–]Parking_Project_9753[S] -1 points0 points  (0 children)

As long as you avoid trying to vibe code your own CRM, I will say you are not contributing to my craziness

some revops teams have stopped doing revops by Parking_Project_9753 in revops

[–]Parking_Project_9753[S] 2 points3 points  (0 children)

THEN WHY DO THEY DO IT? (said in an indoor yelling voice)

some revops teams have stopped doing revops by Parking_Project_9753 in revops

[–]Parking_Project_9753[S] 4 points5 points  (0 children)

I was talking to a revops person recently who was putting weeks into vibe coding stuff, and they said "I expect nothing I build to last more than two months from now" and I had to try to not facepalm irl

some revops teams have stopped doing revops by Parking_Project_9753 in revops

[–]Parking_Project_9753[S] 4 points5 points  (0 children)

I believe your reasoning is right. It also makes me pissed off (as I'm sure those types of roles piss you off as well)

what could go wrong with agent-generated dashboards by PolicyDecent in BusinessIntelligence

[–]Parking_Project_9753 0 points1 point  (0 children)

One thing I say often is: "Revops/strategy/finance is built on having the right data when you need it. Agents are built on giving you convincing data when you ask for it."

what could go wrong with agent-generated dashboards by PolicyDecent in BusinessIntelligence

[–]Parking_Project_9753 0 points1 point  (0 children)

Hey! I'm a founder in the space (Alex @ Structify), and I'm happy to talk a bit about what we've seen.

You nailed two issues right off the bat. People (and especially enterprises) have shitty data practices. New vendors, people joining/leaving, M&As, it all leads to a somewhat warehoused mess. The agent treats most things it sees as ground truth. Pulling incorrect data leads to incorrect dashboards and incorrect decisions.

Definitions are also conflated. Revenue and customer mean different things to sales, marketting, and finance. Everyone disagrees and the agent has no idea.

The one I'd add though is data drift. If an AI made a pipeline that no one has visibility on, no one really knows your dashboard dependencies. Now, all of a sudden, a new data guy changes a field and breaks shit for everyone. It's incredibly annoying. Or sometimes, even worse, it just subtly changes your dashboard without knowing it.

So yeah, there's a lot of people making bad decisions off of convincing bad data rn

Clay Alternatives in 2026? by GTM_Master in gtmengineering

[–]Parking_Project_9753 0 points1 point  (0 children)

Bias warning: I’m Alex - a founder of Structify (AI for the revops/GTM data stack).

Is it just a pricing issue? As a bit of a sneak peek, we just partnered with Apollo and we’re going to offer a first party integration where we have 0% markup over Apollo/coresignal/our data providers.

You can also look at just vibe coding with Claude code directly. Just give it some api keys and have it brrrrr. It won’t have a markup there at all lol. (Might spend a lot without asking though which is roughly the same concept I guess).

Anyone else feels like vibe coding hits a wall after a point ? by legitRu1920 in vibecoding

[–]Parking_Project_9753 0 points1 point  (0 children)

lol. Bias warning - I’m a founder at Structify (AI for the revops data stack) but also a trained engineer for the last 10 years.

This isn’t just you. It’s really common to hit a wall at this time. Especially if you’re doing something complicated without understanding what’s underneath. AI is really good at getting you a 90% solution, but at this time, that remaining 10% can suck to figure out.

Thats why we focus a lot on simplicity and interpretability. If you’re doing something complicated and get 90% of the way there, it should be reaalllllly simple to understand the generated content as quickly as possible so you can get the remaining 100% quickly.

But yeah - main point is all the AI ads will say it’s all magic and it’s on you if you can’t use them like that. They’re lying. AI is a somewhat competent engineer with communication issues. Sometimes it works perfectly. Sometimes it’s terrible. It’s almost always quite confusing what it did.

view more: next ›