Startup Diligence
Diligence report Enterprise Tech / AI app builder / AI software development platform Private unicorn / growth-stage venture-backed software company

Lovable

Lovable Startup Diligence Report

Proceed to confirmatory diligence rather than underwriting from public claims alone. Public evidence supports a real, fast-scaling AI app-builder with premium investors and meaningful usage/customer signals, while the key underwriting questions are ARR durability, paid conversion, margin under AI/cloud costs, customer retention, competitive defensibility, generated-code security/IP exposure and financing terms.

Company profile

Lovable Startup Diligence Report

Eligible for a public-source report: Lovable appears to be an active private unicorn, with CB Insights and company/news sources supporting a latest public $6.6B valuation. The business has strong public financing, product and usage signals, but financial quality, customer economics, technical/security assurance, cap-table economics and legal/privacy artifacts remain private diligence dependencies.

Website
lovable.dev
Sector
Enterprise Tech / AI app builder / AI software development platform
Geography
Sweden / Stockholm with U.S. and global operations signals
Stage
Private unicorn / growth-stage venture-backed software company
Known aliases
Lovable Labs Incorporated, Lovable Labs Sweden AB, Lovable Labs Inc., Loveable Labs Inc. (variant appearing in court-caption mirror), GPT Engineer lineage
Report version
1.0
Timezone
Europe/Stockholm

Executive summary

Strengths

  • CB Insights lists Lovable as a Sweden/Stockholm Enterprise Tech unicorn at $6.6B.
  • Lovable publicly announced a $330M Series B at a $6.6B valuation.
  • Company docs verify Lovable’s natural-language full-stack app-builder, GitHub sync and Supabase backend integration claims.

Risks

  • Financial quality, retention, margins and runway are not public.
  • Competition is intense across AI coding agents, prompt-to-app builders and no-code platforms.
  • AI-generated code/security/IP output risk requires technical and legal artifact review.

Gaps

  • Audited financials, ARR bridge, margins, cash/debt, forecasts and cap table.
  • Top-customer ARR, retention/churn, contract terms, concentration and references.
  • Technical review of generated-code quality, security defaults, incident history and model/cloud costs.
  • SOC/ISO reports, DPA/subprocessor list, insurance, counsel litigation/IP files and material contracts.
  • HRIS headcount, attrition, compensation/equity plans and leadership/org depth.

Recommended next steps

  • Run finance/cap-table diligence before relying on the $6.6B valuation.
  • Run customer diligence on retention, paid conversion and enterprise contract depth.
  • Run technical/security/legal diligence on generated apps, data processing, model providers and IP/AI-output terms.
  • Benchmark win/loss and pricing against Cursor, Replit, Bolt, v0, Bubble and Webflow.

Risk register

high high likelihood

R-006: Intense competition in AI app-building and coding tools

Cursor, Replit, Bolt, Vercel v0, Bubble and Webflow publicly target overlapping AI coding/app-building/no-code jobs.

Diligence request: Validate win/loss, switching costs, differentiation, pricing pressure, retention and competitor displacement by segment.

high medium likelihood

R-002: Valuation step-up and private financing terms may carry hidden economics

Public valuation increased from $1.8B Series A to $6.6B Series B within months, but preferences, secondary sales, option pool and dilution are private.

Diligence request: Review financing documents, liquidation waterfall, option pool, debt/SAFE notes and current 409A/secondary pricing.

high medium likelihood

R-004: AI-generated code may create security, quality and liability exposure

Terms warn that AI output may contain errors and may not be unique or rights-free; security claims need artifact review.

Diligence request: Perform code-generation red-team, security review of sample apps, vulnerability/incident review and enterprise indemnity analysis.

high unknown likelihood

R-001: Financial quality and revenue durability are not public

Headline ARR and usage metrics are public but audited financials, margins, retention, cash, debt and revenue-recognition policy are not public.

Diligence request: Require audited/management financials, KPI pack, ARR bridge, gross margin, cash/debt, cohort retention and forecast model.

high unknown likelihood

R-003: Customer concentration, churn and contract quality are not public

Public testimonials and logos do not disclose account-level ARR, renewal terms, usage depth, concentration or churn.

Diligence request: Request top-customer ARR, cohort retention/NRR, churn reasons, contract terms and independent customer references.

medium high likelihood

R-005: Third-party platform and model dependencies are material

Lovable workflows depend on integrations and infrastructure such as GitHub, Supabase and third-party AI providers; supplier contracts and SLAs are private.

Diligence request: Review supplier contracts, model-provider terms, data-retention restrictions, outages, fallback strategy and gross-margin sensitivity.

medium high likelihood

R-009: Rapid hiring and multi-location scaling may strain culture and execution

Careers page lists 76 roles across multiple geographies and functions, but actual headcount, attrition and management depth are private.

Diligence request: Request HRIS roster, org chart, attrition, regretted loss, comp bands, offer acceptance and leadership hiring plan.

medium medium likelihood

R-007: Brand/IP risk remains despite resolved trademark matter

A trademark lawsuit was dismissed with prejudice, but settlement terms are private and trademark applications/status should be verified officially.

Diligence request: Pull complete PACER docket, settlement, USPTO/EUIPO files, patent/open-source scans and counsel IP opinion.

Chapter 01

01Financial Information

Lovable has strong public financing evidence through a $200M Series A and $330M Series B, with CB Insights listing a $6.6B unicorn valuation; financial statements, revenue quality, cash/debt, cap table and forecast support remain private diligence items.

I.A Annual and quarterly financial information for the past three years

not publicly verifiable confidence: high

Public sources disclose funding and selected self-reported ARR/usage signals, not audited financial statements or detailed revenue by product/channel/customer.

Evidence gaps

  • Audited financials, management accounts, AR aging, cash/debt, revenue by product/channel/geography and cohort retention.

