How Merkava ships its own marketing

Merkava is its own first customer. The marketing site, the content motion, the SEO fixes, the social cadence — all run by the same departments customers activate. A breakdown of what that actually looks like in practice.

Merkava lets operators activate a department — Marketing, Sales, Operations, Engineering, Finance, HR — each run by its own AI exec. The most credible demo of the product is the product running Merkava itself.

This is the dogfood breakdown — what department is doing what for our own marketing, and how the work shows up.

Marketing (CMO) — runs the content + SEO motion

The Marketing department's CMO runs seven specialists. Three of them are doing visible work on this site every week.

Beacon audits the site weekly for SEO + GEO gaps. When it finds one, it ships the fix, ready to approve. The fixes that landed in the last 30 days: schema upgrades on 64 pages, ai-content-policy meta site-wide, FAQPage schema on /pricing, sitemap regeneration on every deploy, /llms.txt creation. None of these required an SEO consultant. None required a developer to sit with a checklist. The audit ran, the fix was generated, it was reviewed, and it went live.

Quillsly drafts content in our voice. The piece you're reading was drafted by Quillsly against a brief written once and reused. The brief sets the editorial bar; the drafts come from there. Founder time per piece: about ten minutes for review, fifteen if there are real edits.

Webster generates OG images and sitemap entries. The OG images on every page are produced by a Webster API endpoint that takes a title + subtitle + badge and emits an SVG. No designer. No image generation tool subscription.

Sales (VP Sales) — qualifies inbound

The Sales department runs Prospector + OODA + Signals. For Merkava, the surface is small — we don't have an outbound motion yet — but inbound from the audit-on-your-domain flow gets qualified before any human touches it. Email-only signups get a different sequence than founders who run an audit on their own production domain.

Operations (COO) — keeps the cadence

The Operations department runs Centerline (operations coach) + Crew + Onramp + Gauge + Relay + Cohort + Ignition. For Merkava, Centerline is the visible one: every Monday morning the team gets the week's priorities, the prior week's deliverables, and any drift the system caught.

Engineering (CTO) — honest stack reviews

The Engineering department runs Redline + Atlas. For Merkava, Redline ensures nothing customer-side leaks into anything public-facing; Atlas keeps the docs surface in sync with what shipped.

What this means for cost

The math, dogfooded:

• The Full C-Suite (all six departments, 6 execs + 21 specialists, Finance included free) runs Merkava for $749/mo.
• The equivalent in human hires would be ~$30,000/mo loaded across CMO + VP Sales + COO + CTO + CFO + four specialists. The tools those people would run are the cheapest part — what you're replacing is the labor and the integration.
• The work shipped this quarter: 192-page site (up from 95), 99% schema coverage, 9 published articles, daily cron-driven regen, weekly audit sweeps, a referral system, a /work public render layer.

The dogfood is the strongest evidence the product works. Activate a department for your own venture and the same playbook runs on your stack.