Because a founder going to market cannot wait 6 months for a brand book. The process is structured around weekly, shippable milestones, with real work delivered at the end of every sprint.

Do I need developers to use this?

No. If your team can use Figma and Google Slides, they can use it. The brand.md file acts as a readable single source of truth for both technical and non-technical team members.

What happens after week 6?

You own the repo, the Figma files, and the MCP. The brand can continue to evolve through pull requests, with optional ongoing support available and no lock-in.

Is this right for my stage?

It is built for pre-seed to Series B founders shipping a product and raising capital. Earlier-stage teams may be better served by a lighter discovery sprint, while later-stage companies can request a custom scope.

The Branx · Brand OS

A full brand
operating system.

Q: What is brand.md, really?

It is a single markdown file in your GitHub repo that describes your brand in a way humans and AI agents can both read, helping generate on-brand assets without a new briefing each time.

Shipped in 6 weeks.

The complete brand operating system for startups. A single source of truth that your team, your tools and your AI agents can all build from, so every asset ships on-brand, forever.

6 weeks

end-to-end

1 repo

to rule them all

∞ assets

On-brand assets

brand.md · acme-labs/brand · main

# brand.md · Acme Labs · v1.0.0

## Maintained by The Branx

## Identity

name: Acme Labs

tagline: "Move fast, build trust."

stage: Series A

## Palette

ink: ■ #050608 /* primary dark */

paper: ■ #f4f3f3 /* off-white bg */

signal: ■ #4466ee /* accent blue */

## Typography

heading: Cabinet Grotesk 200–300

body: Cabinet Grotesk 400

mono: SF Mono

## Voice

tone: direct, warm, zero fluff

avoid: jargon, passive voice

read-like: Stripe + Linear

## Assets

logo: /assets/logo/

social: /social/linkedin/

slides: /decks/pitch-v1.slides

mcp: npx @acme-labs/brand-mcp

Most brand projects end in a PDF
no one opens again.

You'll still get a beautiful brand guide. But we also deliver a brand.md, so every asset your team and AI agents generate stays on brand, automatically.

Context-Ready

Built for the tools you already use.

Claude, Cursor, ChatGPT and Gemini can all read it. No plugins, no onboarding. Point any agent at your repo and it knows your brand.

Always Evolving

A brand that grows with you.

Every update is reviewed, tracked, and easy to roll back. Your brand evolves with your product, without losing consistency along the way.

Single Source

One truth across every team.

Design, engineering and marketing all read from the same file. No scattered Notion pages, no Slack threads, no brand drift between teams.

Live example · Featherless.ai

Left: what users see.
Right: what AI agents read.

Both come from a single brand.md file in your repo. The visual identity and the machine-readable spec are the same source, just two different representations of it.

FOR THE OPEN AI ERA

Scaled performance with zero weight.

Colour palette

Solar Feather

Carbon Shade

Carbon Mist

Amber Forge

Raven Berry

Pine Kernel

Typography

Run the right model.
Instantly.

Barlow · headings & body copy

GEIST MONO · labels · buttons · code

Get instant access → 19,800+ models

brand.md · featherless-ai/brand · main

# Featherless · Brand OS

> FOR THE OPEN AI ERA · Scaled performance with zero weight.

## Identity

name: Featherless

tagline: "FOR THE OPEN AI ERA"

promise: 19,800+ models · 1,000× cheaper · no lock-in

built-by:researchers behind RWKV

## Archetypes

sage: 70% · precise, rigorous, Switzerland of AI

outlaw: 30% · rejects centralised control through architecture

## Palette

solar-feather: ■ #fef47a /* hero bg, CTAs */

carbon-shade: ■ #141413 /* text, dark UI */

carbon-mist: ■ #f1f1f1 /* backgrounds */

amber-forge: ■ #ffc86d

raven-berry: ■ #f8bdf3

pine-kernel: ■ #e1e783

## Typography

heading: Barlow 400 /* H1 56px / H2 48px */

body: Barlow 400 /* 18px / 160% */

mono: Geist Mono 600 /* labels, buttons */

## Voice

tone: precise, technical, quietly confident

avoid: "revolutionary", "game-changing", superlatives

lead: numbers over claims. "1,000× cheaper" not "affordable"

## Assets

logo: /assets/logo/

social: /social/linkedin/

slides: /decks/pitch-v1.slides

figma: /brandbook/featherless.figma

mcp: npx @featherless/brand-mcp

## LLM Seed

archetypes: Sage + Outlaw

promise: open AI era, zero lock-in

numbers: 19800+ models, 1000× cheaper

## Brand OS by The Branx × Featherless.ai

The package

Everything a founder needs to go to market.

01

Brand identity

Logo system, wordmark, palette, typography, voice guidelines and usage rules. Every token extracted into brand.md.

Primary + responsive marks
Color + type tokens (CSS vars)
Voice & tone matrix
Digital brand book (web)
Figma brand book, copy basics in one click

02

Brand applications

Your identity applied to the touchpoints that matter most: home, product, sales and marketing. Shipped in Figma and wired to your identity tokens, ready for any dev or founder.

Marketing homepage (desktop + mobile)
3 core product screens
5 LinkedIn posting templates
12-slide Google Slides pitch deck

03

brand.md

The keystone. A living document in your GitHub repo. Every token, voice rule and asset path in one file that humans read and AI agents use to generate on-brand assets.

Versioned on GitHub
Claude / Cursor / ChatGPT ready
PR-reviewable brand changes
Single source of truth for every team

Six weeks. One scalable brand.

Weekly, shippable milestones. No endless revision rounds. Every week ends with something real you can ship.

Week 01

Discovery & positioning

Week 02

Brand identity development

Week 03

Identity final

Week 04

Homepage mockup

Week 05

Product screens

Week 06

GTM kit & handover

What it looks like in practice.

Point any AI agent at your repo. Watch it ship on-brand, every time.

Terminal · claude @ acme-labs

$ claude "draft a LinkedIn post announcing our Series A,
using brand.md voice + layout template 03"

→ reading brand.md @ main

→ using voice: direct, warm, zero fluff

→ using /social/linkedin/template-03.fig

✓ on-brand palette, type, voice all match

FAQ

The questions founders
actually ask.

No sales talk. Straight answers.

Because a founder going to market cannot wait 6 months for a brand book. Our process is structured around weekly, shippable milestones. You see real work at the end of every sprint, not a big reveal after months of silence.

A single markdown file in your GitHub repo that describes your brand in a way humans and AI agents can both read. Agents use it to generate on-brand assets (decks, social posts, UI copy) without needing a briefing every time.

No. If your team can use Figma and Google Slides, they're already good. Your brand.md becomes the single source of truth, readable by anyone on the team, technical or not.

You own everything: the repo, the Figma files, the MCP. The brand grows with your product through pull requests. Our team is available for retainer work if you want ongoing support, but there's no lock-in, ever.

Built for pre-seed to Series B founders shipping a product and raising capital. If you're pre-product and still exploring, a lighter discovery sprint might be a better starting point. If you're post-Series B with an in-house design team, reach out. We can scope something different.

A full brandoperating system.

Most brand projects end in a PDFno one opens again.

Left: what users see.Right: what AI agents read.