01 Broadside

this is the broadside style

Protest poster meets publication cover. Type so large it becomes image.

[[Author Name]] [Year] · Context
02 / Chapter

the next chapter begins here

One optional sentence that frames what this section is about.

The Argument 03

Core Thesis

orange is not an accent. it is the room.

Broadside [Author Name]
Details 04

Context

when content needs image support

One or two sentences of supporting context. Short. Dense. No padding.

  • First key supporting point
  • Second point, equally direct
  • Third and final — end strong
Image Placeholder

Image caption or source · Year

Broadside [Author Name]
05 By the numbers
$3.5B
Series E closed at $61.5B valuation
[Source] · [Year]
3×
Enterprise deployments up quarter over quarter
Primary research
#1
App Store ranking · [Product Name] · [Date]
App Store Charts
Broadside [Author Name]
01
Before During After
the
session
[Studio X] Guidelines 06 / 10
The Framework 07

Four rules

what separates
signal from noise

  • Ship before it's ready — learn faster than you plan
  • One metric that matters — ignore everything else this quarter
  • The customer is always wrong about solutions, never about problems
  • Speed is a feature — slow companies don't get a second chance
Broadside [Author Name]

On speed

"Move fast and you'll break things. Move slow and something else will break you."
[Industry Leader] [Source] · [Year]
Before · After 09
Before

six-month build cycles

Teams planned for months before shipping anything. By launch, the market had moved.

  • Waterfall planning, quarterly roadmaps
  • User testing at the end, not the start
  • Success measured by features shipped
After

two-week iteration loops

Ship a rough version. Watch what users actually do. Rebuild. Ship again.

  • Weekly user sessions, continuous discovery
  • Metrics reviewed daily, not quarterly
  • Success measured by behavior change
Broadside [Author Name]
Growth Metrics 11

revenue by quarter

USD · Millions · FY 2025
$1.2M
Q1
$1.7M
Q2
$2.1M
Q3
$2.8M
Q4

Source: Internal finance data · Q4 2025 Annual Report

Broadside [Author Name]
12 The Process

how it works

01
Discover
Talk to users. Read the data. Surface what's actually true vs. what the team assumes.
→
02
Define
Narrow to one problem worth solving. Write it as a testable hypothesis, not a feature request.
→
03
Design
Build the simplest thing that could prove or disprove the hypothesis. Skip the polish.
→
04
Deploy
Ship to real users. Measure behavior, not opinions. Repeat from step one with new data.
Broadside [Author Name]
Market Share 13

where the market sits

Leader 40%
Challenger 28%
Followers 20%
Other 12%
TOTAL MARKET: $[X]B · [Year] ESTIMATE

Source: [Industry report] · [Year] · Estimates only

[Author] [Year]
The Hierarchy 14

what actually matters

mission why this exists
strategy what we're betting on
product what we're building
growth how we reach people
operations how we run the day-to-day
[Author] [Year]
The Story 15
how we got here
[Year −3]
the idea
One slide. Three slides. Nineteen rejections. One yes.
[Year −2]
first product
Launched to [N] users. [X]% used it daily after week one.
[Year −1]
the pivot
Killed [X] features. Found the one thing that changed retention.
[Year 0]
now
[N]k users. $[X]M ARR. The hard part starts here.
[Author] / [Year] 15
The Loop 16

build · measure · learn

01
build
Ship the smallest version that could prove the idea wrong.
→
02
measure
What did users actually do? Not what they said — what they did.
↓
↓
04
learn
Update the hypothesis. Kill what didn't work. Double what did.
←
03
decide
Ship to more users or go back to step one. There is no third option.
[Author] / [Year] 16
10 End

let's
talk.

[hello@company.com] · [@handle] · [company.com]

[Author Name] [Year]