Start a conversation

Brand

Cadence Lab brand system.

A working guide for how Cadence Lab should look, sound, and behave across the website, tools, writing, client materials, and public-facing systems.

This page is intentionally separate from the main site. The marketing site explains the work. The brand page defines the system behind the work.

Foundation

The brand should feel refined, trusted, and operational.

01

Clear before clever.

Cadence should sound sharp, but never evasive. The work is serious enough that the language does not need to perform.

02

Trust without blandness.

The visual system should feel calm and enterprise-ready, but not generic, sterile, or template-driven.

03

Systems over decoration.

Every design decision should support rhythm, hierarchy, readability, navigation, or decision-making.

Guide sections

What this page will define.

Voice and tone Logo and wordmark Color system Typography Layout and spacing Interface components Content patterns Usage rules

Voice

Plainspoken, precise, and commercially grounded.

Cadence should sound like a senior operator explaining the real issue: direct, useful, restrained, and clear about tradeoffs. The tone can be memorable, but it should not sound theatrical.

Use

Direct language

Say what is happening, why it matters, and what changes next.

Avoid

Consulting fog

Avoid vague transformation language, false urgency, and AI hype.

Color

Dark, light, and signal color behavior.

Black var(--color-black)
Warm light #F3F1E8
Signal green #48D83F

Typography

Type should create trust before style.

Primary sans

National 2 + Tiempos

Cadence uses National 2 for structure and Tiempos for editorial emphasis. The point is contrast and rhythm: National 2 keeps the system clear, while Tiempos gives major headings an editorial voice.

UI / body: National 2

Display headings: Tiempos Headline

Long-form text: Tiempos Text for essays and editorial pages when a warmer reading texture is needed.

Layout

Rhythm, hierarchy, and section behavior.

Define section spacing, grid behavior, card density, responsive rules, dark/light alternation, and footer/header rhythm here.

UI

Components should feel quiet, useful, and system-ready.

Buttons

Clear next action.

Buttons should be direct, high-contrast, and limited to meaningful choices.

Cards

Structured evidence.

Cards should organize ideas, not decorate the page.

Content

Every page should make the work easier to understand.

Add headline patterns, service copy rules, blog structure, disclosure language, case study structure, and AI tool microcopy here.

Usage

Rules for keeping Cadence coherent.

Add usage rules, do/don’t examples, social avatar guidance, document templates, and implementation notes here.