Naming Architecture

1. Executive Summary

Naming Landscape Diagnosis

ServiceNow's product naming is in active contradiction with the brand strategy. The strategy positions the company as operational infrastructure, yet the product nameplates are drawn from generic AI cohort vocabulary: Now Assist, Now Intelligence, AI Agents, AI Agent Studio, AI Control Tower, AI Experience, AI Specialists, Now Assist Skill Kit, Now LLM, Now SLM. Strip "Now" off and ServiceNow's catalogue is indistinguishable from Salesforce, SAP, Workday, IBM, Adobe, Atlassian, and Microsoft.

What Works vs. What Undermines

Three names work — Now Platform, AI Control Tower, EmployeeWorks.

Three names actively undermine — Now Assist, Now Intelligence, Otto.

Recommended Naming Architecture Principle

Adopt the [X]Works system. "Works" is the single most strategically loaded English noun available: verb of execution, noun of operational machinery, 19th-century industrial suffix, and outcome assertion.

Top Three Immediate Naming Moves

1. Retire "Now Assist" — rename to [X]Works family (ITWorks, CustomerWorks, EmployeeWorks, CreatorWorks, OperationsWorks, FieldWorks, PortfolioWorks)
2. Reposition Otto from product brand to UI surface (like Siri)
3. Promote "AI Control Tower" to strategic master-brand position

2. AI-Native Naming Audit

Cohort Naming Conventions

The AI industry has collapsed into a handful of generic naming conventions. Every major vendor draws from the same bucket of descriptors:

Distinctive Names Analysis

Anthropic — Haiku / Sonnet / Opus / Mythos

The gold standard. Anthropic's tier names are drawn from literary and musical forms — they signal intellectual ambition without claiming AI functionality in the name itself. The naming works because it creates a coherent metaphorical universe (short form → medium form → magnum opus) that maps perfectly to capability tiers without ever saying "small/medium/large." The Mythos leak (Fortune, March 26, 2026) extends the architecture into narrative territory — myth as the ultimate form of human knowledge transmission. Every name sounds like it belongs in a library, not a server rack.

OpenAI — GPT / ChatGPT

Legible only because first. "GPT" is an acronym (Generative Pre-trained Transformer) that succeeded purely through temporal advantage — it was the first consumer-visible AI brand. No latecomer could build brand equity from an acronym this generic. ChatGPT works because "Chat" is the interaction modality and "GPT" was already a household abbreviation. This is not replicable strategy; it's historical accident.

xAI — Grok / Meta — Llama