Hidden risks

  • ARR may include volatile usage, refunds or non-standard revenue recognition until reconciled.

Follow-up questions

  • Provide audited financials, KPI pack, ARR bridge, revenue-recognition policy, cash/debt schedule and AR aging.
Public revenue, usage and unit-economic signals
metricpublic valuesource or gapverification status
ARR$17M ARR claimed in February 2025Company blog; request billing exports and accounting policypartially_verified
Paying customers30,000+ paying customers claimed in February 2025Company blog; request customer definition and billing reconciliationpartially_verified
Projects/visits100,000+ projects/day; 25M+ total projects; 200M+ monthly visits to Lovable-built apps/sitesCompany Series B post; request analytics definitions and bot filteringpartially_verified
Audited financials, margin, cash/debt, AR agingNot publicRequest audited financials, management accounts, cash/debt and AR agingnot_publicly_verifiable

Usage metrics are not substitutes for revenue quality.

I.B Financial Projections

not publicly verifiable confidence: medium

Public valuation step-up indicates investor expectations, but projections, budget-to-actuals, scenario assumptions and capital plans are private.

Evidence gaps

  • Board plan, operating model, downside cases, CAC/payback, gross margin, R&D/customer support hiring plan and financing assumptions.

Hidden risks

  • A rapid valuation step-up may depend on aggressive growth assumptions not visible publicly.

Follow-up questions

  • Provide three-year forecast, budget-to-actuals, valuation bridge and sensitivity cases.
Public valuation trajectory Line chart of public valuation anchors.

I.C Capital Structure

partially verified confidence: medium

Investor names and entities are public, but fully diluted ownership, preferences, debt, options and intercompany structure are not.

Evidence gaps

  • Cap table, stockholder list, option/warrant/debt schedules, entity chart and IP assignments.

Hidden risks

  • Hidden liquidation preferences, SAFEs/notes, secondary sales or option-pool refreshes could change economic ownership.

Follow-up questions

  • Provide fully diluted cap table, financing documents, option plan, debt/SAFE schedule and entity chart.
Capital structure and ownership snapshot
stakeholderpublic positiondiligence caveatverification status
CapitalG and Menlo Ventures AnthologySeries B co-leads at $6.6B valuationShare class, preference, board rights and ownership unknownverified
AccelSeries A lead and returning investor; CB Insights lists Accel as investorOwnership percentage and preferences unknownverified
Lovable Labs Sweden AB / Lovable Labs IncorporatedActive Swedish entity; terms name Delaware corporation as contracting entityGroup structure, parent/subsidiary ownership and intercompany IP assignments unknownpartially_verified
Founders and employeesCofounders publicly named; careers page references equity upsideFounder stakes, option pool, vesting and equity plan are privatenot_publicly_verifiable

I.D Other financial information

partially verified confidence: medium

Public financing history is strong; tax positions, accounting policies, debt and off-balance-sheet obligations are not public.

Evidence gaps

  • Tax positions, accounting policies, revenue recognition memo, supplier commitments and financing-history detail.

Hidden risks

  • Tax, revenue recognition, model-provider usage costs and cloud commitments could materially affect margins.

Follow-up questions

  • Provide tax schedule, accounting policy memo, supplier commitments and round-by-round financing history with terms.
Public funding-round history
dateround or eventamountpost money or valuationlead or investorsverification status
2025-02-25Added funding / seed extension$15M added fundingNot disclosedCreandum; angels including Charlie Songhurst and Thomas Wolf per company postpartially_verified
2025-07-17Series A$200M$1.8B valuationAccel; 20VC, byFounders, Creandum, Hummingbird, Visionaries Club, angelsverified
2025-12-18Series B$330M$6.6B valuationCapitalG and Menlo Ventures Anthology; NVentures, Salesforce Ventures, Databricks Ventures, T.Capital, Atlassian Ventures, HubSpot Ventures and othersverified

Private documents required to confirm securities, preferences, secondary components and proceeds.

Lovable public financing timeline Chronological view of public financing and valuation events.
Chapter 02

02Products

Public documentation supports Lovable’s natural-language full-stack app-builder product, GitHub/Supabase integrations, pricing tiers and enterprise security claims; product quality, deployment security and economic performance need technical diligence.

II.A Description of each product

verified confidence: high

Lovable publicly offers a natural-language app builder with editable code, GitHub sync, Supabase backend integration, pricing tiers and enterprise governance/security features.

Evidence gaps

  • Product-level gross margin, uptime, generated-code defect rate, security incidents, roadmap and adoption by module.

Hidden risks

  • Generated apps may have vulnerabilities, insecure defaults, expensive model/provider costs or unclear IP guarantees.

Follow-up questions

  • Provide product metrics, security incident register, vulnerability scan results, roadmap, cost-to-serve by plan and sample generated-code review set.
Product and SKU matrix
product or featuretarget userpublic capabilityverification status
Natural-language app builderIndividuals, teams, non-technical buildersGenerates production-grade web applications from prompts with editable codeverified
GitHub sync/exportDevelopers and engineering teamsBackup, collaborate, sync changes, work locally and deploy outside Lovableverified
Supabase backend integrationTeams building data-backed appsPostgreSQL database, authentication, storage and serverless functionsverified
Enterprise controlsBusiness and enterprise teamsSSO, roles, publishing controls, SCIM, audit logs and governance claims by plan/pagepartially_verified
Public pricing tiers
tierpublic pricenotable featuresdiligence caveat
Free$0/month5 daily credits up to 30/month, workspace-private projects, unlimited collaborators, 5 lovable.app domains, CloudCost-to-serve and conversion not public
Pro$25/month shared across unlimited users (annual)100 monthly credits, rollovers, top-ups, custom domains, remove badge, user roles/permissionsRealized ASP and usage gross margin not public
Business$50/month shared across unlimited users (annual)Internal publish, SSO, team workspace, personal projects, role-based access, security centerDiscounting and seat/workspace economics not public
EnterprisePlatform fee based on company sizeVolume credit pricing, support, onboarding, design systems, SCIM, custom connectors, publishing/sharing controls, audit logsEnterprise pipeline, contract lengths and expansion not public
Technology integration and dependency matrix
dependencyrolepublic evidencerisk note
GitHubCode backup/sync, collaboration, local IDE workflow and external deploymentLovable docs describe project repository connections and syncReview API permissions, data access and customer ownership process
SupabaseHosted PostgreSQL, auth, storage and serverless backend for appsLovable docs call Supabase native integrationReview RLS defaults, billing, supplier SLAs and outage impact
Third-party AI providersAI generation / AI Gateway via providers such as OpenAI, Google or OpenRouter named in termsTerms reference third-party AI providersReview model-provider contracts, data retention and fallback strategy
Lovable product and dependency architecture Simplified architecture from public docs.
Chapter 03

