Skip to content

Public Roadmap Publisher

Example prompt: "Whenever a Linear roadmap item moves to a new phase like 'Now', 'Next' or 'Shipped', update our public roadmap page in Notion with customer-friendly wording, and post a heads-up in #marketing whenever something moves to Shipped so the team can decide if there's an announcement to make."

The Problem

Customers and prospects ask "what are you working on?" all the time, and the honest answer lives in Linear in language nobody outside the team will understand — engineering shorthand, internal codenames, half-resolved scope debates. Keeping a public-facing roadmap page in sync by hand is a chore the PM forgets between sprints, and the page drifts; by the time someone notices, half the entries are stale, one initiative shipped two months ago without being moved to Shipped, and the team has stopped trusting the page enough to send customers to it.

How GloriaMundo Solves It

We build a workflow triggered by phase changes on Linear initiatives that carry a "public" label. An integration step reads the initiative's title, description, target window, and the new phase. An LLM step rewrites the title and one-paragraph description in customer-friendly language — no codenames, no internal jargon, no commitments we did not mean to make publicly, with a small writing style guide passed in as context so the voice stays consistent. A conditional step picks the right destination column on the public roadmap Notion page based on the new phase: Now, Next, Later, or Shipped. An integration step finds the existing row on that page (matched by initiative ID stored in a hidden field) and updates it, or creates a new row if this is the first time the initiative has been published. A second conditional step branches on whether the new phase is Shipped: if so, an integration step posts a heads-up message to the #marketing Slack channel with the customer-friendly summary so the team can decide whether it warrants an announcement. Glass Box preview shows the rewritten wording and the destination row before anything is posted.

Example Workflow Steps

  1. Trigger (webhook): Fires when a Linear initiative with the "public" label changes phase.
  2. Step 1 (integration): Read the initiative's title, description, target window, and new phase from Linear.
  3. Step 2 (LLM): Rewrite the title and description in customer-friendly language using the team's style guide.
  4. Step 3 (conditional): Map the new phase to the right column on the public roadmap Notion page (Now, Next, Later, Shipped).
  5. Step 4 (integration): Find the existing row for this initiative on the Notion page (or create one), and update the title, description, and column.
  6. Step 5 (conditional): If the new phase is Shipped, continue; otherwise stop.
  7. Step 6 (integration): Post a heads-up message to #marketing in Slack with the customer-friendly summary so the team can decide on an announcement.

Integrations Used

  • Linear — source of truth for internal roadmap phase and content
  • Notion — host of the public-facing roadmap page customers and prospects read
  • Slack — heads-up channel for marketing when something has shipped

Who This Is For

Product managers at companies that maintain a public-facing roadmap as a trust signal — typically B2B SaaS scale-ups where prospects ask about the roadmap during the sales cycle. Especially useful for a single PM running multiple initiatives who would otherwise let the public page drift while focusing on shipping the work.

Time & Cost Saved

Manually keeping a public roadmap in sync — rewording, rearranging, remembering to mark things Shipped — takes about an hour a fortnight when it gets done, and weeks-to-months when it does not. The workflow eliminates the manual sync and the staleness; the PM's attention shifts to the editorial decisions (which initiatives are public-suitable, when to publish, what voice) rather than the bookkeeping.