# Brand systems that survive ten startups

> Tokens, marks, and motion language that scale across a portfolio without looking cloned.

- Author: Kevin Dalvi
- Published: 2026-08-28
- Read time: 8 minutes
- Tags: design, brand, systems
- Canonical: https://www.kevindalvi.com/blog/brand-systems-at-speed

After enough startups, you notice the expensive pattern: every new company reinvents color, type, and logo rules from scratch. Three weeks later you’re arguing about button radius while the product still can’t send an email. I’ve done that. I’m done doing that.

What I want now is a brand system that travels. Shared foundations with enough room for each product to feel owned. Not a franchise look. A toolkit with opinions.

## Tokens first, logos later

I start with a tiny token set: ink, paper, one accent, one warning, type scale, spacing steps. The mark comes after the product has a job. Early logos are usually anxiety with a wordmark. Tokens let engineering ship UI that doesn’t look like a wireframe forever.

Across my portfolio sites, each brand gets its own accent pair, but they share rhythm. Same type families, same density rules, same motion easing. You can tell they’re cousins without mistaking one product for another. That’s the bar.

I also keep a ‘never’ list per brand: no stock gradient heroes, no floating promo chips, no display type that outshouts the product name. Shared prohibitions travel farther than shared logos. They keep AI generated drafts from drifting into the same five defaults every tool loves.

> If every startup needs a full rebrand to launch, your system isn’t a system. It’s a costume department.

## What actually transfers

- Type pairing and size ladder. Locked once, reused often
- Spacing and radius rules that survive dark and light modes
- A motion dialect: duration, easing, what never animates
- Accent colors that change; contrast rules that don’t

I keep a one page brand brief per company: who it’s for, what it should never feel like, three words it should earn. That’s enough. Mood boards are optional. Constraint documents are not.

## Speed without looking cloned

The fear is sameness. The fix isn’t more uniqueness rituals. It’s sharper product voice inside shared rails. Copy tone, illustration style, and domain metaphor do more differentiation than a custom icon set no one remembers.

Practically, I version brand tokens in the same repo as the product. When marketing asks for a one off landing page, they inherit the rails automatically. Drift becomes a PR conversation instead of a silent fork in Figma that nobody reconciles.

When AI can generate a ‘brand kit’ in minutes, taste shows up in what you refuse. I refuse gradient soup, floating badges on heroes, and type that shouts over the product name. The system is there so I can say no faster. And so the next startup doesn’t start at zero.