Media kit

Brand & style guide

The system behind every SaaStock touchpoint — from stage screens to badges to the site you are reading right now.

A two-tier system

SaaStock uses two type systems. Tier 1 — Brand is the everyday system for emails, decks, badges, social, product UI, and any page that gets templated. Tier 2 — Editorial is reserved for a small number of high-impact pages where emotional response matters more than systematic consistency. A page is either fully Tier 1 or fully Tier 2 — never both.

Tier 1 — Brand

Rubik + Space Grotesk

The default system. Use everywhere unless the page explicitly qualifies for Tier 2. Warm, modern, templated.

Tier 2 — Editorial

Archivo Black + Geist Mono + Instrument Serif

Industrial, precise, magazine-like. Reserved for flagship event pages, the Our Story timeline, and any page designed to make someone say “I need to be part of this.”

Tier 1 — Typefaces

Two families. Rubik for impact, Space Grotesk for everything else. The contrast between them does the heavy lifting of hierarchy.

Rubik

Display & headlines

A rounded geometric sans-serif with warmth and weight. Use exclusively for display-size text where you need visual impact. Never use for body copy or UI.

Character set

ABCDEFGHIJKLMNOPQRSTUVWXYZ

abcdefghijklmnopqrstuvwxyz

0123456789 &?!@#$%

500MediumH3, card titles
600SemiBoldH2, section headings
700BoldH1, page headlines
800ExtraBoldDisplay, hero, stage

Space Grotesk

System & body

A proportional sans-serif with monospaced heritage. Tabular figures make it ideal for dates, stats, and data-heavy UI. Handles everything Rubik does not.

Character set

ABCDEFGHIJKLMNOPQRSTUVWXYZ

abcdefghijklmnopqrstuvwxyz

0123456789 &?!@#$%

300LightLarge stat numbers (36px+)
400RegularBody copy, nav, descriptions
500MediumActive nav, overlines, captions
600SemiBoldButtons, CTAs
700BoldEmphasis in body (sparingly)

Tier 1 — Type scale

Nine levels cover every surface. Each level locks in font, weight, size, line height, and tracking — pick the level, not the values.

DisplayRubik 800 · 52 / 1.02 · -0.03em

Where SaaS scales

H1Rubik 700 · 40 / 1.10 · -0.02em

Page headline

H2Rubik 600 · 28 / 1.20 · -0.01em

Section heading

H3Rubik 500 · 22 / 1.25 · 0

Card title or speaker name

BodySpace Grotesk 400 · 16 / 1.60 · 0

Body copy carries the substance — bios, descriptions, paragraphs, and the long-form text that makes up the bulk of any page.

Body smallSpace Grotesk 400 · 14 / 1.50 · 0

Secondary text, captions, metadata, and fine print.

OverlineSpace Grotesk 500 · 12 / 1.40 · 0.08em · uppercase

Founder track

ButtonSpace Grotesk 600 · 15 / 1.00 · 0.06em · uppercase

Get tickets

StatSpace Grotesk 300 · 36 / 1.10 · -0.02em

12,500

Tier 1 — Usage by context

How the scale shows up on the surfaces that matter — stage, web, signage, and event swag.

Hero & stage

Where SaaS scales

Three days. One thousand operators. The annual gathering for B2B SaaS founders and the teams shipping with them.

Get tickets

Speaker card

Patrick Campbell

Founder & CEO, ProfitWell

Badge & signage

Aisha Patel

Head of Growth · Linear

Stats & metrics

12,500

Attendees

240

Speakers

68

Countries

Metadata pills

Founder trackDay 2MainstageIn person

Tier 1 — Pairing rules

Hierarchy comes from contrast between the two families, not from cranking weights.

Do

  • Use Rubik for headlines and Space Grotesk for everything else
  • Use Space Grotesk for all dates, numbers, and stats (tabular figures)
  • Use uppercase + letter spacing for overlines, labels, and buttons in Space Grotesk
  • Use Space Grotesk Light 300 for oversized stat numbers to keep them elegant
  • Maintain clear hierarchy through font family contrast, not just weight

