Overview & Brand Idea
Idea to production, in one place.
BAFOS (Builders And Founders Operating System) is a workspace where a founder or builder starts, tracks and manages a project from first idea to live product. It connects the tools they already use, reads their activity, and shows the state of every project on one dashboard. It does not ask anyone to move their work.
This is the brand book. Read it top to bottom once; after that, use the tokens and components. Further sections cover the logo, voice and messaging, and product UI patterns.
The brand idea: the core dot
Every project is spread across many tools. BAFOS is the point where they meet. The brand shows that as one shape: a ring with a single dot at its centre, the O in BAFOS. The ring is the workspace, the dot is the project at its core, and the colour of the dot is the only warm thing on the page.
Three rules follow from the idea.
- One accent. Ignition orange is used once per view, for the thing that matters most. If everything is orange, nothing is.
- Centre, not decoration. Shapes are built from circles and straight lines. No gradients, no illustration of people or rockets, no abstract blobs.
- Quiet around the signal. Ink, paper and a calm neutral scale carry the product. Colour is reserved for meaning: the accent, links, and project health.
Naming
- Name: BAFOS, always in capitals when written as text, as in the wordmark. Say it "BAY-fos".
- Long form: Builders And Founders Operating System. Use once, on first mention. After that, BAFOS.
- Module names: Connect, Projects, Pulse, Flow, Workspace. Capitalised, never "the Pulse feature". Say "Pulse shows...", not "the Pulse module shows...".
- Never: Bafos, BaFOS, "BAFOS OS" (the S already means system), or "the BAFOS".
Alternative names considered, none checked for trademark or domain availability: Throughline, Keel, Foundry, Cadence, Tether, Mainline, Anvil, Launchline.
Personality
BAFOS talks and looks like a capable colleague who has shipped before: focused, plain-spoken, dependable. Five traits, each with its limit.
| Trait | Means | But not |
|---|---|---|
| Focused | One clear next step, few signals, no clutter | Sparse to the point of hiding things |
| Direct | Says what is true, including bad news, in plain words | Blunt or cold |
| Dependable | Predictable, explains how every number is made | Corporate or slow |
| Builder-grade | Precise, technical where it helps, respects expertise | Jargon for its own sake |
| Calm | Steady under deadline pressure; no alarm unless it is one | Sleepy or flat |
Content fundamentals
Voice. Second person, present tense, active verbs. Short sentences. Name the thing, then say what happens. Use "you" and "your project", never "users".
Case. Sentence case for everything except the product name, module names, and proper nouns. Buttons are sentence case: "Start project", not "Start Project".
Numbers. Use digits and units: "5 min", "14 days", "3 blockers". Round only when the exact figure is noise. Say how a number is made when it drives a decision.
Punctuation. No exclamation marks. No emoji in product UI. No em dashes; use a period or a colon.
Real examples
| Moment | Write | Not |
|---|---|---|
| Empty dashboard | "Connect a tool to see your first project." | "Oops! Nothing here yet. Let's get started!" |
| Project at risk | "At risk: 3 blockers and the last deploy failed." | "Heads up! Your project needs some love." |
| Sync problem | "GitHub needs to reconnect. Last synced 2 days ago." | "Something went wrong." |
| Before a write | "This will move 'Checkout bug' to Done in Linear. You can undo it." | "Are you sure?" |
| Success | "Release 1.4 is live. Tracking starts now." | "Awesome, you did it!" |
| Delete | "Delete this connection and the data synced from it. This takes up to 24 hours." | "Remove integration?" |
See Voice and messaging for the full guide, taglines and boilerplate.