03Customer Information

Public sources show significant usage metrics and named enterprise examples, but account-level ARR, top-customer concentration, churn, revenue by customer and supplier spending are private.

III.A Top customers by application

partially verified confidence: medium

Lovable publicly cites usage scale and several enterprise examples, but not a top-15 customer list or application-level revenue.

Evidence gaps

  • Top 15 customers by ARR/application, deployment dates, product usage and references.

Hidden risks

  • High usage could be concentrated in free/low-ARR accounts or one-off prototypes.

Follow-up questions

  • Provide top customer list by ARR and application, customer references and deployment/usage histories.
Public customer, usage and traction evidence
customer or metricpublic evidencewhat it does not showverification status
Deutsche TelekomCompany says Deutsche Telekom uses Lovable for UI projects and speed-to-marketContract value, renewal status and deployment depthpartially_verified
ZendeskCompany quotes Zendesk product leader on reducing prototype time from six weeks to three hoursCommercial status and number of userspartially_verified
Uber AICompany quotes Uber AI product leader saying Lovable helps create interactive prototypesRevenue, scope and production usepartially_verified
Usage metrics25M+ projects and 100,000+ new projects/day claimedUnique customers, paid mix, retention, bot filteringpartially_verified
Top 15 customers / 5%+ revenue customersNot publicConcentration, contracts, churn and customer referencesnot_publicly_verifiable
Public traction and customer-evidence bars Bar chart of disclosed usage/customer evidence and private customer gaps.

III.B Strategic relationships

partially verified confidence: medium

Public relationships include investors, integrations and enterprise proof points; economic terms are not public.

Evidence gaps

  • Partner agreements, investor rights, co-selling agreements and integration SLAs.

Hidden risks

  • Strategic relationships may include exclusivity, support obligations, data-processing or revenue-share terms that are not public.

Follow-up questions

  • Provide strategic partnership agreements, integration SLAs and investor governance rights.
Strategic relationships and partnerships
relationshipnaturepublic evidencediligence gap
CapitalG / Menlo Ventures AnthologySeries B lead investorsCompany Series B announcementInvestor rights, board seats and preferences
AccelSeries A lead and returning investorCompany and Accel announcementsBoard/governance rights and ownership
SupabaseNative product integration and investor/angel ecosystem signalDocs and Accel announcement list Supabase integration/founder angelCommercial terms and technical SLA
Enterprise users/testimonialsPublic customer proof pointsDeutsche Telekom, Zendesk and Uber AI examplesMSAs, revenue and reference checks

III.C Revenue by customer

not publicly verifiable confidence: high

Revenue by customer and any 5%+ customer concentration are not publicly verifiable.

Evidence gaps

  • Revenue by customer, NRR/churn, concentration, contract value and renewal dates.

Hidden risks

  • A small number of enterprise accounts or platform partnerships could drive disproportionate ARR.

Follow-up questions

  • Provide customer ARR concentration, cohort retention/NRR and contract schedules.

III.D Significant relationships severed within the last two years

not publicly verifiable confidence: medium

No public list of severed customers, partners or suppliers was found; this requires private confirmation.

Evidence gaps

  • Lost customers/partners/suppliers, churn reasons and termination notices.

Hidden risks

  • Lost strategic accounts or model/cloud suppliers could reveal product or commercial weakness.

Follow-up questions

  • Provide two-year lost customer/partner/supplier schedule and churn/lost-deal analysis.

III.E Top suppliers

partially verified confidence: medium

Public docs identify material technology dependencies including Supabase, GitHub and AI providers, but spending and contracts are private.

Evidence gaps

  • Supplier spend, contracts, SLAs, data-processing terms, outage history and fallback plans.

Hidden risks

  • AI model and cloud usage may materially affect gross margin and availability.

Follow-up questions

  • Provide top supplier list, spend by supplier, SLAs, DPAs and business-continuity plans.
Top supplier / cloud-and-infra dependency summary
supplier or dependencyrolepublic signalconcentration risk
SupabaseDatabase/auth/storage/functions for generated appsNative Supabase integration docsMaterial for full-stack apps; customer misconfiguration/security risk
GitHubRepository sync/export/developer workflowGitHub integration docsImportant for code ownership and engineering workflow
AI model providersGeneration and AI GatewayTerms reference providers such as OpenAI, Google and OpenRouterCost, latency, retention and provider-policy risk
Cloud/WAF/security infrastructureLovable Cloud infrastructure protectionSecurity page describes WAF, network isolation, encrypted storage and rate limitsSupplier names/contracts not public
Chapter 04

04Competition

Lovable competes in a crowded AI coding/app-builder category with developer tools, prompt-to-app products and no-code/web platforms; public differentiation is strong but defensibility requires win/loss and retention evidence.

IV.A Competitive landscape by market segment

verified confidence: high

Public competitor pages show overlapping products from Cursor, Replit, Bolt, Vercel v0, Bubble and Webflow.

