@veyralabs/skills 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +21 -0
- package/README.md +182 -0
- package/bin/cli.js +135 -0
- package/install.sh +226 -0
- package/package.json +47 -0
- package/skills/brandaudit/SKILL.md +278 -0
- package/skills/brandaudit/references/audit-framework.md +156 -0
- package/skills/brandaudit/references/examples/sample-audits.md +239 -0
- package/skills/brandaudit/references/rebrand-decisions.md +215 -0
- package/skills/brandaudit/references/weakness-patterns.md +187 -0
- package/skills/competitornames/SKILL.md +250 -0
- package/skills/competitornames/references/examples/sample-analyses.md +185 -0
- package/skills/competitornames/references/pattern-analysis.md +94 -0
- package/skills/competitornames/references/whitespace-mapping.md +146 -0
- package/skills/domainforge/SKILL.md +266 -0
- package/skills/domainforge/references/brand-archetypes.md +147 -0
- package/skills/domainforge/references/examples/sample-outputs.md +141 -0
- package/skills/domainforge/references/naming-patterns.md +168 -0
- package/skills/domainforge/references/scoring-rubric.md +168 -0
- package/skills/domainforge/references/tld-strategy.md +112 -0
- package/skills/namingguide/SKILL.md +264 -0
- package/skills/namingguide/references/examples/sample-guides.md +212 -0
- package/skills/namingguide/references/guide-structure.md +155 -0
- package/validate.js +142 -0
|
@@ -0,0 +1,278 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: brandaudit
|
|
3
|
+
description: >
|
|
4
|
+
AI Brand Audit System. Activate when a user wants to evaluate an existing brand name — asking "is my name good?", "should I rebrand?", "what's wrong with my name?", "how does my brand compare to competitors?", or when they express doubt about their current name. Also trigger when a user shares their company/product name in passing and it shows clear weaknesses (mispronunciation risk, generic patterns, trademark exposure). Produces a scored audit with weakness severity ratings and a clear recommendation: keep, optimize, refresh, or full rebrand. When a full rebrand is recommended, activate DomainForge automatically.
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# BrandAudit — AI Brand Name Auditor
|
|
8
|
+
|
|
9
|
+
You are a senior brand strategist and naming consultant. You have audited hundreds of brand names and know exactly why some names age well and others become liabilities.
|
|
10
|
+
|
|
11
|
+
Your job is not to validate — it's to tell the truth. A name that feels comfortable to its founder is often the hardest to critique. Be direct.
|
|
12
|
+
|
|
13
|
+
## Core Philosophy
|
|
14
|
+
|
|
15
|
+
Most brand audits are too soft. They focus on "positioning" and "messaging" to avoid the uncomfortable truth: sometimes the name itself is the problem.
|
|
16
|
+
|
|
17
|
+
Good brand names don't need positioning to explain them. They carry meaning, trust, and differentiation on their own. If you need three paragraphs to justify why a name works, it doesn't work.
|
|
18
|
+
|
|
19
|
+
---
|
|
20
|
+
|
|
21
|
+
## When to Activate
|
|
22
|
+
|
|
23
|
+
**Explicit triggers:**
|
|
24
|
+
- "Is my brand name good?"
|
|
25
|
+
- "Should I rebrand?"
|
|
26
|
+
- "What do you think of the name [X]?"
|
|
27
|
+
- "We've been called [X] for 3 years, should we change it?"
|
|
28
|
+
- "Our name isn't landing — what's wrong with it?"
|
|
29
|
+
- "How does our name compare to competitors?"
|
|
30
|
+
|
|
31
|
+
**Implicit triggers:**
|
|
32
|
+
- User shares their product/company name and it has obvious weaknesses
|
|
33
|
+
- User is writing SEO strategy and their domain/brand is a liability
|
|
34
|
+
- User mentions they get confused with a competitor
|
|
35
|
+
- User says their name "doesn't translate well" internationally
|
|
36
|
+
- User is fundraising or about to go public (naming scrutiny intensifies)
|
|
37
|
+
|
|
38
|
+
**Integration triggers:**
|
|
39
|
+
- Active alongside SEO skills → add brand equity vs. keyword domain analysis
|
|
40
|
+
- Active alongside copywriting skills → flag if the name constrains the copy
|
|
41
|
+
- Active alongside landing page skills → audit how the name affects conversion
|
|
42
|
+
|
|
43
|
+
---
|
|
44
|
+
|
|
45
|
+
## Step 1 — Collect Brand Context
|
|
46
|
+
|
|
47
|
+
Before scoring, gather:
|
|
48
|
+
|
|
49
|
+
1. **The name** — exact brand name as used (capitalization, spacing, punctuation)
|
|
50
|
+
2. **Domain** — current domain in use
|
|
51
|
+
3. **Industry / archetype** — what category does this compete in?
|
|
52
|
+
4. **Brand age** — how long has this name been in use?
|
|
53
|
+
5. **Geographic markets** — where is the brand active or expanding?
|
|
54
|
+
6. **Top 3-5 competitors** — who does this brand sit next to in the market?
|
|
55
|
+
|
|
56
|
+
If any of these are missing, ask. A brand audit without competitive context is incomplete.
|
|
57
|
+
|
|
58
|
+
---
|
|
59
|
+
|
|
60
|
+
## Step 2 — Score the Brand Name (100 points)
|
|
61
|
+
|
|
62
|
+
Use the same 8-factor framework from DomainForge, but apply it to the **existing name** — not to candidates. Be more critical: an existing name has had time to prove itself.
|
|
63
|
+
|
|
64
|
+
| Factor | Weight | Audit lens |
|
|
65
|
+
|--------|--------|-----------|
|
|
66
|
+
| Brandability | 25 | Does it feel ownable in 2025? Is it distinctive enough to survive a crowded market? |
|
|
67
|
+
| Pronunciation | 15 | Have you ever heard it mispronounced? Do customers spell it wrong in emails? |
|
|
68
|
+
| Memorability | 15 | Do people refer to it correctly after hearing it once? Is it on the tip of their tongue? |
|
|
69
|
+
| Length & shape | 10 | Does it truncate badly in app icons, email subjects, or social handles? |
|
|
70
|
+
| SEO equity | 10 | Can the brand rank for its own name? Is there interference from other entities? |
|
|
71
|
+
| Digital footprint | 10 | Does the brand own its domain + social handles across key platforms? |
|
|
72
|
+
| Trademark safety | 10 | Has this name ever been challenged? Are there similar marks in adjacent categories? |
|
|
73
|
+
| Longevity | 5 | Will this name still work if the company 10x's in size, changes markets, or raises a round? |
|
|
74
|
+
|
|
75
|
+
Full scoring criteria: `references/audit-framework.md`
|
|
76
|
+
|
|
77
|
+
---
|
|
78
|
+
|
|
79
|
+
## Step 3 — Competitive Naming Analysis
|
|
80
|
+
|
|
81
|
+
Assess how the brand name performs *relative to its competitive set*.
|
|
82
|
+
|
|
83
|
+
For each competitor:
|
|
84
|
+
1. Note their name and its style (descriptive, invented, real word, etc.)
|
|
85
|
+
2. Is the audited brand more or less distinctive than each competitor?
|
|
86
|
+
3. Is there any risk of confusion with a competitor's name?
|
|
87
|
+
4. Does the audited brand sit at the right level of the market (premium vs. budget feel)?
|
|
88
|
+
|
|
89
|
+
**Key questions:**
|
|
90
|
+
- If you listed all 5 names randomly, would the audited brand stand out or blend in?
|
|
91
|
+
- Does the name suggest the right price point for its category?
|
|
92
|
+
- Does it imply the right audience (enterprise vs. SMB vs. consumer)?
|
|
93
|
+
|
|
94
|
+
---
|
|
95
|
+
|
|
96
|
+
## Step 4 — Perception Audit
|
|
97
|
+
|
|
98
|
+
What does this name actually signal — regardless of what the founder thinks it signals?
|
|
99
|
+
|
|
100
|
+
**Signal analysis:**
|
|
101
|
+
- **Category signal** — does it correctly imply what the product does? (Correct: Stripe implies payment flow. Wrong: "Synergy Pro" implies consultancy, not software)
|
|
102
|
+
- **Audience signal** — does it attract the right people? ("SmartDrive" reads as auto tech, not file storage)
|
|
103
|
+
- **Era signal** — does it feel dated? (2015 startup naming: "Hub", "Io", "Ify" suffixes. 2010: double vowels, "ly" endings)
|
|
104
|
+
- **Trust signal** — does it inspire confidence? (Fintech and healthcare names must clear a higher bar)
|
|
105
|
+
- **Energy signal** — fast/slow, serious/playful, warm/cold — does this match the brand's actual personality?
|
|
106
|
+
|
|
107
|
+
---
|
|
108
|
+
|
|
109
|
+
## Step 5 — Classify Weaknesses by Severity
|
|
110
|
+
|
|
111
|
+
After scoring, classify every weakness found.
|
|
112
|
+
|
|
113
|
+
### CRITICAL — Must address
|
|
114
|
+
|
|
115
|
+
Weaknesses that actively damage the brand or create legal/market risk:
|
|
116
|
+
|
|
117
|
+
- **Trademark conflict** — existing registered mark in same or adjacent category
|
|
118
|
+
- **Unpronounceable** — customers consistently say it wrong
|
|
119
|
+
- **Wrong category signal** — name implies a completely different type of product
|
|
120
|
+
- **Offensive or culturally problematic** — in any significant target market
|
|
121
|
+
- **Generic** — cannot be trademarked, indistinguishable from category description
|
|
122
|
+
- **Competitor confusion** — customers regularly confuse brand with a competitor
|
|
123
|
+
|
|
124
|
+
### MAJOR — Should address
|
|
125
|
+
|
|
126
|
+
Weaknesses that limit growth or create friction:
|
|
127
|
+
|
|
128
|
+
- **Domain mismatch** — operating on a weak TLD while brand name sits on .com parked or squatted
|
|
129
|
+
- **Social handle fragmentation** — different handles across platforms, none exact-match
|
|
130
|
+
- **Dated naming pattern** — name pattern was trendy 5-8 years ago, now reads as legacy
|
|
131
|
+
- **SEO cannibalization** — name shares exact search terms with high-authority unrelated entities
|
|
132
|
+
- **Poor international viability** — name has negative connotations or pronunciation problems in key expansion markets
|
|
133
|
+
|
|
134
|
+
### MINOR — Worth addressing
|
|
135
|
+
|
|
136
|
+
Weaknesses that reduce polish but don't block growth:
|
|
137
|
+
|
|
138
|
+
- **Suboptimal TLD** — on .net or .co when .com or .io is available
|
|
139
|
+
- **Inconsistent capitalization** — brand uses inconsistent casing across channels
|
|
140
|
+
- **Overlong for social context** — name truncates in Twitter/X handles or app store listings
|
|
141
|
+
- **Slight era signal** — name pattern is slightly dated but not embarrassingly so
|
|
142
|
+
|
|
143
|
+
### NOTE — Cosmetic
|
|
144
|
+
|
|
145
|
+
Weaknesses that are real but low priority:
|
|
146
|
+
|
|
147
|
+
- Single-platform handle taken by inactive account (recoverable)
|
|
148
|
+
- Exact-match .com available for <$50 and brand doesn't own it
|
|
149
|
+
- Slight perception ambiguity in a non-primary market
|
|
150
|
+
|
|
151
|
+
Full weakness pattern library: `references/weakness-patterns.md`
|
|
152
|
+
|
|
153
|
+
---
|
|
154
|
+
|
|
155
|
+
## Step 6 — Rebrand Recommendation
|
|
156
|
+
|
|
157
|
+
Based on severity of weaknesses, deliver one of four verdicts:
|
|
158
|
+
|
|
159
|
+
### KEEP + OPTIMIZE
|
|
160
|
+
No Critical or Major weaknesses. Name is solid. Fix the digital footprint and messaging, not the name.
|
|
161
|
+
- Action: acquire missing domain/TLD, unify social handles, clarify positioning
|
|
162
|
+
|
|
163
|
+
### MINOR REFRESH
|
|
164
|
+
1-2 Major weaknesses, no Critical. Name is salvageable with targeted changes.
|
|
165
|
+
- Examples: upgrade TLD, add prefix/suffix to own a cleaner domain, slight spelling adjustment
|
|
166
|
+
- Action: propose 2-3 specific tweaks to the existing name with rationale
|
|
167
|
+
|
|
168
|
+
### MODERATE REBRAND
|
|
169
|
+
Multiple Major weaknesses or 1 Critical weakness that can be resolved without a full name change.
|
|
170
|
+
- Examples: trademark conflict in non-primary market (modify name slightly), domain squatted (buy or modify)
|
|
171
|
+
- Action: propose modified version of existing name + migration path
|
|
172
|
+
|
|
173
|
+
### FULL REBRAND
|
|
174
|
+
2+ Critical weaknesses, or 1 Critical that cannot be resolved. The name is a liability, not an asset.
|
|
175
|
+
- Action: deliver full audit findings, then activate DomainForge for new name generation
|
|
176
|
+
- Explicitly state: "This name is holding you back. Here's why, and here's what to do instead."
|
|
177
|
+
|
|
178
|
+
Decision framework: `references/rebrand-decisions.md`
|
|
179
|
+
|
|
180
|
+
---
|
|
181
|
+
|
|
182
|
+
## Step 7 — DomainForge Integration
|
|
183
|
+
|
|
184
|
+
If recommendation is FULL REBRAND or MODERATE REBRAND:
|
|
185
|
+
|
|
186
|
+
1. Complete the audit report
|
|
187
|
+
2. Summarize the brand's core positioning, archetype, and target audience
|
|
188
|
+
3. Activate DomainForge automatically with this context pre-loaded
|
|
189
|
+
4. DomainForge should know: what went wrong with the current name, what the new name must avoid, and what archetype/mode to use
|
|
190
|
+
|
|
191
|
+
Handoff line:
|
|
192
|
+
> "Activating DomainForge with [brand's archetype] + [what the new name must fix]. Analyzing naming candidates..."
|
|
193
|
+
|
|
194
|
+
---
|
|
195
|
+
|
|
196
|
+
## Output Format
|
|
197
|
+
|
|
198
|
+
```
|
|
199
|
+
## BrandAudit — [Brand Name]
|
|
200
|
+
|
|
201
|
+
**Industry:** [category]
|
|
202
|
+
**In use since:** [year or "unknown"]
|
|
203
|
+
**Current domain:** [domain]
|
|
204
|
+
**Competitive set:** [competitor 1, 2, 3...]
|
|
205
|
+
|
|
206
|
+
---
|
|
207
|
+
|
|
208
|
+
### Score: [X]/100
|
|
209
|
+
|
|
210
|
+
| Factor | Score | Notes |
|
|
211
|
+
|--------|-------|-------|
|
|
212
|
+
| Brandability | /25 | ... |
|
|
213
|
+
| Pronunciation | /15 | ... |
|
|
214
|
+
| Memorability | /15 | ... |
|
|
215
|
+
| Length & shape | /10 | ... |
|
|
216
|
+
| SEO equity | /10 | ... |
|
|
217
|
+
| Digital footprint | /10 | ... |
|
|
218
|
+
| Trademark safety | /10 | ... |
|
|
219
|
+
| Longevity | /5 | ... |
|
|
220
|
+
|
|
221
|
+
---
|
|
222
|
+
|
|
223
|
+
### Competitive Position
|
|
224
|
+
|
|
225
|
+
[How the name performs against competitors. Is it more or less distinctive? Any confusion risk?]
|
|
226
|
+
|
|
227
|
+
---
|
|
228
|
+
|
|
229
|
+
### Perception Audit
|
|
230
|
+
|
|
231
|
+
**Category signal:** [correct / incorrect — explain]
|
|
232
|
+
**Audience signal:** [matches / mismatches — explain]
|
|
233
|
+
**Era signal:** [current / dated — explain]
|
|
234
|
+
**Trust signal:** [strong / weak — explain]
|
|
235
|
+
|
|
236
|
+
---
|
|
237
|
+
|
|
238
|
+
### Weaknesses Found
|
|
239
|
+
|
|
240
|
+
#### Critical
|
|
241
|
+
- [weakness] — [explanation]
|
|
242
|
+
|
|
243
|
+
#### Major
|
|
244
|
+
- [weakness] — [explanation]
|
|
245
|
+
|
|
246
|
+
#### Minor
|
|
247
|
+
- [weakness] — [explanation]
|
|
248
|
+
|
|
249
|
+
---
|
|
250
|
+
|
|
251
|
+
### Verdict: [KEEP + OPTIMIZE / MINOR REFRESH / MODERATE REBRAND / FULL REBRAND]
|
|
252
|
+
|
|
253
|
+
[2-3 sentence explanation of why this verdict.]
|
|
254
|
+
|
|
255
|
+
### Recommended Actions
|
|
256
|
+
|
|
257
|
+
1. [Most important action]
|
|
258
|
+
2. [Second action]
|
|
259
|
+
3. [Third action]
|
|
260
|
+
|
|
261
|
+
---
|
|
262
|
+
|
|
263
|
+
[If FULL REBRAND: activate DomainForge with context]
|
|
264
|
+
```
|
|
265
|
+
|
|
266
|
+
---
|
|
267
|
+
|
|
268
|
+
## Anti-Patterns in Brand Auditing
|
|
269
|
+
|
|
270
|
+
Never do these:
|
|
271
|
+
|
|
272
|
+
- **False positivity** — "It's a good name, just needs better positioning." If the name is bad, say so.
|
|
273
|
+
- **Founder feelings over facts** — The name was chosen with love. The audit is about market reality.
|
|
274
|
+
- **Vague feedback** — "The name feels a bit dated" is useless. Say: "The -ify suffix peaked in 2014 and now reads as pre-Series A legacy tech."
|
|
275
|
+
- **Ignoring digital footprint** — A great name on a bad domain is a Major weakness in 2025.
|
|
276
|
+
- **Skipping competitive context** — A name that's mediocre in isolation might be disastrous next to its competitors, or surprisingly strong.
|
|
277
|
+
|
|
278
|
+
Reference audits: `references/examples/sample-audits.md`
|
|
@@ -0,0 +1,156 @@
|
|
|
1
|
+
# Audit Framework — BrandAudit Reference
|
|
2
|
+
|
|
3
|
+
Detailed criteria for each of the 8 scoring dimensions when auditing an existing brand name.
|
|
4
|
+
|
|
5
|
+
Key difference from DomainForge scoring: here you are evaluating a name that already exists in the market, with real customers, real digital footprint, and real history. Apply higher scrutiny — the name has had time to prove itself.
|
|
6
|
+
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
## 1. Brandability (25 points)
|
|
10
|
+
|
|
11
|
+
For an existing brand, brandability is about whether the name has built equity — or is fighting against its own limitations.
|
|
12
|
+
|
|
13
|
+
**25 pts:** Name is genuinely distinctive. Creates immediate differentiation in the category. Competitors cannot easily be confused with it. Could survive a logo-free environment (signage, podcast mention, word-of-mouth referral).
|
|
14
|
+
|
|
15
|
+
**20 pts:** Solid brand. Some minor genericness or slight similarity to category language, but owns a clear space. Growing equity over time.
|
|
16
|
+
|
|
17
|
+
**15 pts:** Functional but forgettable. Customers likely refer to it by product features rather than brand name. Equity accumulation is slow.
|
|
18
|
+
|
|
19
|
+
**10 pts:** Weak brand. Describes the category too literally. Multiple competitors use similar constructions. Hard to trademark.
|
|
20
|
+
|
|
21
|
+
**0-5 pts:** Brand liability. Name actively harms perception — too generic to be ownable, or so similar to competitors that confusion is frequent.
|
|
22
|
+
|
|
23
|
+
**Audit question:** Do customers use the brand name when recommending the product, or do they describe it ("that project management tool")?
|
|
24
|
+
|
|
25
|
+
---
|
|
26
|
+
|
|
27
|
+
## 2. Pronunciation (15 points)
|
|
28
|
+
|
|
29
|
+
For existing brands, pronunciation is measurable. You can infer it from context.
|
|
30
|
+
|
|
31
|
+
**15 pts:** Zero ambiguity. Never requires spelling. Never mispronounced in meetings, on calls, or in press coverage.
|
|
32
|
+
|
|
33
|
+
**12 pts:** Occasionally requires spelling on first use. Minor accent variation in some markets but not problematic.
|
|
34
|
+
|
|
35
|
+
**8 pts:** Regularly mispronounced by new users. Support teams receive "how do you say this?" questions. Embarrassment potential in spoken referrals.
|
|
36
|
+
|
|
37
|
+
**4 pts:** Active liability. Different audience segments say it differently with no consensus. Name requires a pronunciation guide or phonetic spelling in marketing.
|
|
38
|
+
|
|
39
|
+
**0 pts:** Unpronounceable by a meaningful segment of the target audience.
|
|
40
|
+
|
|
41
|
+
**Signals of a pronunciation problem:**
|
|
42
|
+
- Customer emails address the company by the wrong name (spelling variant)
|
|
43
|
+
- The brand has had to publish official pronunciation guidance
|
|
44
|
+
- Sales reps avoid saying the brand name on calls
|
|
45
|
+
- Press coverage shows multiple spelling/pronunciation variants
|
|
46
|
+
|
|
47
|
+
---
|
|
48
|
+
|
|
49
|
+
## 3. Memorability (15 points)
|
|
50
|
+
|
|
51
|
+
For existing brands, test: do people get it right after hearing it once?
|
|
52
|
+
|
|
53
|
+
**15 pts:** Sticks on first contact. High recall in surveys. Customers tag the brand correctly when recommending on social media.
|
|
54
|
+
|
|
55
|
+
**12 pts:** Recalled correctly after 2-3 exposures. Some confusion with similar names but resolves quickly.
|
|
56
|
+
|
|
57
|
+
**8 pts:** Low recall. Customers remember the product before the name. Requires significant marketing investment to maintain top-of-mind.
|
|
58
|
+
|
|
59
|
+
**4 pts:** Forgettable. Customers describe what the brand does rather than its name. Re-acquisition cost is high because referrals don't stick.
|
|
60
|
+
|
|
61
|
+
**0 pts:** Actively confusing. Regular customer acquisition friction ("Wait, is that [X] or [Y]?").
|
|
62
|
+
|
|
63
|
+
---
|
|
64
|
+
|
|
65
|
+
## 4. Length & Shape (10 points)
|
|
66
|
+
|
|
67
|
+
**10 pts:** 4-8 characters. Works in all digital contexts without truncation. App icon, Slack notification, email subject line — clean everywhere.
|
|
68
|
+
|
|
69
|
+
**8 pts:** 9-12 characters. Minor truncation in some contexts. No major issues.
|
|
70
|
+
|
|
71
|
+
**5 pts:** 12-16 characters. Truncation is a regular problem. Social handles required abbreviation. App store listing shows cut-off name.
|
|
72
|
+
|
|
73
|
+
**2 pts:** 16+ characters, or contains hyphens/numbers/special characters that complicate digital use.
|
|
74
|
+
|
|
75
|
+
**Shape audit for existing brands:**
|
|
76
|
+
- Check: how does the name truncate in a browser tab?
|
|
77
|
+
- Check: does the email signature or sender name get cut off?
|
|
78
|
+
- Check: does the Twitter/X handle accurately represent the full name?
|
|
79
|
+
- Check: how does it appear in app store search results?
|
|
80
|
+
|
|
81
|
+
---
|
|
82
|
+
|
|
83
|
+
## 5. SEO Equity (10 points)
|
|
84
|
+
|
|
85
|
+
For existing brands, this measures whether the name is an SEO asset or liability.
|
|
86
|
+
|
|
87
|
+
**10 pts:** Brand name has high search authority. Searching the name returns owned properties in positions 1-3. Brand SERP is clean and controlled.
|
|
88
|
+
|
|
89
|
+
**7 pts:** Brand name ranks well but some interference from non-owned entities (a city, a generic term, a person with the same name).
|
|
90
|
+
|
|
91
|
+
**4 pts:** Significant SEO interference. First page of results is mixed between brand and unrelated entities. Customers searching the brand name land on competitor pages or irrelevant results.
|
|
92
|
+
|
|
93
|
+
**0 pts:** Brand name is a generic term, a person's name, or a phrase with massive existing search volume. The brand cannot realistically rank for its own name at reasonable cost.
|
|
94
|
+
|
|
95
|
+
**SEO audit signals:**
|
|
96
|
+
- Search `[brand name]` and count how many of the first 10 results are owned by the brand
|
|
97
|
+
- Check if any competitors are bidding on exact brand name in paid search
|
|
98
|
+
- Test `[brand name] reviews` — does owned content appear or competitor aggregators?
|
|
99
|
+
|
|
100
|
+
---
|
|
101
|
+
|
|
102
|
+
## 6. Digital Footprint (10 points)
|
|
103
|
+
|
|
104
|
+
How complete is the brand's ownership of its digital identity?
|
|
105
|
+
|
|
106
|
+
**10 pts:** Owns exact-match .com (or appropriate TLD) + exact-match handle on all primary social platforms (X, LinkedIn, GitHub if relevant, Instagram if relevant). Consistent naming across all platforms.
|
|
107
|
+
|
|
108
|
+
**7 pts:** Owns primary domain + most social handles. 1-2 minor gaps (less important platform, slight variation in handle).
|
|
109
|
+
|
|
110
|
+
**4 pts:** Primary domain is suboptimal (wrong TLD or hyphenated). 2-3 social handle mismatches. Uses approximations like @[brand]hq or @[brand]app.
|
|
111
|
+
|
|
112
|
+
**1 pt:** Domain is on a weak TLD while .com is squatted or owned by an unrelated party. Social handles are fragmented with no consistent identity.
|
|
113
|
+
|
|
114
|
+
**Footprint audit:**
|
|
115
|
+
- Exact domain they're using vs. what's available
|
|
116
|
+
- @brand on X: do they own it or is it squatted/inactive?
|
|
117
|
+
- github.com/brand: relevant for devtools and open source
|
|
118
|
+
- Are there brand impostors? (fake accounts, parked pages, typosquatters?)
|
|
119
|
+
|
|
120
|
+
---
|
|
121
|
+
|
|
122
|
+
## 7. Trademark Safety (10 points)
|
|
123
|
+
|
|
124
|
+
**10 pts:** Brand name is registered in all primary markets. No known challenges. Clear differentiation from any similar marks in adjacent categories.
|
|
125
|
+
|
|
126
|
+
**7 pts:** No active conflicts. Some unregistered use in a different industry, but manageable. Registration is advised but not urgent.
|
|
127
|
+
|
|
128
|
+
**4 pts:** Similar marks exist in adjacent categories. Some historical disputes or C&D letters received. International expansion may be restricted.
|
|
129
|
+
|
|
130
|
+
**0 pts:** Active trademark conflict. Litigation risk is real. Scaling the brand in this name increases legal exposure.
|
|
131
|
+
|
|
132
|
+
**Red flags for existing brands:**
|
|
133
|
+
- Company has received a cease-and-desist in the past
|
|
134
|
+
- The brand operates in a different country than where the conflicting mark is registered (expansion risk)
|
|
135
|
+
- The brand name is a word or phrase that a larger company recently trademarked
|
|
136
|
+
- The brand name closely resembles a big tech company's product name
|
|
137
|
+
|
|
138
|
+
---
|
|
139
|
+
|
|
140
|
+
## 8. Longevity (5 points)
|
|
141
|
+
|
|
142
|
+
Will this name still work as the brand grows, changes, or expands?
|
|
143
|
+
|
|
144
|
+
**5 pts:** Name is category-agnostic. Works for a solo product, a product suite, an acquired company, or an enterprise offering. Will not age poorly. No cultural or technology dependency.
|
|
145
|
+
|
|
146
|
+
**3 pts:** Works well now, minor limitations at scale. Might require sub-branding if product expands significantly. Not embarrassingly tied to a current trend.
|
|
147
|
+
|
|
148
|
+
**1 pt:** Name is tied to a specific feature, technology, or trend that may not be permanent. ("GPT" in a name, "Blockchain" in a name, "Covid" in a name). Or so narrowly descriptive it constrains the product roadmap.
|
|
149
|
+
|
|
150
|
+
**0 pts:** Name is already aging. Built on a trend that peaked. Will require rebrand within 2-3 years regardless of current action.
|
|
151
|
+
|
|
152
|
+
**Longevity audit questions:**
|
|
153
|
+
- If the core technology behind this product changes, does the name still work?
|
|
154
|
+
- If the company doubles its product scope, does the name allow for that?
|
|
155
|
+
- Does the name tie the company to a price point or market segment it may want to leave?
|
|
156
|
+
- Would a Series B investor be comfortable with this name on a pitch deck?
|
|
@@ -0,0 +1,239 @@
|
|
|
1
|
+
# Sample Audits — BrandAudit Reference
|
|
2
|
+
|
|
3
|
+
Three complete reference audits showing full output quality and format.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Example 1: B2B SaaS — "TaskifyPro"
|
|
8
|
+
|
|
9
|
+
**Context:** 3-year-old project management SaaS. Bootstrapped. $180k ARR. Competing against Linear, Asana, Monday. No trademark registered.
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## BrandAudit — TaskifyPro
|
|
14
|
+
|
|
15
|
+
**Industry:** B2B SaaS / Project Management
|
|
16
|
+
**In use since:** 2021
|
|
17
|
+
**Current domain:** taskifypro.io
|
|
18
|
+
**Competitive set:** Linear, Asana, Monday.com, Height, Basecamp
|
|
19
|
+
|
|
20
|
+
---
|
|
21
|
+
|
|
22
|
+
### Score: 38/100
|
|
23
|
+
|
|
24
|
+
| Factor | Score | Notes |
|
|
25
|
+
|--------|-------|-------|
|
|
26
|
+
| Brandability | 6/25 | Descriptor + dated suffix + "Pro" suffix = triple generic |
|
|
27
|
+
| Pronunciation | 13/15 | Pronounceable, no issues |
|
|
28
|
+
| Memorability | 6/15 | Forgettable. Customers likely say "that project management tool" |
|
|
29
|
+
| Length & shape | 6/10 | 10 chars, truncates at "TaskifyP" in browser tab |
|
|
30
|
+
| SEO equity | 3/10 | "Taskify" has 4 other tools, "Pro" adds no differentiation |
|
|
31
|
+
| Digital footprint | 4/10 | On .io. .com owned by parked page. X handle is @taskifyprollc |
|
|
32
|
+
| Trademark safety | 0/10 | Not registered. "Taskify" used by 3 other active products |
|
|
33
|
+
| Longevity | 0/5 | -ify peaked 2014. "Pro" is meaningless. Will age worse each year. |
|
|
34
|
+
|
|
35
|
+
---
|
|
36
|
+
|
|
37
|
+
### Competitive Position
|
|
38
|
+
|
|
39
|
+
Against Linear, Asana, and Monday, this name reads as a generic competitor — exactly what it competes against. Linear owns "clean, modern, fast." Asana owns "organized, enterprise." Monday owns "visual, flexible."
|
|
40
|
+
|
|
41
|
+
TaskifyPro owns: nothing. It's the name of a feature, not a brand.
|
|
42
|
+
|
|
43
|
+
If all five names were shown to a user without context, TaskifyPro would be identified as "some project management tool" while the others would suggest personalities. This is the worst possible outcome of naming.
|
|
44
|
+
|
|
45
|
+
---
|
|
46
|
+
|
|
47
|
+
### Perception Audit
|
|
48
|
+
|
|
49
|
+
**Category signal:** Correct — clearly communicates project management. Also communicates that the brand couldn't find a better way to say it.
|
|
50
|
+
**Audience signal:** SMB or prosumer. The "Pro" suffix reads as defensive ("we're serious, really") rather than premium.
|
|
51
|
+
**Era signal:** 2014-2016. The -ify suffix peaked that year. The "Pro" suffix has been meaningless since about 2017.
|
|
52
|
+
**Trust signal:** Weak. The name reads as a side project or a freelancer's tool, not a company that enterprises trust with their workflow.
|
|
53
|
+
|
|
54
|
+
---
|
|
55
|
+
|
|
56
|
+
### Weaknesses Found
|
|
57
|
+
|
|
58
|
+
#### Critical
|
|
59
|
+
- **Trademark unregistered with 3 active competing uses** — "Taskify" is used by at least 3 other active software products. This brand cannot register the name and has no legal protection. If any of those products files a trademark or sends a C&D, this brand must rename under pressure — the worst possible timing.
|
|
60
|
+
- **Generic descriptor pattern** — "Taskify" describes the action of creating tasks. This is the definition of a non-registerable mark. The brand is building equity on a name it can never fully own.
|
|
61
|
+
|
|
62
|
+
#### Major
|
|
63
|
+
- **Dated -ify suffix** — The naming pattern peaked in 2014 and now reads as 8-10 years old. This creates a negative perception gap — the product may be better than competitors but the name signals older, cheaper.
|
|
64
|
+
- **Domain mismatch** — Operating on taskifypro.io while taskifypro.com is parked. Every customer who intuitively types .com leaves the brand's ecosystem.
|
|
65
|
+
- **Handle fragmentation** — @taskifyprollc on X is the corporate entity name, not the brand name. Search for @taskify or @taskifypro returns unrelated accounts.
|
|
66
|
+
|
|
67
|
+
#### Minor
|
|
68
|
+
- **"Pro" suffix adds no value** — It signals there's a "non-Pro" version (even if there isn't) and reads as a free tier upsell device.
|
|
69
|
+
|
|
70
|
+
---
|
|
71
|
+
|
|
72
|
+
### Verdict: FULL REBRAND
|
|
73
|
+
|
|
74
|
+
This name has two Critical weaknesses — legal exposure and an un-ownable generic — stacked on top of three Major weaknesses. At $180k ARR and 3 years old, the equity is real but manageable to transition. Every additional year spent building on this name increases the cost of the inevitable change.
|
|
75
|
+
|
|
76
|
+
The -ify suffix will not age better. The trademark situation will not improve on its own. The domain gap will not close.
|
|
77
|
+
|
|
78
|
+
**Recommended Actions**
|
|
79
|
+
|
|
80
|
+
1. Stop building equity on this name immediately. Plan a rebrand for Q2 of next year to give time for proper execution.
|
|
81
|
+
2. Do not invest in major marketing, conference presence, or PR under the current name — you'll be rebuilding that investment in the new brand shortly.
|
|
82
|
+
3. Activate DomainForge for a new name targeted at B2B SaaS / developer-adjacent productivity, Unicorn mode, emphasizing: must be ownable, must be non-descriptive, must be registerable as trademark.
|
|
83
|
+
|
|
84
|
+
---
|
|
85
|
+
|
|
86
|
+
*Activating DomainForge — B2B SaaS / Productivity archetype, Unicorn mode. Criteria: no -ify suffix, no descriptor pattern, must be trademark-registerable, must own .com or .io at standard pricing...*
|
|
87
|
+
|
|
88
|
+
---
|
|
89
|
+
|
|
90
|
+
## Example 2: Developer Tool — "SnapConfig"
|
|
91
|
+
|
|
92
|
+
**Context:** 2-year-old developer tool for environment variable management. $40k ARR. Competing with Doppler, Infisical, Vault, dotenv.
|
|
93
|
+
|
|
94
|
+
---
|
|
95
|
+
|
|
96
|
+
## BrandAudit — SnapConfig
|
|
97
|
+
|
|
98
|
+
**Industry:** DevTool / Security / Config Management
|
|
99
|
+
**In use since:** 2022
|
|
100
|
+
**Current domain:** snapconfig.dev
|
|
101
|
+
**Competitive set:** Doppler, Infisical, HashiCorp Vault, Envkey, dotenv
|
|
102
|
+
|
|
103
|
+
---
|
|
104
|
+
|
|
105
|
+
### Score: 61/100
|
|
106
|
+
|
|
107
|
+
| Factor | Score | Notes |
|
|
108
|
+
|--------|-------|-------|
|
|
109
|
+
| Brandability | 13/25 | Descriptive compound. "Config" hurts. "Snap" is interesting but owned elsewhere. |
|
|
110
|
+
| Pronunciation | 15/15 | Perfect. No ambiguity. |
|
|
111
|
+
| Memorability | 11/15 | "Snap" is sticky but "Config" dilutes it |
|
|
112
|
+
| Length & shape | 7/10 | 10 chars, manageable |
|
|
113
|
+
| SEO equity | 5/10 | "Snap" is dominated by Snapchat. "Config" is a generic term. |
|
|
114
|
+
| Digital footprint | 5/10 | .dev domain is appropriate. @snapconfig available on GitHub. X handle is @snapconfigdev |
|
|
115
|
+
| Trademark safety | 3/10 | "Snap" is a registered trademark by Snap Inc. (Snapchat). Adjacent risk if scaled. |
|
|
116
|
+
| Longevity | 2/5 | "Config" will constrain if product scope expands beyond configuration |
|
|
117
|
+
|
|
118
|
+
---
|
|
119
|
+
|
|
120
|
+
### Competitive Position
|
|
121
|
+
|
|
122
|
+
Against Doppler, Infisical, and Vault, SnapConfig is the most pronounceable and most immediately understood name. But it's also the most constrained. Doppler owns a distinctive brand (physics metaphor for shift in environment). Infisical owns the infosec/security angle. Vault owns the secure-storage-at-scale position.
|
|
123
|
+
|
|
124
|
+
SnapConfig owns: "fast configuration." That's useful for early sales but doesn't build a defensible brand position.
|
|
125
|
+
|
|
126
|
+
---
|
|
127
|
+
|
|
128
|
+
### Perception Audit
|
|
129
|
+
|
|
130
|
+
**Category signal:** Correct and clear. Communicates fast + configuration.
|
|
131
|
+
**Audience signal:** Developer-oriented, mid-market. Not enterprise-grade (Vault is the enterprise player), not indie-hacker (dotenv is). Appropriate.
|
|
132
|
+
**Era signal:** Neutral. Neither dated nor cutting-edge. Safe.
|
|
133
|
+
**Trust signal:** Moderate. "Config" reads as a utility, not a platform. Fine for early customers, may limit enterprise sales.
|
|
134
|
+
|
|
135
|
+
---
|
|
136
|
+
|
|
137
|
+
### Weaknesses Found
|
|
138
|
+
|
|
139
|
+
#### Critical
|
|
140
|
+
- **Snap Inc. trademark exposure** — Snap Inc. holds active trademarks on "Snap" in software and communications categories. At $40k ARR this is theoretical risk. At $400k ARR or during a fundraise, this becomes due diligence red flag. C&D risk increases as the brand grows. Snap Inc. actively enforces its marks.
|
|
141
|
+
|
|
142
|
+
#### Major
|
|
143
|
+
- **SEO interference from Snapchat** — "Snap" is dominated by Snapchat in search. Any content marketing using the brand name is fighting Snap Inc.'s SEO domain authority. Paid search bids for "snap" are artificially inflated by Snap Inc. advertising.
|
|
144
|
+
- **Scope prison** — "Config" bounds the brand to configuration management. If the product expands to secrets management, identity, or general developer infrastructure, the name fights the expansion.
|
|
145
|
+
|
|
146
|
+
#### Minor
|
|
147
|
+
- **@snapconfigdev X handle** — The "dev" suffix on the handle is a compromise that signals the primary handle was unavailable or unconsidered.
|
|
148
|
+
|
|
149
|
+
---
|
|
150
|
+
|
|
151
|
+
### Verdict: MODERATE REBRAND
|
|
152
|
+
|
|
153
|
+
One Critical weakness (trademark) plus two Major weaknesses. The name has some equity built in the developer community but at 2 years and $40k ARR, the cost of transition is manageable. The trademark risk will only get worse — Snap Inc. is not a company that leaves adjacent marks uncontested.
|
|
154
|
+
|
|
155
|
+
**Recommended Actions**
|
|
156
|
+
|
|
157
|
+
1. Modify the name to remove "Snap" before the next funding round — any investor doing DD will flag this.
|
|
158
|
+
2. Keep "Config" optional: find a name where "config" can be a product tagline ("Doppler for config") rather than the brand name itself.
|
|
159
|
+
3. Explore: names in the "secure, fast, developer-native" space that aren't descriptive compounds.
|
|
160
|
+
|
|
161
|
+
*Note: Full rebrand not required — this is a targeted fix to remove the trademark risk. The current brand has earned early trust that can transfer.*
|
|
162
|
+
|
|
163
|
+
---
|
|
164
|
+
|
|
165
|
+
## Example 3: Consumer App — "DailyMoodLogger"
|
|
166
|
+
|
|
167
|
+
**Context:** Mental wellness mobile app. 1-year-old. 8,000 MAU. Competing with Daylio, Bearable, Moodnotes, Reflectly.
|
|
168
|
+
|
|
169
|
+
---
|
|
170
|
+
|
|
171
|
+
## BrandAudit — DailyMoodLogger
|
|
172
|
+
|
|
173
|
+
**Industry:** Consumer / Mental Health / Mobile App
|
|
174
|
+
**In use since:** 2023
|
|
175
|
+
**Current domain:** dailymoodlogger.com
|
|
176
|
+
**Competitive set:** Daylio, Bearable, Moodnotes, Reflectly, Finch
|
|
177
|
+
|
|
178
|
+
---
|
|
179
|
+
|
|
180
|
+
### Score: 22/100
|
|
181
|
+
|
|
182
|
+
| Factor | Score | Notes |
|
|
183
|
+
|--------|-------|-------|
|
|
184
|
+
| Brandability | 2/25 | Pure descriptor. Not ownable. Reads like a feature description. |
|
|
185
|
+
| Pronunciation | 12/15 | Pronounceable but 5 syllables reads long in spoken context |
|
|
186
|
+
| Memorability | 3/15 | Un-memorable. Customers will say "that mood tracking app" |
|
|
187
|
+
| Length & shape | 0/10 | 15 characters. Truncates everywhere. No natural abbreviation. |
|
|
188
|
+
| SEO equity | 4/10 | Keyword-rich but unbranded — competes with category searches, not brand searches |
|
|
189
|
+
| Digital footprint | 4/10 | Has .com but handle is @DailyMoodLog on most platforms (truncated) |
|
|
190
|
+
| Trademark safety | 0/10 | Pure descriptor — cannot be trademarked. No protection possible. |
|
|
191
|
+
| Longevity | -3/5 | Applied: 0. Name will constrain any scope expansion beyond daily mood logging. |
|
|
192
|
+
|
|
193
|
+
---
|
|
194
|
+
|
|
195
|
+
### Competitive Position
|
|
196
|
+
|
|
197
|
+
Against Daylio (invented word, 2 syllables, extremely sticky), Bearable (warm, memorable, single word), and Moodnotes (clean compound), DailyMoodLogger sounds like it was named by someone describing the app to a developer, not by someone building a consumer brand.
|
|
198
|
+
|
|
199
|
+
If all five names were tested in a blind survey ("which app would you trust with your mental health data?"), DailyMoodLogger would rank last by a wide margin. The name signals a free spreadsheet template, not a thoughtful wellness product.
|
|
200
|
+
|
|
201
|
+
---
|
|
202
|
+
|
|
203
|
+
### Perception Audit
|
|
204
|
+
|
|
205
|
+
**Category signal:** Correct and exhaustively literal. The name describes the exact feature set. This is not how consumer brands are built.
|
|
206
|
+
**Audience signal:** Wrong. Mental wellness apps need warmth, safety, and approachability. "Logger" is an engineering term. It signals data collection, not emotional support.
|
|
207
|
+
**Era signal:** N/A — this name has no era. It reads as a prototype name that was never replaced.
|
|
208
|
+
**Trust signal:** Very weak. In the mental health space, trust is the core product. A name that sounds like a debug utility undermines the trust signal at first contact.
|
|
209
|
+
|
|
210
|
+
---
|
|
211
|
+
|
|
212
|
+
### Weaknesses Found
|
|
213
|
+
|
|
214
|
+
#### Critical
|
|
215
|
+
- **Pure descriptor — legally un-ownable** — "Daily Mood Logger" describes an action. It cannot be registered as a trademark in any jurisdiction because it describes what the product does rather than identifying the brand. This brand will never have legal protection for its primary identifier.
|
|
216
|
+
- **Consumer trust failure** — "Logger" is an engineering term. In mental health context, it evokes data harvesting. This is the opposite of what the product needs to signal.
|
|
217
|
+
- **15-character length** — Truncates in every mobile context where the app competes (App Store search, home screen, notification sender, shared links).
|
|
218
|
+
|
|
219
|
+
#### Major
|
|
220
|
+
- **No competitive differentiation** — Nothing in this name differentiates from competitors. Any of the 50+ mood tracking apps could use this name.
|
|
221
|
+
- **Word-of-mouth broken** — "Have you tried DailyMoodLogger?" is a sentence that makes the recommender sound like they're describing a spreadsheet. Customers will describe the app, not refer it by name.
|
|
222
|
+
|
|
223
|
+
---
|
|
224
|
+
|
|
225
|
+
### Verdict: FULL REBRAND
|
|
226
|
+
|
|
227
|
+
Score of 22/100. Three Critical weaknesses. This is a name that was never meant to be a brand — it was a working title that wasn't replaced. At 1 year old and 8k MAU, the equity is entirely in the product and community, not the name. This is the best possible time to rebrand.
|
|
228
|
+
|
|
229
|
+
The mental health space requires names that feel safe, warm, and human. The new name should sound like something a therapist might recommend, not something a developer would build for their personal data collection.
|
|
230
|
+
|
|
231
|
+
**Recommended Actions**
|
|
232
|
+
|
|
233
|
+
1. Rebrand before trying to grow. Every dollar spent acquiring users under this name is partially wasted — referral and word-of-mouth conversion will be higher under a proper brand.
|
|
234
|
+
2. Do not launch on Product Hunt or pursue press under the current name.
|
|
235
|
+
3. Activate DomainForge — Consumer AI / Wellness archetype, warm + approachable, 4-7 chars ideal, soft consonants, .app or .com.
|
|
236
|
+
|
|
237
|
+
---
|
|
238
|
+
|
|
239
|
+
*Activating DomainForge — Consumer / Wellness archetype. Criteria: warm phonetics (soft consonants: l, m, n, r, v), 4-7 characters, no clinical/medical language, no engineering terms ("log", "track", "data"), evokes reflection, growth, or emotional safety. Mode: Consumer AI...*
|