Brand book · v1.1 · October 2026

How Better Data Today looks, sounds, and shows up — on every surface.

BDT is a senior tracking practice run by one lead, serving in-house marketing teams directly and agencies through a wholesale Partner Program. This brand book is the source of truth for how the brand expresses itself across the website, proposals, client deliverables, email, and social.

Owner: Jose Almeida hello@betterdatatoday.com betterdatatoday.com
  1. 01Concept & positioning
  2. 02Logo
  3. 03Color
  4. 04Typography
  5. 05Layout & components
  6. 06Voice & language
  7. 07Numbers in copy
  8. 08White-label rule
  9. 09Applications
  10. 10Resources
01 — Concept

A senior tracking practice that makes ad platforms bid on profit, not clicks.

The brand is built around a single wedge: the measurement layer between a business's data and its P&L. BDT exists to rebuild that layer end-to-end — GA4, server-side GTM, Meta CAPI, Google Ads Enhanced Conversions, Consent Mode v2, offline conversion routing — so bidding models optimize for the numbers that matter.

1

Specific over superlative

We lead with the number ("€187k revenue, €41k profit"), not the adjective ("better accuracy"). Concrete beats clever.

2

Senior lead, no handoff

One person owns the account from scope to delivery. No junior layer, no account-manager layer, no offshore stack.

3

Written before built

Scope is written before the work starts. Documentation ships with the work. There is no verbal-only deliverable.

4

Dual audience, two faces

Direct clients see the signal-engineering wedge on the homepage. Agencies see wholesale rates and white-label integration on /agencies. Never blend the two.

03 — Color

Three roles — ink, cream, coral — plus a controlled accent set.

The system is intentionally narrow. Ink and cream do 90% of the layout; coral is reserved for the single most important action or figure on a surface. Capability dots and semantic tones exist for data visualization and status, not decoration.

Core

Ink #0B0B0B Primary text · dark panels · primary buttons
Cream #FAFAF7 Page background · base canvas
Coral — UI #FF4A60 Headline accent · primary CTA · "bad number"
Known drift. The logo files ship with #E35865; the website UI token (--accent) uses #FF4A60. The two reads as the same color at a glance but diverge in strong color-managed contexts (print, dark mode screenshots). Flag for alignment before the next proposal template refresh.

Supporting

Ink 2#1A1A1ABody copy
Muted#5C5C5CSub-copy
Muted 2#8A8A8ACaptions
Line#E8E8E2Borders · dividers
Surface#FFFFFFCards · elevated containers
Accent soft#FFF2F4Highlight boxes · badges
Accent ink#B1102AText on accent-soft · critical state

Semantic & capability

Green#1A7A3A"Good number" · pass
Amber#B57200Warning · at-risk
Capability blue#1C92FFOffline conversions
Capability purple#5C42FBServer-side & consent
Capability yellow#FFC431Ecommerce & app
Capability orange#F07800Docs & ops
Capability lime#81E644Analytics & reporting
Rule of thumb. Coral never fills a background block larger than the final CTA panel. If a surface needs more color than coral provides, use the capability dots on cards — not the base coral — so the single-focus wedge stays intact.
04 — Typography

Two typefaces. One does the work.

Onest is the voice of the brand; JetBrains Mono is the voice of the data. Any screen can be built with these two faces alone. There is no editorial serif, no condensed display, no handwritten accent.

Aa Onest
  • RoleHeadlines, body copy, UI
  • Weights400 · 500 · 600 · 700 · 800
  • SourceGoogle Fonts
  • LicenseSIL Open Font License 1.1
Aa JetBrains Mono
  • RoleEyebrows, data, prices, trust lines
  • Weights400 · 500
  • SourceGoogle Fonts
  • LicenseSIL Open Font License 1.1

Scale

Your ad platforms are bidding on the wrong number.
H1 — Display clamp(40px, 6vw, 68px) · 800 · −0.035em
We rebuild the tracking layer behind your ad platform bids.
H2 — Section clamp(30px, 3.6vw, 44px) · 700 · −0.03em
Server-side & Consent
H3 — Card title 22px · 700 · −0.02em
We rebuild the measurement layer end-to-end — GA4, server-side GTM, Meta CAPI, Google Ads Enhanced Conversions.
Lede 20px · 400 · muted
Every change runs through our QA checklist before it ships. Audits come with a 0–100 tracking quality score and a prioritized fix list.
Body 16px · 400 · 1.6
POAS · Offline Conversions · sGTM · CAPI
Eyebrow Mono · 12px · 0.14em · uppercase · muted
€187,432
Data figure Mono · 22px · 500 · ink or coral
The eyebrow pattern. Every section starts with a one-line mono eyebrow (uppercase, 0.14em letter-spacing), followed by an H2, followed by a lede paragraph. If a section opens any other way, it isn't a BDT section.
05 — Layout & components

Three canvas types do everything.

Cream canvas for most of the site, surface cards for grouped detail, and ink panels for emphasis moments (the problem statement and the final CTA). The same three canvases carry across proposals, presentations, and the website.

Canvases

Cream
Default canvas · ~70% of surfaces
Surface
Cards, matrix, elevated groupings
Ink
Problem statement & final CTA only

Signature component — the bidding comparison card

The hero card is the shape of the BDT argument. Dashed dividers, mono figures, ink labels, and the coral/green split between a "bad number" and a "good number." Reuse this pattern anywhere two figures need to be contrasted — proposals, audit reports, slide decks.