Evidence gaps

  • Market share, win/loss, retention by competitor, pricing benchmarks and customer-switching evidence.

Hidden risks

  • Large platforms can copy features, subsidize pricing or bundle with existing developer/cloud ecosystems.

Follow-up questions

  • Provide competitive win/loss, pricing/discounting, NPS by alternative and renewal/churn reasons.
Competitor comparison matrix
competitorsegmentpublic positioningoverlap with lovablesource
CursorAI coding agent / IDEAI coding agentTargets developers; less non-technical app-builder positioningCursor homepage
Replit AIAI app builder/developer platformTurn natural language into apps and websitesStrong direct overlap in prompt-to-app workflowReplit AI page
BoltAI builder for websites/apps/prototypesCreate stunning apps & websites by chatting with AIDirect prompt-to-app and prototype overlapBolt homepage
Vercel v0Full-stack web apps with AIBuild Full-Stack Web Apps with AIDirect web-app generation overlap, strong deployment ecosystemv0 homepage
BubbleNo-code AI app builderBuild web & mobile apps with the only no-code AI app builderCompetes for non-technical app creationBubble homepage
WebflowWeb platform / agentic webAgentic web platform for modern businessesCompetes for business website/app workflowsWebflow homepage

Funding data for competitors was not collected to avoid weak citations; request a dedicated market map for financing depth.

Basis-of-competition scoring
axislovable public positioncompetitive pressurediligence need
Non-technical app creationStrong; mission to empower the 99% and natural-language full-stack app generationHigh from Replit, Bolt, v0, BubbleWin/loss by persona
Developer workflow ownershipGitHub sync and editable codeHigh from Cursor/Replit/v0Repository export quality and developer retention
Enterprise governance/securitySSO, SCIM, audit logs, compliance badgesHigh from Webflow/Vercel/Replit enterprise motionsSOC reports, enterprise pipeline and security questionnaire results
Pricing pressureFree/Pro/Business/self-serve plus enterprise feeLikely high; pricing across AI tools can compressDiscounting, usage-cost margin and churn by plan
AI app-builder competitive market map Qualitative map of adjacent competitors by user technicality and app-generation scope.
Chapter 05

05Marketing, Sales, and Distribution

Public evidence supports a hybrid product-led and enterprise GTM motion using free/self-serve pricing, templates/docs/community, enterprise demos and public proof points; CAC, payback, sales productivity and channel attribution are private.

V.A Strategy and implementation

verified confidence: medium

Public pricing, enterprise pages, docs/templates and customer proof points indicate self-serve PLG plus enterprise sales.

Evidence gaps

  • Channel attribution, CAC, payback, sales cycle, funnel conversion and budget plan.

Hidden risks

  • Growth may depend on viral free usage with uncertain paid conversion or high model costs.

Follow-up questions

  • Provide CRM funnel, attribution model, CAC/payback, sales productivity and marketing budget.
Distribution channels and GTM motions
channelpublic evidencelikely rolediligence gap
Self-serve free/pro/business pricingPricing page with Free, Pro and Business tiersProduct-led acquisition and conversionConversion, CAC, payback and refunds
Enterprise demo/direct salesEnterprise page and enterprise pricing/platform feeLarge account expansion and governance-led salesPipeline, sales cycle and enterprise win rate
Templates/docs/communityHomepage/templates, docs and community linksActivation and SEO/product educationAttribution and activation analytics
Investor/customer proof pointsSeries B customer examples and investor networkEnterprise trust and brand buildingReference conversion and contract value
Public marketing-signal summary
signalevidencestrengthrisk or gap
Large funding announcements$200M Series A and $330M Series B announcementsHigh awarenessValuation narrative may exceed revenue quality
Usage scale claims25M+ projects and 200M+ monthly visits to built apps/sitesStrong PLG signalDefinitions and paid conversion not public
Enterprise testimonialsDeutsche Telekom, Zendesk, Uber AI examplesEnterprise credibilityCommercial status not public
Active recruiting76 open roles across multiple functions and locationsScaling signalBurn and hiring productivity not public
Public GTM channel mix indicators Qualitative channel-mix bar using public evidence presence.

V.B Major Customers

partially verified confidence: medium

Major customer relationship trends and pipeline are not public beyond testimonials and usage examples.

Evidence gaps

  • Pipeline, bookings, customer health, expansion plans and top-account references.

Hidden risks

  • Testimonials may be pilots, prototypes or low-ARR deployments.

Follow-up questions

  • Provide pipeline by stage, top-account health, renewal calendar and references.

V.C Principal avenues for generating new business

partially verified confidence: medium

Principal public acquisition avenues appear to be self-serve, community/docs/templates, and enterprise demo/direct sales.

Evidence gaps

  • Channel source data, conversion cohorts and paid/free segmentation.

Hidden risks

  • Organic usage may not scale into durable paid accounts.

Follow-up questions

  • Provide acquisition funnel by channel and cohort conversion to paid/enterprise.

V.D Sales force productivity model

not publicly verifiable confidence: high

Sales productivity, quotas, compensation, sales cycle and planned sales hires are not public.

Evidence gaps

  • Sales comp plans, quota attainment, ramp time, pipeline conversion, sales cycle and planned hires.

Hidden risks

  • Hiring ahead of repeatable enterprise productivity could increase burn.

Follow-up questions

  • Provide sales productivity model, quotas, attainment, comp plans and hiring plan.

V.E Ability to implement marketing plan with current and projected budgets

not publicly verifiable confidence: high

Marketing budget adequacy cannot be verified publicly.

Evidence gaps

  • Marketing budget, CAC/payback, headcount plan and scenario forecast.

Hidden risks

  • Rapid category competition can raise CAC and compress payback.

Follow-up questions

  • Provide marketing plan, budget, CAC/payback and sensitivity cases.
