Squarespace Layoffs: What 300 Job Cuts Mean
Squarespace is cutting about 300 jobs, mostly in product and engineering. Here’s what the layoffs reveal about private ownership, AI and website builders.
Squarespace's 300 Job Cuts Point to a Wider Change in Website Building
Squarespace is cutting about 300 jobs, around 19% of its workforce, roughly two years after private equity firm Permira took the website builder private. Most of the reductions are in product and engineering, according to a companywide memo from CEO Anthony Casalena. The company had about 1,800 employees worldwide.
A layoff of this size is a big deal for employees. It's also a window into the pressure on established software companies: Squarespace is trying to simplify how it's organized and move faster, while the market around it is changing - especially as AI tools make it easier to create websites and as search and discovery get reshaped. The company hasn't said AI caused the cuts, so it wouldn't be accurate to treat that as the explanation.
The more useful questions are what the restructuring signals about Squarespace's priorities, what private ownership changes (and doesn't), and whether customers should tweak how they evaluate the platform. This article sticks to what's clearly reported, notes what's still uncertain, and then lays out a practical way to think about what it could mean for users and the broader website-builder market.
What happened at Squarespace?
Squarespace is laying off about 300 employees - about 19% of a workforce of roughly 1,800. The cuts are concentrated in product and engineering, according to a memo from Casalena reported by Business Insider. That concentration matters, but it doesn't automatically tell you what will change in day-to-day product work. The company hasn't said which specific projects or functions will be affected.
Casalena described the change as moving toward smaller teams, more "player-coaches," and a simpler organizational structure. A company spokesperson said the goal was to simplify operations, sharpen priorities, and help Squarespace move faster. Those are stated goals, not proof that the new setup will translate into better products or quicker decisions.
The reported severance package includes at least 16 weeks of base pay, with extra weeks tied to tenure. Benefits are expected to continue through May 2027. Employees leaving the company can keep their company laptops, and the company will continue supporting workers on work visas. After the memo, Casalena addressed remaining staff in a livestream reported to have lasted about a minute, with comments disabled. A separate all-hands meeting was planned.
The layoffs also line up with a major ownership change. Permira agreed to acquire Squarespace for $6.9 billion in May 2024. The deal closed in October at a reported valuation of about $7.2 billion, taking the company off the New York Stock Exchange after about three years as a public company. This happens roughly two years after it became private.
What the numbers do - and do not - tell us
A 19% cut shows the scale, but it doesn't clarify Squarespace's financial situation, expected savings, or how big individual teams might become after the reorg. The company hasn't tied the layoffs to a specific performance target or named the product areas that will change.
For employees, the immediate questions are job loss and the terms of departure. For customers, it's more operational: will the changes affect support, product development, or the reliability of the services the business relies on? The announcement alone doesn't answer that. You'll likely learn more from subsequent product updates, how quickly support responds, and whether Squarespace keeps its roadmap moving.
Why do the layoffs matter for Squarespace's strategy?
Squarespace is a mature software company, not a startup testing whether people want a website builder. Casalena founded it in 2004, and it grew around drag-and-drop templates for websites, online stores, and booking pages. The company's challenge now is keeping the product useful and competitive as the cost - and expectations - of building a basic online presence keep shifting.
That's not a small task. A platform with a large set of features has to keep existing functions working, support different kinds of customers, and still invest in improvements without making the product harder to use. Smaller teams can reduce coordination overhead and make priorities clearer. They can also reduce overall capacity, concentrate decisions, and leave fewer people to maintain existing systems. Which effect dominates will depend on execution, not on the phrase "simplification."
Private ownership changes the incentives, too. Public companies report to investors on a schedule and face constant market scrutiny. Being private changes the reporting environment, but it doesn't remove the need to grow sustainably and control costs. A workforce reduction could be part of resetting costs or reorganizing teams, but the reporting available doesn't establish Permira's role in the decision or the exact financial rationale behind it.
The trade-off behind smaller teams
Smaller teams work best when leaders set clear priorities and give teams enough authority to make decisions. They can backfire if the workload stays the same while headcount drops. In that case, what looks like "efficiency" can show up later as slower delivery, more incidents, less experimentation, or a backlog of maintenance work.
If you want a way to judge the restructuring, watch for three areas:
- Priority clarity: Does Squarespace say what it's investing in and what it's moving away from?
- Delivery quality: Do meaningful improvements keep coming without more bugs, regressions, or disruption?
- Customer-facing capacity: Can users still get timely help, especially for payments, domains, and business-critical pages?
This is a better test than assuming layoffs automatically make a company either more efficient or less reliable. Headcount changes are an input. The outcomes - what users experience and what the product delivers - are what matter.
Are AI and market changes driving the cuts?
Squarespace has been adding AI features. Its Blueprint tool can generate websites and help write copy for sites, blog posts, and product descriptions. Meanwhile, the broader market is moving too: AI website generators can make basic site creation faster and cheaper, and chatbots may answer questions that previously sent people to search results and small business websites.
Those kinds of shifts put real pressure on website builders. If a basic site can be assembled with less manual work, a template library alone may be less differentiating. Platforms may have to compete on more than design - commerce, scheduling, payments, integrations, analytics, ease of use, and the reliability of the overall business workflow. That's a general industry point, not proof that Squarespace is responding in each of those areas.
It's also important to separate context from cause. Squarespace didn't link the layoffs to AI, and neither did The Verge in the reporting referenced here. The company's explanation was that it needs to adapt its operating model, including smaller teams and a simpler structure. AI could be part of the broader competitive environment influencing decisions - but the reporting available doesn't show that automation replaced the roles being cut.
Why AI doesn't explain every workforce reduction
Reorganizations often happen alongside technological change, but timing alone isn't evidence of causation. To make the AI story stick, you'd need specifics like what tasks are being automated, whether teams are being consolidated, what capabilities are being added, and how the work is expected to change. Those details haven't been provided here.
The same applies across the software industry. For example, Dropbox was also reported to be reducing staff, but another company's cuts don't prove a shared cause. Businesses reduce headcount for many reasons - cost targets, leadership changes, shifts in product strategy, or efforts to remove layers of management. More than one factor can be in play, and public announcements rarely include the full picture.
For customers and workers, the practical question isn't just whether AI is involved. It's whether the product still solves real problems better than alternatives, and whether the organization has the capability to deliver on that promise. Pay attention to what the company builds and how the service behaves, rather than treating a cause the company hasn't confirmed as settled.
What should Squarespace customers do now?
The layoffs don't, by themselves, mean Squarespace is shutting down or that customers need to migrate immediately. Moving a website has real costs: rebuilding pages, checking redirects, reconnecting commerce or booking tools, updating domain settings, and testing the result. A rushed move based only on a workforce announcement can introduce more risk than it removes.
That doesn't mean you should ignore the news. If your site supports revenue, bookings, leads, or any core business process, treat the platform like a real dependency and maintain a reasonable exit plan. That's basic risk management for any hosted service, whether the provider has announced layoffs or not.
A practical platform-risk checklist
- Keep an independent copy of important content. Preserve text, images, product details, and key page information in formats you can access outside the platform. Confirm what can be exported and what may need to be copied manually.
- Know who controls the domain. Record the registrar, account owner, renewal date, and access credentials. Losing access to the domain can cause more immediate damage than changing website software.
- Map critical dependencies. List services tied to the site - payment processing, email marketing, booking systems, analytics. Note who owns each account and how you'd reconnect them elsewhere.
- Check the support path. Identify how to reach support and what account details you'd need if a business-critical issue happened. Do this before an incident, not during one.
- Review the product against your actual needs. Track whether features you rely on are maintained and whether the roadmap still fits your business. Don't treat a feature announcement as proof of long-term product quality.
- Estimate migration effort before you need it. A simple brochure site and a store with products, subscriptions, and integrations won't have the same switching cost. Make a rough inventory so you can decide calmly if circumstances change.
When a switch makes sense
Consider moving if you have a concrete reason: persistent support issues, a missing capability that blocks growth, costs that are no longer acceptable, or repeated reliability problems. Compare the total operating cost, not just the monthly subscription. Factor in migration work, ongoing maintenance, transaction fees, integrations, and the time your team will spend managing the new setup.
If the platform still meets your needs, a backup plan may be enough for now. If your site is central to your business and the platform no longer fits, start evaluating alternatives before a crisis forces the decision. The rule is simple: respond to what you can observe about product and service performance - not speculation about what a headcount reduction might mean.
Conclusion
Squarespace is cutting about 300 jobs, with most of the reductions in product and engineering. The company says it wants a simpler organization so it can move faster. Whether that leads to sharper execution or reduces the capacity to maintain and improve the product will show up in what customers experience next.
These layoffs come amid private ownership and a shifting website-building market. But the reporting available doesn't establish that AI caused the cuts. For customers, the sensible approach is neither panic nor complacency: keep control of your content and domain, understand your dependencies, and judge the platform based on reliability, support, and whether it still fits your needs. If you're going to change platforms, let the evidence drive the decision - not the speculation that a headline invites.