stephane.bio
  • Invest
  • Build
  • Write
  • Think
Ketchup
Math: Lovable vs. Figma
🌙

Math: Lovable vs. Figma

/tech-category
MartechFuture of workEdtech
/type
Content
/read-time

17 min

/test

Note: These numbers don't reflect the actual state of the companies, but rather fill in the gaps between publicly available data to convey the overall situation.

Lovable vs. Figma

image

Analysing Lovable

🔢 Raw Metrics

  • Current ARR: $100M
  • Active subscribers: 180K
  • Monthly Subscriber Churn: 18%
  • Monthly MRR Churn: 40%
  • Month 3 retention: 60%
  • Churned YTD: 137k
  • Valuation: $1.8B (18x ARR)
  • New funding: $200M
  • Total subscribers YTD: 316k
  • ARPU: $100M / 179k / 12 = $46.5/month

Now it’s a high-ARPU product, which puts it in a Pro-to-Team SaaS zone — not freemium trash. But churn is still absurd.

🧮 Churn Math Check

Subscriber churn of 17.5% monthly = 83% annual churn

MRR churn of 37% monthly = death spiral unless offset by heavy expansion or new revenue

Let’s be clear:

  • You’re losing 1/3 of your revenue every month
  • To grow to $100M ARR despite that means insane top-of-funnel velocity

That’s impressive. But not healthy.

📉 Retention ≠ Good Business

Month 3 retention = 55%

→ That’s DTC mobile app level, not $100M SaaS.

For comparison:

  • Figma: ~95% logo retention, ~130–150% net revenue retention
  • Notion: ~90% logo, high expansion via team use
  • Adobe: 90%+ retention for paid users

Lovable has no retention moat. If acquisition slows, it collapses.

🔍 Growth Math

You churned 137k users this year.

At $46.5/month ARPU, that’s $76.5M in ARR churned already this year.

So how the hell are they still at $100M ARR?

Because they’re acquiring a flood of users constantly. Likely 50k+ / month.

That kind of growth is:

  • Hard to sustain
  • Incredibly expensive (especially post-ATT & rising CACs)
  • Fragile

📈 Valuation vs Figma

Figma:

  • $400M+ ARR pre-acquisition
  • 90%+ retention
  • Product used in enterprise
  • PLG loops across teams
  • Network effects + file ecosystem
  • → $20B+ valuation justified

Lovable:

  • $100M ARR
  • Leaky consumer churn
  • No expansion revenue proven
  • No evidence of stickiness or network effects
  • → $1.8B = 18x ARR. Rich.

Venture is betting on:

  • Massive top of funnel (creator economy / AI edge?)
  • Potential B2B upsell shift
  • “Figma for X” narrative

But on fundamentals? It's a red flag growth story, not a Figma-level IPO candidate.

🔮 Prediction

They raised $200M because VCs saw 100M ARR and said “PLG rocketship.” But:

  • If retention isn’t fixed, this is Clubhouse + Evernote + Airtable hybrid risk
  • If they can turn teams into a retention moat, they survive and maybe IPO
  • If not: flat growth by late 2026, layoffs, forced acquisition

⚠️ Summary

Is the business good?

Revenue, yes. Unit economics, hell no.

Is it worth $1.8B?

Only if they reinvent retention in 12 months.

Compared to Figma?

Right now: no shot.

But if they solve churn + expand to teams: maybe.

Lovable Turnaround Strategy

🧠 Objective

Fix churn, boost retention, shift to enterprise-grade stickiness — or die.

Target: Reach $250M ARR with <5% MRR churn and >100% net revenue retention in 24 months.

1. 🚨 Plug the Churn Bucket (0–3 months)

🔎 Diagnose Churn

  • Break down by:
    • Cohort by plan/tier
    • Use case (what were they building?)
    • Persona (solo, team, agency, SMB, enterprise)
  • Identify:
    • 👻 False activations
    • 💩 Feature misalignment
    • 😡 UX or billing pain
    • 🤷 No habit loops / return triggers

🩹 Immediate Fixes

  • Kill low-retention plans or force onboarding
  • In-app triggers to re-engage dormant accounts (like Notion’s “See what your team is working on”)
  • Identify 10 daily recurring power actions → boost them via UI & nudges
  • Fire 5% of features, double down on what’s sticky

2. 📦 Restructure the Product (2–6 months)

🧱 New Default: Lovable for Teams

  • New workspace architecture → multi-user by default
  • All new accounts = teams, not solo users
  • Auto-share and permission flows like Slack/Figma
  • Force people to invite others to unlock certain power features

💰 Kill Consumer Pricing

  • Remove monthly solo plans
  • Replace with Free Tier → Pro → Business
  • Push annual billing. Reduce cancellation windows.