Do not

  • Use Rubik for body copy, descriptions, or long-form text
  • Use Space Grotesk Bold 700 for headlines (overlap with Rubik loses hierarchy)
  • Mix both fonts at the same size and weight in the same block
  • Use Rubik below 18px (it loses its character at small sizes)
  • Use more than two weights of Rubik on a single page

Tier 2 — Where to use it

The editorial system is opt-in, never the default. Use it for pages whose purpose is emotional impact over templated consistency.

Use Tier 2 for

  • Historical event pages (`/usa/2023` … `/usa/2026`, `/europe/2016` … `/europe/2025`)
  • The `/about/our-story` narrative timeline
  • Annual hero landing pages for the next flagship event (e.g., `/usa/2027`)
  • Any standalone page designed to make someone say "I need to be part of this"

Do not use Tier 2 for

  • Email templates, newsletters, drip sequences
  • Sponsor decks, partnership proposals
  • Badge and signage printing
  • SaaStock Local event pages (use Tier 1)
  • Blog posts, help docs, support pages
  • Any page multiple people will update without design review

Tier 2 — Typefaces

Three families. Archivo Black for authority, Geist Mono for precision, Instrument Serif Italic for editorial warmth. Each font occupies a register the others can’t.

ARCHIVO BLACK

Display & headlines

Single-weight ultra-heavy grotesque — the font itself is the statement. Use at 36px+ for maximum impact. Reads as “conference you fly to,” not “product you sign up for.”

Character set

ABCDEFGHIJKLMNOPQRSTUVWXYZ

0123456789 &?!@#$%

400Black (only)Hero, section titles, CTA headlines, editorial stats

Geist Mono

Data & metadata

True monospace by Vercel. Every character occupies the same width — makes stats feel like a dashboard readout and labels feel like system output. Credibility through typography.

Character set

ABCDEFGHIJKLMNOPQRSTUVWXYZ

abcdefghijklmnopqrstuvwxyz

0123456789 &?!@#$%

400RegularMetadata, breadcrumbs, sponsor names, code snippets
500MediumOverlines, stat labels, nav, badges (uppercase)

Instrument Serif

Editorial accent

High-contrast transitional serif. Used in italic to create tonal contrast — a speaker’s talk title in serif italic under a bold sans-serif name makes the page feel like a magazine feature, not a sponsor grid.

Character set

ABCDEFGHIJKLMNOPQRSTUVWXYZ

abcdefghijklmnopqrstuvwxyz

0123456789 &?!@#$%

400Italic (primary)Subheadlines, speaker talk titles, accent phrases
400Regular (rare)Pull quotes, editorial callouts

Tier 2 — Type scale

Each role is assigned to a specific font — Archivo Black for display, Geist Mono for data, Instrument Serif Italic for accents, Archivo for body.

DisplayArchivo Black 400 · clamp(48–72) / 1.02 · -0.03em · uppercase

SaaStock USA 2026

H1Archivo Black 400 · 40 / 1.10 · -0.02em · uppercase

Page headline

H2Archivo Black 400 · 28–36 / 1.10 · -0.01em · uppercase

Section heading

H3Archivo Black 400 · 22 / 1.20 · 0 · uppercase

Card title

SubheadlineInstrument Serif Italic · 18–22 / 1.40 · 0

Three days. One stage. The operators rewriting B2B SaaS.

BodyArchivo 400 · 16 / 1.60 · 0

Editorial body copy uses Archivo regular — pairs naturally with Archivo Black and stays readable in long runs.

OverlineGeist Mono 500 · 11–12 / 1.40 · 0.08em · uppercase

Mainstage · Day 02

Stat numberArchivo Black 400 · 36 / 1.10 · -0.02em

1,500+

Stat labelGeist Mono 500 · 11 / 1.40 · 0.06em · uppercase

Founders in the room

ButtonArchivo 600–700 · 14–15 / 1.00 · 0.06em · uppercase

Get the pass

MetadataGeist Mono 400 · 11–12 · 0.06em

2026.06.04 · Boston, MA · ED-026

Tier 2 — Usage by context

How the editorial system shows up on a flagship event page. Authority on top, precision in the data, italic serif for accent.

