# The Landing Page Market's Assumptions (and Which Ones AI Is Breaking) > Source: > Published: 2026-08-17 00:00:00+00:00 Every software market is built on assumptions. As long as they hold, nobody sees them: they are the air the industry breathes. When they stop holding, the companies built on top discover their product solved a problem that no longer exists. The landing page builder market — Unbounce, Instapage, Leadpages and company — has spent fifteen years built on half a dozen assumptions. Some remain solid. Others are creaking right in front of us, and generative AI has quite a lot to do with it. This is the analysis we ran internally before building [Landing Builder](/en/landing-builder), and we think it is useful to anyone choosing a tool — or building a product — in this space. ## Assumption 1: “Building a page is hard enough to pay for an editor” This is the category’s founding assumption. In 2010 it was unquestionable: putting up a landing page required a developer, a server and several days. The drag-and-drop visual editor was a reasonable revolution. In 2026, generating a page with AI costs a prompt. Tools like v0, Lovable, or the generators baked into any builder produce a complete landing page in seconds. **The editor, as a core value proposition, is running out of ground to stand on.** Does that mean the category dies? No: it means the value migrates. When producing the page is free, what becomes scarce is everything around it: making your brand’s fifty landing pages look like they come from the same company, getting every lead into the CRM with its attribution, keeping the data GDPR-compliant, having the URL live on your domain and build SEO. The page is the commodity; the platform is the product. That is why our bet with [AI generation](/en/landing-builder/create-landing-with-ai) is not “generate anything”, but “generate on top of your brand system, with guardrails”. ## Assumption 2: “Charging per visit is an acceptable model” Almost all the big builders tier their plans by unique visitors, conversions or contacts. The implicit assumption: the customer will accept the price going up when their campaigns work. The mechanics are elegant from the vendor’s point of view. The entry plan looks affordable. The real cost shows up months later, when the campaign takes off — and by then you have dozens of landing pages, your lead history and your integrations inside the platform. The price jump arrives exactly when switching tools hurts the most. It is not an accident of the model: **it is the model**. This assumption is breaking down through knowledge: more and more buyers know that serving a cached landing page behind a CDN costs pennies, whether it gets a thousand visits or a hundred thousand. Once the customer understands that per-visit pricing reflects no real cost, they start seeing it for what it is: [a tax on their own success](/en/landing-builder/pay-per-visit-pricing). Flat-rate players turn that perception into a sales argument. ## Assumption 3: “The landing page lives outside your website” For years it did not matter that your landing pages hung off a vendor subdomain or were served as a JavaScript app Google could barely read: they were destination pages for paid traffic, and SEO was some other team’s problem. That wall has come down. The cost of paid traffic rises year after year, and companies now expect every piece of content to contribute organic rankings. A landing page on the vendor’s domain, rendered client-side, is an asset working for someone else’s domain — we already wrote about [why no-code landing pages don’t rank](/en/blog/en-why-no-code-landing-pages-dont-rank). The assumption flips: the landing page has to live on your domain, with real server-rendered HTML, or you are giving away half its value. ## Assumption 4: “The form is how you capture leads” The category’s entire model revolves around the form: it is charged for, optimized, A/B-tested. The assumption is that the user will fill in fields in exchange for something. This is the most uncomfortable assumption to question, because for now it remains mostly true. But the cracks are visible: conversational agents that qualify better than a five-field form, WhatsApp as the dominant conversion channel in many markets, embedded calendars that jump straight to the meeting. The day the form stops being the standard, the value will not be in the capture widget — it will be in the data *pipeline*: which campaign each contact is attributed to, which CRM it travels to and under what consent. Whoever builds on the form-as-widget will have a problem; whoever builds on the lead’s data will not. ## Assumption 5: “Marketing can’t touch production” The market’s founding friction: marketing needs to launch and development has a three-week backlog. The builder exists to sidestep that bottleneck. Coding agents are eroding this assumption from the unexpected side: marketing now *can* ask an AI for a page and deploy it. But that does not eliminate the problem — it transforms it. An organization where every campaign spawns orphaned code, with no analytics, no brand governance and nobody to maintain it, has traded a bottleneck for a debt. The question stops being “who builds my landing page?” and becomes “who governs the fifty landing pages we have already generated?”. The answer is still a platform — but one that assumes creation is cheap and governance is the expensive part. ## Assumption 6: “A US SaaS is fine for European data” For a decade, nobody asked where the leads from a form ended up. That silence is over: EU–US data transfer frameworks have spent years being struck down and rebuilt in the courts, and legal teams have learned to ask. Every landing page form is personal-data processing, and the party liable before your data-protection authority is not the tool vendor: **it is you**. For US builders this is a structural weak flank, hard to fix with a “trust center” page. For European ones it is the most boring and most effective competitive advantage there is: [European hosting, a signed DPA and full export](/en/landing-builder/landing-pages-gdpr) unblock legal and procurement before the conversation even gets to features. ## Assumption 7: “A/B testing sells (even though almost nobody can use it)” A/B testing has been the category’s star selling point for a decade. The tacit assumption: it does not matter that most customers lack the traffic to reach statistical significance — the *promise* of scientific optimization sells itself. The math is stubborn: detecting a 20% relative improvement on a 3% conversion rate takes thousands of visits per variant. Most SMBs do not have them, and a test without a sufficient sample is worse than not testing, because it dresses noise up as data. We believe this assumption breaks through honesty: that is why we published a [significance calculator](/en/landing-builder/ab-testing-calculator) that tells you, with your real numbers, whether you should be testing buttons or rewriting your value proposition. ## What to do with all this If you are choosing a tool, turn the assumptions into questions: does the price move with my success? Do the pages live on my domain? Where is my data and can I take it with me? Does the AI generate *my* brand or a generic page? The answers quickly separate products built to retain you from products built to serve you. And if you build products in this space, the lesson is more general: your market’s assumptions have an expiry date, and AI just moved it up. The time to audit them is before a competitor does it for you. At Soamee we built [Landing Builder](/en/landing-builder) betting on the side we believe wins each of these assumptions: flat-rate pricing, your domain, your data in Europe, AI with a brand system and uncomfortable truths about testing. If you want to see it in action, [ask us for a demo](/en/landing-builder#contacto).