Three disciplines.
One team that ships.
Media operations, growth & SEO, and web development — all in-house, all production-tested across the four publications we operate. We don't outsource. We don't white-label. You talk to the people who build.
Newsroom systems, end to end.
Editorial CMS, publishing workflows, cross-site syndication, scheduled distribution, and the boring infrastructure that lets a small team look big.
We build the kind of editorial tooling that publishers usually pay enterprise vendors $50K+/year for — but tighter, faster, and tuned to how your newsroom actually works. No 47-tab admin. No 3-day setup wizards. Just the fields editors need, the workflows that match how stories actually move.
- Custom editorial CMS built on WordPress or headless — author roles, section editors, embargoes, scheduled drops
- Cross-publication syndication — write once, route to N publications with category mapping
- Newsroom dashboards for ops: pipeline, drafts, performance, by-author analytics
- RSS + IndexNow + email distribution automated on publish
- Author / contributor systems with author bio, byline credit, payment tracking
Search performance that ships.
Technical SEO, structured data, AI crawler access, and the discovery infrastructure that gets your work read in 2026 — across Google, Bing, Yandex, and the AI assistants quietly replacing them.
Most agencies sell SEO like it's still 2019: title tags, keyword density, "10x content". We don't. Our work is upstream — fixing the data layer Google's parsers actually read, the schema AI assistants need to cite you, and the crawl infrastructure that gets new content seen in hours, not weeks.
- Schema.org engineering — Person, NewsMediaOrganization, Article, FAQPage, ItemList — the kind that unlocks rich results
- IndexNow + sitemap automation for instant Bing + Yandex discovery
- AI crawler optimization — GPTBot, ClaudeBot, PerplexityBot, Applebot-Extended access + llms.txt design
- Core Web Vitals tuned to actual editorial templates, not synthetic benchmarks
- Search infrastructure audits — what's costing you crawl budget, indexation, and citations
Custom platforms, by people who run them.
WordPress at the editorial edge, FastAPI / Python services in the middle, SQLite / PostgreSQL for data — built for media operations, on-call platform engineering, and tooling we'd want to use ourselves.
We've been on the receiving end of agency code that ships on Friday and breaks on Monday. We don't ship that. Every system we build, we run — same code, same uptime expectations, same on-call as our own publications.
- WordPress & custom themes — editorial-first, not page-builder-first
- REST API & headless integrations — Next.js, Astro, native iOS/Android consumers
- FastAPI / Python services — admin platforms, ETL pipelines, AI workflows
- SQLite + PostgreSQL data layer — operational, not just analytical
- Performance & ops — Lighthouse 95+, edge caching strategy, observability
Four steps. Two weeks to first ship.
-
01
Brief & scope
30-minute kickoff call. We turn the conversation into a written brief, scope, and price within 48 hours.
-
02
Audit or sprint
Audits run 1–2 weeks and end with a written report + rollout plan. Build sprints run 2–6 weeks with weekly demos.
-
03
Ship & iterate
We ship early, ship often. Production code by week two on most engagements. Slack-ready feedback loop the whole way.
-
04
Operate or hand off
You choose: take over with documentation + training, or keep us on retainer for ops and ongoing improvements.
The questions everyone asks.
Do you take on outside clients, or only your own publications?
What stack do you build on?
Do you offer monthly retainers or one-time projects?
How do you handle AI search visibility?
Where are you located, and do you take meetings in person?
What does engagement pricing look like?
Ready to ship something serious?
Most engagements start with a 30-minute call. Tell us what you're working on — we'll either be the right team or point you to who is.