Lovable: Seats Are Free, Compute Is Not

The strongest commercial proof that credit-led pricing scales — and a running experiment in how much metering illegibility a market will tolerate.

Case Facts

In One Breath

Lovable — the Stockholm prompt-to-app company that went from launch to $100M ARR in eight months and $500M by month nineteen — is the field's flagship credit-led business: plans are priced by the credits they include, not by seats, workspaces take unlimited members, and one pooled balance covers building, hosting, and the AI features inside deployed apps. The design is credit-native almost across the board — rollover, pooling with per-member limits, published draw order, top-ups, auto top-up — and the tier ladder runs from $25 to $4,300 a month. What it is not is legible: build-mode burn is complexity-weighted to compute, costs are knowable only after the fact, users are billed when the agent fixes its own mistakes, and the credit itself changes dollar value depending on the plan. The market has responded with both the fastest revenue ramp in software history and the most sustained credit-complaint corpus in this chapter. Both facts are true, and both are about the same design.

1. The Business and the Buyer

Lovable launched in November 2024 (rebranded from GPT Engineer), hit #1 on Product Hunt, and compounded to a claimed $100M ARR by July 2025, $200M by November 2025, and roughly $500M by June 2026, with about 8 million users (Product Growth teardown; Taskade history). It raised a $200M Series A at $1.8B in July 2025 and a $330M Series B at $6.6B in December 2025, backed by CapitalG, Menlo Ventures, NVIDIA and Salesforce's venture arms (TechCrunch, Dec 2025; Lovable Series B post); press reports place a further mid-2026 round near a $13B valuation (ValueAdd VC).

The buyer began as the "vibe coder" — a non-technical founder or hobbyist for whom the reference alternative was a $5,000–$30,000 freelance or agency build, or not building at all. By 2026 the declared motion is enterprise: Nursa gave 200+ employees access; eXp Realty cancelled millions in SaaS contracts for Lovable-built software (Lovable blog). The archetype is Process Automator — it substitutes for software-development labor — with a structurally important secondary layer: Lovable Cloud and the AI gateway meter the running of finished apps, making Lovable part infrastructure vendor, billed through the same credits.

2. The Model As Built

Foundation (C1–C4). The unit is an abstract credit. Pro starts at $25/month for 100 monthly credits and scales through eleven published tiers to 10,000 credits at $2,250/month; Business carries identical credit tiers at exactly double the price ($50–$4,300); annual billing discounts ~16% (subscription plans docs). The Pro volume curve is gentle: $0.25 per credit at the bottom, $0.225 at the top. Enterprise is a custom platform fee with volume-based credit pricing. Seats do not exist as a price axis: "plans are priced by the credits they include, not by seats," and workspaces take unlimited members on every plan including Free (pricing FAQ).

Consumption is two-mode. Plan mode — thinking, investigating, comparing approaches — costs a deterministic 1 credit per message and never touches code. Build mode is usage-based and complexity-weighted, with published fractional examples: recolor a button 0.50, remove a footer 0.90, add authentication 1.20, build a landing page with images ~2.00 — labeled "illustrative examples," with actual cost visible per message after the fact (credits and usage docs). Stopped requests are charged for work completed. A third consumption stream meters deployed apps: Cloud usage (database, storage, edge functions) and AI-gateway calls draw from the same balance after small monthly grants (20 Cloud credits, 4 AI credits) are exhausted.

And one sentence in the FAQ deserves italics it doesn't get: credits "are not necessarily equal in value across different plans." Business credits cost twice as much, yet Cloud and AI run-costs are the same dollar amount on both plans — so a Business workspace consumes half the credits for identical run usage, while build actions (priced in credits) effectively cost double (pricing FAQ). The credit is a plan-relative currency with two exchange rates inside one unit.

Lifecycle (C5–C13). Unused monthly plan credits roll over automatically while the subscription is active, expiring two months after issue — a sliding window equivalent to the Capped Rollover (1× Rule). Top-up credits (one-time or auto top-up, Pro and Business) last twelve months. Daily grants — 5 build credits every day on all plans, capped at 30/month on Free — expire nightly. Draw order is published: usage-specific grants first, then general credits closest to expiry. Pooling is the model's showpiece: everyone in the workspace builds from one shared balance, and owners can set a default per-member monthly credit limit with individual overrides — the Organizational Credit Pool pattern, complete with its governance valve. Cancellation is unusually gracious: paid credits freeze on downgrade to Free and reactivate if you resubscribe before expiry. No refunds, published plainly (credits and usage docs; pricing FAQ).

Governance and GTM (C14–C17). The 2026 "one balance" migration rebuilt the billing surface: Plans & credit usage now shows spend by member, by project, by build-versus-run, and even by which AI model deployed apps consume (Lovable billing announcement). Audit logs are Enterprise-only. There is no cost estimator before a Build-mode prompt, and no machine-readable pricing model — though the docs publish an llms.txt index, so an agent can at least parse the tier tables in prose. Change management has a split record examined below.

3. The Design Audit

The staircase chain that matters: the July 2025 decision to weight credits by compute (C2) — rational as Agent mode's variable costs arrived — pushed unpredictability into every downstream cell. Because burn became stochastic, the missing top-ups (C8) became intolerable ("I'm forced to double my expenditure... no option to simply buy $25 worth" — r/lovable, Sept 2025), forcing the January 2026 fix (Lovable on X). Because failed attempts bill like successful ones (C2 failure policy), the no-refund rule (C9) reads as charging for defects: "if the outcome isn't what you wanted and you need to revert, you still lose your tokens" (r/lovable, Sept 2025). One user estimated 30–40% of interactions were spent asking the agent to fix its own errors (r/lovable, Dec 2024). The two-mode design is the partial answer: Plan mode at a flat 1 credit is a deliberately deterministic refuge — an anxiety valve the other cases in this chapter lack.