Chapter 06

06Research and Development

Public docs show active product architecture and integrations, and hiring signals show R&D scaling; private diligence must verify roadmap, model/provider economics, generated-code quality, vulnerabilities and engineering productivity.

VI.A Description of R&D organization

partially verified confidence: medium

Public materials identify cofounders and active engineering/product/design hiring, but the full R&D org and spend are not public.

Evidence gaps

  • R&D org chart, spend by workstream, roadmap ownership, incident/vulnerability history and development velocity.

Hidden risks

  • R&D may be bottlenecked by model reliability, technical debt from rapid growth or scarce senior engineering/security hires.

Follow-up questions

  • Provide R&D org chart, roadmap, engineering metrics, incident log and model/provider cost roadmap.
Key R&D personnel and leadership signals
name or rolepublic role signalsourcediligence gap
Anton OsikaCofounder/CEO; Swedish registry lists CEO of Lovable Labs Sweden ABAccel, Ratsit, Lovable video/blogEmployment agreement, vesting, key-person risk
Fabian HedinCofounder publicly named by Accel and company blogAccel and Lovable blogCurrent operating role, vesting and IP assignment
Engineering/product/design rolesCareers page lists open roles across engineering, product and designLovable careersActual filled team, seniority and hiring plan
Security/trust functionSecurity page/trust center and vulnerability contact indicate security operationsSecurity/trust pagesSecurity team staffing, incidents and roadmap

VI.B New Product Pipeline

partially verified confidence: medium

Public docs show current capabilities and integrations, but new product timing, development cost and roadmap risks are private.

Evidence gaps

  • Product roadmap, development budget, model-provider contracts, vulnerability backlog and quality metrics.

Hidden risks

  • Generated-code security and model/provider economics may create roadmap delays or margin pressure.

Follow-up questions

  • Provide roadmap, PRD/backlog, R&D budget, model-provider contracts and security quality metrics.
Public product and research pipeline
project or capabilitypublic statuscritical technologyverification status
Natural-language full-stack generationGenerally available product per docs/homepageLLMs, code generation, application scaffoldingverified
GitHub sync/exportDocumented integrationGitHub app permissions and bidirectional syncverified
Supabase-backed app backendDocumented integrationPostgreSQL, authentication, storage, serverless functionsverified
Security scanning / enterprise controlsPublic security claims and trust centerVulnerability detection, access control, audit loggingpartially_verified
Model-provider roadmap/costsNot public beyond provider referencesOpenAI/Google/OpenRouter or other model contractsnot_publicly_verifiable
R&D workstream architecture map Map public R&D workstreams to diligence tests.
Chapter 07

07Management and Personnel

Public sources verify cofounders/CEO, active Swedish entity and substantial hiring signals; full management roster, org chart, compensation, equity, attrition and employee relations require private HR diligence.

VII.A Organization Chart

not publicly verifiable confidence: medium

Only a partial public org chart can be inferred from cofounder/CEO references and careers departments.

Evidence gaps

  • Current org chart, reporting lines, board/observer roles and key-person succession.

Hidden risks

  • Leadership gaps may be hidden during rapid multi-location scaling.

Follow-up questions

  • Provide current org chart, leadership biographies and board/observer roster.
Public management and operating org chart Publicly verified people/roles and unverified functional layers.

VII.B Historical and projected headcount by function and location

partially verified confidence: medium

Public hiring signals show a move from a 15-person early team to 76 open roles, but actual headcount and projected hiring are private.

Evidence gaps

  • HRIS headcount history, location/function breakdown, hiring plan, offer acceptance and recruiting spend.

Hidden risks

  • Open roles can signal aggressive burn and execution risk without validated productivity.

Follow-up questions

  • Provide HRIS export, hiring plan, accepted offers and attrition by function/location.
Headcount and hiring signals
signalpublic valuesourcediligence gap
Early team size15-person team in early 2025 company post/videoLovable funding blog and videoHRIS roster and contractor count
Open roles76 positions shown on careers pageLovable careersAccepted offers, planned hires and recruiting spend
LocationsStockholm, San Francisco, London, Boston and remote locationsLovable careersLegal employer, payroll, immigration and employment-law compliance by country
DepartmentsDesign, Engineering, Finance & Business Operations, Marketing, People, Product, SalesLovable careersMix of current vs future headcount and management layer
Headcount and hiring public signal trend Bar chart of public team/hiring anchors.

VII.C Senior management biographies

partially verified confidence: medium

Public sources identify Anton Osika and Fabian Hedin, but broader senior-management biographies are not public.

Evidence gaps

  • Senior management bios, employment history, reference checks and background checks.

Hidden risks

  • Insufficient public visibility into management depth below founders.

Follow-up questions

  • Provide management bios, references, background checks and key employment agreements.
Senior management roster
name or rolepublic title or signalsourcediligence gap
Anton Vincent Fredrik Palfi OsikaCEO of Lovable Labs Sweden AB; cofounder/CEO publicly referencedRatsit; Accel; Lovable videoEmployment agreement, board role, equity and key-person plan
Fabian HedinCofounder publicly referenced by Accel/company materialsAccel; Lovable blogCurrent title, responsibilities, employment agreement and equity
Board / investor representativesNot fully public; lead investors publicly namedFunding announcementsBoard minutes, observer rights and consent rights
Functional leadersCareers page implies scaling leadership needs across functionsCareers pageActual org chart and leadership biographies

VII.D Compensation arrangements

not publicly verifiable confidence: medium

Compensation arrangements and benefits are not public beyond general careers-page benefit language.

Evidence gaps

  • Employment agreements, comp bands, bonus plans, severance and benefits documents.

Hidden risks

  • Misaligned comp or key-person arrangements could impair retention.

Follow-up questions

  • Provide key employment agreements, compensation bands, bonus plans and benefits summary.

