There's more depth than you think

You ran your first review

You pasted a PRD into SPM. It scored every gap. It asked you questions you hadn't considered. You improved sections that had been sitting half-finished for a week. The document got better. You felt better about it.

That's where most people stop. One document, one nano app, one review.

But that's like going to the gym once, doing bench press, and thinking you've seen the whole gym.

There's always a next frontier

A PM who's solid at writing PRDs might never have pressure-tested their competitive analysis. Someone who nails competitive analysis might have blind spots in how they frame growth strategy. A PM who thinks in growth loops might struggle to translate that into measurable OKRs.

Every domain in product management has its own set of expert expectations. What counts as "thorough" in a PRD is completely different from what counts as "thorough" in a stakeholder management plan.

SPM has 30 expert reviews across the PM lifecycle:

Each one has its own set of expectations, its own scoring rubric, its own clarification questions. The expert who reviews your PRD asks different questions than the expert who reviews your growth strategy. They should. They're different disciplines.

The shift that happens around review 5

The first few reviews are about your document. "Is this section complete? Did I miss rollback criteria? Is my hypothesis testable?"

Around review 5, something changes. You stop thinking about the document and start thinking about your thinking. You notice patterns: "I always skip counter-metrics." "I never define what success looks like before I define the solution." "Every time I write a competitive analysis, I compare features instead of positioning."

Those patterns are your blind spots. Not in one document. In how you approach product work.

Master one, discover the next

Here's what actually happens when PMs use SPM across multiple nano apps:

1. 1
   You nail your PRD

   Rollback criteria, success metrics, scope boundaries, all tight. Score: 82%.
2. 2
   You try competitive analysis

   SPM asks: "Are you comparing features or strategic positioning?" You realise you've been doing feature tables your whole career.
3. 3
   You try growth strategy

   SPM asks: "Is your growth loop self-reinforcing or does it require constant fuel?" A question nobody on your team has ever asked.

Each nano app is a new frontier. You graduate from one, and the next one finds blind spots you didn't know you had. That's not a limitation of SPM. That's the nature of product management. It's too broad for anyone to be expert at everything.

It gets more personal over time

The more you use SPM, the more it understands where you're strong and where you need challenge. Not because it tracks you. Because the pattern of which questions make you pause and which ones you breeze through tells a story.

A PM who consistently scores high on metrics but low on stakeholder communication has a different growth path than one who nails stakeholder alignment but struggles with hypothesis framing. SPM adapts. The questions get harder where you need them. They step back where you don't.

Think of it like a training partner who knows your body. They don't waste your time on exercises you've mastered. But they still make you do squats, because squats are fundamental. Some expectations are non-negotiable regardless of your experience. That's the floor. Everything above it is personalised to you.

When you stop needing SPM for problem statements, we've won

If a PM internalises the mental model for problem statements and doesn't use SPM next time, that's a BIG WIN for us. That's the outcome we're building for.

But even when you've built the mental muscle, SPM is designed to:

• Challenge your assumptions. You internalised the framework, but SPM still catches the assumptions you made this time. This is exercising the muscle you already built.
• Open 30+ other frontiers. Competitive analysis, growth loops, strategy, OKRs, and growing. At every stage, SPM asks grounded and elevated questions you haven't faced in that domain yet.

And the same thinking model applies across all four modules of the platform:

• Signal Intelligence: PM synthesises customer signals. SPM challenges: "Is this a root cause or a symptom?"
• Strategy & Roadmap: PM prioritises initiatives. SPM challenges: "Does this connect to an OKR, or is it scope creep?"
• PRD Intelligence: PM writes the spec. SPM challenges: "Is this hypothesis testable?"
• Communication & Impact: PM drafts the release note. SPM challenges: "Can sales explain why this matters tomorrow?"

Every module automates the first draft. SPM challenges the decision behind it.

You built the muscle. But muscles need exercise. SPM is the default thinking partner, whether you want to grow muscle or exercise it.

30 reviews. You've used one.

If you've run one analysis, you've seen 3% of what SPM can do. Try a different nano app. Pick the one that scares you. The one where you think "I'm probably fine at this."

That's usually where the blind spots live.