Meta's Wearables team names everything — product features, hardware lines, companion experiences, and the internal programmes that tie them together. Each name carries strategic weight: it shapes how consumers understand a product, how the media covers a launch, and how the brand accumulates equity over time. The process deserved a purpose-built home.
"Every new project meant rebuilding the same process from zero — and the institutional knowledge about why a name was chosen was lost between cycles."
Brief, evaluation, and communications existed in separate documents with no automatic handoff between stages.
Each project defined its own scoring criteria, making it impossible to compare quality or decisions across the portfolio.
Every naming recommendation doc, leadership email, and Workplace post was drafted manually — despite containing largely the same structural information.
Leadership had no live view of naming projects by owner, tier, or approval status. Status updates required chasing individuals.
Namestorm Agent is a full-stack web application that guides a naming team from initial brief through to approval-ready communications — in a single, connected session. It replaces the patchwork of documents with a structured workflow where every stage feeds the next, and every decision is preserved.
The platform was designed around the team's actual process, not a generic workflow. The evaluation framework mirrors Meta's internal naming principles. The communications templates follow the exact structure required for VP-level and Director-level approvals. And the tracker reflects the three-tier naming governance model the team already uses.
Generates 3–4 distinct naming directions with up to 8 candidates each, guided by a structured brief including product context, audience, markets, and name type (proper noun or descriptive).
Every name is scored against up to 5 custom 'razors' — sharp evaluation criteria chosen from a curated library covering memorability, brand equity, legal risk, localisation safety, and more.
Produces the full approval communication suite — Naming Recommendation Doc, Leadership Approval Email, and Workplace Post — pre-populated from the brief, leading with recommendation then rationale.
A live dashboard showing every naming project by owner, tier, and approval status — with urgency highlights for projects approaching their decision deadline within three weeks.
The most immediate impact was speed. A process that previously required assembling multiple documents across several days — coordinating between brief writers, evaluators, and communications drafters — can now be completed in a single focused session. The AI handles the generative and formatting work; the team focuses on judgment.
But the deeper gain was consistency. Because every project now runs through the same evaluation framework and the same communications structure, the quality of naming decisions is no longer dependent on who is running the process or how much time they have. A junior team member working alone produces the same structured output as a senior team working collaboratively.
Most significantly, the coherence of the team's consumer narratives improved markedly. Because the recommended name, its rationale, and its competitive context all flow from a single brief into every downstream communication, the story told in the recommendation doc, the leadership email, and the Workplace post is the same story — told consistently, at the right level of detail for each audience.
Brief-to-approval-ready communications in a single session, replacing a multi-day, multi-tool process.
Consistent evaluation framework means every name is judged against the same criteria, every time.
One brief feeds every downstream communication — the same story, told consistently across all audiences and formats.
"The team spends less time reformatting information and more time making good naming decisions."
Namestorm Agent is an example of what becomes possible when AI is applied not to a single task in isolation, but to an entire workflow. The value is not in any one feature — it is in the connections between them: brief to namestorm, namestorm to evaluation, evaluation to communications, communications to approval. Each stage is made better because it inherits the context from the stage before it.
It also demonstrates the importance of designing AI tools around the specific language, governance structures, and quality standards of the team that will use them. A generic naming tool would not have served this team. What they needed — and what was built — was a tool that understood their process, spoke their language, and produced outputs that met their standards without requiring them to rewrite everything from scratch.
The Namestorm Agent is available as a Moylan Catalyst tool or as part of a full AI Transformation engagement.