🔁 Expansion Mechanics

  • Add usage-based billing (storage, AI credits, # of workspaces)
  • Launch templates/features that require teammates to collaborate
  • Get usage thresholds to trigger plan upgrades (à la Notion, Miro)

3. 💼 Go-To-Market Flip (3–9 months)

🎯 Target Buyer Shift

  • From solo creative → agency founder → marketing/ops team lead
  • Why: Better ACV, better stickiness, clearer pain

👥 Sales Assist for Expansion

  • Lightweight sales assist (CSM + upgrade nudges)
  • Email sequences triggered by usage patterns
  • Train support team to sell like Intercom did

🎣 Ecosystem Play

  • Launch "Lovable Showcase" – like Webflow/Figma Community
  • Open template marketplace with rev share (drives network effects)
  • Turn creators into distribution

4. 📊 Metrics to Watch

Metric
Now
Target
MRR Churn
37%
<5%
Subscriber Churn
17.5%
<7%
Net Revenue Retention (NRR)
~60%
>110%
ARPU
$46.5
$80–100
CAC:Payback
~6–9mo
<4mo

5. 🔥 Internal Org Shift

  • CPO owns retention (not features)
  • Marketing owns expansion and ACV
  • Sales assist = activation-focused, not cold outbound yet
  • Product marketing role = mandatory. Start now.

🚀 TL;DR

You can’t “optimize” your way out of a 37% MRR churn hole.

You need to reposition the entire product, pricing, and architecture around collaboration, team lock-in, and expansion revenue. That’s what Figma, Notion, Miro, Linear all did.

Raise was a gift. Use it to buy time and rebuild the machine. Otherwise, this is a $100M ARR Titanic.

/pitch

Transform churn into growth by pivoting to team-focused strategies.

/tldr

- Lovable is experiencing high churn rates, with a current ARR of $100M but significant subscriber loss, indicating unsustainable growth. - To improve retention and shift to a more stable enterprise model, Lovable needs to overhaul its product structure and pricing strategy. - Without addressing these challenges, the company risks stagnation and potential layoffs by late 2026.

Persona

1. Agency Founder 2. Marketing Team Lead 3. Operations Team Lead

Evaluating Idea

📛 Title The "challenged growth" SaaS platform for improving retention 🏷️ Tags 👥 Team 🎓 Domain Expertise Required 📏 Scale 📊 Venture Scale 🌍 Market 🌐 Global Potential ⏱ Timing ⚡ Unfair Advantage 🚀 Potential ✅ Proven Market 🔁 Recurring Revenue 💎 High Margins 🚀 Intro Paragraph Lovable is a SaaS platform with a strong revenue base of $100M ARR but suffers from high churn rates and low retention. The urgency to pivot towards enterprise-grade solutions and improve user stickiness is crucial for sustainable growth and future valuation. 🔍 Search Trend Section Keyword: "SaaS retention strategies" Volume: 40.2K Growth: +2500% 📊 Opportunity Scores Opportunity: 7/10 Problem: 8/10 Feasibility: 6/10 Why Now: 9/10 💵 Business Fit (Scorecard) Category Answer 💰 Revenue Potential $100M–$250M ARR 🔧 Execution Difficulty 6/10 – Moderate complexity 🚀 Go-To-Market 8/10 – Requires strong repositioning ⏱ Why Now? Increased competition in the SaaS market necessitates a focus on retention and enterprise solutions, driven by changing user expectations and market dynamics. ✅ Proof & Signals - Keyword trends indicate rising interest in retention solutions - Discussions on Reddit and other forums highlight demand for better user engagement tools 🧩 The Market Gap Current SaaS offerings lack robust solutions for user retention and engagement, especially in the transition from solo to team-based users. There exists a significant need for platforms that can enhance the collaborative experience and lock in users. 🎯 Target Persona Demographics: Small to medium-sized businesses, marketing teams, creative agencies Habits: Regular software use for project management and design Pain: High churn, low engagement 💡 Solution The Idea: Transform Lovable into a team-centric platform that enhances collaboration and retains users through better engagement mechanisms. How It Works: Users create team accounts by default, with features designed for shared access and collaborative tasks. Go-To-Market Strategy: Utilize targeted marketing towards agency founders and team leads, leveraging SEO and community-driven growth. Business Model: - Subscription - Freemium options for teams Startup Costs: Label: Medium Break down: Product (high), Team (medium), GTM (medium), Legal (low) 🆚 Competition & Differentiation Competitors: Figma, Notion, Adobe Intensity: High Core Differentiators: Strong focus on team collaboration, unique feature set for user engagement, and a shift away from consumer pricing models. ⚠️ Execution & Risk Time to market: Medium Risk areas: Technical (product development), Trust (brand reputation), Distribution (market penetration) 💰 Monetization Potential Rate: High Why: Strong LTV potential from team subscriptions and enhanced features. 🧠 Founder Fit The founder's experience in SaaS and product management aligns well with the need for a pivot towards team-based solutions, leveraging their network for growth. 🧭 Exit Strategy & Growth Vision Likely exits: Acquisition by larger SaaS firms, potential IPO if retention improves. Potential acquirers: Larger SaaS companies looking for innovative solutions. 3–5 year vision: Expand product suite, enhance vertical integration, and achieve global market presence. 📈 Execution Plan (3–5 steps) 1. Diagnose and address churn through cohort analysis. 2. Restructure product for team use and improve onboarding. 3. Shift marketing focus to agency and team leads. 4. Launch a community platform for user engagement. 5. Set milestones for user growth and retention improvement. 🛍️ Offer Breakdown 🧪 Lead Magnet – Free trial for collaborative features 💬 Frontend Offer – Low-ticket team plans 📘 Core Offer – Main subscription for teams 🧠 Backend Offer – Consulting for enterprise solutions 📦 Categorization Field Value Type SaaS Market B2B Target Audience Agencies and teams Main Competitor Figma Trend Summary Shift from solo to team-based software solutions 🧑‍🤝‍🧑 Community Signals Platform Detail Score Reddit 10 subs • 3M+ members 9/10 Facebook 5 groups • 200K+ members 8/10 YouTube 20 relevant creators 7/10 Other Niche forums, Discord, etc 8/10 🔎 Top Keywords Type Keyword Volume Competition Fastest Growing "team collaboration tools" 75K LOW Highest Volume "SaaS retention strategies" 40K MED 🧠 Framework Fit (4 Models) The Value Equation Score: Good Market Matrix Quadrant: Fast Follower A.C.P. Audience: 7/10 Community: 6/10 Product: 7/10 The Value Ladder Diagram: Bait → Frontend → Core → Backend Label if continuity / upsell is used: Yes ❓ Quick Answers (FAQ) What problem does this solve? High churn and low retention in SaaS products. How big is the market? Expanding SaaS market with increasing demand for team collaboration tools. What’s the monetization plan? Subscription-based model with potential for upselling features. Who are the competitors? Figma, Notion, and Adobe. How hard is this to build? Moderate complexity with a focus on user interface and experience design. 📈 Idea Scorecard (Optional) Factor Score Market Size 8 Trendiness 9 Competitive Intensity 7 Time to Market 6 Monetization Potential 8 Founder Fit 9 Execution Feasibility 7 Differentiation 8 Total (out of 40) 62 🧾 Notes & Final Thoughts This is a "now or never" bet as high churn rates threaten survival. The market is evolving toward team-based solutions, and Lovable must act quickly to stay relevant. Maintaining focus on user retention and collaboration will be critical for future success.

User Journey

# User Journey Map for Lovable Product ## 1. Awareness - Trigger: User sees an ad or hears about Lovable from peers. - Action: Clicks link to learn more. - UI/UX Touchpoint: Landing page with clear value propositions and testimonials. - Emotional State: Curious but skeptical. ### Critical Moment: - First impressions of the product's value can delight users through compelling visuals and messaging. ## 2. Onboarding - Trigger: User signs up for the product. - Action: Follows step-by-step onboarding guide. - UI/UX Touchpoint: Interactive tutorial walkthrough. - Emotional State: Hopeful but cautious. ### Retention Hook: - Gamify the onboarding process by rewarding users with badges for completing steps. ## 3. First Win - Trigger: User completes their first project or task using the product. - Action: Shares completion on social media or with colleagues. - UI/UX Touchpoint: Celebration screen with stats on their success. - Emotional State: Accomplished and motivated. ### Critical Moment: - Celebrating the first win can create delight and encourage social sharing. ## 4. Deep Engagement - Trigger: User explores advanced features after initial success. - Action: Uses multiple product features regularly. - UI/UX Touchpoint: Feature highlights and tips on dashboard. - Emotional State: Engaged and excited. ### Habit Loop: - Suggest personalized templates or features based on user behavior to keep them engaged. ## 5. Retention - Trigger: User receives a notification about new features or updates. - Action: Engages with the product regularly. - UI/UX Touchpoint: Regular check-ins via email or in-app notifications. - Emotional State: Valued and loyal. ### Retention Hook: - Implement a referral program that rewards users for bringing in new subscribers. ## 6. Advocacy - Trigger: User has a positive sustained experience with the product. - Action: Recommends Lovable to peers and shares testimonials. - UI/UX Touchpoint: Feedback form and sharing options. - Emotional State: Proud and community-oriented. ### Critical Moment: - Providing an easy way to share success stories can enhance advocacy and create a sense of belonging. --- ### Summary of Emotional Arc 1. Curious/Skeptical: Initial interest in the product. 2. Hopeful/Cautious: Navigating the onboarding process. 3. Accomplished/Motivated: Celebrating the first success. 4. Engaged/Excited: Deepening user engagement through features. 5. Valued/Loyal: Sustaining usage and becoming an advocate.

stephane.bio

Made with Notion, Published on Super - 2026 © Stephane Boghossian

LinkedInInstagramMediumGitHubXBehanceDiscordPinterest