Brand basics

Give the idea enough shape to make decisions

Brand does not need to become a three-week side quest before you build.

You do not need a full identity system, a 40-slide brand deck, or seventeen logo directions. You need enough direction to write, design, name, test, and publish without spiraling every time you open a builder.

By the end, you should have:

• a working name
• a simple positioning line
• a domain direction
• basic voice direction
• rough color and type choices
• a logo or wordmark direction
• a list of brand decisions you are not making yet

1. Start with the positioning line

Before you choose colors, write one plain-English line about what the product is.

Not the final homepage headline. Not a tagline. Not the sentence that needs to carry your entire brand on its tiny little back.

This is the internal version that keeps you honest.

Use this format:

[Product] helps [customer] do [job/outcome] without [pain/current workaround].

Example:

Looplight helps B2B SaaS support leads spot recurring customer issues without reading every ticket manually.

A good positioning line makes three things obvious:

• who it is for
• what it helps them do
• what pain or workaround it replaces

If it sounds like it could describe 40 other tools, keep tightening.

2. Choose a working name

A working name is enough for now.

It should be easy to say, easy to remember, and not wildly misleading. It does not need to be perfect, emotionally profound, or available across every social handle you will never use.

Good early names usually do one of three things:

• describe the job
• suggest the outcome
• create a clear feeling

For example, a support insights product might use a name that suggests clarity, patterns, signals, loops, or visibility. An ecommerce ops product might use a name that feels fast, organized, steady, or operational.

Avoid names that are:

• too clever to understand
• too close to competitors
• hard to spell
• hard to say out loud
• too narrow for where the product could reasonably go
• too broad to mean anything

You can change the name later. You just need something good enough to build around.

3. Check the domain

You do not need the perfect domain to keep going. You do need a domain direction that will not make the product harder to trust, remember, or share.

Start with the obvious version of the name. If it is taken, try simple modifiers before you spiral into a weird spelling crime.

Useful domain options:

• get[name].com
• use[name].com
• try[name].com
• [name]app.com
• [name].app
• [name].co
• [name].ai

Avoid domains that are:

• hard to spell
• hard to say out loud
• full of hyphens
• too close to another product
• using an extension that makes the product feel less trustworthy
• cute in a way that only makes sense after a five-minute explanation

Also do a quick check for obvious conflicts: similar product names, confusing competitors, and social handles you may actually use.

You are not solving the entire brand system here. You are making sure the name can survive a landing page, a demo, and someone saying it in a Slack thread.

4. Define the voice

Voice is how the product talks when you are not in the room.

You do not need a full brand voice guide yet. You need a few rules that help you make product, onboarding, website, email, and error-message decisions consistently.

A useful voice direction should answer:

• How should the product sound when the user is confused?
• How should it sound when something goes wrong?
• How much personality is appropriate?
• What should it avoid?
• What should someone trust about it?

Voice matters because it shows up everywhere people decide whether they trust you: onboarding, empty states, tooltips, pricing, emails, docs, support, and the product itself.

5. Pick a visual direction

Visual direction is not the same as a full brand system.

At this stage, you need enough to make the first version feel intentional: a rough color palette, type direction, logo or wordmark direction, and a few visual references.

Start with 3–5 words that describe how the product should feel.

Then translate those words into a few basic choices.

Color

Choose a rough palette, not a final brand system.

You only need enough color direction to make the product feel intentional and usable. A support or operations product might need calm neutrals and restrained accents. A creative tool might have more room for expressive color. A finance or security product probably needs to feel stable before it feels fun.

Decide:

• the overall color mood
• one or two accent colors
• where color should help users make decisions
• any category colors you want to avoid

Type

Choose a type direction based on the product's job.

If users need to scan data, forms, tables, or workflows, legibility matters more than personality. For most early apps, boring-but-readable is better than beautiful-but-annoying.

Decide whether the type should feel:

• technical or editorial
• friendly or precise
• premium or practical
• expressive or quiet
• dense and utility-first or more spacious

Logo or wordmark

You do not need a perfect logo yet.

For most early products, a simple wordmark or clean text treatment is enough. An icon can come later unless the product needs to live somewhere an icon matters: browser extension, mobile app, Shopify app, Slack app, Chrome toolbar, or app marketplace.

Decide:

• whether a wordmark is enough for now
• whether the product needs an icon early
• whether the name suggests a simple visual idea
• whether the mark will still work small

References

Collect a few references so the direction is easier to explain.

These can be products, websites, apps, packaging, editorial layouts, dashboards, or brands that feel close to the direction. You are not copying them. You are using them to make taste visible.

If your product is solving a stressful workflow, maybe it should not look like a neon crypto casino. Unless the customer is somehow stressed neon crypto people, in which case good luck and please hydrate.

6. Decide what not to design yet

Brand work can become productive procrastination very quickly.

Before you spend a week perfecting the logo, decide what you are not doing yet.

You probably do not need:

• full brand guidelines
• custom illustrations
• complex motion language
• merch
• 12 logo lockups
• a mascot with lore
• a pitch deck aesthetic system
• a full design system before the product exists

You do need enough direction to make the first version feel coherent.

That usually means:

• working name
• positioning line
• domain direction
• voice rules
• visual words
• rough colors
• type direction
• simple logo or wordmark direction
• a few references

The goal is to create enough brand direction to make decisions, not enough brand direction to avoid building.

Prompt

This prompt is not here to create a fake brand empire. It's here to give your product enough direction to make decisions.

Brand baseline

Take all of my notes and organize them into a simple brand baseline for my app.

Please structure it into:

1. Working name
2. Plain-English positioning line
3. Customer
4. Job or outcome
5. Pain or workaround it replaces
6. Domain options
7. Obvious naming or competitor conflicts
8. Voice direction
9. What the voice should avoid
10. Visual direction
11. Basic color direction
12. Basic type direction
13. Logo or wordmark direction
14. Visual references
15. Brand decisions to avoid for now

Use this format for the positioning line:

[Product] helps [customer] do [job/outcome] without [pain/current workaround].

Then audit the brand baseline.

Please flag:

- where the positioning line is too vague
- where the name is confusing, too clever, or too close to another product
- where the domain options may create trust or memorability issues
- where the voice does not match the customer
- where the visual direction does not match the problem
- where I may be overbranding too early
- what I should decide now vs. later

Be direct. If I'm using brand work to procrastinate on building or validation, tell me.

Before you move on