Introduction: a layoff that is really about the whole industry
I have spent years building websites the slow way: WordPress, a page builder, real content, and real clients asking about speed, SEO, and who actually owns the site when the project ends. So when a company as established as Squarespace announces it is cutting almost a fifth of its staff, I do not skim past it. Layoffs at a website builder are never just about one company. They are a signal about where the whole business of making websites is heading.
On November 2, 2026, Squarespace confirmed it is restructuring and reducing its global workforce by approximately 19%, representing around 300 employees. The Verge first reported the cuts, and a company spokesperson confirmed them to TechCrunch. The official line was about simplifying how the company operates, sharpening its priorities, and moving faster into its next phase of growth. What the statement did not do is mention AI as a cause. That omission matters, because the context is impossible to ignore: generative AI tools that build a working website from a few lines of typed description — "vibe-coding" builders — have, in TechCrunch's words, largely upended the industry.
What Squarespace actually announced
Let us start with the facts, because this story has already been retold in ways that go further than the evidence. Squarespace is cutting about 19% of its global workforce, roughly 300 people. The statement, attributed to public relations specialist Jeff Seedman, said: "Squarespace is restructuring its organization and reducing its global workforce by approximately 19%, representing around 300 employees. The changes are intended to simplify how we operate, sharpen our priorities and enable the company to move faster as we position Squarespace for its next phase of growth."
That framing is worth quoting exactly, because it does not blame AI, the economy, or a failed product. Reporting from Business Insider, cited by Neowin and others, added detail from a memo by CEO Anthony Casalena: the reductions fell most heavily on product and engineering teams, Casalena called it one of the most difficult decisions in the company's history, and the aim is smaller teams, more "player coaches," and a simplified structure. The same reporting said affected staff would receive a minimum of 16 weeks' base pay, plus extra weeks depending on length of service, benefits continuing through May 2027, and payment of the November 20, 2026 vesting of the legacy RSU cash award where applicable.
The numbers imply a company of roughly 1,600 people before the cuts and about 1,300 after — a significant reshaping, not a trim. It comes from a company with real history: Squarespace went public in 2021 at a valuation of around $10 billion, then went private again in 2024 in a Permira deal reported at roughly $6.9 billion when agreed, closing at about $7.2 billion.
The part Squarespace did not say out loud
Here is where I want to be careful, because this is exactly where coverage of AI layoffs usually goes wrong. Squarespace did not say AI caused these cuts. Its statement does not mention AI at all. If I wrote that Squarespace "fired 300 people because of AI," I would be inventing a claim the company never made, and you should be suspicious of any article that does.
What is true is the context. TechCrunch placed the cuts against the rise of vibe-coding builders, tools that let a user describe a site in plain language and get a functional front end back with far less effort than the old template-and-drag workflow. Squarespace's own roadmap points the same way: it launched Blueprint, an AI-assisted starting-point tool, in 2024, and it is now taking signups for Forma, an upcoming AI-native platform still on a waitlist. A company does not build an AI-native platform while cutting a fifth of its workforce by accident.
The same day made the contrast sharper. SUSE, the enterprise Linux company, told staff on November 2 that about 10% of its roughly 1,900 employees would go, and its CEO explicitly cited AI and automation. Two companies, two announcements, one day — one naming AI plainly, one not naming it at all.
Why vibe-coding hit website builders first
Website building was always going to be one of the first industries AI disrupted. A website is one of the few products where the gap between "I can describe what I want" and "here is a working version" is now small enough for a machine to cross. A prompt like "a booking site for a yoga studio with class times, prices, and a contact form" used to be the start of a two-week project. Now it is the start of a two-minute generation. The result is not always good, and it is rarely finished, but it exists — and "exists" is powerful when a small business owner is comparing it with a quote for a custom build.
The money followed the same logic. Wix bought Base44, an AI website builder, for $80 million. Lovable raised a $400 million Series C round at a reported $13.3 billion valuation. Google launched Stitch, a tool for quickly generating user interface designs. When a rival can hand a new user a working site in minutes, the old pitch — pick a beautiful template, spend a weekend customising it — starts to sound slow, however good the templates are.
I have tested enough of these tools to say this honestly: the generated site is usually the easy 80%. It looks fine on a laptop, the sections are in the right order, and the demo content reads plausibly. The hard 20% is everything a real business actually needs — real copy that says something true, real photos, booking logic that matches how the business works, SEO that brings in traffic from search, speed on a bad mobile connection, and a way to change things six months later without starting over. That hard 20% is where professional builders still earn their money. But the easy 80% used to be billable work too, and its disappearance is exactly why a company like Squarespace needs fewer people building the old way.
What this means if you build on WordPress and Elementor
Does the Squarespace news threaten WordPress users, or vindicate us? My answer is both — and the balance depends on how we respond.
First, the vindication. WordPress's great strength has always been ownership. Your site is your database, your files, your hosting choice, and your export path. If a page builder changes direction, you can change builders. If a host raises prices, you can move hosts. That portability is the opposite of a closed builder, where leaving often means rebuilding. In a world where platforms restructure and pivot to AI-native products, portability is risk management, not a nerdy technical preference.
Second, the threat. WordPress is not immune to vibe-coding. The same tools that generate a Squarespace-style site can generate a WordPress theme or landing page, and WordPress itself is moving toward AI agents — we covered the plan to bring MCP, the Model Context Protocol, into WordPress core, which would let AI agents work inside WordPress sites directly. The question is not whether AI comes to WordPress. It already has. The question is whether WordPress uses AI to make its users more capable, or turns into just another prompt box with a database attached.
Third, the opportunity. The builders who survive this shift will be the ones who sell the hard 20%: strategy, real content, performance, accessibility, SEO, integrations, and maintenance. A prompt can generate a hero section. It cannot interview a client, understand why their bookings drop on Tuesdays, or fix a checkout that loses orders on mobile. Those are human jobs, and they are the jobs clients remember paying for.
The practical lessons I am taking from this
Own your export path. Whatever platform you build on, know how you would leave it, and test that path before you need it. On WordPress, that means regular full backups you have actually restored somewhere. A platform's roadmap is not a promise; its export tool is the closest thing to one.
Sell outcomes, not pages. When a client can generate ten pages in an afternoon, "I built you ten pages" stops being a selling point. "Your bookings went up, your site loads in under two seconds, and you rank for the searches your customers actually type" still is.
Learn the AI tools instead of fearing them. I use AI in my workflow now — for first drafts, boilerplate code, and summarising long documentation — and then I check, edit, and take responsibility for the result. The builders who refuse AI entirely will be slower than the ones who use it well. The builders who paste AI output unchecked will be worse than both.
Watch Forma, not just the layoffs. Squarespace's next platform matters more than its last headcount. If Forma ships as a genuinely good AI-native builder, it will raise the bar for every WordPress AI feature. If it ships as a thin prompt wrapper, it will tell us that even the incumbents are struggling to turn generation into a product.
And keep perspective. Three hundred people losing their jobs is a human story before it is a market story. The severance terms reported — a minimum of 16 weeks' pay, benefits through May 2027 — are better than many layoffs in this industry, but that does not make the event good news.
What to watch next
Three things will tell us whether this was a smart restructuring or the start of a harder story: the Forma launch and whether existing users move to it; whether other closed builders follow with their own cuts or AI-native relaunches — Wix, with Base44 already in hand, is the obvious one to watch; and whether WordPress's own AI moves, including MCP in core, give independent builders the same generative speed without giving up ownership. If WordPress gets that combination right, the Squarespace story becomes an argument for open platforms.
Conclusion
Squarespace cutting about 19% of its workforce, roughly 300 people, is not proof that AI has replaced website builders, and it is not proof that it has not. It is proof that the website-building industry has changed fast enough that one of its biggest names is rebuilding itself around smaller teams and an AI-native product, while being careful not to say the quiet part out loud. For WordPress and Elementor users, the lesson is not panic and it is not smugness. It is ownership, outcomes, and honest use of the new tools. The easy 80% of building a website is now cheap. The hard 20% — the part that makes a site actually work for a real business — is more valuable than ever, and it is still, for now, a human job. Build for that, keep your export path open, and watch what Forma does next.
Frequently asked questions
Did Squarespace blame AI for the layoffs?
No. Its statement described a restructuring to simplify operations, sharpen priorities, and move faster. It did not mention AI as a cause. The AI context comes from TechCrunch's reporting on vibe-coding builders and from Squarespace's own AI products, Blueprint and the upcoming Forma platform.
How many people are affected by the Squarespace layoffs?
About 300 employees, approximately 19% of Squarespace's global workforce, according to the company's confirmation to TechCrunch. Reporting suggests the cuts fell most heavily on product and engineering teams.
What is vibe-coding, and why does it matter for website builders?
Vibe-coding means describing what you want in plain language and letting an AI generate a working front end from that description. It matters because it collapses the time and skill needed for the first version of a website, which pressures traditional template-based builders to change how they work.
What is Squarespace Forma?
Forma is Squarespace's upcoming AI-native platform, currently on a waitlist. It follows Blueprint, its AI-assisted starting-point tool launched in 2024. Forma's launch will show how seriously Squarespace is betting on AI-generated site building.
Should WordPress users worry about vibe-coding?
Not panic, but pay attention. AI can now generate WordPress themes and layouts too, and WordPress core is moving toward AI agent support. WordPress's advantage is ownership and portability: you control your content, hosting, and export path in a way closed-builder users do not.
What should freelance web builders do after this news?
Focus on the work AI cannot fake: strategy, real content, performance, SEO, accessibility, integrations, and maintenance. Own your export path, measure outcomes for clients, and use AI tools with human review rather than ignoring them or pasting their output unchecked.
