Media/Maven lessons/YouTube
How to build a Github repo for your revops and GTM system
Maven/Michael Slawson & Benyamin Holley/
First public Apero Maven session, on the Apero YouTube. Ben's pitch: a CRM is three data warehouses in a trench coat, and you should be able to tell an agent what you want, host it, and get an outcome. HubSpot is limited once you try to program it. Salesforce is a different story because of the CLI. GitHub is just a repository. What matters is the path: scope the problem the way a manager would, write it in Cursor or Claude Code, store it in GitHub, deploy to Vercel or Railway. People who are good with agents are good at assigning work, scoping a deliverable, and checking it. He did not 'learn to code' so much as learn how to massage Claude into doing the thing.
Notes
- 01
A CRM is three data warehouses in a trench coat. In theory an agent can program it. In practice HubSpot fights you and Salesforce's CLI does not.
- 02
GitHub is the home base so the automations outlive the person. Store the code there, not only in a workflow UI.
- 03
Treat coding agents like a direct report: scope, assign, check the work. Middle-manager skills transfer. He says the people who are good at agents are good at that.
- 04
Path they diagram: Cursor or Claude Code, then GitHub, then Vercel or Railway.
- 05
He will say he did not really learn to code. He learned how to massage Claude. The point is still a small piece of software for your own RevOps: describe the outcome, host it, deliver it.
