For ClickUp users

You configured everything.
You're still not sure what the team is doing.

ClickUp runs the tasks. It does not design the work. Henry draws the seven-stage operational model your Spaces are supposed to serve, so the statuses, automations, and dashboards finally point at something real.

The pattern we keep hearing
"I have 14 Spaces, 42 custom statuses, 28 automations, and a dashboard with nine widgets. And last week my best customer churned and none of it told me it was coming."
— COO, 38-person services firm · composite of 9 recent calls
The confusion

A task list is not an operational model.

ClickUp's strength is that it can become almost anything: a CRM, a dev tracker, a client portal, a finance board. Each team in your company has found its own answer to "what should this look like?"

The result is a workspace that is locally coherent and globally incomprehensible. Sales has a Space. Delivery has a Space. Success has a Space. Each has its own status ladder. Handoffs happen by Slack. A customer appears as a lead, then a project, then an account, and somewhere in between the thread drops.

Henry doesn't touch your ClickUp config until the underlying customer journey has been designed as one artifact — seven stages, shared contracts, defined handoffs (the AAAERRR framework from Deliberate Work). Then your Spaces have something to be Spaces of.

Symptom 01

Every team lead configured their Space alone. You now have 11 ways to mean "in progress."

Symptom 02

Automations fire reliably. No one remembers why half of them exist.

Symptom 03

The dashboard widgets are green. The customer is not.

Symptom 04

Handoff between teams happens in DMs because no one trusts the Space boundaries.

Where Henry sits in your hierarchy

One layer above your Spaces.

ClickUp's native hierarchy is Workspace → Space → Folder → List → Task. Henry adds one concept that makes the rest resolve: a shared seven-stage model the Spaces inherit from.

Before · shape without meaning
▾Workspace
▾Sales Space
Leads · Pipeline · Accounts · Meetings
▾Delivery Space
Projects · Sprints · Blockers · Retros
▾Success Space
QBRs · Tickets · Renewals · Advocacy
▾Ops Space
Hiring · Finance · Vendor · Other
Four islands. No shared vocabulary for the customer.
After · Spaces inherit from the journey
▾Workspace
◆Customer Journey (Henry, design layer)
▾Sales Spacerenders A1–A3
▾Delivery Spacerenders A3 + E
▾Success Spacerenders R1–R3
▾Off-ramp Spacerenders E-Exit + Off-board
Four Spaces, one model. Handoffs are stage transitions, not DMs.
The mapping

How Henry's design lands in ClickUp.

Each deliverable from Henry becomes a concrete ClickUp artifact. Nothing exotic — status ladders, custom fields, automations, and dashboard widgets you already know how to build. See how it works for the full diagnosis-to-specification flow.

Henry deliverable What it is Where it lives in ClickUp
AAAERRR pipeline Seven-stage journey shared across Spaces. Unified custom status set applied to every customer-touching List.
Stage contract Entry, exit, failure conditions per stage. Task template per stage + required custom fields.
Sentinel set Leading indicators that something is drifting. Automations: when field X crosses threshold Y, change status + notify owner.
Role charter Clear owner per stage; no shared accountability. Default assignee per status + one-owner-per-task rule.
Handoff protocol What must be true before a stage transition is allowed. Automation: block status change unless required fields are filled.
Emergency Exit protocol Designed response to sentinel triggers. Separate List with intervention → graceful close → win-back statuses.
Weekly review instrument Ten questions answered every Friday. Dashboard with exactly ten widgets. No more.

ClickUp is a rendering target, not a dependency. The design works in Linear, Jira, Monday, or Asana.

What it looks like rendered

One status ladder, every team reading the same score.

Here is a single customer's workflow crossing three Spaces, all using the Henry-designed stage set. Every task inherits the stage. Dashboards roll up by stage, not by Space.

Brightwell Partners · customer thread 7 tasks · 3 spaces
Qualify: fit, urgency, budget, decision process
A2 · Acquisition
Sales
Proposal sent + decision criteria confirmed
A2 · Acquisition
Sales
Signed · kickoff scheduled
A3 · Activation
Sales → Delivery
Onboarding milestone 1: workspace setup
A3 · Activation
Delivery
Onboarding milestone 2: first value delivered
A3 · Activation
Delivery
Transition to core loop · weekly cadence begins
E · Engagement
Success
Sentinel armed · 7-day silence + usage −40% trigger
R1 · Retention
Automation
Same customer. Three Spaces. One status vocabulary. The handoff tasks are explicit, not implicit.
Take something useful before you commit

The status-ladder audit template.

A one-page framework to audit every custom status in your ClickUp workspace and collapse them into the seven-stage journey. You'll find out, usually in under an hour, how many of your statuses mean the same thing and how many stages of the journey have no status at all.

Free download · no email required

ClickUp Status-Ladder Audit

Print the template. List every custom status in every Space. Map each to the seven AAAERRR stages. What's left over is noise. What's missing is where your customers are disappearing.

PDF · 4 pages · 60-minute exercise
Download template

If the audit alone gives you the clarity you needed — that's a win. If it reveals bigger design work underneath, Henry is what comes next.

Your ClickUp is configured. Now let's design what it's configured for.

Fifteen minutes with Joe. Bring your Spaces list. We'll look for the stage of the journey nobody owns.

Book 15 minutes with Joe →

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