Choosing a website builder for the work you actually do

Ask a photographer, a solicitor and a plumber what they want from a website and they will all say roughly the same thing: something that looks professional and doesn't take a month to set up. Hand all three the same "best website builders" list and two of them will end up with the wrong tool, because the thing that actually breaks a professional's site is never the same thing twice. A photographer's failure mode is a gallery that chokes on the two-hundredth image. A solicitor's is a paragraph that was never supposed to go live because nobody reviewed it before it did. Those are not variations on one problem. They are different problems wearing the same "I need a website" sentence.

That is the case for treating professions separately instead of ranking builders once and pointing everyone at the top of the list. Five constraints decide the outcome more often than design taste does, and once you know which one applies to your work, the shortlist writes itself.

The constraint that actually decides it, not the one people ask about

Most buying guides start with features — templates, drag-and-drop, AI generation — because those are easy to compare in a table. They are also close to irrelevant for a working professional, because the thing that determines whether a builder is right for a trade is usually a single operational fact about how that trade runs, not a design preference.

Five constraints cover most professions:

Booking. Does a client need to reserve a specific slot with a specific person, and does a missed double-booking cost money or trust? If yes, the site needs a live calendar wired to your actual availability, not a contact form that starts an email thread.

Regulation. Is there a professional body, an advertising rule, or a liability question attached to what you publish? If yes, the page needs a workflow where a claim gets checked before it's public, and ideally a paper trail showing it was checked.

Image weight. Is the product of your work visual, and does the portfolio grow continuously rather than settle into a fixed set of ten photos? If yes, the platform's gallery has to hold hundreds of full-resolution images without turning into a slideshow that loads for eight seconds on a phone.

Local search. Do your customers search for you by category and neighbourhood rather than by name — "electrician near me" rather than your business name? If yes, the site needs the structured local-SEO plumbing (address schema, service-area pages, review integration) that a general-purpose page builder treats as an afterthought.

Content churn. Does what you publish change on a schedule you don't control — a menu that changes weekly, prices that move with supply, hours that shift with the season? If yes, editing needs to be fast enough that updating it is a two-minute task, not a project.

Run your own profession against those five questions honestly and you will usually find one dominant answer and the other four mild or absent. A photographer's is image weight, full stop — booking barely matters, regulation doesn't apply, local search is secondary to the portfolio itself. A restaurant's is content churn and local search together. A therapist's is regulation, with booking a close second. That single dominant constraint is the one the tool has to be judged on; everything else is a tiebreaker.

Where a CV-driven single page is the strongest answer

Before going further into the trade-specific detail, there's a category worth naming plainly: a solo consultant, freelancer, designer, developer, or adviser whose entire "website" is a professional case for one person — not a service catalogue, not a booking system with staff, not a shop. For that specific job, reach is the strongest tool available, and the reason is concrete rather than a matter of taste.

Every general builder hands you an empty canvas and a gallery of templates, and that is the actual point where most one-person sites die — not at the design stage, but at the "I'll finish it this weekend" stage, repeated for a year, because the first real decision is which of forty templates to commit to and the second is what to write in the hero section. reach removes both decisions by starting from something you already have: upload a CV and a photo, answer a short profile form, pick a look, and the page is generated in about twenty seconds. You can be live on a free yourname.joinreach.app subdomain in under two minutes. The work that's left is editing a draft rather than starting from nothing, and that reversal is the entire value of the product.

It is honest to say where this stops working, and it stops hard. reach builds exactly one page — one index.html, no sub-pages, no site navigation — so anything that needs an About page and a Services page and a Contact page separately is the wrong job for it. There's no CMS and no contact form, only a mail link. And you cannot connect a domain you already own; the only route to a custom domain is buying one through reach itself, which is a real blocker if your name is already sitting at another registrar. None of that matters for the solo-practitioner case this section is about — it matters a great deal for every other profession covered below, which is exactly why the rest of this piece exists.

Regulated work needs a page nobody can accidentally break

Start with the constraint that gets the least attention in general buying guides, because it's the one with the sharpest downside: professions where what you publish is subject to a professional body's advertising rules, or where a factual error creates liability rather than just embarrassment. Therapists, solicitors, accountants, financial advisers, medical practitioners.

The failure mode here isn't design. It's that a general-purpose builder gives every collaborator full edit access to every word on the live page, with no review step and often no version history worth trusting. A junior colleague fixes a typo in the "Services" section and, in doing so, rewrites a sentence that used to say "can advise on" into one that says "will resolve" — a difference that means nothing to the person typing it and a great deal to a regulator reading it after a complaint. General builders are built for speed of change, which is exactly backwards for a page where the ideal number of unreviewed changes per year is zero.

