Workspace Maturity Score: why we hide most of the product on day one

A new Lazynext workspace doesn’t look like Lazynext. There’s no canvas, no automations, no tables, no docs. There are decisions and outcomes. That’s it.

This is deliberate, and it’s the single most contested product decision we’ve made.

The score, in full

Every workspace has a hidden integer called `wms_score`, clamped 0–100. It bumps when you do real things in the product. There are five events, each weighted by how much signal they carry about a team that’s actually using the product the way it’s meant to be used:

• decision_created: +2
• outcome_recorded: +3 (the loop closing is more valuable than opening it)
• teammate_invited: +5 (a single-player workspace caps out fast — we want this to bump hardest)
• decision_public_shared: +2
• integration_connected: +4

Four layers, four thresholds

The score maps to one of four layers, and each layer unlocks a slice of the product:

• Layer 1 (0–14): Decisions and outcomes only. The product is two screens.
• Layer 2 (15–34): Tasks and threads unlock — you can now coordinate around the decisions you’re making.
• Layer 3 (35–59): Docs and tables unlock — the workspace is now a real reference surface, not just a decision log.
• Layer 4 (60+): The full canvas, automations, and integrations unlock. This is where Lazynext looks like the marketing site shows it.

A team that invites three colleagues, logs ten decisions, records two outcomes, and shares one decision publicly hits Layer 4 in a single afternoon. A team that opens the product, pokes around, and closes the tab never gets past Layer 1. We think both outcomes are correct.

Why this is unpopular and why we kept it

The standard objection: "I want to see what I’m paying for." Fair. So we shipped a single toggle in workspace settings called Power user mode. Flip it and every layer unlocks regardless of score. We default it off.

The reason we default it off: the highest-churn pattern in workflow software is the 90-day signup who never logged a single decision because they spent the first two weeks customizing views, building automations, and configuring integrations against an empty database. They built infrastructure for work that never showed up. The score-gate forces the early loop to be the work itself, not the configuration.

How the gate enforces itself

Two layers of enforcement. The sidebar and command palette both call `isFeatureUnlocked(feature, score, powerUserOverride)` before rendering — if the feature is locked, it’s not in the menu. That’s the soft gate. The hard gate is at the API level: routes that create locked node types check the same function server-side and return 402 if you somehow craft the request anyway. (You can; we don’t hide it; the locked surface just doesn’t advertise itself.)

The unlock moment

When a layer threshold is crossed, the next time you load the workspace home you get a small toast: "You unlocked Tasks and Threads. They’re in the sidebar now." Nothing else changes — no celebration animation, no upsell. The product treats the unlock as a fact of the team’s growth, not a reward for engagement-hacking. We tested the celebratory version. It read as condescending. We took it out.

What this gives up

A real loss: the screenshot-driven evaluation. A prospect lands, signs up, and wants to see the canvas. They get an empty decisions screen instead. That’s a real conversion cost we’ve eaten. The compensating bet is that teams who bounce because of this would have churned in week 3 anyway, and teams who stay through Layer 1 are roughly 4x more likely to still be active at day 90. The data on this is early but the gap is wide enough that we’re running with it.

What it gives back

A workspace at Layer 4 looks the way it does because the team got there. Every tile in the canvas, every automation rule, every integration is downstream of decisions that were actually made and outcomes that were actually recorded. The complexity is earned. That’s the only reason we trust it not to rot.

The override, plainly

Settings → Workspace → "Show me everything from the start." One click. We don’t hide it, we don’t guilt you, we don’t require you to confirm. If you’re an experienced user who knows what you want, the gate is two seconds out of your life. The default is the only opinion we’re defending here.