Hero

SaaStock USA 2026

Three days. One stage. The operators rewriting B2B SaaS.

Get the pass

Speaker card

Patrick Campbell

Founder & CEO, ProfitWell

“The next decade of vertical SaaS pricing”

Stat bar

1,500+

Founders

240

Speakers

68

Countries

Edition metadata

2026.06.04·BOSTON, MA·EDITION 026

Section heading

Founder track

SCALING TO $50M

How the 0.001% break out of the messy middle.

Tier 2 — Pairing rules

The three-font system works because each font stays in its register. Cross the lines and the page reads as inconsistent, not editorial.

Do

  • Use Archivo Black exclusively for display and headlines — hierarchy comes from size, not weight
  • Use Geist Mono for anything that communicates data, system status, or metadata
  • Use Instrument Serif Italic sparingly — one or two uses per page (subheadline + talk titles) is ideal
  • Keep Instrument Serif in italic — the roman weight overlaps too much with Archivo in tone
  • Use Archivo (regular weight) for body copy — it pairs naturally with Archivo Black

Do not

  • Use Instrument Serif for body, buttons, labels, or navigation — it is an accent, not a workhorse
  • Use Geist Mono for headlines or body paragraphs — it is for metadata and data
  • Use more than three instances of Instrument Serif on a single page
  • Mix Tier 1 and Tier 2 fonts on the same page — pick one system per page
  • Use Archivo Black at small sizes (12–14px) for dense UI — it overwhelms in long runs

Why three fonts instead of two

The editorial system gives the page three distinct registers. Two sans-serif fonts cannot create this tonal shift.

01 · AuthorityArchivo Black

Industrial weight that communicates institutional scale. “SAASTOCK USA 2026” at 72px reads as a conference you fly to. Rubik at the same size reads as a friendly product.

02 · PrecisionGeist Mono

True monospace for stats and metadata. “1,500+” next to an uppercase mono label reads like a dashboard readout, not a marketing claim. Credibility through typography.

03 · Editorial warmthInstrument Serif

Italic serif as accent. When a talk title appears in serif italic under a bold sans-serif speaker name, the page feels curated, like a magazine feature.

Which tier? Decision tree

When starting a new page, work down this list and stop at the first match.

1

Will multiple people edit this page without design review?

Tier 1
2

Is this an email, deck, badge, blog post, or Local event page?

Tier 1
3

Is this a flagship event page, the Our Story timeline, or an annual hero landing page?

Tier 2
4

Not sure?

Tier 1

Cross-tier rules

The two systems do not blend. These are the hard lines.

Never do any of these

  • Never use Rubik and Archivo Black on the same page
  • Never use Space Grotesk and Geist Mono on the same page
  • A page is either fully Tier 1 or fully Tier 2 — no mixing
  • The footer on Tier 2 pages uses the editorial system, not Tier 1 fonts
  • Navigation on Tier 2 pages uses Geist Mono, not Space Grotesk

Implementation

Drop these snippets into any SaaStock surface. CSS variables keep both tiers consistent across products.

CSS variables

:root {
  /* Tier 1 — Brand */
  --font-display: 'Rubik', sans-serif;
  --font-system: 'Space Grotesk', sans-serif;

  /* Tier 2 — Editorial */
  --font-editorial-display: 'Archivo Black', sans-serif;
  --font-editorial-body: 'Archivo', sans-serif;
  --font-editorial-mono: 'Geist Mono', monospace;
  --font-editorial-accent: 'Instrument Serif', serif;
}

Google Fonts embed

<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>

<!-- Tier 1 — Brand -->
<link
  href="https://fonts.googleapis.com/css2?family=Rubik:wght@500;600;700;800&family=Space+Grotesk:wght@300;400;500;600;700&display=swap"
  rel="stylesheet">

<!-- Tier 2 — Editorial -->
<link
  href="https://fonts.googleapis.com/css2?family=Archivo+Black&family=Archivo:wght@400;500;600;700&family=Geist+Mono:wght@300;400;500&family=Instrument+Serif:ital@0;1&display=swap"
  rel="stylesheet">