Filter
Exclude
Time range
-
Near
Adeleke| shopify website design| sales strategist retweeted
RevOps, SalesOps, and BusinessOps are very hot skills And the best part is, if you have a background in marketing and sales, you can easily transition into any of these roles.
One niche you want to check out as a Nigerian or African that would make you shit loads of money is Revops, they charge crazy. The relationship between sales and marketing, it's a big deal because it deals with revenue of a business. I told you already. Leave design alone.🫵🏾
2
6
135
Lovejoy_eliteva retweeted
One niche you want to check out as a Nigerian or African that would make you shit loads of money is Revops, they charge crazy. The relationship between sales and marketing, it's a big deal because it deals with revenue of a business. I told you already. Leave design alone.🫵🏾
9
4
41
1,370
Replying to @yuhikimura_lab
よりRevOpsを加速させる必要がある気がします!ここら辺を理解していないIT業界の企業から落ちていくイメージですね
2
6
Built a RevOps operating system for an AI consulting firm run by a 20-year veteran. SMBs get enterprise ops infrastructure without the headcount. Signal over noise, every day.
6
Carlos retweeted
How much did inconsistent data cost you this quarter? RevOps isn't just another department. It's the brain of your company, and without that system, every team is on its own. And that's where your cash flow pays the price.
1
3
Ramon Murbartian retweeted
Giving away the exact Claude Code framework I'd use to run all of GTM from one terminal: ads, outbound, RevOps, content. Free. Without real structure, Claude drifts after a couple of sessions and the output falls apart. With it, the system gets sharper every week. Our head of growth Ivan Falco built the whole thing. It comes down to 5 layers, each with one job: → Identity: a single CLAUDE.md that loads every session. It defines who the agent is, the rules it follows, and how it routes each task. → Rules: they live in a rules folder and load automatically based on where you're working. Outbound rules in outbound, ad rules in ads. → Skills: step-by-step workflows that only activate when a task matches them, like building a sequence, auditing a campaign, or writing a report. → Agents: subagents built for one job each, like research, QA, or code review. Each runs in its own context so it doesn't clog the main thread. → Memory: a MEMORY.md that persists across sessions. What the agent learns once carries into every session after. The layer that makes it durable is governance. You split the brain from the muscle. The brain handles governance, the muscle handles execution. An execution agent never rewrites its own rules. When it spots something worth changing, it files a proposal. You review it, confirm it, and only then does the change go live and get logged. That single rule is why the system compounds instead of drifting. Ivan put the whole framework into one guide: the folder structure, the governance loop, every skill and agent. Reply "FRAMEWORK" and I'll send it over. Must be following so I can DM.
19
23
43
3,723