
Design systems that earn their keep
A design system isn't a Figma flex. It's how you ship faster and look like one company instead of five. Here's how I build ones that pay for themselves.
You don't need a 40-page brand book. You need to look like the company you're becoming. Here's the founder's version of branding that actually moves numbers.

A founder I know spent three months and the price of a used car on a "brand identity." What came back was a 40-page PDF. Mood boards. A logo with a paragraph about its negative space. An archetype. Nobody on his team has opened that file since the day it landed.
Meanwhile his product still looked like a template someone bought on a Tuesday. Same three fonts everyone uses. A blue that could belong to four hundred other SaaS companies. That is the gap that makes founders say they hate branding, and they're right to hate that version of it. The good version is smaller, cheaper, and does what the PDF never could. It makes you look like the company you're becoming, before your revenue catches up to the claim.
Marty Neumeier said it cleanest: a brand is a person's gut feeling about your company. Not the logo. Not the font. The feeling someone gets in the half-second before they decide whether you're worth a reply.
You don't shape that feeling with a nicer typeface. You shape it by keeping a promise, over and over, until people stop bracing for you to break it. The logo is the sticker on the jar. What people remember is what was inside the last three times they opened it. So when a founder says they want "branding," I hear something else. They want to be remembered on Thursday for the meeting they had on Monday. That's the real job.
Before anyone touches a color, I want two answers. Who is this for, specifically. And what does it replace in their life.
"For everyone" reaches no one. "For solo accountants drowning in client email" writes half your homepage for you. The sharper the who, the easier every design choice gets, because now the work has a person to please instead of a committee to impress.
The second answer matters as much. Every product replaces something, even if that something is a messy spreadsheet or a nagging feeling. Name what you replace and you've named your competition, your pitch, and the promise your brand has to keep. Pixels come after this. Never before.
Here's the flinch, and here's the fix. Most of what agencies bill for is theatre. A small, ruthless set of assets, applied the same way everywhere, beats a thick book applied nowhere.
| Brand book theatre | The founder's minimum |
|---|---|
| 40-page PDF nobody opens | A one-page reference the whole team uses |
| Twelve logo lockups for platforms you're not on | One wordmark, one small mark, done |
| A palette of nine colors | One color you own, plus black and a near-white |
| Archetypes and a spirit animal | One sentence on who you talk to |
| A big launch reveal | The same look on every screen people touch |
That's the whole kit for an early company. You can build it in a week, not a quarter, and you'll use every part.
Here's my sales brain talking. Branding is how you get remembered and trusted before you ever get bought. A buyer meets you a few times before they act. Your ad. Your site. Your invoice. If those look like three different companies, their gut files you under "risky" without using the word. When the color and the voice and the promise line up, the buyer relaxes. A relaxed buyer converts. A guarded one bounces.
Same idea I wrote about in build for the buyer, not just the user. Consistency reads as competence. Nobody decides it consciously. Everybody feels it, and feeling is what closes.
Don't polish a brand for a product nobody wants yet. If you're still hunting for the thing people will pay for, keep it plain and pour every hour into the product. A clean, boring look beats a beautiful one wrapped around a guess.
Spend the week on brand when people are paying you, when you're about to raise or hire or launch to strangers, and when the gap between how good your product is and how cheap it looks starts costing you deals. That gap is the signal. That's when looking like the company you're becoming starts paying rent.
Almost never, early on. A rebrand is for companies whose reputation has outgrown their old look. If you're pre-launch or pre-traction, you don't have a brand to redo yet. You have a first one to get right, cheaply, and that's a much smaller job.
The founder's minimum and nothing past it. One name, one wordmark, one color, one voice, applied the same way everywhere. Skip the archetypes and the sixty-page guidelines until you have a team big enough to need rules written down.
Product first, every time. A clean wordmark in a good typeface will carry you a long way on day one. What can't wait is a product worth remembering. Build the thing people talk about, then dress it to match what they're already saying.
Yes, through trust. People buy from companies that feel safe, and consistency is what makes you feel safe before anyone's read a word about you. When your ad, your site, and your checkout agree on who you are, hesitation drops. Lower hesitation is higher conversion.
Branding for founders isn't a mood board or a spirit animal. It's a sharp answer to who this is for, plus a tiny set of assets you apply everywhere. Get those right and you stop looking like a template and start looking like the company you're building toward. That's not vanity, it's how strangers decide to trust you with money. Pick the promise you want people to remember, then keep it on every screen they see.
If that's the kind of brand you want, here's how I approach brand identity. And if you've got something worth looking the part, tell me what you're building.
Prabir Singh
Full-stack engineer from Mumbai. Twenty years in sales, now I build products that sell. More about me or start a project.

A design system isn't a Figma flex. It's how you ship faster and look like one company instead of five. Here's how I build ones that pay for themselves.

One language from the phone to the database. Here's why every project I take on is TypeScript end to end, and why I stopped apologising for it.

Express shaped a generation of Node APIs. Here's why my new backends start with Hono instead, and the three places it actually changes how I build.