← All documents

Brand kit · Working draft

Software, not a realtor flyer.

Every named competitor in §01 of the business plan — Real Geeks, Placester, BoomTown, Lofty — reaches for the same corporate blue and a house icon. KeyRingOS looks like the tool it is: a templated engine a two-person company runs, not a marketing agency's brochure. This document is the visual and verbal identity, working draft.

closingboss.io
01 — Color

Warm ink, warm paper, one committed accent.

Near-black rather than pure black, warm off-white rather than stark white — softer than a spec document, closer to how Notion or Linear read than how a realtor's site does. Pine is the one accent, used sparingly: primary buttons, links, the wordmark. Not the internal working-doc blue these spec pages use (that's a documentation convention, kept deliberately separate from the product's own identity) — a color no competitor in this category has claimed.

Ink#171d1a
Paper#faf8f3
Pine#1c4a34
Pine, soft#eaf1ec
Considered and rejected — clay/terracotta. Warmer and more of-the-moment in SaaS brand work generally, but it reads closer to boutique-lifestyle than the confident, unglamorous tool this is meant to be. Pine keeps some real-estate resonance (money, land, growth) without tipping into any competitor's actual palette — Real Geeks and Placester are blue, BoomTown is navy, Lofty is blue-purple, Redfin is red. None are anywhere near green.
02 — Type

System-first. No webfont dependency to manage.

One sans for everything a person reads, one mono for labels and anything numeric — the same split these spec documents already use, carried into the product. System font stacks, not a hosted webfont: one less dependency, one less render-blocking request, and modern system fonts (San Francisco, Segoe, Inter where installed) already read as "software" rather than "print."

KeyRingOS
sans / 800 / headlines
One system, live listings to close.
sans / 600 / subheads
The dashboard, the CRM, the site, the card — one login, one bill.
sans / 400 / body
One plan · $149/mo
mono / labels, prices, meta
03 — Wordmark

Mixed case, tight, a mark that's actually a card.

Set as "KeyRingOS," not lowercased to "keyringos" — the opposite call from most SaaS marks (stripe, notion, linear all go lowercase even when the brand name is capitalized in running text), because this name is a compound of three real words, one of them an actual acronym. Lowercased, "keyringos" reads as an unfamiliar blob of letters; the internal capitals are what let it parse as "Key" + "Ring" + "OS" at a glance instead of one long word — and capitalizing OS specifically borrows the same signal iOS and macOS already trade on: a real operating system, not just an app. The mark isn't a house or a pin, the two most overused real-estate icons — it's a simple key. Not a metaphor stretch: a key is literally what changes hands at a real estate closing, and it echoes the KeyRingOS name directly without duplicating the product's own wordmark. Same mark anchors both lockups — KeyRingOS below, and "ClosingBoss" in the marketing site's own header.

KeyRingOS
Directional concept — not a finished asset
04 — Voice

The tone these spec documents already have.

Plainspoken, specific, allergic to real-estate-marketing cliché — no "dream home," no "your journey starts here," no stock-photo language. Numbers are real or labeled as estimates, never implied precision. This isn't a new voice to invent; it's what plan.html, spec.html and ia.html already sound like, made explicit so it holds on the marketing site too.

Not this

Vague superlatives standing in for a real claim. "The most powerful platform for modern agents."

Borrowed real-estate sentiment. "Your dream home is one click away."

Unlabeled precision on a number that isn't one. "Get your home's exact value instantly."

This

A specific, checkable claim. "Live listings and a real CRM, one plan, $149/mo."

What the thing actually does. "One card. Tap it, they've got your listings and your number."

Honest about what's automated and what isn't. "A real number, from the agent — not a computer's guess."

05 — Buttons

One filled, one outlined, one bare. That's the whole system.

Three treatments cover every case in the IA (business plan §10, information architecture throughout): a filled pine button for the one primary action on a screen, an outlined button for everything secondary, and a bare text-style button for low-emphasis actions inside a table row or card. No color beyond pine and ink — no red/green semantic button colors; a destructive action (removing an agent from a brokerage, say) gets confirmed in a dialog, not signaled by a red button.

primary — filled pine
secondary — outline
ghost — bare text
disabled
One primary button per screen. If two actions feel equally important, one of them is secondary — that's a real decision to make while building each screen, not a rule to skip because both options seem important in the moment.