Grok (from Heinlein's "Stranger in a Strange Land," meaning to understand intuitively) is distinctive, ownable, and phonetically memorable. Llama (Large Language Model Meta AI) is a forced acronym that accidentally produced a friendly, memorable animal name. Both work because they are proper nouns with no functional descriptor — they name the thing without describing what it does.

SAP — Joule

Named after James Prescott Joule, the unit of energy. This is the strongest enterprise AI name in the cohort. It signals: (a) scientific precision, (b) measurable output (energy/work), (c) historical authority (Victorian-era physics), (d) phonetic distinctiveness. "Joule" sounds like nothing else in enterprise software. The only weakness: it replaced "SAP Business AI," proving SAP recognized the generic-name trap.

Adobe — Sensei and Firefly

Sensei (2016) was early and distinctive — the martial arts master metaphor positions AI as expertise. Firefly (2023) is the generative AI brand, evoking light, creativity, natural wonder. Both succeed because they are metaphorical proper nouns that do not describe AI functionality. Adobe is the only vendor with two distinctive AI sub-brands.

Atlassian — Rovo

Short, phonetically punchy, meaningless (a neologism). Rovo works because it sounds like a thing, not a description. Its weakness is that it has no semantic payload — unlike Joule or Sensei, "Rovo" carries no associative meaning. It is distinctive but not loaded.

Salesforce — Einstein → Agentforce Migration

Salesforce traded the most distinctive AI name in enterprise software (Einstein — genius, relativity, scientific revolution) for a generic compound (Agentforce — "Agent" + "force," indistinguishable from workforce, salesforce, taskforce). This is a cautionary tale: Einstein was famous, unique, and loaded with meaning. Agentforce is legible, uniform, and empty. Salesforce chose architectural consistency over brand distinctiveness.

Workday — Illuminate → Sana Migration

A 13-month case study in naming instability. Workday launched "Illuminate" (September 2024) as its AI platform brand — metaphor of light, understanding, clarity. By late 2025, they had acquired Sana and were migrating to "Sana" as the AI brand. This double-rename signals strategic uncertainty to the market. The lesson: naming changes are expensive in credibility, not just marketing dollars.

IBM — watsonx

Watson was the strongest AI brand name in enterprise history (Jeopardy!, 2011). IBM diluted it by over-applying it to everything, then attempted a reset with "watsonx" (lowercase w, added x). The "x" suffix is borrowed from SpaceX/Tesla's naming energy but reads as desperate on a 112-year-old company. Watson's brand equity was earned through a singular cultural moment; watsonx is trying to borrow that equity while signaling "this time it's different."

Five Anti-Patterns in AI Naming

1. Bare "AI" prefix — Guarantees commodification. "AI Agents" is not a brand; it is a category descriptor.
2. Function-as-name — "Assist," "Intelligence," "Copilot" describe what the product does, not what it is. They become invisible as the function becomes table-stakes.
3. Acronym overload — LLM, SLM, RAG, GPT. These are engineering identifiers, not brand names. They signal "for developers" even when the product is for business users.
4. Forced portmanteau — "Agentforce," "Illuminate," "Moveworks" (before acquisition). Compound words that sound invented rather than discovered.
5. Celebrity naming — "Einstein," "Watson," "da Vinci" (Intuitive Surgical). Borrows authority but creates no ownable semantic territory. Eventually the celebrity association overwhelms the product association.

Three Principles That Work

1. Stripe — The Verb-as-Brand

Stripe is a word that means: (a) a mark, (b) a type/kind ("people of that stripe"), (c) the magnetic stripe on a credit card. The name works because it is a real English word with latent payment associations, but it is NOT a descriptor of what the product does. You cannot replace "Stripe" with a generic phrase. This is the test of a strong name.

2. Bloomberg Terminal — The Proper-Noun Infrastructure

Nobody says "financial data terminal." They say "Bloomberg." The product name became the category name because it was a proper noun applied to infrastructure. When infrastructure earns a proper noun, the proper noun becomes the category. This is the prize: when "ServiceNow" means "operational infrastructure" the way "Bloomberg" means "financial data."

3. Apple's "i" Architecture — The Prefix System

iPhone, iPad, iMac, iCloud. Apple proved that a single-letter prefix, consistently applied across a product family, creates an instantly recognizable naming system. The "i" means nothing independently — its power is purely architectural. It says "this is an Apple product" without describing functionality. This is the closest analogue to the proposed [X]Works system.

3. ServiceNow Current Naming Assessment

Full Naming Inventory by Layer

Master Brand Layer

• ServiceNow — Corporate master brand
• Now Platform — Technical platform brand
• ServiceNow AI Platform — AI-specific platform positioning

Workflow Domain Products

• ITSM — IT Service Management
• ITOM — IT Operations Management
• ITAM — IT Asset Management
• CSM — Customer Service Management
• HRSD — HR Service Delivery
• FSM — Field Service Management
• SecOps — Security Operations
• GRC — Governance, Risk, and Compliance
• SPM — Strategic Portfolio Management
• ServiceNow CRM — Customer Relationship Management (new entrant, directly challenging Salesforce with generic category name)

AI Feature Layer

• Now Assist — Primary AI assistant brand (embedded across workflows)
• Now Assist Skill Kit — Developer toolkit for building Now Assist capabilities
• Now LLM v2.0 — ServiceNow's proprietary large language model
• Now SLM v2.0 — ServiceNow's proprietary small language model
• Now Intelligence — Legacy AI/ML feature brand (being subsumed)

Agentic / Orchestration Layer

• AI Agents — Autonomous workflow agents
• AI Agent Studio — Builder environment for AI agents
• AI Control Tower — Governance and oversight dashboard
• AI Agent Fabric — Infrastructure for multi-agent orchestration
• AI Experience — End-user facing AI interface layer
• AI Guardian — Trust and safety governance layer
• AI Specialists — Pre-built domain-specific agents
• Autonomous Workforce — Marketing term for the agent ecosystem

Data / Analytics Layer

• RaptorDB Pro — High-performance database engine
• Workflow Data Fabric — Cross-instance data integration
• Context Engine — Contextual intelligence for AI decision-making
• Data Catalog — Metadata management and discovery

Conversational / Front Door Layer

• ServiceNow Otto — Conversational AI interface (named product brand)
• MyNow — Personalized employee portal experience

New Operational Naming

• EmployeeWorks — Employee workflow suite (first "[X]Works" name in market)
• Employee Slate — Employee experience dashboard

Scoring Against Operational-Authority Strategy

Each name is evaluated against a single question: Does this name reinforce ServiceNow's positioning as operational infrastructure authority?

The "Now" Prefix — Keep, Evolve, or Retire?

The "Now" prefix appears across three naming tiers: Now Platform (infrastructure), Now Assist (AI feature), and Now Intelligence (legacy AI). The question is whether "Now" is an asset or a liability.

The Case for Keeping "Now"

• "Now" reinforces temporal urgency — operational speed, real-time execution
• "Now" creates naming consistency across the portfolio
• The master brand already contains "Now" (ServiceNow)
• Brand recognition is built over 20 years of usage

The Case for Retiring "Now" from Products

• "Now" is a modifier, not a substantive — it adds urgency but not meaning
• "Now Assist" = "Now" + generic verb. The prefix cannot save a generic name.
• Apple does not prefix every product with "Apple" — iPhone is not "Apple Phone"
• Bloomberg does not put "Bloomberg" on every feature — it is implied
• Over-application of "Now" dilutes the master brand's temporal claim

Recommendation

Keep "Now" for the platform layer only. "Now Platform" works. "Now Assist" does not. The principle: "Now" should appear where infrastructure is being named. It should not appear where functionality is being described. Let the [X]Works system carry the product layer.

Apple comparison: Apple uses "i" for consumer devices (iPhone, iPad), "Mac" for computers (MacBook, iMac), and "Apple" for services (Apple Music, Apple TV+). Three prefixes, three tiers, clear architecture. ServiceNow should use "Now" for infrastructure, "[X]Works" for products, and retire generic AI prefixes entirely.

Bloomberg comparison: Bloomberg Terminal, Bloomberg Intelligence, Bloomberg Law, Bloomberg Government. The master brand IS the prefix at every tier. This is the alternative model — but it requires the master brand to be as short as "Bloomberg." "ServiceNow" at eleven letters is too long for universal prefixing. Hence the need for "[X]Works" as a product-tier architecture.

4. Naming Architecture Recommendation

The [X]Works System

"Works" carries four simultaneous meanings, all strategically aligned:

1. Verb of execution — "It works." The product delivers outcomes.
2. Noun of operational machinery — "The works." Industrial infrastructure, clockworks, waterworks.
3. 19th-century industrial suffix — Steelworks, ironworks, gasworks. Signals manufacturing-scale operations.
4. Outcome assertion — "This works for us." Pragmatic, results-oriented, no-nonsense.

No other English word carries this quadruple payload. "Works" simultaneously claims: operational infrastructure (brand strategy), proven outcomes (customer value), industrial scale (enterprise positioning), and pragmatic authority (CIO language).

Full Naming Proposal — 15-Name System

Additional Candidates for Future Domains

• DataWorks — Data operations, analytics infrastructure
• NetworkWorks — Network operations, connectivity management
• HealthWorks — Healthcare operations, clinical workflow
• PublicWorks — Government/public-sector operations (bonus: "public works" is already a term of civic infrastructure)
• TradeWorks — Financial services, trading operations

How the System Sounds Different from AI-Native Brands

Phonetic audit: The [X]Works names occupy a completely different phonetic space than AI-native brands. Compare:

• AI Agents, AI Studio, AI Experience — breathy, abstract, aspirational
• Copilot, Agentforce, Illuminate — compound, synthetic, manufactured
• ITWorks, FieldWorks, SecurityWorks — percussive, concrete, mechanical

The [X]Works names sound like they belong in an industrial catalog, not a tech marketing deck. This is the point. They signal: we build operational machinery, not AI features.

Romaniuk Distinctiveness Analysis

Applying Jenni Romaniuk's distinctiveness framework (How Brands Grow Part 2), each [X]Works candidate is scored on:

5. The Transition Plan

Phase 1 — Introduce, Do Not Rename (0–6 Months)

The critical principle: introduce the [X]Works names as additions, not replacements. Let the market encounter them as new product launches, not confusing rebrandings.

• Launch ITWorks as a named experience within ITSM — "Now Assist in IT" becomes "ITWorks, powered by Now Platform"
• Amplify EmployeeWorks (already in market) — make it the public proof-point for the [X]Works architecture
• Begin using AI Control Tower as the master governance brand in all AI-related communications
• Quietly stop marketing "Now Assist" as a standalone brand — let it fade from keynotes, hero pages, and campaign headlines
• Reposition Otto in documentation as "the conversational interface to [X]Works products" — never as a standalone product name
• Commission trademark searches for all [X]Works candidates in relevant classes
• Begin analyst briefings using [X]Works language to seed category creation
• Update Knowledge conference branding to feature [X]Works naming prominently

Phase 2 — Rename Core Products (6–12 Months)

At this point, the market has encountered [X]Works names for two quarters. Analyst reports mention them. Customers reference them. The rename feels like formalization, not disruption.

• Formally rename Now Assist experiences to their [X]Works equivalents across all domains
• Launch CustomerWorks as the CRM product brand (retiring "ServiceNow CRM" before it calcifies)
• Launch SecurityWorks and GovernanceWorks as the SecOps and GRC rebrandings
• Promote AI Control Tower to master-brand status for all AI governance communications
• Demote Now Intelligence entirely — fold remaining features into the [X]Works products
• Update all product documentation, SKU names, and pricing pages to [X]Works architecture
• Retrain sales teams on [X]Works positioning (operational infrastructure, not AI features)
• Update Gartner/Forrester/IDC submission materials to use [X]Works taxonomy

Phase 3 — Full Architecture Deployment (12–24 Months)

By month 12, the [X]Works architecture is the default naming system. Phase 3 is about completeness and consistency.

• Retire all remaining "AI [Function]" names (AI Agents → subsumed under CreatorWorks; AI Experience → subsumed under relevant [X]Works product)
• Retire "Now Assist Skill Kit" — rename to CreatorWorks SDK
• Launch sector-specific [X]Works brands as market demand warrants: HealthWorks, PublicWorks, TradeWorks
• Establish the [X]Works naming governance committee — no new product name may be created outside the architecture without CMO+CPO approval
• Achieve consistent naming across: website, documentation, SKUs, contracts, analyst materials, keynotes, partner materials, and training content
• Begin measuring brand distinctiveness metrics (Romaniuk framework) for each [X]Works name independently
• Sunset all legacy acronym brands (ITSM, ITOM, CSM, HRSD) in customer-facing materials — retain only in technical documentation and API naming
• Publish the ServiceNow Naming Architecture as an external brand asset (similar to Salesforce's naming system documentation)

What This Transition Costs — Rough Scoping

Naming transitions are expensive. The cost is not in trademark filings (minimal) — it is in:

• Sales enablement — Retraining 15,000+ sales reps on new naming. Estimated 2-3 quarters for full adoption.
• Partner materials — 500+ partner organizations need updated collateral, training, and co-marketing assets.
• Documentation — 50,000+ pages of product documentation need systematic renaming.
• Contract language — Existing contracts reference "Now Assist" and other current names. Legal review required for renewal cycles.
• Analyst relationships — Gartner Magic Quadrant submissions, Forrester Wave evaluations, IDC MarketScape positions all reference current naming.
• SEO/SEM — Paid and organic search equity built around current names must be redirected.
• Customer confusion window — 6-12 month period where customers encounter both old and new names. Requires clear mapping documentation.

The cost of NOT renaming is higher: permanent brand commodification in the fastest-growing enterprise software category. The [X]Works architecture costs one year of transition pain. Generic naming costs a decade of indistinctiveness.

6. Testing Framework — The 5-Question Naming Test

Every proposed name — whether [X]Works or any alternative — must pass all five tests. A name that fails any single test should not ship.

Test 1: Does This Sound Like an AI Company?

The Phonetic Test. Read the name aloud. Does it sound like it belongs in a lineup of AI startups (Anthropic, Cohere, Perplexity, Mistral)? If yes — it fails.

The goal is to sound like operational infrastructure, not artificial intelligence. ServiceNow should sound like Bloomberg, Siemens, Honeywell — companies whose products are the invisible backbone of industries. The name should evoke machinery, not magic.

• "Now Assist" — Sounds like an AI company. FAILS.
• "AI Agents" — Sounds like an AI company. FAILS.
• "ITWorks" — Sounds like industrial operations. PASSES.
• "AI Control Tower" — Sounds like aviation/military infrastructure. PASSES.

Test 2: Does This Sound Like Operational Authority?

The Bloomberg Terminal Test. Would this name sound natural on a Bloomberg Terminal screen? Would a bond trader see this name and think "infrastructure" rather than "chatbot"?

The benchmark is Bloomberg Terminal — a product so deeply embedded in financial operations that its name IS the category. ServiceNow's product names should carry the same weight: inevitable, load-bearing, institutional.

• "Now Intelligence" — Sounds like a feature toggle. FAILS.
• "ServiceNow Otto" — Sounds like a virtual assistant. FAILS.
• "SecurityWorks" — Sounds like critical infrastructure. PASSES.
• "RaptorDB Pro" — Sounds like a database engine. PASSES.

Test 3: Is This Distinctive from ALL Competitors' Naming?

The Romaniuk Uniqueness Metric. List every competitor's AI product name. Can this name be confused with any of them? If there is ANY phonetic, semantic, or structural overlap — it fails.

Distinctiveness is not about being "creative" — it is about being impossible to confuse. The name must occupy unique phonetic and semantic space in the buyer's memory. If a CIO could accidentally swap your product name with a competitor's in conversation, the name has failed.

• "AI Agents" — Identical to Salesforce, Microsoft, SAP naming. FAILS.
• "Now Assist" — Structurally identical to "Workday Assistant," "Joule." FAILS.
• "EmployeeWorks" — No competitor uses [X]Works. PASSES.
• "AI Control Tower" — No competitor uses aviation metaphor. PASSES.

Test 4: Would a CIO Say This Name with Respect?

The CIO-in-Suit Test. Imagine a CIO presenting to their board of directors. Would they say this product name with confidence, or would they feel slightly embarrassed? If there is any cringe potential — it fails.

CIOs are the primary buyers. They present to CFOs, CEOs, and boards. The product name will be spoken in rooms where gravitas matters. Names that sound "techy," "cute," or "trendy" undermine the buyer's authority when spoken aloud in executive settings.

• "Otto" — CIO would not name-drop a chatbot mascot to the board. FAILS.
• "Now Assist Skill Kit" — Sounds like a children's educational product. FAILS.
• "AI Control Tower" — CIO says with authority: "We've deployed the AI Control Tower." PASSES.
• "OperationsWorks" — CIO says: "We run on OperationsWorks." PASSES.

Test 5: Does This Name Get STRONGER as AI Becomes Commodity?

The 2030 Press Release Test. Write a press release dated 2030. By then, every enterprise product has AI built in. AI is no longer a differentiator — it is electricity. Does the product name still carry weight? If the name depends on "AI" being special, it fails.

This is the most important test. Most AI product names are built on the assumption that "AI" is a value-signal. By 2030, AI will be as unremarkable as "cloud" is today. Names that lean on "AI" as their differentiator will sound dated — like products still calling themselves "cloud-native" in 2026.

• "Now Intelligence" — In 2030, ALL software is "intelligent." Name is meaningless. FAILS.
• "AI Agents" — In 2030, ALL platforms have agents. Name is generic. FAILS.
• "ITWorks" — In 2030, "IT operations that work" is still a compelling value claim. PASSES.
• "AI Control Tower" — In 2030, AI governance is more important than ever. PASSES (gets stronger).

Single-Sentence Verdict

Closing Argument

ServiceNow's naming architecture is in contradiction with its brand strategy. The strategy says "operational infrastructure authority." The names say "AI feature vendor." This contradiction is not cosmetic — it is structural. Every time a customer encounters "Now Assist" or "AI Agents," they file ServiceNow in the same mental category as Salesforce, Microsoft, SAP, and Workday. The operational-infrastructure positioning leaks out through generic naming faster than marketing can pour it in.

The fix is not a creative rebrand. It is a disciplined renaming that aligns product nameplates with strategic positioning. The [X]Works system does this mechanically: every product name asserts operational outcomes (verb), industrial machinery (noun), manufacturing scale (suffix), and pragmatic authority (connotation). No competitor can follow ServiceNow into this space without sounding derivative — because "Works" is native to ServiceNow's strategic territory and foreign to AI-native brands.

EmployeeWorks is already in market. It is the seed crystal. The system grows from there: ITWorks, CustomerWorks, SecurityWorks, FieldWorks, OperationsWorks. Each name passes all five tests. Each name gets stronger as AI commoditizes. Each name sounds like infrastructure, not features.

The CIO who buys in 2028 will not remember which vendor had the best "AI Assistant." They will remember which vendor's products sounded like they were built to run operations at industrial scale. That is the naming prize. [X]Works claims it.