VII.E Incentive stock plans

not publicly verifiable confidence: high

Equity incentive plans are not public.

Evidence gaps

  • Equity plan, grants, vesting schedules, 409A, exercise data and option-pool utilization.

Hidden risks

  • Option-pool refreshes can dilute investors and retention risk may rise if grants are underwater or uneven.

Follow-up questions

  • Provide equity plan, cap table, grant ledger, vesting and 409A history.

VII.F Significant employee relations problems, past or present

not publicly verifiable confidence: medium

No public employee-relations issues were identified in reviewed sources, but absence is not verifiable without HR/legal records.

Evidence gaps

  • HR claims, investigations, complaints, training, works-council/labor matters and settlement agreements.

Hidden risks

  • Rapid hiring across jurisdictions increases employment-compliance risk.

Follow-up questions

  • Provide employee-relations claims schedule, investigations and employment-compliance review.

VII.G Personnel Turnover

not publicly verifiable confidence: high

Turnover data for the last two years is not public.

Evidence gaps

  • Two-year attrition, regretted loss, termination reasons, engagement surveys and retention plans.

Hidden risks

  • High attrition could be masked by high hiring velocity.

Follow-up questions

  • Provide two-year attrition/regretted-loss data and retention plan.
Departures, turnover and compensation gaps
topicpublic signalverification statusdiligence request
Turnover by function/locationNo turnover table found in public sources reviewednot_publicly_verifiableProvide two-year attrition, regretted loss and exit interview themes
Compensation arrangementsCareers page references equity upside and benefits, not contracts or comp bandspartially_verifiedProvide offer templates, comp bands, bonus plans and key employment agreements
Equity/incentive stock plansEquity upside referenced but plan documents not publicnot_publicly_verifiableProvide equity plan, grants, vesting, 409A and option exercise history
Employee relationsNo public employee-relations disputes found in reviewed sourcesnot_publicly_verifiableProvide HR claims, investigations, works-council/labor matters and compliance training records
Chapter 08

08Legal and Related Matters

Public legal evidence includes terms/privacy/security pages, trademark filings and a trademark lawsuit that appears dismissed with prejudice; legal, regulatory, insurance, contract, IP and security artifacts still require counsel/data-room review.

VIII.A Pending lawsuits against the Company

partially verified confidence: medium

The only identified public litigation against Lovable Labs in this run is the Lovably trademark matter, which appears dismissed with prejudice as to Lovable Labs Inc. in April 2026.

Evidence gaps

  • Complete docket, settlement agreement, counsel litigation schedule and insurance notice.

Hidden risks

  • Settlement terms, covenants or residual trademark obligations may be private.

Follow-up questions

  • Provide counsel letter, complete docket, settlement and litigation schedule.
Legal matters against the company
case or mattercourt or forumfiled or status datepublic statusdiligence note
Lovably Inc. v. Lovable Labs Inc.S.D.N.Y., 1:25-cv-06614Filed 2025-08-11; dismissal filing 2026-04-06PacerMonitor mirror indicates voluntary dismissal with prejudice against Lovable Labs Inc.; Justia shows TRO/preliminary-injunction order scheduleRequest full docket, settlement and counsel confirmation
Other pending lawsuits against companyU.S./Sweden/EU searches in accessible public sourcesAs of accessed dateNo other public matters identified in this standard-depth runRequest counsel litigation schedule; run comprehensive paid docket searches

Absence of public findings is not proof of no litigation.

Legal and IP timeline Timeline of public IP filings and litigation events.

VIII.B Pending lawsuits initiated by Company

not publicly verifiable confidence: medium

No company-initiated lawsuits were identified in accessible public sources reviewed.

Evidence gaps

  • Litigation schedule, demand letters, trademark oppositions and counsel confirmation.

Hidden risks

  • Demand letters, oppositions or enforcement settlements may not be public.

Follow-up questions

  • Provide company-initiated litigation and IP enforcement schedule.
Company-initiated lawsuits
case or matterpublic evidenceverification statusdiligence request
Company-initiated lawsuitsNo public company-initiated lawsuits identified in accessible sources reviewednot_publicly_verifiableProvide litigation schedule and IP enforcement matters from counsel
IP enforcement / demand lettersNot publicnot_publicly_verifiableProvide demand letters, settlement obligations and trademark opposition history

VIII.C Environmental and employee safety issues and liabilities

not publicly verifiable confidence: low

As a software company, environmental/safety exposure appears limited publicly, but workplace safety, remote-work and employment compliance are private.

Evidence gaps

  • Workplace safety policies, employment compliance, office leases and incident logs.

Hidden risks

  • Multi-location hiring can create occupational health, remote-work and employment-law obligations.

Follow-up questions

  • Provide workplace safety policies, office lease/insurance details and employment compliance review.

VIII.D Material patents, copyrights, licenses, and trademarks

partially verified confidence: medium

Public trademark filings exist in the U.S. and EU; patents, copyrights, open-source licenses and IP assignments require legal diligence.

Evidence gaps

  • Official trademark files, patent search, open-source SBOM, copyright/IP assignments and invention assignment agreements.

Hidden risks

  • Brand disputes, generated-code IP issues, open-source obligations or missing contractor assignments could impair defensibility.

Follow-up questions

  • Provide official IP docket, patent/trademark searches, open-source policy/SBOM and IP assignment chain.
Material IP assets
assetjurisdictionstatussourcediligence note
LOVABLE word/design markUnited StatesSerial 99194755; New Application; filed 2025-05-20 per JustiaJustia TrademarksPull official USPTO TSDR and ownership chain
Lovable markEuropean UnionEUTM application 019173396; registered; filed 2025-04-15 per TrademarkElite mirrorTrademarkElite EU mirrorPull official EUIPO file and oppositions
PatentsGlobalNo confirmed patent family found in this standard-depth public reviewPublic search not exhaustiveRun official Espacenet/WIPO/USPTO/PRV patent searches
Generated code/customer data rightsContractualTerms state no transfer of customer data or AI output ownership to Lovable but disclaim output uniqueness/rights-free statusLovable TermsReview enterprise agreements, indemnity and open-source license processes

