> For the complete documentation index, see [llms.txt](https://handbook.opencoreventures.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.opencoreventures.com/startup-manual/marketing/brand.md).

# Brand

Branding is a continuous process of shaping how people perceive, experience, and emotionally connect with you, your product, and your company. It is not a name and logo. A name and logo mean nothing if people don't recognize them and associate them positively. &#x20;

At pre-seed, people back the founder before they back the product. For an open core company, they're also backing the open source project. Your brand is a combination of the two. Who you are, your vision for the project you're building on, and how you connect them shape everything you do and say. Positive public perception of you and the project drives the brand forward at this stage.&#x20;

This is an advantage. Most startups build brand from a blank page. You are starting with a project people already care about. This reputation is your foundation, and your job is to carry the trust people have in the project over to you and the company.&#x20;

## Connecting founder and project

How that trust transfers depends on your relationship to the project. People should be able to tell in a sentence how you’re connected to the project and why that makes you the right person to build the company.

### You created or maintain the project.&#x20;

Your work is your track record. Every release, design decision, and reply in an issue thread has already shown people how you think and what you care about. Your brand continues that public record. You’re not introducing yourself; you’re introducing what comes next.

### You’re a long-time contributor or community member.&#x20;

Your credibility comes from what you’ve done in the project. Lead with your contributions, what you’ve learned about how people use the project, and the problems you’ve seen up close.

### You’re new to the project you're starting a company around.&#x20;

You’ll need to earn standing in the community before you speak for it. Credit the maintainers, show up where the community gathers, contribute, and be clear about what the company adds. Borrowed trust transfers slowly, and you have to earn it back if you lose it.

## Minimal Viable Brand (MVB)&#x20;

Don't overinvest in brand mechanics at this stage. You don't want to lock yourself into a concept before you have product-market fit.&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://handbook.opencoreventures.com/startup-manual/marketing/brand.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
