IRevenue narrative
Why revenue moved, not just that it did.
Quanta pairs each chart with a written caption your finance team actually reads. Variance gets a paragraph, not a tooltip.
observed
$4.2M
Q1 net revenue · +18.4% YoY
YoY trend
Quanta · Issue №47Spring 2026Charts: 23Editors: 4Read time: 9 min
Issue №47Analytics, set in lead.
The reading roomfor your data.
Quanta is the analytics surface modern teams build their weekly issue on — first-party data, written-prose narratives, and charts that respect their readers.
SQL · dbt · ClickHouseIssues · PDF · URLEditor + reader, separated
Issue №47Quanta Press · Friday
Lead
Q1 closed +18.4%. Subscriptions led; pro-services lagged a quarter.
Net revenue · 16 weeks+18.4%
+18.4%
net rev
yoy
+4.2pt
gross margin
qoq
−7%
ps revenue
qoq
The chart above suppresses the holiday spike to make the Q1 trend legible. Detailed cohort breakdowns appear on page 4 of the issue.
Abstract — Spring 2026
The age of dashboards designed by everyone and read by nobody is over. Quanta argues for a smaller, slower, better-written analytics surface — one that makes a chart and the sentence next to it the same first-class object. The result is fewer screens, longer reads, and a finance team that no longer asks where the numbers live.
Editions composed at
Stripe AtlasField Notes Co.Loam & Co.Northwind LabsMercury OSPlover StudioSubstrateFoundry 47Obscura MapsLinnea BakeryVerge EditionsStripe AtlasField Notes Co.Loam & Co.Northwind LabsMercury OSPlover StudioSubstrateFoundry 47Obscura MapsLinnea BakeryVerge Editions
/ chart specimen
Five charts.
One typeface.
Quanta ships with a tight set of editorially-tuned chart types. No 3-D pie. No rainbow. No defaults that betray your reader.
Q4 · Q1net revenue $M
Slope-line · varianceQ4 vs Q1
cohortD30 retention
w14
60.0%
w15
72.9%
w16
79.7%
w17
77.3%
w18
66.7%
w19
53.0%
w20
42.6%
w21
40.4%
w22
47.4%
w23
42.3%
w24
73.1%
w25
79.8%
Sparkline strip · cohortslast 12 cohorts
Net revenue · Q1
$4.2M
+18.4% YoY · +4.6% QoQ
Audited · finance@quanta
Single numbernet revenue
monthly · stacked direct referral paid
J
F
M
A
M
J
J
A
S
O
N
D
Stacked bars · channelacquisition mix
uptime · daily99.97%
−90dtoday
Heat strip · uptime90 days
/ four narratives
Issues teams already ship.
Each of these is a layout. Pick one, plug your warehouse, and publish a Friday issue your CFO will read on the train.
IIActivation funnel
Where users drop, and why nobody noticed.
Cohort retention rendered as a single sparkline strip. Cold-tail signals surface before the weekly review.
observed
47.2%
Day-30 activation, last cohort
cohort decay
IIIOperations log
The shipping queue, finally legible.
Operational dashboards composed of small, dense charts that fit one screen — no scroll-and-forget tile soup.
observed
1,328
orders fulfilled this week
queue depth
IVMarketing weekly
An issue, not a dashboard.
Quanta auto-publishes a weekly PDF of your top 9 charts with editor-written summaries. Stakeholders subscribe — no logins.
observed
Issue №47
this week's edition
channel mix
/ pipeline
From warehouse
to reading room.
A single read-only connection, a folder of SQL models, an issue scheduled for Friday at 8:00. The same query feeds the chart, the caption, and the export.
- sourcesSnowflake · BigQuery · ClickHouse · Postgres
- modelingSQL · dbt-compatible · cached
- deliveryPDF issue · private URL · email
- residencyEU · US · SG · AU
quanta.pipelinefriday 08:00
/ honest comparison
What you stop maintaining.
We benchmarked the same finance readout in Quanta and in a typical BI + Notion + Slack stack. Here is what changed.
Dimension
Quanta
Typical BI + Notion + Slack
Time-to-first-chart
4 minutes
2–6 weeks
Embedded narratives
First-class
Slack screenshots
Chart density
Editorially designed
Default presets
Stakeholder sharing
Read-only PDF + URL
Seat fee per viewer
Data residency
EU / US / SG / AU
Single region
Modeling layer
Inline SQL + dbt
Bring-your-own warehouse
from the readers
“Our exec readout is a Quanta issue now. Nobody opens the BI tool we used to pay for. Nobody asks where the dashboard is.”
Adelaida Pérez-Costa
Head of Operations, Linnea Bakery
0%
Issue delivery uptime, 12 months audited
0 min
Median time-to-first-chart
0K
Issues published last week
0K
Readers across customer issues
/ pricing
Editors pay.
Readers don't.
Stakeholders subscribing to your weekly issue should never see a login. They never do.
Tier
Reader
$0/ month
Studio
$48/ editor / month
Press
Customannual
Seats
Unlimited readers
Unlimited readers · 8 editors
Unlimited
Sources
1 source
Up to 24 sources
Unlimited + private warehouse
Issue cadence
Weekly digest
Daily + scheduled
On-demand white-label
SLA
Community
99.95% credit-backed
99.99% with named TAM
/ correspondence
Letters to the
editor.
Both — and we think that distinction is the bug. Quanta gives editors the same surface analysts use to query, so a chart and the paragraph next to it are produced once and read by everyone.
We connect to your existing warehouse (Snowflake, BigQuery, ClickHouse, Postgres) read-only. Quanta caches small aggregates in your chosen region — never raw rows. EU / US / SG / AU residency is honored at the routing layer.
An issue is a layout — a snapshot of your top metrics, written summaries and embeds, published as a clean PDF and a private URL. Stakeholders subscribe by email and get a new issue at your cadence. No logins.
Yes. The modeling layer is plain SQL with a dbt-compatible folder structure. The editorial layer sits above it, so queries are reusable across charts and narratives without copy-paste.
You pay per editor — the people composing issues. Readers are unlimited on every tier. There is no per-row, per-query or per-export charge on Studio and below.
/ recent issues
From the back catalog.
- 2026-04-22ChartsSlope-line chart promoted to GA — purpose-built for variance reads.
- 2026-04-09NarrativesInline citations link prose to the underlying SQL cell.
- 2026-03-31SourcesClickHouse Cloud + MotherDuck connectors.
- 2026-03-18PricingReader tier removed seat caps. All issues now public-shareable.