2. 1. The Concept and Core Insight
The Problem Nobody Has Named Yet
Right now, someone is Googling your exact name and finding someone else. That someone else is getting your LinkedIn followers, your cold email replies, your job opportunities. They didn't ask for this. Neither did you. You are involuntary rivals in the same Google SERP, and you have never spoken.
This person is your namesake. You share a name, and in the digital age, that means you share a search result, a first impression, and an identity footprint. There are millions of these accidental collisions happening silently every day, and nobody has built the infrastructure to make them intentional.
The Insight: Namesakes as an Underexplored Social Graph
Every social network is built on an existing relationship: Facebook on real-world friendships, LinkedIn on professional connections, Twitter on interest graphs. Namesake is built on the name graph. Your tribe is defined not by what you chose, but by what you were given. It is the only social graph that predates the internet.
The name graph has properties no other graph has:
- Universal membership: every human on earth belongs to at least one namesake cluster
- Involuntary tie: the connection exists before the platform does, making the discovery moment inherently emotional
- SEO entanglement: namesakes compete on Google whether they want to or not, creating a shared economic interest
- Name psychology: research on nominative determinism (the tendency to pursue careers that fit your name) means namesakes often cluster in similar fields
- Identity resonance: meeting someone with your exact name is genuinely memorable, creating natural virality
Concrete Scenarios That Make This Real
| Scenario | The Pain | Namesake's Solution |
|---|---|---|
| Junior dev "James Wilson" can't rank on Google because a famous journalist named James Wilson dominates the SERP | Zero personal brand, missed recruiters, zero credibility | James connects with the journalist James, they differentiate their online presence together, coordinate anchor texts, cross-link niche content |
| Startup founder "Claire Dupont" gets emails meant for another Claire Dupont (a lawyer in Lyon) | Constant confusion, lost leads, reputational risk | Both Claires are aware of each other, can redirect misdirected contacts, add a note to their profiles ("not the lawyer Claire Dupont") |
| Tech recruiter trying to find "Alex Chen the Go engineer" among 400+ Alex Chens on LinkedIn | Can't find the right person, cold outreach hits the wrong people | Namesake API differentiates namesakes by field, location, recent activity, enabling precise targeting |
| Person discovers their namesake has a criminal record and is affecting their background checks | Rejected job applications, denied loans, reputational damage for something they didn't do | Namesake alerts you when a namesake event might affect you (new arrest record, viral news, etc.) |
| Author "Marie Laurent" can't get her book to rank because another Marie Laurent wrote a bestseller | Confused readers, lost sales, diluted brand | Both authors connect, cross-promote, and jointly build "Marie Laurent" as a recognized multi-creator brand |
The Name: Namesake
The product is called Namesake. The word literally means "person who shares your name."
It is English, clean, memorable, and immediately communicates the concept with no explanation needed.
Domain: namesake.app or getnamesake.com. Tagline: "Find the others."
3. 2. Market Analysis
TAM: Everyone With a Name
The total addressable market is literally all humans on the internet. That is 5.5 billion people as of 2026. The more useful framing is the segment that has a reason to care about their name's digital footprint: professionals, creators, public figures, job seekers, entrepreneurs, and anyone who has Googled themselves.
| Segment | Size | Pain Level | Willingness to Pay |
|---|---|---|---|
| Professionals (job seekers, career switchers) | ~500M globally | High (namesake confusion on Google / LinkedIn) | Medium ($5-20/month) |
| Founders and entrepreneurs | ~50M globally | Very high (personal brand = company brand) | High ($20-50/month) |
| Creators (YouTubers, writers, podcasters) | ~50M globally | Very high (name is their business) | High ($20-50/month) |
| Victims of namesake identity confusion | ~10M globally with active pain | Extreme (criminal record, viral scandal, wrong profession) | Very high ($50-200/month for monitoring) |
| B2B: Recruiters and HR teams | ~5M globally | High (can't identify the right person) | Very high ($200-500/month per seat) |
| B2B: Identity verification companies | ~10K companies | Medium (namesake disambiguation is an unsolved edge case) | API pricing ($0.01-0.10 per query) |
SAM: The Addressable Personal Brand Market
The personal brand software market is estimated at $4.2B in 2025, growing at 12% annually. Adjacent markets: online reputation management ($10B+), identity verification ($18B), and professional networking ($30B with LinkedIn dominating). Namesake sits at the intersection of all three.
Name Distribution: The Data Behind the Opportunity
Name concentration creates the opportunity. In the US alone:
- The top 1,000 surnames cover 70%+ of the US population
- "James Smith" has 38,313 people in the US (Social Security data)
- "Maria Garcia" is the single most common full name in Spain, with 40,000+ bearers
- In France, "Jean Martin" appears ~15,000 times; "Marie Dupont" ~12,000 times
- In China, "Zhang Wei" (张伟) is estimated at 300,000+ people
Even "rare" names have namesakes at scale. A name appearing 200 times in a country of 70 million is still a room of 200 people who have never met, all competing for the same Google result.
Existing Players: Who's Doing This Badly
| Player | What They Do | Gap Namesake Fills |
|---|---|---|
| Shows "other people named X" accidentally in search results | No intentional namesake connection, no coordination tools, no alerts | |
| Google People Cards | Let you add yourself to Google results (India only, discontinued) | Discontinued. No coordination between namesakes. No community. |
| BrandYourself | Personal SEO and reputation management | Treats each person individually, ignores the namesake dynamic entirely |
| ReputationDefender (Norton) | Enterprise-level ORM, suppress negative results | $1,000s/month, no namesake awareness, purely reactive |
| About.me | Personal landing page | No name-graph layer, no discovery of namesakes, dead product |
| Spokeo / BeenVerified | People search / background check aggregators | List namesakes as data, not as a community or network |
Nobody has built the network. Everyone treats namesakes as a disambiguation problem. Namesake treats them as a connection opportunity.
4. 3. Product Design and Features
Core Loop
- You enter your full name
- Namesake shows you a map of all known people with your name (aggregated from public data: LinkedIn, Twitter/X, GitHub, personal websites, news articles)
- You claim your profile and enrich it (location, profession, links)
- You can view, message, and collaborate with your namesakes
- You receive alerts when something new happens in your name-space (a namesake goes viral, a new professional namesake enters your field, a namesake event appears in news)
Feature Tiers
| Feature | Free | Pro ($12/mo) | Business ($49/mo) |
|---|---|---|---|
| Discover all namesakes | Up to 20 results | Unlimited | Unlimited + API |
| Claim your profile | Yes | Yes | Yes |
| Send connection requests to namesakes | 3 per month | Unlimited | Unlimited |
| Namesake alerts (news, new profiles) | Weekly digest | Real-time | Real-time + webhook |
| SEO differentiation tools | No | Yes (schema.org markup generator, disambiguation page) | Yes + competitor gap analysis |
| Namesake score (how likely you are to be confused) | Basic | Full | Full + trend |
| Criminal / negative press alert on namesakes | No | Yes | Yes |
| API access (for recruiters, HR, KYC) | No | No | Yes |
| White-label namesake disambiguation widget | No | No | Yes |
The "Namesake Score"
The Namesake Score (0-100) measures how likely you are to be confused with a namesake online. Inputs:
- Name commonality (rarer = lower score)
- Number of namesakes in your professional field
- Search volume for your full name
- Your current Google SERP position (estimated from indexed URLs)
- Activity level of your most prominent namesake
- Presence of negative content associated with any namesake
A score of 80+ means you are likely losing business to a namesake today. This score creates urgency, drives upgrades, and is inherently shareable ("my namesake score is 87, what's yours?").
Technical Architecture
MVP stack: Go backend (fast, cheap to run), PostgreSQL (person graph + name index), Next.js frontend (SEO-first, server-side rendering critical for pages that need to rank on Google). Data ingestion: crawl public profiles via official APIs (LinkedIn, GitHub, Twitter) and HTML scraping for personal websites, news aggregators. Name normalization layer handles transliterations, accents, and cultural name order variants.
5. 4. Business Model
Revenue Streams
| Stream | Model | Price | Target Customer | Year 1 Potential |
|---|---|---|---|---|
| Pro subscriptions | Monthly / annual SaaS | $12/month or $99/year | Professionals, creators, job seekers | $240K ARR (2,000 paying users) |
| Business subscriptions | Monthly SaaS | $49/month or $399/year | Founders, brand managers, PR agencies | $117K ARR (200 paying accounts) |
| API (B2B) | Usage-based | $0.05/query, $500/month flat for up to 20K queries | Recruiters, HR platforms, KYC/AML vendors | $60K ARR (10 accounts) |
| Namesake monitoring (enterprise) | Annual contract | $2,000-10,000/year | Public figures, executives, high-profile individuals | $50K ARR (10 contracts) |
| Verified Badges (one-time) | One-time payment | $19 one-time | Anyone wanting to officially claim their profile | $38K (2,000 badges) |
Unit Economics
| Metric | Value | Assumption |
|---|---|---|
| Free to Pro conversion | 3-5% | Typical for personal software with high emotional engagement |
| Monthly churn (Pro) | 2-4% | Monitoring tools tend to be sticky once alerts are configured |
| CAC (organic / viral) | $0-5 | Core loop is inherently shareable, SEO-first strategy |
| CAC (paid) | $20-40 | Facebook/Instagram ads targeting "Google yourself" audience |
| LTV (Pro, annual) | $144 (12 months average) | At 3% monthly churn |
| LTV:CAC ratio (organic) | 30-50x | Excellent. This is the target distribution channel. |
| Gross margin | 85-90% | Pure SaaS, minimal marginal cost per user |
The Freemium Logic
Free tier is not a courtesy. It is the data engine. Every free user who claims their profile enriches the graph for paying users. A recruiter paying $49/month for API access gets better data because 50,000 free users have self-reported their profession and location. The free product directly subsidizes the paid product's quality.
6. 5. Business Plan (Milestones and Financials)
Phase 0: Pre-launch (Months 1-2)
- Build the name index: crawl LinkedIn (via public search), GitHub, Twitter, Wikidata, and open government databases (US Census name frequency, INSEE for France)
- MVP: enter a name, see a list of namesakes with basic info, claim your profile
- Launch on Product Hunt and Hacker News "Show HN"
- Target: 5,000 signups in first 2 weeks
- Zero spend. Founder + 1 engineer.
Phase 1: Traction (Months 3-6)
- Implement Namesake Score and alerts
- Launch Pro tier ($12/month)
- SEO content strategy: "Who is [CommonName]?" landing pages (e.g. "/james-smith" showing all James Smiths)
- First B2B pilots with 2-3 recruiting agencies
- Target: 50,000 registered users, 500 paying Pro ($6K MRR)
Phase 2: Growth (Months 7-12)
- Launch Business tier and API
- Expand to French, German, Spanish markets (local name databases)
- Partnership with personal branding coaches and ORM agencies (affiliate model)
- First $10K MRR milestone
- Target: 200,000 registered users, 2,000 paying Pro/Business ($20K MRR)
Financial Projections
| Metric | Month 3 | Month 6 | Month 12 | Month 24 |
|---|---|---|---|---|
| Registered users | 10,000 | 50,000 | 200,000 | 1,000,000 |
| Paying users (Pro + Business) | 150 | 750 | 3,000 | 15,000 |
| MRR | $1,800 | $9,000 | $36,000 | $180,000 |
| ARR | $21,600 | $108,000 | $432,000 | $2.16M |
| Monthly burn (lean team) | $5,000 | $8,000 | $15,000 | $40,000 |
| Ramen profitable | No | Yes (barely) | Yes (comfortably) | Profitable |
Team
| Role | When | Notes |
|---|---|---|
| Founder / CEO | Day 0 | Product + growth. Needs to be obsessed with identity and naming. |
| CTO / Backend Engineer | Day 0 | Go + data pipelines. The data indexing work is the core technical challenge. |
| Growth / Content Marketer | Month 6 | SEO engine. Hired once first $10K MRR reached. |
| B2B Sales | Month 10 | For API and enterprise deals. Commission-based to start. |
Funding Strategy
Bootstrap to $10K MRR, then raise a small pre-seed ($300-500K) to accelerate data indexing and international expansion. The product is capital-efficient by design. A $500K raise extends 18+ months of runway at a lean burn rate. YC is the obvious target given the consumer social + B2B API dual model. The namesake angle is a genuinely novel concept that pitches well ("Facebook for people with the same name") and has clear monetization paths.
7. 6. Go-To-Market Plan
ICP (Ideal Customer Profile)
Primary ICP: professionals and creators who have already Googled themselves and found a namesake. This is not a segment you need to educate. They already know the pain. They are just waiting for someone to build them a tool. Secondary ICP: recruiters who have sent the wrong LinkedIn message to the wrong "David Kim."
Launch Strategy
Week 1: Product Hunt + Hacker News
Launch on Product Hunt with a clear tagline: "Find everyone who shares your name and stop losing business to them." The concept is inherently interesting to the PH and HN audience. Frame the HN post as "Show HN: I built a tool to find all your namesakes and understand how they affect your Google presence." The novelty of the concept will drive organic sharing.
Week 2-4: Viral Seeding
Message 200 people on LinkedIn with very common names: "Hey David, I noticed there are 47 other David Nguyen's in software engineering. I built something for this." The open rate on this message will be extremely high because it is genuinely specific and surprising. Do this manually for the first 200 to gather feedback before scaling.
Month 1-3: SEO as GTM
The product's website should itself rank for "[First Name] [Last Name]" searches. Every
public profile page on Namesake (namesake.app/james-smith) is a landing page
that surfaces when someone Googles "James Smith." This is the self-reinforcing loop:
the product is indexed by Google, so people find the product while Googling their own name.
Build public, indexable profile pages from day one.
Channel Strategy by Acquisition Phase
| Phase | Primary Channel | Target | Cost |
|---|---|---|---|
| 0-1K users | Manual outreach + PH/HN launch | First 1,000 engaged users | $0 (time only) |
| 1K-10K users | SEO (public name pages) + referral program | Organic growth via search | $0-500/month content |
| 10K-100K users | Twitter/LinkedIn content + paid social | Mass consumer awareness | $2-5K/month |
| 100K+ users | Partnerships (personal branding coaches, ORM firms, HR platforms) | B2B pipeline + affiliate | Revenue-share, 20-30% |
B2B GTM (API and Enterprise)
Target recruiters at LinkedIn Talent Solutions conferences and HR Tech (Las Vegas, June). Cold email template for recruiting agencies: "Your team is sending LinkedIn messages to the wrong David Kim 12% of the time. We've built an API that disambiguates namesakes with 94% accuracy using profession + location + activity signals. 10-minute integration, $500/month. Happy to show you a live demo."
Target for KYC/AML compliance: there are ~1,500 companies doing identity verification in the EU and US. Namesake disambiguation is a real problem in KYC: two people with the same name born the same year exist (twin namesakes). GDPR-compliant API with EU data residency is a product differentiator for European compliance buyers.
8. 7. Growth Hacking Playbook
The Core Viral Mechanic: The Namesake Score Card
Every user gets a shareable image card: "My Namesake Score is 73/100. There are 847 people named [Name] online and 12 of them are in my industry. See yours at namesake.app." This card is designed for Twitter/X, LinkedIn, and WhatsApp. The hook: everyone is curious about their own score. The share mechanic: showing your score signals self-awareness and generates replies from other namesakes. This is the Wordle mechanic applied to identity.
Hack 1: Google Autocomplete Hijacking
When someone Googles "John Smith software engineer" or "Marie Dupont LinkedIn," Namesake's
public profile page for John Smith should appear in the top 5. Build these pages with
proper schema.org Person markup, aggregated public data, and strong internal
linking. Google surfaces these pages because they answer "who are all the John Smiths?"
better than any other site. This is the product's primary organic channel.
Hack 2: The "Namesake Letter" Email
When a new user signs up, auto-send an email to their known namesakes (who are registered on the platform): "Someone who shares your name just joined Namesake." This is the same mechanic as LinkedIn's "X viewed your profile." It creates a closed loop where one user's signup triggers another user's activation. This mechanic scales faster than paid acquisition.
Hack 3: The Namesake Alert as a Reactivation Tool
When a namesake appears in the news, gets a viral LinkedIn post, or publishes a book, send an alert to all registered users with that name: "Your namesake [Name] just went viral on LinkedIn (32K likes). This might affect how people find you. View the impact report." This converts dormant free users into paying users because the alert creates real, immediate urgency.
Hack 4: The Common Name Playbook (Programmatic SEO)
Create 100K+ landing pages with patterns like:
/james-smith-- "847 James Smiths: Who Are They?"/james-smith/engineers-- "James Smiths in Software Engineering"/james-smith/france-- "James Smiths in France"/most-common-names/france-- "The 100 Most Common Names in France (and how to stand out)"
These pages rank passively, capture searchers with the exact pain point, and funnel them to signup. Target: 500K monthly organic visitors within 12 months of launch.
Hack 5: The Twitter Thread Weapon
Post threads like: "I searched for every 'Alex Chen' on LinkedIn. Here's what I found: There are 2,400 of them. 847 are in tech. 23 are senior engineers at FAANG companies. 3 of them wrote books. We built a tool for this..." These threads are inherently engaging because they combine data, identity, and curiosity. Even people named Alex Chen who aren't on Twitter will have the thread shared to them by friends who are.
Hack 6: The Namesake Club (Community Flywheel)
Create curated "namesake clubs" for the most famous names: the John Smith Club, the Marie Dupont Club, the Mohammed Al-Hassan Club. These are group chats / forums on the platform. The clubs generate content (discussions, debates, "who's the most successful John Smith?"), which generates SEO content, which attracts more John Smiths, which grows the club. Community content is the cheapest content to produce.
Hack 7: The Recruiter Backdoor
Reach out to every recruiter on LinkedIn who has publicly complained about finding the wrong person. Search LinkedIn for "sent message wrong person name" or "confused candidate same name." These are warm leads who already articulate the problem. The first 50 B2B customers come from this search, not from ads.
Hack 8: The Hall of Fame
Build a public "Hall of Famous Namesakes": pairs of famous people with the same name (there are two "Michael Jordan"s: the basketball player and a soccer player). There are two "Elon Musk"s on LinkedIn. There are multiple "Steve Jobs"s. This page gets shared because it is genuinely interesting and funny. It drives brand awareness with zero spend.
Referral Program Design
| Action | Reward | Mechanics |
|---|---|---|
| Refer a free user who signs up | 1 month Pro free | Unique referral link, tracked via cookie + email |
| Refer a paying user | 2 months Pro free (both referrer and referee) | Stripe billing credit automation |
| Share namesake score card | Unlock "extended namesake search" (see 50 vs 20) | Immediate gratification, no friction |
9. 8. Defensibility and Moat
Why This Gets Harder to Copy Over Time
| Moat Type | How Namesake Builds It | Timeline |
|---|---|---|
| Data network effects | Every user who claims a profile enriches the graph for all other users. A competing product starting from zero has worse data forever. | Strong after 100K claimed profiles |
| Community network effects | Namesake clubs and direct connections between namesakes create social switching costs. You don't leave the app where your namesakes are. | Strong after 12 months |
| SEO dominance | 1M+ indexed public pages for common name combinations. Google starts treating Namesake as the canonical source for "who is this person?" queries. | Strong after 18 months |
| B2B API stickiness | Once an HR platform or KYC vendor integrates the Namesake API, the integration cost creates lock-in. Data quality compounds as more profiles are claimed. | Strong after first 10 API customers |
| Brand recognition | "Namesake score" becoming a common concept (like "Klout score" but useful) creates brand moat. People will say "check your Namesake score" organically. | Strong after viral inflection point |
Why LinkedIn Won't Kill This
LinkedIn has the data but not the incentive. Surfacing namesakes prominently would cannibalize profile views and confuse their engagement metrics. LinkedIn's business model depends on you being discoverable as an individual, not as part of a name cluster. Building tools that help you coordinate with competitors (your namesakes are your profile competitors on LinkedIn) goes against their incentives. This is the same reason LinkedIn never built a proper "viewed by your namesake" feature.
10. 9. Risks and Mitigations
| Risk | Severity | Mitigation |
|---|---|---|
| Privacy concerns / GDPR | High | Only aggregate publicly available data. EU data residency. Right to erasure implemented from day one. Consult GDPR lawyer before EU launch. Do not store sensitive data. |
| LinkedIn / Twitter blocks scraping | Medium | Rely primarily on official APIs and self-reported data. Build opt-in import flows ("connect your LinkedIn to claim your profile"). The scraping is bootstrap only. |
| Low willingness to pay | Medium | The B2B API monetizes the data asset regardless of B2C conversion. If consumer doesn't pay, enterprise will. Dual-channel protects against this risk. |
| Harassment (using namesake data to impersonate) | High | No raw contact info shown publicly. Messaging goes through the platform. Rate limiting. Verified badges create accountability. TOS clearly prohibit impersonation use cases. |
| Cold start problem (nobody's namesakes are on the platform) | Medium | Seed with aggregated public data before launch. The product is valuable even without the other party: the discovery ("there are 12 other you's") is valuable on day one. |
| "Interesting but not urgent" problem | Medium | The Namesake Alert creates urgency. The Score creates a number to improve. The SEO damage framing creates financial pain. Urgency must be built into the product, not assumed. |
| Name normalization complexity | Low-Medium | Start with English-speaking markets. Expand language support iteratively. Arabic, Chinese, Korean names have different rules; handle them in version 2+. |
11. 10. Verdict and Next Steps
Why This Works
Namesake is built on a real, universal, and completely unaddressed pain. The insight is non-obvious (nobody has framed namesakes as a tribe before), which gives it media traction. The core loop is inherently viral (discovering your namesakes is inherently shareable). The SEO flywheel is self-reinforcing. The B2B API provides a revenue floor that doesn't depend on consumer behavior.
The business is defensible because the data asset compounds. The first mover who builds the largest claimed-profile database wins. That database is the product. The interface is secondary.
Why Now
Personal branding has never been more economically important. The creator economy means your name is your business card. Remote work means your Google presence is your first impression. The rise of AI-generated content has made real human identity more valuable and more confusing (AI can now generate content attributed to your namesake, making the disambiguation problem actively dangerous). The timing is correct.
First 30 Days Action Plan
- Day 1-7: Build the name index MVP. Crawl Wikidata for famous people, GitHub for developers, US Census for name frequency data. Build a simple web UI: enter a name, see a list.
- Day 8-14: Add profile claiming. Build the Namesake Score algorithm. Test with 10 beta users from personal network.
- Day 15-21: SEO-optimize the public name pages. Add schema.org Person markup. Submit sitemap to Google Search Console.
- Day 22-28: Soft launch to 200 manual outreach targets (common-name professionals). Gather feedback. Iterate.
- Day 29-30: Launch on Product Hunt. Write the HN Show HN post. Schedule the first viral Twitter thread.
The Honest Pitch
This is a business that could stay small and profitable forever, or could scale to millions of users. Both outcomes are good. At $10K MRR it is a lifestyle business. At $200K MRR it is a fundable consumer startup. At $2M ARR it is an acquisition target for LinkedIn, BrandYourself, or a major ORM firm. The exit paths are clear. The market is real. The product has not been built. That combination does not appear often.