We read 753 live acquisition listings for named no-code tooling. The headline discount is mostly a composition artifact. Inside SaaS, no-code is priced better per dollar of revenue and hits a lower ceiling.
The question turns up every time someone chooses a stack. If I build this on Bubble or Webflow, or let an AI builder write it, will anyone buy it later? The usual answer is a confident no, delivered by people who write code for a living and have never looked at a sale.
We can look. Our acquisitions corpus holds 800+ live software listings with disclosed revenue, profit and multiples, and the listing text names the stack often enough to split the population. Across 753 listings with a usable profit multiple, 83 name no-code or low-code tooling somewhere in their description or stack field. For the wider picture of what is listed and at what price, see the state of SaaS acquisitions and our SaaS valuation guide.
The uncontrolled comparison says no-code sells at 3.00x profit against 3.50x, a 14% discount. We do not think that number should be quoted, including by us, because most of it disappears the moment you control for what kind of business it is. The controlled answer is more interesting and more useful, and it is not a discount story at all.
A listing is classified as no-code when its description or stack field names a no-code, low-code or AI-builder tool. The match set is Bubble, Webflow, WordPress, Squarespace, Wix, Framer, Softr, Glide, Adalo, FlutterFlow, Airtable, Zapier, Make, n8n, Lovable, Bolt, v0, Replit Agent, plus the literal phrases no-code, nocode and low-code.
This is a disclosure measure, not a technical audit. It tells you what the seller chose to write down. A business built on Bubble whose listing never mentions it is counted as code here, which means our no-code group is a floor and every gap we measure is conservative in the same direction.
Two terms recur. Profit multiple is asking price divided by trailing twelve-month profit. Revenue multiple is asking price divided by trailing twelve-month revenue. Both are asking prices, not closing prices, which matters and which we return to in the limits.
The stack decision is made at the start and the resale consequence lands years later, so almost nobody who answers the question has observed both ends of it. The people most confident that no-code kills resale value are engineers, and the people most confident it does not are selling no-code courses.
The 2026 version of the question is sharper because AI builders moved the debate. The founder communities during our capture window carried “Vibe coding is making software worse, and I think the market is going to correct itself hard” from r/SaaS, and “I’m fixing vibe-coded apps while everyone else is still busy laughing” from r/EntrepreneurRideAlong, alongside “Security holes I find in almost every vibecoded app”. Every one of those is a claim about durability, which is exactly what a multiple prices. We looked at the revenue side of that debate separately in do vibe-coded apps make money and vibe coding problems and how to fix them.
We checked what currently ranks for this question before writing. Every result on the first page is a Bubble-versus-Webflow tool comparison, several of them published by the platforms themselves or by agencies that build on them. Not one page answers what a business built on those tools sells for.
The reason is structural and worth naming, because it is the same reason our plugin ecosystem comparison had no competition either. The only parties motivated to write about a no-code platform are the platform and its agencies, and neither has access to acquisition data, the way a listings corpus does, nor an incentive to publish it if the answer were unflattering. A cross-ecosystem resale comparison is a category of content the incumbents cannot produce.
We took every live listing with a profit multiple between 0.1x and 15x and trailing revenue above zero, which gives 753 listings. We searched the full description text and the structured stack field for the tool names above, giving 83 no-code listings and 670 without a marker.
We then repeated every comparison inside single categories, because the corpus mixes SaaS, mobile, agency, ecommerce and content businesses that trade at very different multiples for reasons that have nothing to do with tooling. That control is the whole methodological point of this page and it changes the headline.
All figures are medians. Sample sizes are printed in every table, and we decline to draw conclusions from buckets holding fewer than about 15 listings, of which there are several and which we report as gaps rather than hide.
| Group | Listings | Median profit multiple | Median revenue multiple | Median TTM revenue | Median margin |
|---|---|---|---|---|---|
| Names no-code tooling | 83 | 3.00x | 2.00x | $68,000 | 72.6% |
| No marker | 670 | 3.50x | 1.90x | $126,500 | 62.5% |
Read straight, that says no-code carries a 14% profit-multiple discount and half the revenue. It is the number we expected to publish, and it is the number almost any analysis of this corpus would produce, because it is what the data says before you ask what kind of businesses are in each group.
No-code tooling is not distributed evenly across business types. It is concentrated in agencies and in marketing sites, which trade at low multiples regardless of how they were built. Of the 83 no-code listings, 16 are agencies and only 47 are SaaS.
Agencies in this corpus carry a 3.00x median profit multiple against 3.80x for SaaS, before tooling enters the picture at all. So a group that is disproportionately agency will look discounted even if no buyer has ever thought about Webflow. This is the same composition artifact we caught in what transfers when you sell a SaaS, where an apparent 57% premium inverted entirely once the comparison was restricted to one category.
The rule we now apply, and would ask anyone quoting these figures to apply: never compare multiples across a mixed corpus when the thing you are testing is correlated with business type. Control first, then look.
| Category | Group | n | Profit multiple | Revenue multiple | Median TTM revenue | Median margin |
|---|---|---|---|---|---|---|
| SaaS startup | No marker | 294 | 3.80x | 2.20x | $101,000 | 68.9% |
| SaaS startup | No-code named | 47 | 3.60x | 2.80x | $61,000 | 78.9% |
| Agency startup | No marker | 73 | 3.00x | 1.10x | $379,000 | 43.8% |
| Agency startup | No-code named | 16 | 2.15x | 1.15x | $310,500 | 52.8% |
| AI startup | No marker | 34 | 4.35x | 2.55x | $89,000 | 57.4% |
| Ecommerce startup | No marker | 63 | 2.80x | 1.00x | $243,000 | 24.0% |
| Mobile startup | No marker | 97 | 3.50x | 2.00x | $75,000 | 67.3% |
Inside SaaS, the profit-multiple gap collapses from 0.50x to 0.20x. That is a 5% difference on 294 against 47 listings, and we would not want anyone to build a stack decision on it. The AI, ecommerce and mobile no-code buckets hold two, three and zero listings respectively, so they are omitted from interpretation and shown here only so the absence is visible.
The column most people would not predict is the revenue multiple. Inside SaaS, no-code listings ask 2.80x trailing revenue against 2.20x for everything else. That is a 27% premium, running in the opposite direction to the profit multiple.
Both can be true at once because the two multiples are linked by margin. A business with a higher margin converts more of each revenue dollar into profit, so pricing it at the same profit multiple automatically produces a higher revenue multiple. The revenue premium is therefore not buyers rewarding no-code. It is arithmetic following the margin.
But it is still the number that matters if you are comparing against a revenue-based rule of thumb, which most founders do. On that basis a no-code SaaS is worth more per dollar of revenue than a hand-built one, and anyone telling you otherwise has not checked. Our full multiple distributions are in SaaS valuation multiples and profit multiples by category.
Median margin inside SaaS is 78.9% for no-code listings against 68.9% for the rest, a ten-point gap. In agencies it is 52.8% against 43.8%, a nine-point gap in the same direction.
The mechanism is not mysterious. A no-code business pays a platform subscription instead of paying for engineering, infrastructure and the maintenance that surrounds them. At small scale that trade is strongly favourable, which is exactly the range these listings occupy. The revenue distribution behind that is in the state of indie SaaS revenue and revenue benchmarks by category.
It is also the trade that reverses at scale, because a platform fee that scales with usage eventually costs more than the engineer it replaced. Nothing in this corpus lets us see that crossover, because there are too few large no-code businesses in it. Which turns out to be the finding.
| Measure | No marker (n = 294) | No-code named (n = 47) |
|---|---|---|
| Median TTM revenue | $101,000 | $61,000 |
| Share clearing $100,000 revenue | 51.4% | 42.6% |
| Share clearing $500,000 revenue | 17.7% | 10.6% |
| 90th percentile revenue | $772,400 | $537,000 |
| Median profit multiple | 3.80x | 3.60x |
| Median margin | 68.9% | 78.9% |
A no-code SaaS is 40% less likely to reach half a million in trailing revenue and its 90th percentile sits 30% lower. That is where the cost actually lands. Per dollar earned it is priced almost identically. It is simply less likely to earn many dollars.
Whether the tool causes the ceiling or merely attracts founders who were going to hit one anyway is not something we can separate here, and we would be lying if we claimed otherwise. Both mechanisms are plausible and they are not mutually exclusive. The scope-and-ceiling question is measured directly in how small your MVP should be. What we can say is that the ceiling is the part worth planning around, and the multiple is not.
The one place the tooling penalty is unambiguous is agencies: 2.15x against 3.00x across 89 listings, a 28% discount, and the largest tooling gap anywhere in the corpus.
That fits what buyers of service businesses care about. An agency’s value is its client relationships and its delivery capability, which is why freelance demand and paid job postings read differently from product demand, and an agency that advertises the no-code platform it builds on is describing a capability any competitor can buy for a monthly fee. The tooling is not a moat, and naming it in the listing tells the buyer so.
For software the same logic applies with less force, because the product itself carries the customers. We covered how agencies price and what transfers inthe state of SaaS acquisitions and the due diligence checklist.
| Marker | Listings | Profit multiple | Revenue multiple | Median TTM revenue | Median margin |
|---|---|---|---|---|---|
| No marker | 668 | 3.50x | 1.90x | $126,500 | 62.4% |
| Site builder or CMS | 52 | 2.65x | 2.00x | $65,000 | 76.0% |
| Says no-code, no tool named | 19 | 3.60x | 2.70x | $56,000 | 80.4% |
| Automation or spreadsheet backend | 8 | 3.20x | 2.05x | $61,500 | 66.4% |
| AI builder named | 4 | 2.65x | 2.00x | $444,000 | 71.3% |
| Classic no-code app platform | 2 | 5.55x | 4.20x | $251,500 | 78.9% |
The only bucket large enough to interpret is site builders and CMS platforms at 52 listings, and it carries the lowest multiple in the table at 2.65x on the second-highest margin at 76.0%. That is the same signature we found for WordPress plugins inhow to sell a WordPress plugin: high margin, low multiple, which is what it looks like when buyers price durability rather than profitability.
The most newsworthy number in this analysis is a small one. Four listings out of 753 name an AI builder such as Lovable, Bolt, v0, Replit Agent or Cursor. Two name Bubble, Adalo, Glide or a similar app platform.
Given how much of the 2026 discourse assumes a coming flood of AI-built products hitting the resale market, that absence is the story. As of September 2026 it has not arrived in acquisition listings in any measurable quantity.
There are three readings and we cannot separate them, so we are giving all three rather than picking the most quotable.
Timing. AI builders became mainstream recently and a business typically needs twelve months of trailing revenue before it is listable. Products built in 2025 and 2026 may simply not be old enough to appear yet, in which case this number will change and we will re-run it.
Disclosure. Sellers may be deliberately omitting the tool, since naming it invites exactly the durability objection this article is about. Our measure is disclosure, not audit, so this is entirely possible and would mean the true count is higher.
Survival. The products may not be reaching listable revenue at all. That reading is consistent with what we measured in do vibe-coded apps make money and with the roughly half of products in our revenue corpus that have traffic and no revenue, documented in how much traffic a SaaS actually needs.
Put the margin and multiple columns together and the buyer’s position becomes legible. They can see a no-code business is more profitable today. They pay slightly less per dollar of that profit anyway. The only coherent explanation is that they are discounting how long the profit lasts.
That is a rational position rather than a prejudice. A business on a hosted platform carries risks a self-hosted one does not: pricing changes, feature deprecation, terms changes, and a migration path that is genuinely hard. The same dependency logic drives micro SaaS without API dependency and API wrapper business ideas. None of those show up in trailing profit, and all of them show up in the multiple.
It is also a much smaller discount than the engineering consensus implies. Five percent inside SaaS is a rounding error next to the 40% difference in reaching half a million in revenue.
The clean comparison for platform risk is a plugin ecosystem, where the platform relationship is total. WordPress plugin listings in our corpus carry a 2.80x median profit multiple on an 88.9% margin, the highest margin and nearly the lowest multiple of any group we have measured.
The no-code SaaS listings sit between that and hand-built software, at 3.60x on 78.9%, which is roughly where you would put them if platform dependency were the variable being priced. The ordering is consistent across three separate analyses, which is the strongest evidence we have that durability rather than tooling snobbery is what the multiple reflects. The ecosystem comparisons are in Shopify apps against WordPress plugins, how to sell a Shopify app and micro SaaS without API dependency.
Community evidence, labelled as anecdote, from public founder subreddits during our September 2026 capture and anonymized to the subreddit.
| What was posted | Source | What it maps to |
|---|---|---|
| “Vibe coding is making software worse, and I think the market is going to correct itself hard” | r/SaaS | A durability claim, which is what a multiple prices |
| “I’m fixing vibe-coded apps while everyone else is still busy laughing” | r/EntrepreneurRideAlong | A market forming around remediation cost |
| “Security holes I find in almost every vibecoded app” | r/SaaS | Diligence risk that never appears in trailing profit |
| “I launched my first SaaS two weeks ago and the code turned out to be the easy part” | r/microsaas | The build was never the constraint |
| “How I stopped building thin AI wrappers and switched to deep workflow integrations” | r/microsaas | Depth as the answer to commoditization |
| “I keep seeing posts about leaving Webflow for AI coding” | r/webflow | Migration pressure running toward code, not away |
The last one is the current top organic result for our target query, which tells you the live debate is about migrating off no-code rather than about what it is worth. That is a question about cost, and this page is the only measured answer to the question about value.
Our review corpus of 1M+ complaints across Capterra, G2 and the app stores contributes one independent point here. Across the categories we have analysed in depth, the recurring buyer complaints are cost, support, integration and reporting. None of them is about how the software was built.
End users cannot tell and do not care. That matters, because it means the durability discount is coming entirely from acquirers doing diligence, not from customers churning. A no-code product with real retention is not at risk from its users, which is consistent with the margin and revenue multiple both favouring it. We broke the complaint themes out incustomer support software limitations, the most hated software and why SaaS customers churn.
On resale grounds specifically, the answer this data supports is that it barely matters, and the engineering consensus overstates the penalty by a wide margin.
Three things follow directly from the numbers above.
Lead with margin, because it is your strongest column and it is the one that actually differs. A 78.9% median against 68.9% is a real advantage and buyers price margin directly.
Anticipate the durability objection rather than waiting for it, because it is what the multiple gap consists of. Document the migration path, the platform contract and the concentration of platform-specific logic. That converts an unpriceable unknown into a priceable one.
And be aware that naming the tool is a choice. Our own measure is disclosure-based precisely because plenty of sellers do not name it, and the 28% agency gap suggests that in some categories naming it costs real money. We are not advising anyone to conceal a material fact, and a buyer will find it in diligence regardless. The practical point is to frame it rather than let it be discovered. More on that in how to sell your SaaS and what transfers when you sell a SaaS.
| Your situation | What the data says | Action |
|---|---|---|
| Choosing a stack for a small SaaS | 5% multiple gap inside SaaS | Optimise for shipping speed, not resale |
| Aiming for a $500k+ business | 10.6% against 17.7% reach it | The ceiling is the real constraint. Plan the migration |
| Building an agency on a no-code platform | 2.15x against 3.00x | The discount is real. Build a moat that is not the tool |
| Selling a no-code SaaS now | 2.80x revenue, 78.9% margin | Lead with margin, document the migration path |
| Buying a no-code SaaS | Same price per dollar of profit | Diligence the platform contract, not the code style |
| Built with an AI builder | 4 of 753 listings | No resale precedent exists yet. Treat as unpriced |
| Benchmark | Value | Basis |
|---|---|---|
| Listings naming no-code tooling | 83 of 753 | 11.0% |
| Uncontrolled profit multiple gap | 3.00x against 3.50x | n = 83 and 670 |
| Controlled profit multiple gap, SaaS | 3.60x against 3.80x | n = 47 and 294 |
| Revenue multiple, SaaS | 2.80x against 2.20x | favours no-code |
| Median margin, SaaS | 78.9% against 68.9% | favours no-code |
| Clearing $500k revenue, SaaS | 10.6% against 17.7% | the ceiling |
| 90th percentile revenue, SaaS | $537,000 against $772,400 | the ceiling |
| Agency profit multiple gap | 2.15x against 3.00x | n = 16 and 73 |
| Site builder and CMS bucket | 2.65x on 76.0% margin | n = 52 |
| Listings naming an AI builder | 4 | of 753 |
| Listings naming a no-code app platform | 2 | of 753 |
Computed on September 21, 2026 against a live warehouse. Population is every live acquisition listing with a profit multiple between 0.1x and 15x and trailing revenue above zero, giving 753 listings. Classification searches the full listing description and the structured stack field for the tool names listed in the definition section, case-insensitively.
Every comparison is repeated within a single business category, and the controlled figures are the ones we stand behind. Medians throughout. Margin is trailing profit divided by trailing revenue, computed per listing before taking the median. Sample sizes appear in every table and buckets under roughly 15 listings are reported without interpretation.
Listings are referenced only in aggregate. No listing identifier, URL or seller-identifying detail appears anywhere on this page, and community quotes are attributed to the subreddit only.
| Source | What it contributed | Limitation |
|---|---|---|
| Acquisitions corpus (800+ live listings) | Every multiple, margin, revenue and classification figure | Asking prices, not closing prices. No time-on-market or sale-completion data. |
| Listing description and stack fields | The no-code classification itself | Disclosure, not audit. Undisclosed no-code businesses count as code, making every gap conservative. |
| Revenue intelligence corpus (8,600+ startups) | Context on how many products reach listable revenue at all | Carries no stack field, so it cannot independently confirm the no-code split. |
| Review corpus (1M+ complaints) | Evidence that end users never complain about how software was built | Reviews come from buyers of established software, so the corroboration is indirect. |
| Founder subreddit capture (September 2026) | The live durability debate and the migration-direction quote | Anecdote. Voted threads over-represent strong opinions. |
| Live search results | Confirmation that no published page answers this question | One geography, one point in time. |
The single biggest limit is that this is a disclosure measure. We are comparing businesses that mention their tooling against businesses that do not, which is not quite the same as comparing no-code against code. Both the size of our no-code group and the size of every gap are therefore floors.
The second is that the per-tool table is mostly too thin to use. Four AI-builder listings and two app-platform listings are reported because their absence is informative, not because two listings at 5.55x means anything. We would rather print the n and say so than drop the rows.
The third is causation. We cannot tell whether no-code tooling causes a lower revenue ceiling or whether founders who would hit a lower ceiling anyway are more likely to choose it. That question is not answerable with listing data and we have not pretended it is. The related survivorship traps are catalogued in common validation pitfalls and why startups fail.
The recipe is two steps. Classify listings by searching description and stack text for tool names, then compare multiples within a single business category rather than across the corpus. The second step is the one that matters, and skipping it produces the 14% headline that we do not think should be quoted.
The same listings are queryable through our tools. See getting started with the acquisitions database, using listings as market validation, reading the buyer thesis and the acquisitions MCP tools for programmatic access.
BigIdeasDB tracks 800+ live acquisition listings with disclosed revenue, profit and multiples, alongside 8,600+ revenue-verified startups and 1M+ documented complaints. Price your product against real listings rather than rules of thumb.
Open the acquisitions database →This analysis exists because we hold asking prices, revenue, profit and listing text in one place and can slice them by category. Any single broker sees their own deals; a platform sees one ecosystem. The cross-ecosystem comparison is the thing neither can produce.
For the surrounding decisions: valuation multiples and profit multiples by category cover pricing, finding acquisition targets and buying against building cover the buy side, how much traffic a SaaS needs and whether shipping more products payscover the operating decisions that get you to a listing in the first place, and how to value a SaaS business is the practical guide.
The same control that reshaped this analysis flipped another one. Seeis your SaaS an asset or a job, where banding by size reverses an apparent penalty on businesses that run without their owner.
Slightly, and much less than most people assume. Inside the SaaS category the median profit multiple is 3.60x for listings naming no-code tooling against 3.80x for the rest, a 5% gap across 47 and 294 listings. On revenue multiples no-code is actually priced higher, 2.80x against 2.20x.
Because they do not control for business type. Across the whole corpus the gap looks like 3.00x against 3.50x, a 14% discount, but no-code is concentrated in agencies and marketing sites, which trade at lower multiples regardless of tooling. Control for category and most of the gap disappears.
The revenue ceiling. Only 10.6% of no-code SaaS listings clear $500,000 in trailing revenue against 17.7% of the rest, and the 90th percentile sits at $537,000 against $772,400. Price per dollar of profit is nearly identical. The number of dollars is not.
Yes, substantially. Median margin inside SaaS is 78.9% for no-code listings against 68.9% for the rest, a ten-point gap, and in agencies it is 52.8% against 43.8%. A platform subscription is cheaper than engineering and infrastructure at the revenue scale these listings occupy.
The only bucket large enough to report is site builders and CMS platforms, which covers Webflow,WordPress, Wix and similar, at a 2.65x median profit multiple on a 76.0% margin across 52 listings. Bubble and comparable app platforms appear by name in only two listings, which is not enough to publish a figure.
Barely. Four listings out of 753 name an AI builder such as Lovable, Bolt, v0, Replit Agent orCursor. As of September 2026 the expected wave of AI-built products hitting the resale market is not visible in acquisition listings in any measurable quantity.
Three possible reasons and we cannot separate them: products built in 2025 and 2026 may not yet have the twelve months of trailing revenue a listing needs, sellers may be omitting the tool to avoid the durability objection, or the products may not be reaching listable revenue at all.
More so. Agencies naming no-code tooling carry a 2.15x median profit multiple against 3.00x for other agencies, a 28% gap across 16 and 73 listings. It is the largest tooling penalty anywhere in this corpus, because an agency whose capability is a monthly subscription has no moat.
Because a multiple prices durability, not current profit. Platform pricing changes, feature deprecation and a hard migration path are all risks that never appear in trailing profit and all appear in the multiple. It is the same signature we see in WordPress plugin listings, which carry the highest margins and nearly the lowest multiples we have measured.
On these numbers, almost certainly not. A 5% multiple gap inside SaaS is far smaller than the cost and risk of a rewrite, and you would lose the ten-point margin advantage that a profit multiple is applied to. Documenting the migration path is much cheaper than executing it.
There is no evidence they do. Across a review corpus of 1M+ complaints, the recurring themes are cost, support, integration and reporting, as catalogued in small business software pain points and the most requested features. None of them concerns how the software was built. The durability discount comes from acquirers doing diligence, not from users churning.
We cannot tell from this data, and it is the most important open question. Our corpus holds asking prices with no time-on-market or completion data, so a listing at 3.60x that never sells looks identical to one that sells at 3.60x in a week.
BigIdeasDB Research. (2026). What Does a No-Code SaaS Actually Sell For?. BigIdeasDB. Retrieved from https://bigideasdb.com/what-no-code-saas-actually-sells-for