Source fidelity
drafts are built from approved documents, not pasted or remembered text.
Use caseProduct Marketing
Every launch runs from the source of truth, under your rules.
Every launch runs the same governed process, from the source of truth, with claims and release status checked before review. Launches no longer depend on one person, and you can see which agents run on the current rules.
The problem
Your launch process lives in one PMM's head. Everyone else's drafts start from whatever doc they have open. Nothing checks release status or approved claims until you read the final draft, so an unreleased feature or an uncleared customer name can slip through. And every launch queues behind the one person whose process works.
Example power-user workflow
Launch from approved sources
Your best PMM runs launches as a fixed process, not a writing exercise:
Her agent runs that same process every launch, under the same rules.
Who it serves
Heads of product marketing and PMM leads who own positioning, approved claims and launches.
Gather source docs
Pull the approved PRD and shipped changes.
Check release status
Confirm each feature is ready to talk about.
Use approved positioning
Map each change to the agreed messaging.
Build the launch kit
Create the brief, battlecard, then email.
Verify every claim
Check against the approved list before leaving draft.
Learning from sessions
Example signals to surface
Illustrative signals. Availability varies by connected agent and workflow.
Release-status checks
release status is checked before a feature appears in copy.
Claims checked against the approved list
every claim is checked before it ships.
Launch-asset sequencing
the same brief → battlecard → email order on every launch.
Reuse of approved positioning
approved message blocks are pulled in rather than rewritten from scratch.
Editorial edits that recur
the same banned phrases and naming fixes, caught across drafts.
Drafts approved on first review
assets accepted without a rewrite round.
How Halofy makes it repeatable
Product Marketing
The approved setup
A playbook bundle, backed by team rules.
In the playbook
- The launch-kit-from-source recipe
- Her voice rules and skill files
- The knowledge-base MCP settings
Team guardrails
- A Required claims and roadmap policy
- An Advisory formatting policy
- The knowledge base on the MCP allowlist
It is delivered to every PMM's agent. Approved positioning is also published at the shared parent scope, so Sales agents inherit it.
What they use
- power-user signals
- playbooks (bundled setup)
- skills
- instructions
- Required/Advisory policies
- MCP allowlist
- team memory with sources
- shared parent scope
- compliance standing
- adoption tracking.
Outcomes
What your team can work toward
Adoption, output and time-saving figures are targets, not measured customer results.
~5% → ~85% power-user coverage.
Your best PMM's launch process becomes how the whole team launches.
Output up ~20% across the PMM team
on launch workflows.
~25% less time on repeat launch workflows
for every PMM who adopts the playbook.
Make your best team's habits everyone's default.
One approved playbook. Every connected agent on the team.