The brand you did not build will cost more than you think

BrandStrategyAug 14, 2026

There is a metric most founders only learn about when they are sitting across from an investor.

A founder without a structured brand gives up, on average, between 30% and 40% of equity in an angel or pre-seed round. A founder with clear positioning, a cohesive identity, and a well-constructed market narrative gives up between 10% and 15% for the same check.

Midpoint of the 30-40% and 10-15% ranges described above.

The difference is not the product. It is the perception of risk.

When an investor cannot quickly read what a company is, where it is going, and why it will get there, they price that risk. They do it by reducing the valuation, demanding more equity, or simply not moving forward with the conversation.

"The technically brilliant founder frequently perishes on the invisible shelf of app stores and digital distribution platforms through sheer ineptitude in market narrative."

This is not a pitch problem. It is a structural one.


What an investor reads before reading the deck

Before opening any spreadsheet or listening to any presentation, whoever is about to put money into a company is already reading signals.

The company website. The founder's profile. The product name. The way the problem is described in the first sentence of the introduction email. The consistency between what the brand says it is and what the company actually delivers.

These signals are not superficial. They are proxies for maturity. An experienced investor knows that a company that cannot communicate clearly externally probably cannot align internally either. And internal alignment is what converts capital into execution.

The 30% to 40% dilution figure exists because lack of brand structure is perceived as organizational risk. And risk prices equity.


What brand structure actually solves

When I run a brand strategy project, the first deliverable is not the logo. Not the brandbook. Not the color palette.

It is the answer to a question most founders have never explicitly formulated: why will this business, this brand, this product still exist ten years from now? And why will it be this team, with this approach, that makes it happen?

That answer organizes everything that comes after.

In every project I have run through F&A Works, the process begins with immersion. Two to four sessions with the founding team. At least eight hours of conversation before touching any framework or visual direction.

The goal is not to collect ready answers. It is to generate the largest possible volume of real input about the business. How the team sees the current moment. What they want to leave behind. Where the tensions between short and long-term vision live. And where the gaps between what they say and what they actually do are hiding.

That last part is always the most revealing.

In the DietIt project, the founders described the product as a management software for nutritionists. But as the conversation deepened, what emerged was a thesis about chronic care, about the transformation of nutrition from an occasional aesthetic service into a continuous health front. That distinction, which started as a detail in immersion, became the core of the positioning: "Less software, more partnership. The tool that evolves with your practice."

No competitor was saying that. Everyone was talking about features. DietIt started talking about relationship.


The three problems structured brand solves before fundraising

01. The valuation problem.

A founder who arrives at a round with a fragmented brand, inconsistent tone of voice, and generic positioning gives the investor every argument to compress the valuation. A structured brand removes those arguments one by one.

Clear positioning reduces perceived risk. Consistent tone of voice demonstrates communication maturity. Coherent brand architecture signals that the founder is thinking long-term, not just about launch.

02. The fundraising narrative problem.

The pitch deck is not a standalone product. It is the synthesis of a narrative that needs to exist before the deck. When that narrative is not built, the deck reflects the confusion inside the team, not the clarity the investor needs to see.

In the Yellow Panda project, a Brazilian game studio, the first strategic decision was to separate two concepts the team was mixing: audience and workforce. The brand was not built to attract service buyers. It was built to attract people who identify with the studio's purpose. That distinction changed the tone of communication, the channels used, and the priority order of messages, which directly impacted how the studio presents itself to publishers and investors.

03. The long-term cap table problem.

A well-structured angel round gives up between 10% and 15% of equity. A Seed round gives up another 15% to 20%. To arrive viable at a Series A, original founders need to hold at least 50% to 60% of control.

A founder who opens the first round giving up 30% to 40% because of poor positioning makes the cap table unviable before reaching the halfway point. It is not a matter of luck in negotiation. It is a matter of prior structure.

Illustrative waterfall using the midpoints and targets described above, not a measured outcome.

"Investing R$ 40k in a positioning project represents roughly 3% to 4% of the average check the founder is about to seek. It is a microscopic expenditure designed to preserve millions in undiluted equity."
  • Positioning investment3.5%
  • Rest of the check preserved96.5%

How the process connects strategy to implementation

Strategy that does not reach implementation does not exist as strategy. It exists as a document.

That distinction guides every delivery. In several projects, the diagnosis identifies a perception problem the team has never verbalized: the company already operates with more maturity than it communicates, or the opposite, projecting more scale than it has actually built. That gap creates concrete business consequences: partners and investors cannot assess the real size of the operation, and the audience cannot identify the existence of a larger structure behind what they see.

The solution is rarely a campaign. It is usually a brand architecture reorganization: separating the different fronts of the operation under a single coherent structure, and being explicit about which relationships are subordinate and which are partnerships. That structure changes how the company speaks to each audience without fragmenting the central identity.

Implementing this kind of decision is not automatic. That is why the work does not end with the strategic deliverable. The two months of implementation consulting I offer after each project exist precisely to ensure the structure that was built reaches the market faithfully, not just on paper.

"Strategy that does not reach implementation does not exist as strategy. It exists as a document."

What stays out is also a decision

A detail that separates strategy from checklist: most of the value of a good positioning lives in what it excludes.

In the DietIt project, the personality definition was accompanied by an explicit list of what the brand deliberately is not: not aggressive with competitors, does not use technical jargon with the professional, does not sell by feature lists, and does not practice non-transparent pricing. These limits are not negatives. They are what makes the positioning defensible.

When a founder can say with conviction what the company will not do, and why, that is the signal that the strategy worked. Because a brand without limits does not have positioning. It has intention.


The question that closes every project

At the end of every project, I ask one question: can the founding team use this tomorrow as a decision filter, without me in the room?

If the answer is yes, the strategy worked. If the answer is no, I produced a good document. And a document is not a strategy.

That question is the standard I hold every project to, from initial positioning through to market implementation. Not the quality of the document. The quality of the decisions it enables after it is delivered.

Next upBefore you create, you have to extract