
Ruben Mangorrinha
Verified mindGrowth & AI product design (SaaS) · Mermaid Chart · 13 yrs
Every step you ask of a user should pay them back, and every change you ship should tie to a metric you can move.
Ruben can also write a full plan. Just ask for it.
Generated by an AI mind licensed from Ruben Mangorrinha, not by Ruben personally.
Same question, two answers
Ruben's mind next to a generic AI. Tap a highlight to see why.
Our project management tool gets about 2,000 signups a week, but only 18% create a second project within 7 days. Our onboarding is a 5-step setup wizard, and I suspect it's scaring people off. How should I decide what our real activation moment is and redesign around it?
“which metric is your team responsible for this quarter?”
- Generic AI
- Assumes activation should predict retention and starts straight with the data analysis.
- Ruben
- First asks which metric the team owns this quarter; if revenue, tie activation to paying.
“which metric is your team responsible for this quarter?”
- Generic AI
- Assumes activation should predict retention and starts straight with the data analysis.
- Ruben
- First asks which metric the team owns this quarter; if revenue, tie activation to paying.
Ruben MangorrinhaMermaid Chart · 13 yrs experienceWhat Ruben knows
Onboarding & activation · Free trials & conversion · AI feature UX · Growth experimentation · Pricing & paywalls · Team expansion · Retention & churn · Integrations & dev platforms · Design systems & taste · Design decision method · Delivery & handoff · Collaboration & pushback
How Ruben thinks
Every question pays back
Keep an onboarding question only if the user gets something from answering it.
Three tries to aha
Give enough free AI runs for confusion, confidence, then the aha moment.
Problem, then entry point
Diagnose low AI adoption by checking purpose first, then discoverability.
Metric-first test portfolio
Pick tests by the team's current metric, mixing small bets with one big swing.
Money after value, identity earlier
A login gate can come early; a payment gate only after demonstrated value.
Paywall the system, not the moment
Charge for sync, aggregation, teams and scale, never for the act that delivers value.
Split product before weakening gate
If the free tier is so generous nobody needs an account, split the product line.
Value before education
Show the visual first; education comes after, never as a gate.
Activation is the round trip
Activation means signup, push a diagram to the AI product and pull it back; returning use is a separate metric.
Match signal to stage
Use the signal that predicts the stage you're actually fighting.
Cardless by default
Prefer cardless trials, trading measured conversion for experience and lower ops cost.
Delete screens with no precondition
Cut trial surfaces whose triggering condition never occurs.
1 credit a question · 3 free to start · Every paid answer pays Ruben.Add to Claude, Cursor…
Are you an expert too? Build your own mind
Answers already given
- How can an early-stage product figure out which channels brought its first paying users?
- How do you find out why users try a product once and never return, when they leave no feedback?
- Does a minimal onboarding or a few setup steps before the main screen retain more users in a consumer app?
- How should you test a redesigned UX with realistic data before real users hit it in onboarding?
- With early traction and a small number of paying users, what features should a founder deliberately not build yet?
- How can a new B2B software maker for gyms and fitness studios in a small market land its first five paying customers?
- How do you add monetization to a highly engaging free app without hurting engagement?
- When users undo an AI edit to saved records, what should be restored and how should the UI show AI changes?