4. The Value Test

EVE reconstruction, core segment (non-technical builder, small team). Reference value: a freelance or agency MVP at $5,000–$30,000, weeks of lead time; or a technical path (Cursor, Claude Code) that requires skills the buyer lacks. Lovable's positive differentiation is speed and accessibility; a working landing page costs ~$0.50 of credits and a one-page MVP roughly $7.50–$15 at Pro rates (Zite review, July 2026). Even a heavy month on the largest Pro tier ($2,250) is a fraction of one agency sprint. Project-level VtB is comfortably above 10, frequently above 100 — penetration economics again, but here with an expansion ladder that actually captures some of it: the 11-tier ramp, the Business 2× plane, and the run-layer meter that grows with an app's success.

That run layer is the quiet answer to the outcome question. Lovable's contract never prices outcomes — no OAR instrumentation, no realized-value clause — but Cloud and AI-gateway consumption scale with a deployed app's traffic and usage. A successful app pays Lovable more, automatically, through infrastructure. This is outcome participation through the meter rather than the contract — the AWS strategy wearing a credit costume — and it explains why the company can afford cost-calibrated build pricing: the land is the build; the expand is the run.

The two dials: dial one (price per credit) is genuinely worked — volume curve, annual discount, and the Business plane that charges 2× per credit for governance features, a rare case of value-based differentiation applied to the unit itself. Dial two (weights) is cost-calibrated: "the price of an action tracks the compute it burns" (Product Growth). Nothing in the weight system knows that authentication for a revenue-bearing app is worth more than a button recolor on a hobby page. As with Perplexity, value capture at the action level is accidental; unlike Perplexity, the tier ladder and run layer recover much of what the weights leave on the table.

5. What the Market Did Next

The commercial verdict is unambiguous: fastest software ramp on record, ~$500M ARR in 19 months, a valuation that tripled in five months (TechCrunch; Product Growth). The design verdict is a four-era complaint record that tracks each metering change:

1. Era 1 (Nov 2024 – Jun 2025), message quotas. Flat per-message pricing; complaints center on wasted messages fixing errors (r/lovable, Dec 2024). Tier changes in January 2025 grandfathered existing users (Lovable changelog).

2. Era 2 (Jul 2025), Agent mode. Complexity-weighted credits arrive in beta: "12 credits just for one code review... proceed with caution" (r/lovable, July 2025).

3. Era 3 (Sept 2025), agent by default. Users call the forced migration "a covert price hike" and object to paying for reverts (r/lovable, Sept 2025); "such mistakes used to cost 1/5 of what they cost today" (r/lovable).

4. Era 4 (Jan–mid 2026), fractional pricing, top-ups, one balance. Top-ups finally ship; a new pricing structure lands "without prior notice" and mid-task agent stops generate extra billable messages (r/lovable, Feb 2026); the unified balance migration converts Cloud/AI dollars to credits at plan rates (Lovable), drawing mixed reviews from users who preferred the dollar-denominated Cloud allowance (Trustpilot BR).

Aggregate third-party signal, as of mid-2026: Trustpilot 3.9/5 across ~1,289 reviews, with credit velocity the leading grievance ("you pay €25 a month and spend it in two days" — Trustpilot ES); G2's summarized cons put "lack of clarity in the credit system" first, tagged to 40 reviews (G2); an independent review scores pricing predictability 2/5 against speed 5/5 (Zite). The pattern repeats the Perplexity finding with more data: users do not resent the credit abstraction — they resent not knowing, in advance, what a unit of work will cost, and paying full price when the agent fails.

Scorecard

6. Lessons for the Practitioner

1. Credits-not-seats is a proven primary packaging axis. Making every seat free converts each invited colleague from a licensing negotiation into a consumption driver, and the per-member credit limit supplies the governance that seat prices used to. Lovable is the existence proof at $500M ARR. (C7/C15; Chapters 9–10.)

2. A deterministic mode is an anxiety valve for a stochastic meter. Plan mode at a flat 1 credit gives users a safe place to think while Build mode's burn floats. Every complexity-weighted model should ship with a flat-priced refuge. (C2; Chapter 7.)

3. Billing for the agent's own failures is the fastest way to convert enthusiasts into auditors. Charging pro-rata for stopped work and full price for error loops made "wasted credits" the community's organizing grievance across all four pricing eras. Failure policy is a design cell, not a support queue. (C2/C9; Chapters 7, 14.)

4. Do not overload the unit. A credit that costs 2× on Business, buys 2× the run-usage but the same build-work, and converts from dollars at "your plan's credit rate" is doing packaging work a price list should do. "Credits are not necessarily equal in value across different plans" is a sentence that should terrify a governance auditor — and an agent will read it literally. (C1/C4; Chapters 7, 13.)

5. If you meter cost at build time, own an asset that meters value at run time. Lovable's cheap, cost-calibrated build credits land customers; the Cloud and AI-gateway meter grows with every successful app. The pair works precisely because the second meter exists — copying the first half without the second is how credit businesses stall. (Chapters 5, 8, 10.)
   Pull quote: The market rendered a split verdict with perfect clarity: the fastest revenue ramp in software history, and a three-point-nine on Trustpilot — both awarded to the same metering decision.