Startup branding: what you need before website and marketing

Name the audience, their situation, the alternative they use today, the promised value and the evidence you have. Avoid claiming to serve everyone with the best quality. A positioning statement should help decide which projects, features and messages belong.

For an illustrative specialist service, the audience might be a German startup launching multilingual customer pages; the problem is inconsistent language and implementation quality; the value is a coherent release; the evidence is a documented process and technical expertise. This is a planning example, not a claim about a client.

Question	Useful output
Who is the priority customer?	A defined role and situation
What problem matters?	A concrete cost, friction or unmet goal
What is the alternative?	The existing behavior or competing approach
What value do we promise?	An outcome within our delivery scope
What evidence supports it?	A demonstrable capability, method or real result

Write a plain explanation of the offer, three reasons to consider it and answers to common objections. Define the vocabulary you use and the claims you cannot yet prove. The homepage, service page and advertisement should tell compatible versions of the same story.

Use customer language without copying jargon from competitors. For a new product, explain the task before introducing an unfamiliar category name. For a professional service, explain the process and boundaries instead of making vague claims of excellence.

A logo should remain recognizable in a navigation bar, a small avatar and a document. Define a primary mark, a small-size treatment where necessary and safe placement. Deliver usable vector files and appropriate raster exports with documented rights.

Check typography with real headings, paragraphs and numerals. For German, test long compounds and umlauts. For Arabic, test joining behavior, weight, line height and mixed-script names. Do not select a typeface only from a short English specimen.

Define background, text, accent, border and interactive roles. Test readable text and visible focus on the combinations actually used. A vivid accent can be useful in a small amount but unsuitable for small text on a pale surface.

Use color alongside wording or shape for error and success states. Record approved combinations rather than handing over an unstructured palette. Dark and light applications need deliberate rules if both will be used.

Position

Audience, problem, value and evidence.

Assets

Logo variants and rights-aware exports.

Type

Readable Latin and Arabic rules where needed.

Color

Functional roles and tested combinations.

Message

Offer explanation, reasons and boundaries.

Examples

Website, ad and social applications.

Apply the system to a real homepage headline, a service paragraph, a phone screen, a small advertisement and a social avatar. Check whether the offer is understood quickly and whether the identity still reads at its smallest size.

Do not approve only a beautiful presentation board. Ask whether the system can be produced by the team with the tools and content it owns. Reusable templates should support real messages rather than force every campaign into the same decorative composition.

Specify source files, exports, font and image licenses, account ownership and editing responsibilities. A visual identity does not establish trademark availability. Review names and registration questions through the relevant official process or qualified advice.

Keep a simple asset register so a future developer knows which font may be embedded, which image may be reused and which mark is approved. This prevents a low-cost design from becoming a licensing or production problem later.

A first release can use a concise positioning document, logo, two typography roles, a functional palette, core messaging and a few application templates. The exact scope depends on channels and languages; it does not require a large brand book by default.

After launch, collect questions and usage failures. Change the message when the business learns something material, and update visual rules when a real application exposes a weakness. Consistency is useful; freezing an untested assumption is not.

1. 01 Position Agree audience, problem and credible value.
2. 02 Build Create a small functioning identity.
3. 03 Apply Test website and acquisition materials.
4. 04 Handover Deliver assets, rights and usage rules.
5. 05 Learn Revise using real business feedback.

For implementation: Explore the relevant service.