For Notion users

Your workspace is beautiful.
Your business still can't find itself.

Notion is where the docs live. It's not where the work is designed. Henry maps the seven stages of customer journey, then hands you the blocks, databases, and relations to build in Notion.

The pattern we keep hearing
"We have four workspaces, sixteen databases, and a template gallery three screens deep. I still can't tell you which customer is about to churn, or why."
— Head of Ops, Series A SaaS · composite of 11 recent calls
The confusion

Notion is a surface. Not a design.

Notion does one thing extraordinarily well: it gives you a blank page that bends into any shape you need. That is its gift and its trap.

The gift: nothing is in your way. The trap: nothing is in your way. So the team builds. A CRM here. An onboarding doc there. A project tracker that grew out of a retro. By month eighteen, you have a workspace that looks like organization and feels like archaeology.

The problem isn't Notion. Notion is doing exactly what you asked it to do. The problem is that no one designed the business that Notion was supposed to hold. The database schema is downstream of the operational model, and the operational model is missing.

Henry is the design layer above Notion. He maps the seven stages of the customer journey (the AAAERRR framework from Deliberate Work), specifies what data each stage owns, and hands you a build spec. Notion renders it.

Symptom 01

Three places to look up a customer. None of them agree.

Symptom 02

Templates for everything. A system for nothing.

Symptom 03

The onboarding doc is 47 screens long and your team still DMs you with the same four questions.

Symptom 04

You can filter every view by every property, and still can't answer "who's stuck at activation?"

The mapping

How Henry's design lands in your workspace.

Every deliverable Henry produces maps to something you already know how to build in Notion. Nothing new to learn. Just a schema that finally describes the business. See how it works for the full flow from diagnosis to specification.

Henry deliverable What it is Where it lives in Notion
AAAERRR pipeline The seven-stage customer journey, instrumented. Master database with Stage select property + board view grouped by stage.
Stage contract Entry, exit, and failure conditions for each stage. Template-per-stage page linked from the contract database.
Sentinel set The leading indicators that fire before something breaks. Formula columns + synced database that surfaces red rows.
Role charter Who owns what stage, and what "owning" means. Teamspace page + relation from stage → person.
Emergency Exit protocol The designed off-ramp for customers the Flywheel can't hold. Linked sub-database with intervention → graceful close → win-back toggles.
Off-boarding path The designed completion ritual at peak goodwill. Checklist template attached to the customer record on completion.
Weekly review instrument The ten questions the team answers every Friday. Recurring synced view + toggle list at top of home page.

Notion is a rendering target, not a dependency. The design works in Airtable, Coda, or a spreadsheet.

What it looks like rendered

One database. Seven stages. No more archaeology.

Here is what a single customer record looks like moving through the AAAERRR pipeline in Notion. Same page. Same property schema. Every stage owned, every gap visible.

Customer
Current state
Stage
A1
Alvarez & Co.
Inbound from partner referral · unqualified
Awareness
A2
Brightwell Partners
In discovery · decision criteria drafted
Acquisition
A3
Corrigan Labs
Signed · onboarding day 6 · milestone 2 pending
Activation
E
Delmar Group
Core loop engaged · 11 weekly sessions · on pattern
Engagement
R1
Ennerdale Holdings
Sentinel tripped: 14-day silence, usage −62%
Retention · AT RISK
R2
Fairweather Studio
Expansion conversation scheduled · seat +40%
Revenue
R3
Garwood Advisors
Wrote a case study · introduced us to 2 peers
Referral
Why this is different from your current Notion setup
Most Notion workspaces organize by artifact type — a database of customers, a database of tasks, a database of meetings, a database of docs. Henry organizes by stage of the relationship. Artifacts become properties of the stage record. The workspace stops being a filing cabinet and starts being a live dashboard of where every relationship actually is.
Does Henry build the Notion workspace for me?
No. Henry produces the design — schema, views, relations, formulas, template structure. You or your ops person renders it in Notion (usually a one-to-two-day build). This is deliberate: the design is decoupled from the tool so it survives when you outgrow Notion or switch to a custom system.
What if we're already deep in Notion and it's a mess?
That is the most common starting point. Henry's diagnosis begins where you are. The output is a migration path: which databases collapse, which ones stay, what gets archived, and in what order, without freezing the business.
Take something useful before you commit

The seven-stage diagnosis worksheet.

Eight pages. One per stage, plus a summary. Print it, work through it with your ops lead, and you'll know in an afternoon which stage of the journey is costing you the most and where your Notion schema is lying to you. Use it with Henry or without him.

Free download · no email required

AAAERRR Diagnosis Worksheet

A paper-and-pen audit of your customer journey across all seven stages. For each stage: entry condition, exit condition, owner, the sentinel you wish you had, and the number you can't currently answer.

PDF · 8 pages · 45-minute exercise
Download worksheet

If the worksheet alone fixes your problem — we'd love to hear about it. If you finish it and realize you want a second set of eyes, that's what Henry is for.

Let's see what your workspace is hiding.

Fifteen minutes with Joe. We'll open your Notion, look at one customer, and see if the schema tells a true story.

Book 15 minutes with Joe →

Prefer async? Join the launch list — we review applications weekly. Or see who Henry is for.