VIII.E Insurance coverage and material exposures

not publicly verifiable confidence: high

Insurance coverage is not public.

Evidence gaps

  • Cyber, E&O, D&O, EPLI, IP and general liability policies, limits, retentions and claims history.

Hidden risks

  • AI output, security incident, IP/trademark and privacy claims could exceed coverage if exclusions apply.

Follow-up questions

  • Provide insurance schedule, policies, exclusions, claims history and broker loss runs.

VIII.F Material contracts

not publicly verifiable confidence: high

Material customer, supplier, model-provider, cloud, investor and enterprise terms are not public; public terms contain important AI-output disclaimers.

Evidence gaps

  • Top customer MSAs, supplier/model contracts, DPAs, SLAs, investor rights and contract schedule.

Hidden risks

  • Enterprise contracts may include indemnities, SLAs, data-processing duties or most-favored pricing not visible publicly.

Follow-up questions

  • Provide material contract schedule, top MSAs, supplier/model contracts, DPAs and SLAs.

VIII.G Regulatory agency problems

partially verified confidence: medium

No public agency enforcement was identified, while privacy/security pages show GDPR, SOC/ISO and data-processing claims requiring artifact review.

Evidence gaps

  • SOC/ISO reports, DPA, subprocessors, regulator correspondence, privacy impact assessments and incident register.

Hidden risks

  • Privacy, data-transfer, AI safety, consumer-protection or generated-code security issues could emerge after scale.

Follow-up questions

  • Provide compliance reports, DPA/subprocessors, DPIAs, incident register and regulator/counsel correspondence.
Regulatory, privacy, agency and contract exposure summary
areapublic evidenceverification statusdiligence request
Privacy/data protectionPrivacy policy references GDPR/UK GDPR/U.S. privacy laws, DPO contact and separate DPA for Business/EnterpriseverifiedProvide DPA, subprocessor list, data map, DPIA and regulator correspondence
Security/complianceTrust center lists SOC 2 Type I/II, ISO 27001:2022 and GDPR signals; reports require accesspartially_verifiedProvide SOC/ISO reports, bridge letter, exceptions and pen-test reports
AI output/customer responsibilityTerms require independent review/testing and disclaim output uniqueness/rights-free statusverifiedReview enterprise indemnities, acceptable-use controls and insurance
Regulatory/agency actionsNo public agency enforcement found in accessible sources reviewednot_publicly_verifiableCounsel letter and regulator search across relevant jurisdictions
Insurance/material contractsNot publicnot_publicly_verifiableProvide insurance policies, customer MSAs, supplier agreements and material contract schedule
Report risk heatmap Risk heatmap for top diligence risks.

Evidence