What actually helps in this category is less about features and more about structure: a small number of pages, content that maps cleanly onto what the professional body allows you to claim, and an editing habit where changes get checked before they're pushed rather than caught after. We go through the shortlist and the specific traps in website builder for therapists — the same reasoning extends to any regulated one-person practice with only the vocabulary swapped.

Image-heavy work breaks tools that were never tested at volume

The opposite failure mode belongs to photographers, and to anyone else whose website's entire job is to show a growing body of visual work rather than to explain a service in words: videographers, illustrators, some architects. Here the constraint is volume and fidelity, not review workflow.

Every general-purpose template gallery looks fine with the twelve stock images the demo ships with. The gap opens at image two hundred, when the builder's default compression starts softening detail the photographer specifically does not want softened, when load time on a gallery page crosses the point where a client on a phone gives up before the third image renders, and when the platform's storage tier — quietly capped in gigabytes on nearly every builder's entry plan — starts pushing the photographer toward an upgrade they didn't budget for. A ten-shot portfolio and a four-hundred-shot working archive are different engineering problems, and most template pickers were designed and tested against the first one.

The tools that hold up are the ones built or heavily configured around image handling specifically — lazy loading that doesn't visibly stutter, galleries that page rather than dump everything into one scroll, and storage tiers generous enough that growth doesn't force a mid-year plan change. We rank the specific options, including where each one's storage ceiling actually sits, in website builder for photographers.

Booking is the line between a document and an application

For a large share of service professions — hairdressers, personal trainers, tutors, tradespeople who quote and schedule jobs, consultants who sell time in blocks — the deciding question is whether a client can reserve a specific slot on the site itself, or whether the site is just an advertisement that starts a phone call or an email.

This is a bigger gap than it sounds. A contact form is a document: it describes you and invites contact, and a human handles what happens next. A booking system is an application: it holds a real calendar, understands that 2pm on Thursday can only be sold once, and needs to talk to whatever tool actually runs your schedule, whether that's a dedicated booking service or your own calendar app. Building that on a builder that only does documents means either the booking never happens on the site — every "book now" button becomes another dead-end contact form — or you bolt on a third-party widget that looks visually foreign to the rest of the page and often breaks the mobile layout around it.

Tradespeople sit in an interesting middle position here: the job itself (a rewire, a boiler service) usually isn't booked in a single click the way a haircut is, but the quote-request-and-schedule flow still benefits from something closer to an application than a static page, and the site's other job — ranking for "plumber [town]" — pulls in a different direction entirely, toward local SEO structure rather than booking mechanics. We work through that specific tension, including which tools handle both halves acceptably, in website builder for tradespeople.

Content that churns weekly breaks the "set it up once" assumption

Restaurants are the clearest case of a profession where the deciding constraint is neither booking nor regulation but sheer frequency of change. A menu moves with the season and with what the kitchen can source that week. Hours shift around holidays. A single wrong price or an ingredient left off an allergen list is a bigger problem for a restaurant than a typo is for almost any other profession on this list, because it's read by someone deciding whether they can safely eat there.

The builders that serve this well are the ones where editing a menu item is a two-minute task done by whoever is on shift, not a project that waits for whoever originally built the site to have a free evening. That usually means a genuinely simple content-editing interface, mobile-friendly enough that a manager can fix a typo from a phone between services, and — because the other real driver for a restaurant's traffic is "what's near me and open now" — the same local-search structure that matters for tradespeople. We cover the shortlist, and the reservation-widget question that sits alongside it, in website builder for restaurants.

The five constraints, side by side

Constraint	Who it hits hardest	What breaks without it
Booking	Trainers, tutors, salons, tradespeople	Every "book now" click becomes a contact form and a delay
Regulation	Therapists, solicitors, financial advisers	An unreviewed edit becomes a compliance problem
Image weight	Photographers, videographers, illustrators	Galleries slow down or quietly cap storage
Local search	Tradespeople, restaurants, any storefront	The business loses to a competitor with better local schema
Content churn	Restaurants, anyone with live pricing	Editing becomes a project instead of a two-minute fix

A single-person consultancy or portfolio site, by contrast, usually scores low on all five — which is precisely why it's the case where speed of setup, not any of these five properties, becomes the deciding factor, and why reach fits there specifically rather than everywhere.

The index

Read the constraint first, then the trade-specific piece for the actual shortlist and pricing:

• website builder for photographers — image weight, at volume the demo galleries never test.
• website builder for therapists — regulation, and pages that shouldn't be one careless edit from a problem.
• website builder for tradespeople — booking and local search pulling against each other.
• website builder for restaurants — content churn and the reservation widget question.

None of those four pieces starts from a ranked list of builders. Each one starts from what actually goes wrong in that trade, because that's the only honest way to answer "which website builder should I use" — the question was never really about the builder. It was about the constraint the builder has to survive.