Wix, Squarespace or custom: when a builder beats a custom site
Wix or Squarespace versus a custom site for a local business, from a one-person AI agency's view: what each does well, budget, editing, moving, who each suits.
A hairdresser with one chair and a busy diary asks a local designer for a website. She wants her prices, a few photos of her work and a way to book. She also wants to change the prices herself when she puts them up in January, without calling anyone.
The designer builds custom sites with an AI agent, and could build her something lovely. But halfway through the first call he wonders whether the honest answer is Wix.
Sometimes it is. A website builder such as Wix or Squarespace beats a custom site when the owner wants to edit it themselves, the needs are simple, and a monthly subscription suits them better than paying for a build and a care plan. A custom site wins when the business needs something the builder does badly, wants ordinary files it can take anywhere, or will have someone looking after the site. This comparison sets the two side by side, fairly, so you can say which fits before anyone signs.
Features below were read from each company's own pages. Prices change, so budget is described in rough terms only.
Builder or custom at a glance
| What matters | Wix or Squarespace | Custom site |
|---|---|---|
| Rough budget | A monthly subscription the owner pays, often tens of dollars a month | A larger build fee up front, then hosting and any care plan |
| Who makes small changes | The owner, in the builder's editor | You, on a care plan, or the owner if you set up an easy way to edit |
| Hosting, security and updates | Handled by the platform | Handled by you or the host you choose |
| Bookings, shop, forms | Built in or added from the platform's apps | Added by you, from services you choose |
| Unusual features | Limited to what the platform allows | Whatever you can build and look after |
| Moving the site later | Wix: can't be moved to another host. Squarespace: partial export of content | Ordinary files you can move |
| Who it suits | Owners who want to do it themselves on a small budget | Owners who want help, or need something specific |
What do Wix and Squarespace do well?
Plenty, and it's worth saying so plainly to a client.
The owner can change things. Both builders are made for people who aren't developers. Changing a price, swapping a photo or adding a notice about holiday hours takes minutes, without waiting for anyone. For many small businesses that independence matters more than anything else on this list.
The technical work is done for them. Hosting, security certificates and software updates are the platform's job. Nobody has to remember to update anything.
Common features are built in. Booking, simple online shops, forms, galleries and blogs are part of the product or a few clicks away. For a hairdresser, a café or a yoga studio, that often covers everything.
One bill. The owner pays one subscription, directly, and knows what it costs.
They work with designers. Both companies have programmes for people who build sites for clients. Wix describes Wix Studio as its web platform built for agencies. Squarespace has a partner programme, Squarespace Circle, for people who build Squarespace sites for others, with benefits such as priority support. So "builder" doesn't have to mean "no designer". You can design and set up the site on the builder, hand it over, and stay on for help.
Where do builders fall short?
Three places.
Moving away. Wix's help centre is direct about it: a Wix site is built with Wix's own technology and needs to be hosted and run on Wix to work properly, so it can't be moved to another host. It also says the content built on Wix belongs to the owner. In practice, leaving Wix means rebuilding the site somewhere else, using the owner's text and photos.
Squarespace offers more, but not everything. Its help centre describes an export to a file in WordPress format that includes basic pages, one blog with its posts, text and image blocks. Other page types, style settings and custom code don't export. Moving away still means rebuilding the design.
Neither is a reason to avoid them. It's a reason to say it before the owner chooses, and to make sure the account is in the owner's name from day one.
Unusual needs. A builder does what the platform allows. If a business needs a particular booking rule, a connection to its own stock system or a page that behaves in an unusual way, you'll spend your time working around the builder instead of building.
Growing past the template. Many small sites never need more than a builder. Some do, and when they do, the rebuild is the same work as leaving.
When does a custom site make more sense?
When at least one of these is true:
- The business needs something specific that a builder does badly, and it matters to how they make money.
- The owner wants files they can take anywhere. A custom site built as ordinary files can move to any host, and the owner can hand it to another designer.
- Someone is looking after it. If the owner would rather send you a message than log in to an editor, a custom site on a care plan fits the way they already work.
- Speed and control matter. A small custom site can be very light and quick to load, because it only contains what it needs.
A custom site today doesn't have to mean a long, expensive build. Many designers now build with an AI agent and spend their time on the brief, the review and the handover. Webflow vs Framer compares that way of working with two designer-focused builders.
The trade is that someone has to keep it working. Updates, backups, the security certificate, the contact form: on a builder they're the platform's job, and on a custom site they're yours or the host's. Put that in the care plan and the price.
What about AI website builders?
They sit in between: a builder that drafts the site for you from a description. They can be quick for a simple first site, and they share the same questions about editing, moving and ownership as any builder. Durable AI website builder and the 10Web review look at two of them in the same fair way.
Which should you recommend to a client?
Ask four questions on the first call.
- Who will change the site, and how often? If the answer is "me, every week", lean towards a builder.
- What does the site need to do? List it. If every item is something the builder does well, a builder is fine.
- What would happen if they wanted to leave? Say what moving away would involve for each option, in one sentence.
- Do they want help after launch? If yes, a custom site on a care plan, or a builder site with a small support plan, both work. If no, a builder they can run alone is kinder.
For the hairdresser, the answers were: herself, a few times a year; prices, photos and booking; she hadn't thought about leaving; and no, she didn't want a monthly plan. That's a builder. The designer set it up on her own account, charged for the design and setup, and showed her how to change prices. She may come back when she opens a second chair. If she does, he'll know where the site lives and who owns it.
Whose name should the account be in?
The client's, whichever path they choose. On a builder, the subscription and the domain should be in the business's name, paid by the business, with you added as a collaborator. On a custom site, the domain and the hosting account should be the client's too. Keeping client accounts in the owner's name sets out why that matters more than which tool you pick.
If most of your work is custom sites built with your agent, the page for web designers running a one-person AI agency shows how that business runs around the build, and building, reviewing and delivering client websites covers the build itself. And when the honest answer is a builder, saying so is still good business. The client remembers who told them the truth.