# Nameshot Voice Guide

## Communication Style

Nameshot speaks with a warm, playful, quietly confident voice. It makes a technical utility feel charming and approachable—more like a helpful desktop companion than software making grand promises.

The tone is casual and conversational, with short sentences, gentle humor, and occasional whimsical phrasing. It is clear about product capabilities and privacy without becoming corporate, overly technical, or alarmist.

### Key stylistic elements

- Lead with a relatable annoyance, then show the satisfying improvement.
  - “Goodbye ‘Screenshot 2026-07-11 at 09.52.23.’ Hello ‘Passive-Aggressive Roommate Note.’”
- Use concise, plain-language sentences.
  - “Your files never leave your Mac.”
  - “Every rename can go back.”
- Personify the app as a small, helpful character: “the little guy,” “its eyes following each one,” “feed the little guy.”
- Balance playful language with concrete reassurance.
  - “With a pinch of local Apple Intelligence.”
  - “No Wi-Fi? No problem.”
- Use reassuring repetition for key objections, especially around privacy, subscriptions, and reversibility.
  - “Nothing to buy, nothing to cancel.”
  - “No account. No models to download. No API keys.”

### Vocabulary preferences

Favor simple, human words: **name, tidy, drop, drag, fix, learn, helper, folder, screenshot, undo, yours for good**.

Use light, evocative terms for clutter: **mess, wasteland of a folder, proper name**.

Avoid enterprise language such as **workflow optimization, AI-powered solution, seamless integration, leverage, robust, revolutionary**, or **best-in-class**.

## Content Patterns

Nameshot content centers on turning an everyday digital annoyance into a small moment of order. Key themes include:

- Screenshot clutter and unreadable default filenames
- Automatic, human-readable naming
- Privacy and offline operation
- One-time pricing over subscriptions
- Easy correction and undo
- Learning personal naming preferences over time
- Low-friction Mac-native behavior

### Structural approach

Use a progression from problem to relief:

1. Show the familiar messy reality.
2. Introduce the simple action.
3. Explain what Nameshot does.
4. Reassure the audience about privacy, control, and reversibility.
5. Invite them to try it.

Feature sections should have brief, benefit-led headings:
- “Built for the mess you already have.”
- “Undo is one click.”
- “Naming things is hard.”

Explain technical details only after the plain-language benefit. Prefer lists of short statements over dense paragraphs.

### Calls to action

CTAs are direct but low-pressure:
- “Join the beta on TestFlight.”
- “Try it free for 7 days.”
- “Read the privacy policy.”
- “Drag one onto the little guy.”

Pair CTAs with reassurance when relevant:
- “Nothing to buy, nothing to cancel.”
- “No subscription, Family Sharing included.”

## Audience Interaction

Address the audience directly using **you** and **your**, with an understanding, peer-like relationship. The brand assumes people are capable but busy; it does not lecture them for having disorganized files.

Use friendly nudges and small asides:
- “Psst. Drag one onto the little guy.”
- “Even that one folder.”
- “Like you always do.”

The tone should feel supportive rather than salesy. When discussing limitations or requirements, state them plainly and calmly.

## Guidelines & Examples

### Do

- Use short, friendly sentences.
- Make product benefits tangible with filename examples.
- Use playful language sparingly to add personality.
- Be specific and transparent about privacy and system requirements.
- Emphasize user control: undo, corrections, settings, and local processing.
- Describe the app as a helper, not a replacement for the user.

**On-brand phrases**
- “Your screenshots, automatically named.”
- “Take a screenshot. The little guy does the rest.”
- “Your files never leave your Mac.”
- “Tidy up entire folders.”
- “One price. Yours for good.”
- “Correct it when it’s wrong and it’ll automatically adapt to your style.”

### Don’t

- Overstate AI capabilities or imply perfect results.
- Use jargon-heavy technical explanations as the first line of copy.
- Sound corporate, aggressive, or overly polished.
- Rely on urgency, scarcity, or pushy sales language.
- Call users “customers,” “users,” or “teams” when “you” works.
- Make privacy claims vague; state exactly what does and does not happen.

### Content formats

Nameshot works especially well in:
- Short product headlines and subheads
- Feature cards with one clear benefit
- Before-and-after filename examples
- Step-by-step “how it works” sections
- Friendly FAQ answers
- Compact privacy and pricing reassurance
- Playful microcopy for buttons, tooltips, and empty states