Live ad-spend example

Google Ads is optimizing for
Revenue as conversion value
€187k
Your P&L sees
Actual profit after COGS + returns
€41k
Gap the bidding model can't see
Low-margin SKUs scaled at high spend
78%

Buttons

Primary — ink → Accent — coral → Ghost — outline

One primary per surface. Coral is reserved for CTAs on dark panels, where ink buttons would disappear. Pill shape (border-radius 999px) is non-negotiable.

06 — Voice & language

Direct, specific, no fluff — and never the same tone to both audiences.

BDT serves two audiences and switches register between them. On the homepage, the reader is a Head of Growth, CMO, or CFO at a direct client — the problem is their P&L. On /agencies, the reader is an agency owner — the problem is their margin on tracking work. The voice stays specific in both; the pain shifts.

Core rules

Rewrites

Avoid

"We leverage world-class analytics expertise to help you unlock the full potential of your data."

Use

"We rebuild GA4, sGTM, and Meta CAPI so your bidding models see profit, not revenue."

Avoid

"Our team of senior analytics engineers delivers best-in-class implementation across all major platforms."

Use

"One senior lead owns the account from scope to delivery. No junior handoff."

Avoid

"We'll help improve your tracking accuracy and provide actionable insights."

Use

"Audit returns a written report with a 0–100 quality score, prioritized fixes, and a next step."

Two audiences, two openers

Direct clients

Lead with the P&L.

"Your ad platforms are bidding on the wrong number." The pain is CAC drift, mis-attributed conversions, revenue scaling without margin scaling.

Agencies

Lead with the margin.

"Your senior tracking slot, white-labeled." The pain is junior staff breaking things, freelancers disappearing, and the cost of a €90k senior hire for workloads that don't fill a full seat.

07 — Numbers in copy

If a number can replace an adjective, replace it.

BDT is a numbers-first brand. Figures carry the argument, not adornment. The brand's house voice converts qualifiers into concrete values wherever possible — currency, hours, percentages, scores, counts of events.

Formatting standards

TypeFormatExample
CurrencySymbol first, no space, thousands separator€4,000
Large currencyRound to k/M once past five figures€187k
HoursLowercase "hrs," slash for cadence10 hrs/mo
TurnaroundHours or days, never business-days jargon48-hour average turnaround
Scores0–100 range with en dash0–100 tracking quality score
PercentagesNo decimal unless < 10%78% · 3.4%
DatesDDMMYYYY in file names, "Oct 2026" in copy21102026 · October 2026

The two-figure contrast

When comparing before/after or revenue/profit, pair the figures in a card using the "bad number" (coral) and "good number" (green) colors. The contrast is the point — never dilute it with a neutral middle figure.

08 — White-label rule

The deliverable belongs to the client. The brand belongs on the proposal.

BDT does not appear on client-facing deliverables when the engagement is through an agency partner. The agency's logo and client details go on the audit, the tracking plan, the dashboard. BDT's brand only shows up on surfaces the agency owner reads — proposals, SOW drafts, and internal docs.

BDT-branded
  • Homepage, /audit, /agencies, /case-studies, /blog
  • Proposals TO agencies (BDT_[Agency]_[Client]_[Date].gdoc)
  • Internal SOPs & templates in /1. SOP/
  • Partner Program onboarding docs
  • Email signatures and LinkedIn
White-labeled (agency- or client-branded)
  • Tracking audits, event aggregations, QA reports
  • Tracking plans and tech specs
  • GTM / sGTM container documentation
  • Looker Studio dashboards
  • Any file in a client's 5. Delivered to the Client/ folder
Direct clients: BDT branding is allowed on deliverables when the engagement is direct (not via an agency). When in doubt, the delivery-qa skill scans for branding leaks before anything ships.
09 — Applications

Where the system shows up.

The brand expresses itself in six core surfaces. Any new surface should be judged by whether it already fits one of these patterns before a new one is invented.

01

Website

Cream canvas, Onest headlines, mono eyebrows, dashed-divider cards, two dark panels (problem + final CTA). Nav is sticky with a blurred cream background. Footer is ink.

02

Agency proposals

BDT-branded (the one exception to the white-label rule). Mirrors the homepage structure: eyebrow + headline + scope, then a pricing table using the same three-column shape as the website matrix. File name: BDT_[Agency]_[Client]_[Date].gdoc.

03

Tracking plans & audits

White-label — agency or client branding. Technical content uses GA4 (snake_case) and Meta (PascalCase) naming conventions. Scores use the 0–100 pattern. Produced via tracking-plan and tracking-audit-agent.

04

Looker Studio dashboards

Client's palette, not BDT's. BDT's role: structure, named ranges, and annotations. Default typography if the client has no system of their own.

05

Email

Plain-text first. No HTML signature on cold outreach. No URLs in email bodies (Gmail wraps them in tracking redirects). No em-dashes. Signature: name, role, phone optional.

06

LinkedIn & social

Carousel covers use ink background + coral accent + Onest 700. Post hero figures use the "two-figure contrast" pattern. Jose posts in first person; BDT posts in third.

10 — Resources

Assets, references, and who to ask.

Color tokens

All colors live as CSS variables in /public/css/mockup.css. Reference them with var(--accent), var(--ink), etc.

Contact

Brand questions, logo requests, or press: hello@betterdatatoday.com.

Brand book v1.1 · October 2026 · maintained by Jose Almeida