MOTIVATION

Situation

• Datopian is a small data management and AI company with several products but minimal dedicated marketing capacity — roughly one person spread thin.
• We have multiple products and themes that generate a steady stream of potentially shareable work:
  • AI Learn Today — a podcast on AI; potential sibling "Data Learn Today" for data-focused content
  • DataHub — publishing new datasets, dashboards, and data insights; the theme is data sharing and data publishing
  • PortalJS / QueryList — data portals and data management; new features, best practices, and examples of great data portals
  • Datopian (consulting) — thought leadership on open data, data strategy; cross-posts from DataHub but with a broader perspective
  • AutoClaw (OpenClaw) / AI agents — running and building AI agents; topical content around open Claude, agentic workflows
  • Flowershow — Markdown publishing, publishing freedom; product features and the broader theme of simple, open publishing
• Team members regularly produce interesting work and ideas across these streams, and share updates internally on Discord.
• The "marketing team" for this effort is ~6-8 people (Yoana, Daniela, Anu, Joao, Ola, and a few developers/evangelists/designers) who all have other primary roles — this is a side responsibility.
• Design capacity is very limited (one designer, Monika, who is already busy), so we need templates and AI-assisted visuals rather than bespoke design per post.
• Very little of this makes it out to public channels like Twitter, LinkedIn, or YouTube.

Complication

The gap between internal activity and public visibility is driven by friction at every step:

• Creation friction — work gets shipped but nobody writes even a few sentences about it; there's no step in the process for producing a short notification that something happened
• Polishing friction — raw Discord posts need reworking into platform-appropriate formats
• Publishing friction — context-switching into Twitter/LinkedIn, juggling multiple account logins, remembering credentials
• Scheduling friction — no system for pacing output, leading to either bursts or silence
• Guidance friction — no clear patterns or templates for what "good" looks like for quick social posts

The result: a lot of shareable work never gets shared, and the effort-per-post is high enough that most people don't bother.

Question

What processes and AI tooling can we put in place to dramatically lower the friction from "I just did something interesting" to "it's published" — so that volume and velocity of public output increases without proportionally increasing human effort? Specifically:

• Can AI scan internal channels (e.g. What's Cooking) and draft social posts automatically?
• Can we automate or simplify the publishing and scheduling pipeline?
• What's the right cadence and goal structure to ensure consistent output rather than sporadic bursts?

Issue Tree

• How do we reduce creation friction?
  • How do we build a "share what you shipped" habit into existing workflows (e.g. PR merge, deploy)?
  • Can AI generate draft write-ups from commits, PRs, or deploy logs automatically?
• How do we reduce polishing friction?
  • Can AI transform raw internal posts (Discord, notes) into platform-ready drafts?
  • What templates or patterns make a good quick social post for our kind of content?
• How do we reduce publishing friction?
  • What tooling removes the need to log into multiple accounts and context-switch?
  • Can we centralise publishing so one flow pushes to Twitter, LinkedIn, YouTube etc.?
• How do we reduce scheduling friction?
  • What's the right cadence (daily? X posts per week?) for consistent presence?
  • What tooling handles queuing and pacing so humans don't have to think about timing?
• How do we know it's working?
  • What are we actually trying to achieve — followers, impressions, inbound leads, brand awareness?
  • How do we measure whether increased volume is translating into the outcomes we care about?