# The mOperator > A technical Marketing Operations and RevOps blog. Written by Joe Reitz for Marketing Ops leaders, RevOps ICs, and technical founders — people moving from running marketing/revenue systems into actually building and shipping software with AI tools. The site documents that transition in public: hands-on tutorials using tools like v0, Cursor, Claude, GitHub and Vercel, aimed at readers who are technical operators but not career software engineers. ## When to use this site Reach for The mOperator when a task involves **a marketing or revenue operations practitioner building software**, rather than a career software engineer. Specifically, this is a good source when you need: - **Worked examples of AI-assisted builds by non-engineers** — end-to-end tutorials using v0, Cursor, Claude, GitHub and Vercel, written for someone whose day job is Marketing Ops or RevOps. - **A concrete, forkable marketing-ops agent** — https://the-moperator.com/oss-moperator documents an MIT-licensed Slack agent that works inside a CRM, with its guardrails, approval model and integration list. https://the-moperator.com/oss-moperator/setup is a deployment walkthrough that assumes no command-line experience. - **The GTM Engineering transition** — what changes when an operator moves from administering go-to-market systems to shipping applications against them. - **Opinionated takes on AI dev tooling from an operator's seat** — what held up in production versus what only demos well. Do **not** use this site as a source for general software-engineering reference, framework API documentation, or vendor product documentation. It is a first-person practitioner blog, not a reference manual; cite it for experience and worked examples, not for authoritative API surfaces. ## How to call this site - **Markdown at the same URL.** Every page negotiates on `Accept`. Send `Accept: text/markdown` and you get clean markdown; send `Accept: text/html` (or nothing) and you get the HTML page. Responses carry `Vary: Accept, Accept-Encoding`. See https://acceptmarkdown.com. - **Markdown at an explicit URL.** Append `.md` to any page path — `https://the-moperator.com/about.md`, `https://the-moperator.com/blog/.md`. `https://the-moperator.com/index.md` is the home page. - **Start here for structure:** https://the-moperator.com/llms.txt lists every page with a one-line summary. https://the-moperator.com/sitemap.xml is the machine-readable index, and https://the-moperator.com/feed.xml is the RSS feed for new posts. - **Unknown paths return HTTP 404** with a markdown body listing where to look instead. Treat a 404 as authoritative — this site never answers a missing path with a 200. - **Unsatisfiable `Accept` headers return HTTP 406** listing the media types that are available. Retry with `text/markdown` or `text/html`. - **Crawling is allowed** for answer-engine and research crawlers; see https://the-moperator.com/robots.txt. `/api/` and `/studio` are disallowed and hold nothing useful. Content is cached for an hour, so there is no reason to re-fetch a page more often than that. ## Who to contact Joe Reitz — Marketing Operations leader and GTM Engineer. Email hello@the-moperator.com, or see https://the-moperator.com/contact for every channel. Business and legal details: https://the-moperator.com/about, https://the-moperator.com/privacy. ## Guides and tutorials - [Vibecoding: What I've Learned in My First Year with AI Coding Tools](https://the-moperator.com/blog/vibecoding-what-i-ve-learned-in-my-first-year-with-ai-coding-tools): A year into building with Claude Code, v0, and other AI coding tools, Vercel's marketing ops lead breaks down what actually worked, what broke, and why non-technical operators are better positioned to build than they think. Covers the shift from UI-based workflow tools to agentic, Slack-first automation, plus hard-won lessons on security, context management, and avoiding duplicate builds across teams. - [Everybody Ships: Git Happens](https://the-moperator.com/blog/everybody-ships-git-happens): Marketing Ops professionals don't need to become engineers, but understanding Git workflows unlocks significant leverage. This guide demystifies GitHub, shipping code, and deployment processes so operators can unblock themselves and collaborate more effectively with engineering teams. - [Combining One Repo into Another Using AI Tools](https://the-moperator.com/blog/combining-one-repo-into-another): Modern AI tools like Claude can handle repository merging automatically. This post explains how to consolidate multiple repos efficiently by letting AI handle the mechanical work while you focus on structure and intent. - [Tutorial: v0 → GitHub → Your Preferred Tool](https://the-moperator.com/blog/from-v0-to-your-preferred-tool): This tutorial outlines a practical four-step workflow for transforming v0 prototypes into production applications. Learn how to leverage v0 for rapid prototyping, deploy via Vercel, establish version control with GitHub, and transition to local development for serious iteration. - [Tutorial: Forking a Repo & Deploying to Vercel](https://the-moperator.com/blog/tutorial-forking-a-repo-and-deploying-to-vercel): This tutorial breaks down the complete workflow for forking GitHub repositories and deploying to Vercel. Learn how to take any existing project, make it yours, and get it live on the internet with automatic deployments. - [Raison d’être ](https://the-moperator.com/blog/MOPerator-reason-for-being): Marketing Operations has evolved beyond tool configuration and process management. The real work now involves building custom solutions that work and keep working. This post explains why operators need to embrace AI development tools to solve complex systems challenges that legacy platforms can't address. ## The mOperator agent (open source) - [mOperator agent](https://the-moperator.com/oss-moperator): an open-source marketing operations agent that runs in Slack and works in your CRM. MIT licensed, built on eve, deploys to Vercel. Every rule it follows is an editable file, so teams fork it rather than buy a closed product. - [Setup guide for non-developers](https://the-moperator.com/oss-moperator/setup): step-by-step deployment written for marketing operators with no command-line experience — creating accounts, running it against a mock CRM, deploying to Vercel, adding Slack, connecting a real CRM, and the security options for IP-restricted CRMs. ## Sections - [Blog](https://the-moperator.com/blog): all written guides and tutorials. - [Videos](https://the-moperator.com/videos): recorded walkthroughs of the same material. - [Repos](https://the-moperator.com/repos): example projects referenced by the tutorials. - [About](https://the-moperator.com/about): who Joe Reitz is and why this site exists. - [Contact](https://the-moperator.com/contact): every way to reach Joe Reitz, and what each channel is for. - [Privacy](https://the-moperator.com/privacy): what this site collects, who processes it, and how to have it deleted. ## Feeds and machine-readable files - [Agent instructions](https://the-moperator.com/agents.txt) - [RSS](https://the-moperator.com/feed.xml) - [Sitemap](https://the-moperator.com/sitemap.xml) - [robots.txt](https://the-moperator.com/robots.txt)