Naming Philosophy
Names matter. They signal intent, set expectations, and shape how people relate to what you build. Here's how we think about naming at Common Nexus.
Why "Common Nexus"
The parent company name was chosen deliberately to be generic enough to support diverse projects, while still carrying meaning.
Common
"Common" suggests accessibility and shared ground. It's public-facing rather than exclusive. It implies something that belongs to everyone, not locked behind walls or gatekeeping. There's also a quiet confidence in it—common things are essential things.
Nexus
A nexus is a point of convergence—a place where multiple things meet and connect. It supports the idea of a holding company that houses different practices (software, media) and different products without forcing them into a single category.
Together
"Common Nexus" describes a gathering place for accessible, practical things. It's not trendy or time-bound. It doesn't over-specify (we avoided putting "Data," "Privacy," "Digital," or "Labs" in the name). It's a foundation that can hold whatever we build.
Why a Generic-Creative Holding Name
Many companies make the mistake of encoding their current product into their company name. This creates problems:
- It limits future possibilities
- It dates the company as trends change
- It forces awkward pivots when the business evolves
- It conflates the parent entity with a single product
By choosing a name that's meaningful but not overly specific, Common Nexus can support future projects we haven't imagined yet—apps, media, writing, audio, film, or something else entirely.
Brand Architecture
Our naming structure follows a simple hierarchy:
Parent
Common Nexus LLC
Divisions
Common Nexus Apps
Common Nexus Media
Products
Independent names (e.g., "Quiet", "Field")
Optionally: "by Common Nexus"
Products have their own brand identities. The parent company provides endorsement and trust ("by Common Nexus") without dominating the product's identity. This allows each app or media project to stand on its own while still being part of a coherent family.
Principles for Product Names
When naming apps and projects under Common Nexus, we follow these guidelines:
Short and calm
One or two syllables when possible. Names should feel quiet, not aggressive or attention-seeking. A name like "Quiet" says more than "QuietTaskManagerPro."
Non-invasive language
We avoid words that sound like surveillance, tracking, or monitoring. No "Watch," "Track," "Monitor," "Spy," "Scan," or similar. Even if the app does observe something, the name shouldn't feel like a threat.
Not overly descriptive
Product names don't need to explain exactly what the product does. "Field" could be a note-taking app, a project manager, or a meditation tool. The ambiguity is intentional—it leaves room for the product to be understood through use, not through the name alone.
Timeless over trendy
We avoid naming conventions that will date quickly: no "-ly" suffixes, no "-ify" endings, no random vowel removals, no forced portmanteaus. Names should feel as appropriate in 10 years as they do today.
Natural metaphors
We're drawn to words from nature, space, and physical experience. These tend to be simple, ancient, and universally understood. They carry resonance without being clichéd.
Example Name Candidates
These are examples of names that fit our philosophy. We're not claiming trademark or domain availability—these are illustrations of the naming direction we favor.
Quiet
Calm, understated, non-intrusive
Field
Open space, cultivation, grounded
Current
Flow, continuity, present moment
Veil
Privacy, protection, subtle barrier
Signal
Communication, clarity, intentional
Margin
Space, boundary, breathing room
Tide
Natural rhythm, ebb and flow
Fern
Organic, quiet growth, resilience
Ledge
Foundation, perspective, vantage point
Thresh
Threshold, beginning, separation
Steady
Reliability, consistency, calm
Cove
Shelter, safety, protected space
Notice the pattern: single words, mostly one or two syllables, derived from nature or physical concepts, carrying subtle meaning without over-explaining.
What We Avoid
Equally important is what we don't do:
- No surveillance language: Track, Watch, Monitor, Scan, Spy
- No growth-hacking tone: Boost, Hack, Crush, Scale, Disrupt
- No forced cleverness: Flickr-style vowel drops, random capitalization
- No trend-chasing: AI-, Crypto-, -GPT, -Chain prefixes/suffixes
- No anxiety-inducing words: Alert, Urgent, Critical, Now
- No generic tech words: Hub, Lab, Tech, Digital, Smart, Pro
The Goal
Ultimately, we want names that feel like they've always existed. Names that are calm, confident, and unbothered by trends. Names that you can say aloud without feeling like you're performing. Names that let the product speak for itself.
Good names are quiet. They don't shout. They wait to be discovered.