Skip to content

Product Naming Strategy

This document outlines AI Wallet's approach to product naming and branding across different audiences and development phases, with strategic use of codenames for market positioning. Objective: Define clear naming conventions that minimize competitive exposure while maintaining marketability and audience alignment.

Naming Philosophy

Core Principles

  • Clarity: Name should clearly communicate the product's value proposition
  • Differentiation: Stand out in a crowded AI tools marketplace
  • Scalability: Name should work for both technical users and end consumers
  • Protection: Use codenames to minimize competitive exposure during early stages

Strategic Approach

AI Wallet operates as a multi-layered product with different names serving different purposes: - Internal Product Name: "AI Wallet" (full vision, investor/accelerator communications) - Beta/Codename: Softened name for closed beta and developer partnerships - SDK Namespace: Technical naming for developer integrations - Consumer Facing: Simplified name for end-user communications

Codename Strategy for Closed Beta

Rationale for Codename Use

  • Exposure Mitigation: "Wallet" language signals marketplace ambitions that may trigger competitive responses
  • Scope Clarification: Softer names help position as infrastructure/service rather than platform
  • Audience Alignment: Different names for different audience segments reduce threat perception
  • Market Testing: Ability to test multiple positioning strategies without brand commitment

Top Choice: ArcPass - Meaning: "Arc" (curve/connection) + "Pass" (authentication/key) - Positioning: Login + consent for AI apps - Benefits: - Clearly technical/infrastructure focused - Easy to pronounce and remember - SDK-friendly namespace (@arcpass/sdk) - Not threatening to existing platform players

Alternative Options: - Keystone ID: The identity stone for AI - RelayID: Route auth + budgets, not keys - Conduit: Connect users ↔ apps safely - Port: One secure port into AI tools - PassportX: Bring-your-own AI identity - Tessera: One tile that unlocks the mosaic

Usage Guidelines

Internal Communications: Always use "AI Wallet" to maintain strategic clarity Developer Relations: Use codename (ArcPass) for technical discussions Closed Beta Partners: Introduce as "ArcPass (formerly AI Wallet)" to show evolution Investor/Accelerator Communications: Lead with "AI Wallet" vision, mention codename for implementation

Audience-Specific Naming

For Developers/LOI Partners

Primary Name: ArcPass (or chosen codename) Tagline: "Drop-in authentication and billing for AI applications" Technical Namespace: @arcpass/sdk, ArcPassProvider, useArcPass()

Messaging Example: "We're building ArcPass, a developer SDK that handles user authentication, usage tracking, and budget enforcement for AI applications. Think of it as 'Auth0 for AI usage' - you get the plumbing, we handle the complexity."

For End Users

Primary Name: AI Wallet Tagline: "One account for all your AI tools" Positioning: Consumer-friendly, not technical

Messaging Example: "AI Wallet is your personal account for AI tools. Top up once, use across multiple apps, and control your spending with clear limits and receipts."

For Investors/Accelerators

Primary Name: AI Wallet (full vision) Secondary: ArcPass (implementation detail) Positioning: Ecosystem play with distribution network potential

Messaging Example: "AI Wallet starts as ArcPass - a developer SDK for AI billing and identity. Long-term, it becomes the neutral identity and distribution layer for the AI ecosystem, similar to how Stripe became the default payment layer for the internet."

For Enterprises

Primary Name: AI Wallet Enterprise Alternative: AI Governance Platform Positioning: Compliance and control focus

Messaging Example: "AI Wallet Enterprise provides centralized identity, spend governance, and compliance tracking across your AI tool ecosystem. Built for enterprises who need audit-ready usage receipts and policy enforcement."

Technical Implementation

SDK Naming Conventions

Package Names: - @arcpass/sdk - Core SDK - @arcpass/react - React components - @arcpass/server - Server-side utilities - @arcpass/types - TypeScript definitions

Component Names:

import { ArcPassProvider, ArcPassLogin, ArcPassGate } from '@arcpass/react';

API Endpoints:

POST /api/arcpass/auth
POST /api/arcpass/budget/check
GET /api/arcpass/usage

Domain and Branding

Primary Domains: - aiwallet.com (long-term brand) - arcpass.dev (beta/developer focus) - arcpass.io (alternative beta domain)

Social Media: - @aiwallet (main brand) - @arcpassdev (developer community) - Handle transitions carefully to preserve SEO

Migration Strategy

Phase 1: Closed Beta (ArcPass)

  • Launch as ArcPass for developer integrations
  • Use "Works with ArcPass" branding
  • Technical documentation uses ArcPass naming
  • Public messaging focuses on developer pain points

Phase 2: Market Validation

  • Begin introducing "AI Wallet" in user-facing contexts
  • Maintain ArcPass for technical discussions
  • Start SEO optimization for both names
  • Prepare for brand transition

Phase 3: Public Launch (AI Wallet)

  • Transition to AI Wallet as primary brand
  • ArcPass becomes technical namespace
  • Migrate developer community gradually
  • Update all public-facing materials

Phase 4: Enterprise Expansion

  • AI Wallet Enterprise for B2B sales
  • Maintain consumer AI Wallet brand
  • Technical integrations still use ArcPass internally

Competitive Considerations

Threat Level Assessment

Low Threat Positioning (ArcPass): - Positioned as developer infrastructure - Similar to existing auth providers (Auth0, Clerk) - Not immediately threatening to major platforms - Easier to get partnerships and integrations

High Vision Communications (AI Wallet): - Save for investor/accelerator contexts - Use when discussing market opportunity - Include in strategic planning documents - Reserve for post-MVP public communications

Competitor Responses

If asked about marketplace ambitions: "For now, ArcPass is focused on solving developer pain points around AI billing and identity. The long-term vision is to create a more connected AI ecosystem, but that's secondary to building great developer tools."

If pressed on platform strategy: "We're building infrastructure that happens to create network effects. The priority is making developers' lives easier, not becoming a platform. If that leads to ecosystem growth, that's a natural progression."

Implementation Checklist

Technical Setup

  • [ ] Secure arcpass.dev and arcpass.io domains
  • [ ] Set up npm organization and package repositories
  • [ ] Create technical documentation with ArcPass branding
  • [ ] Implement SDK with ArcPass namespace

Marketing Materials

  • [ ] Create ArcPass landing page focused on developers
  • [ ] Develop technical content and case studies
  • [ ] Prepare investor deck with AI Wallet vision
  • [ ] Create transition plan for brand migration

Community Management

  • [ ] Set up developer community around ArcPass
  • [ ] Create Discord/Slack for technical discussions
  • [ ] Plan gradual introduction of AI Wallet to end users
  • [ ] Prepare FAQ for naming questions

Success Metrics

Technical Adoption

  • SDK downloads and npm package usage
  • Developer integration time and success rates
  • Community engagement around ArcPass
  • Technical documentation usage and feedback

Business Metrics

  • Conversion from ArcPass to AI Wallet brand
  • Investor/accelerator response to naming strategy
  • Competitive response to different positioning
  • Customer confusion or clarity around product scope

Long-term Brand Health

  • SEO performance for both naming strategies
  • Brand recognition and recall
  • Community sentiment around transitions
  • Partnership acceptance across different naming approaches

Source Attribution

Primary source: Competition-Narratives-MVPSpecs-04Nov25-ChatGPTPlus.pdf