Evidence claims
IDClaimStatusSources
EC-001 CB Insights lists Lovable as a private unicorn with a $6.6B valuation, date joined 2025-07-17, Sweden/Stockholm, Enterprise Tech, and investors Accel and Hummingbird Ventures. verified high SRC-001
EC-002 Lovable publicly announced a $330M Series B at a $6.6B valuation led by CapitalG and Menlo Ventures Anthology fund. verified high SRC-002SRC-003
EC-003 Lovable publicly announced a $200M Series A at a $1.8B valuation led by Accel with participation from 20VC, byFounders, Creandum, Hummingbird, Visionaries Club and angels. verified high SRC-004SRC-005
EC-004 In February 2025 Lovable claimed $15M added funding led by Creandum and reported $17M ARR, 30,000+ paying customers, 25,000 new projects per day and 1.2M+ apps built since launch. partially verified medium SRC-006
EC-005 Accel stated Lovable launched publicly in late November 2024, had over 2.3M active users by July 2025, and was cofounded by Anton Osika and Fabian Hedin. partially verified medium SRC-005
EC-006 Lovable claimed first-year scale of 100,000+ new projects daily, 25M+ total projects, half a billion visits to Lovable-built sites/apps in six months, and 6M+ daily visits/200M+ monthly. partially verified medium SRC-002
EC-007 Lovable publicly cites enterprise usage/testimonials involving Deutsche Telekom, Zendesk, Uber AI, and other unnamed large enterprises. partially verified medium SRC-002SRC-021
EC-008 Lovable product documentation says it builds production-grade web applications from natural language, including frontend, backend, database, authentication, integrations and editable code that can sync to GitHub. verified high SRC-007SRC-009
EC-009 Lovable has a native Supabase integration that provides a hosted PostgreSQL database, authentication, storage and serverless functions for generated apps. verified high SRC-010
EC-010 Lovable publicly lists Free, Pro, Business and Enterprise pricing tiers, including Pro at $25/month and Business at $50/month shared across unlimited users under annual billing, plus Enterprise platform-fee pricing. verified high SRC-008
EC-011 Lovable publicly claims enterprise security controls, no customer-data model training, SOC 2/ISO/GDPR trust-center signals, SSO/SAML/OIDC/SCIM, WAF controls, network isolation and encrypted data storage. partially verified medium SRC-011SRC-012
EC-012 Lovable Terms name Lovable Labs Incorporated and disclaim reliance on AI output: users must independently review and test AI output; outputs may not be unique, rights-free, accurate or suitable. verified high SRC-014
EC-013 Ratsit lists Lovable Labs Sweden AB as active in Stockholm with organisation number 559506-1739, formed 2024-10-17, registered 2024-11-21, and Anton Vincent Fredrik Palfi Osika as CEO. verified medium SRC-016
EC-014 Lovable careers page shows active hiring across Stockholm, San Francisco, London, Boston and remote locations with 76 positions across design, engineering, finance/business operations, marketing, people, product and sales. verified medium SRC-015
EC-015 Public trademark mirrors show a U.S. LOVABLE application (serial 99194755, filed 2025-05-20) and an EU LOVABLE mark (application 019173396, filed 2025-04-15, status registered). partially verified medium SRC-017SRC-018
EC-016 A trademark-related U.S. lawsuit, Lovably Inc. v. Lovable Labs Inc., was filed in S.D.N.Y. in August 2025; a PacerMonitor docket mirror shows a voluntary dismissal with prejudice against Lovable Labs Inc. on April 6, 2026. verified medium SRC-019SRC-020
EC-017 Lovable Privacy Policy states it covers Free and Pro plans, references separate Business/Enterprise terms and DPA, and says Lovable processes data under GDPR/UK GDPR and U.S./other privacy laws with a DPO contact and Stockholm EU address. verified high SRC-013
EC-018 Public competitor pages show adjacent AI coding/app-builder products from Cursor, Replit, Bolt, Vercel v0, Bubble and Webflow. verified high SRC-024SRC-025SRC-026SRC-027SRC-028SRC-029
EC-019 Lovable has active public operations: CB lists it as a unicorn, its Swedish entity is active, its careers page shows 76 roles, and its trust/blog/docs pages are live; no public IPO, acquisition or shutdown evidence was found in the sources reviewed. verified medium SRC-001SRC-002SRC-015SRC-016
EC-020 Audited financial statements, AR aging, revenue by product/customer/geography, cash/debt, forecasts, cap table, option pool, liquidation preferences and debt instruments are not publicly available in reviewed sources. not publicly verifiable high SRC-001SRC-002SRC-004SRC-006
EC-021 Revenue by customer, customer concentration, churn, NRR, cohort retention, sales pipeline and current contract status are not publicly verifiable; public materials provide logos/testimonials and usage metrics only. not publicly verifiable high SRC-002SRC-005SRC-021
EC-022 R&D roadmap, model-provider contracts, vulnerability history, product quality metrics and development costs are not public; current docs demonstrate integrations and security claims but not roadmap execution economics. not publicly verifiable medium SRC-007SRC-009SRC-010SRC-011SRC-015
EC-023 Lovable’s GTM appears product-led/self-serve plus enterprise-led: public pricing, free tier, templates/docs/community, enterprise demo motion and customer proof points are visible. verified medium SRC-002SRC-008SRC-021
EC-024 No public evidence found of pending company-initiated lawsuits, agency enforcement actions, insurance coverage or material contracts beyond public terms/privacy/security pages and the resolved Lovably matter. not publicly verifiable medium SRC-014SRC-017SRC-018SRC-019SRC-020
Sources
IDPublisherTitleAccessed
SRC-001 CB Insights The Complete List Of Unicorn Companies 2026-06-11
SRC-002 Lovable Lovable raises $330M to power the age of the builder 2026-06-11
SRC-003 CNBC Vibe coding startup Lovable's latest funding round values it at $6.6 billion, sources say 2026-06-11
SRC-004 Lovable Lovable Raises $200M, Valued at $1.8B, Just Eight Months After Launch 2026-06-11
SRC-005 Accel Accel's $200M Series A in Lovable: Enabling the Last 99% 2026-06-11
SRC-006 Lovable Announcing $15m added funding to build the last piece of software 2026-06-11
SRC-007 Lovable Documentation Welcome to Lovable - Lovable Documentation 2026-06-11
SRC-008 Lovable Lovable Pricing 2026-06-11
SRC-009 Lovable Documentation Connect to GitHub - Lovable Documentation 2026-06-11
SRC-010 Lovable Documentation Connect to Supabase - Lovable Documentation 2026-06-11
SRC-011 Lovable Security at Lovable 2026-06-11
SRC-012 Lovable / Vanta Trust Center Lovable Trust Center 2026-06-11
SRC-013 Lovable Lovable Privacy Policy 2026-06-11
SRC-014 Lovable Lovable Terms & Conditions 2026-06-11
SRC-015 Lovable Careers at Lovable 2026-06-11
SRC-016 Ratsit Lovable Labs Sweden AB i Stockholm 2026-06-11
SRC-017 Justia Trademarks LOVABLE Trademark Application of Lovable Labs Incorporated - Serial Number 99194755 2026-06-11
SRC-018 TrademarkElite Lovable EU Trademark Filing & Registration 2026-06-11
SRC-019 PacerMonitor LOVABLY INC. v. LOVABLE LABS INC. (1:25-cv-06614) 2026-06-11
SRC-020 Justia Dockets & Filings ORDER with respect to Motion for TRO for Lovably Inc. v. Lovable Labs Inc. 2026-06-11
SRC-021 Lovable Enterprise App Builder | Collaborative AI App Builder | Lovable 2026-06-11
SRC-022 Lovable Redefining Software Creation from the Heart of Stockholm 2026-06-11
SRC-023 Lovable / Lenny video page Building Lovable: $10M ARR in 60 days with 15 people | Anton Osika 2026-06-11
SRC-024 Cursor Cursor: AI coding agent 2026-06-11
SRC-025 Replit Replit AI - Turn natural language into apps and websites 2026-06-11
SRC-026 Bolt / StackBlitz Bolt AI builder: Websites, apps & prototypes 2026-06-11
SRC-027 Vercel v0 by Vercel - Build Full-Stack Web Apps with AI 2026-06-11
SRC-028 Bubble Bubble: Build web & mobile apps with the only no-code AI app builder 2026-06-11
SRC-029 Webflow Webflow: The agentic web platform for modern businesses 2026-06-11

Disclaimer

This report is a public-evidence diligence snapshot, not investment advice. Important financial, legal, technical, and contractual facts remain non-public and should be verified directly with management and primary documents before any investment decision.