Independent guidance for choosing, owning, and maintaining a business website No paid rankings.

WebsiteSolutions.us Menu

Decision guide

How to Choose a Website Solution for Your Small Business

Five ways to get a website, compared by who does the work and who stays responsible afterwards -- not by which is best.

Huy V., Founder and Editor Last reviewed Updated

The bottom line

There is no best approach, and anyone who names one without asking about your business is describing their own. Start from two things: who will make routine changes, and who will keep the site running afterwards. Those two answers narrow five options to about two, and the rest is comparing the two.

Best fit for
Who edits the content, who handles updates and backups, and who answers the phone when something breaks.
Avoid when
A product comparison before you have decided which kind of arrangement you are buying -- that compares things that are not alternatives.
Main tradeoff
More control and portability generally means more responsibility; less responsibility generally means more dependence on one provider or platform.

Please note: This is editorial guidance for a general audience. It is not advice about your particular business, and it is not a recommendation of any provider or product.

Evidence: Editorial assessment Last verified

"Website solution" can mean four different things. It can mean software you operate, a person you hire, a company you hire, or an ongoing service you subscribe to. They are not variations of one thing, and the most common way a website decision goes wrong is choosing a product before deciding which of those four you are actually buying.

That is why this page does not compare products. It compares arrangements, by the two questions that turn out to matter most: who makes changes, and who is responsible after launch.

Step 1: decide what customers have to be able to do

Write this down before anything else, because every later question depends on it. Separate what the site must do at launch from what it might do one day.

  • Learn about you and get in touch
  • Schedule or book an appointment
  • Request a quote
  • Buy products
  • Pay an invoice or a deposit
  • Join, or log in to something
  • Read content you update often
  • Use a workflow specific to how you work

Most of these are possible on most approaches. The reason to write them down is that one or two of them will quietly rule out a specific product later, and it is much cheaper to discover that now than after the build has started.

Step 2: decide who will operate the site

This is the question that narrows five options to two, and it is not really about technology. Someone has to do each of these after launch, and on several rows the honest default answer is nobody.

Who does what, after launch The jobs that continue once the site is live
The job If you operate it Builder or self-hosted If you hire someone Freelancer or agency If you buy a service Managed arrangement
Initial setup You Them, to your brief Them
Content entry The job most often assumed to be the provider's and most often not. You Agree it explicitly -- it is rarely included by default Usually you, at least for the words
Routine edits You You or them, as agreed Usually them, within limits
Hosting The platform, or a host you pay Whoever the agreement says Them
Software updates The platform for a builder; you for self-hosted Only if you have arranged it Them
Security and backups Nobody by default is the common answer, and the expensive one. The platform for a builder; you for self-hosted Only if you have arranged it Them
Troubleshooting You, with platform support Whoever the agreement says Them
Domain and DNS control The business should hold this in every arrangement. You You, with delegated access for them You, with delegated access for them
Analytics and Search Console You, as administrator and verified owner You, with named access for them You, with named access for them
Export and migration, if you leave You Agree what is delivered, before you need it Agree what is delivered, before you need it

A caution marks something that commonly surprises people later.

Evidence: Editorial assessment Last verified

Every row here belongs to somebody in every arrangement. Where the answer is "nobody, by default", that is not a gap in this table -- it is the thing to settle before you choose.

The rows to look hardest at are updates, security and backups. They are invisible while they are being done and expensive when they are not, and they are the jobs most often assumed to belong to whoever set the site up. On a hosted builder the platform carries them. On a self-hosted site they belong to you unless you have specifically paid somebody for them.

Step 3: compare the five approaches

The five approaches Compared by responsibility and fit, not by quality
What to compare Hosted builder A product you operate Self-hosted WordPress Software you install and run Freelancer One person you hire Agency A team you hire Managed service An ongoing arrangement, not one product
May suit you when A straightforward service site the owner wants to edit directly. Content depth or flexibility matters and maintenance is genuinely somebody's job. A defined project with one accountable specialist. A project with several workstreams or stakeholders may benefit from a provider that takes responsibility for coordination. Verify who will perform each discipline and who is accountable across them. The owner values continuing responsibility over maximum portability.
Owner responsibility Content, settings, and the subscription. Everything the host does not do: updates, plugins, backups, recovery. The brief, the content, and approving work. The brief, the decisions, and the budget. Content and the relationship; the rest is the point of the service.
Provider responsibility The platform runs the software and the hosting. Whatever you have agreed and paid for -- possibly nothing. What the agreement says. With one person, whatever is not written down has nobody else to fall back on. May cover strategy, design, development, content or other disciplines under one engagement. Verify which disciplines are actually included, who performs each part, how the work is priced, and who is accountable across them. Defined by the service terms. Read what is included before assuming.
Typical control pattern On every approach, the business should hold the domain and the core accounts. You own the platform account; helpers get collaborator access. You own the hosting account, the domain, and an administrator login. You own the accounts; the freelancer gets named access to them. You own the accounts; team members get named access. Varies most here. Ask whose account the site lives in before you start, and whether you hold it with them granted access or they hold it with you granted access. Those are not the same arrangement.
Maintenance responsibility The row most often assumed rather than agreed. The platform, for the software and hosting. You, or a person or plan you pay -- a managed WordPress host is one such arrangement. Nobody by default. Only if you have arranged it separately from the build. Only if you have arranged it separately from the build. The provider -- that is what the recurring fee buys.
Portability considerations Depends on the specific platform, host, licences and access -- never on the category. Export coverage differs sharply by platform. Run one and look at it. Files and database are usually movable; what a specific setup needs may not be. Depends entirely on the platform chosen and the access you hold. Depends entirely on the platform chosen and the access you hold. Ask what you would receive, in what format, and how quickly.
Main advantages Little to run, quick to start, one bill. Flexibility, and no single company between you and the site. One person who knows your project, usually at lower cost than a team. Potential access to several disciplines through one engagement, with continuity when the actual staffing, documentation and handoff arrangements support it. Somebody is responsible, continuously, without you arranging it.
Main limitations You work within what the platform offers. Every component is a thing that can break and needs updating. Capacity and continuity rest on one person. Higher cost, and more process than a small project may need. A recurring commitment, and dependence on that provider. If it ends, the site continues only so far as you hold the accounts and can obtain the files.
Warning conditions An export you have never run, on a site you could not rebuild. Nobody has actually agreed to do the maintenance. No written scope, and no arrangement for what happens if they are unavailable. Paying for coordination on a project that has nothing to coordinate. "Managed" used without saying what is managed, or whose account holds the site.
When to avoid it You need a workflow the platform does not support. Nobody will reliably keep it updated and backed up. The project requires capabilities, capacity, or continuity that the freelancer cannot provide alone or through a clearly identified team. The project is small and well defined. Portability and direct control matter more to you than convenience.
Sensible next decision Try the editor yourself before committing. Decide who maintains it, and price that, before choosing it. Write the brief first, then ask two or three people to respond to it. Write the brief first, then ask to see how approvals, changes, access, documentation and handoff are handled. Ask what is included and what is not, whose account it lives in, whether you can revoke their access yourself, and what you receive -- and how quickly -- if either side ends it.

A caution marks something that commonly surprises people later.

Evidence: Editorial assessment Last verified

These are editorial assessments of what each arrangement tends to mean, not properties any of them is guaranteed to have. A freelancer and an agency are not ranked here, and neither is better: they are different arrangements. The specific platform behaviours behind the portability row are cited per platform in the section below it.

None of these is better than the others, and the table is not ranked. What separates them is where responsibility sits and how much of it you want.

Two rows deserve a caution, because they are the ones most often stated as facts about a category when they are not.

Portability is not a property of an approach. It depends on the specific platform, the host, the licences and the access you hold. Some concrete examples, each from the platform's own documentation rather than from a general impression: Wix states that a site must run on Wix's servers and cannot be exported to be hosted elsewhere. Within Wix, the site itself can be transferred to another Wix account, or a copy of it can be sent while the original stays in the sender's account. A Squarespace export produces a WordPress-compatible XML file that leaves out store, album, index, info, calendar and portfolio pages, style settings and custom CSS, and covers only one blog page. Shopify exports products, customers and orders as CSV and lets you download a theme, but orders cannot be imported back, and discount codes, issued gift cards, saved reports and traffic data do not transfer.

Those are three different answers to "can I leave", and none of them is the category's answer. Ask about the specific product, and run the export before you need it.

Provider quality does not follow from provider size. A freelancer may run a better process than an agency, and an agency may be more replaceable than a freelancer. What differs between them is the shape of the arrangement -- one accountable person against a team with more range and more continuity -- not how professional the work is.

"Managed website service" is an arrangement, not a product category. Two things sold under that name can differ completely in what is managed, whose account the site lives in, and what you receive if you leave. Treat the name as the start of a question.

Caution: Whichever approach you choose, the domain and the core business accounts should be in your business's name. That is the one recommendation on this page that does not depend on which option you pick.

Step 4: work through the questions

Questions that narrow the field

Read both answers to each. Most point at more than one approach, which is the honest result.

Several approaches can suit one business, and most of these questions point at more than one. Nothing here is scored or added up — read what each answer points toward and why, and narrow the field yourself. Nothing you read here is recorded.

  1. Question 1. Will you make routine text and photo changes yourself?

    If yes

    Points toward: Hosted website builder, Self-hosted WordPress

    Both put day-to-day editing in your hands without a call to anybody. That is the point of them, and it is worth little if nobody will use it.

    If no

    Points toward: Freelancer, Agency, Managed website service

    If changes will be requested rather than made, what matters is how quickly somebody answers and what that costs -- not how friendly the editor is.

  2. Question 2. Do customers need to book, pay, or buy on the site?

    If yes

    This does not narrow the field on its own.

    This narrows nothing on its own -- every approach can do it -- but it is the requirement most likely to rule out a specific product later, so establish it before anyone proposes one.

    If no

    Points toward: Hosted website builder, Managed website service

    A site that informs and collects enquiries is the case these are built for, and the simpler arrangement is easier to keep running.

  3. Question 3. Do you need design or functionality beyond what standard templates offer?

    If yes

    Points toward: Self-hosted WordPress, Freelancer, Agency

    Someone has to build the part that does not come in the box, and that is either a person you hire or a platform you can extend.

    If no

    Points toward: Hosted website builder, Managed website service

    Paying for flexibility you will not use buys complexity you will.

  4. Question 4. Will somebody reliably handle updates, backups, security and recovery?

    If yes

    Points toward: Self-hosted WordPress, Freelancer, Agency

    A self-managed site is a reasonable choice when the maintenance is genuinely somebody's job -- named, paid for, and still true in a year.

    If no

    Points toward: Hosted website builder, Managed website service

    Not a criticism: most small businesses do not have this, and choosing an arrangement where somebody else carries it is the realistic answer.

  5. Question 5. Does your budget suit a one-off project better than a monthly commitment?

    If yes

    Points toward: Freelancer, Agency

    A defined project has a defined end. What it does not have is anybody responsible on the day after it, which you would then arrange separately.

    If no

    Points toward: Hosted website builder, Managed website service

    A recurring cost buys continuing responsibility. It also continues, which is the thing to be sure about before starting.

  6. Question 6. Is being able to move to another provider later important to you?

    If yes

    Points toward: Self-hosted WordPress, Freelancer, Agency

    Portability is not a property of a category -- it depends on the specific platform, host, licences and access -- but arrangements where you hold the accounts and the files give you more to move.

    If no

    Points toward: Hosted website builder, Managed website service

    Accepting more platform dependence in exchange for less to run is a legitimate trade, as long as it is made deliberately and you know what an export from that platform would actually contain.

  7. Question 7. Are you replacing a site that already receives search traffic?

    If yes

    Points toward: Freelancer, Agency, Managed website service

    Migrating addresses and redirects is the part that quietly loses traffic when it is skipped, and it is worth having somebody accountable for it.

    If no

    This does not narrow the field on its own.

    Starting fresh removes the migration risk entirely, which widens the field rather than narrowing it.

  8. Question 8. Does the work span several websites, systems, integrations or stakeholders?

    If yes

    Points toward: Freelancer, Agency, Managed website service

    Work on that scale usually calls for stronger coordination and broader technical coverage. That may point toward an agency, a managed service with the required scope, or an experienced freelancer or specialist team -- the capability is what matters, not the size of the provider. Verify who coordinates the work, which systems they can support, and what happens when responsibility crosses provider boundaries. A conventional DIY builder is the least likely fit here, because the coordinating is the work and there is nobody in that arrangement doing it.

    If no

    Points toward: Hosted website builder, Self-hosted WordPress, Freelancer, Managed website service

    One accountable person, or one product, is less to manage and less to pay for.

Step 5: think about cost as a shape, not a number

This page deliberately gives no figures. What is useful at this stage is the shape of the spending, and the three layers it falls into.

Build. Your own time, or a project fee. One-off, and easy to compare between quotes because it is the number everybody leads with.

Operate. Platform or hosting, the domain, email, paid apps or plugins, maintenance, support, and payment processing fees. Recurring, easy to underestimate, and the layer that decides what the site really costs.

Change or leave. Getting the content out, redesigning, migrating, redirects, and replacing whatever did not transfer. Rarely budgeted, and the reason the portability row above matters.

An approach with a low build cost and a high operate cost can be more expensive over three years than the reverse. Compare the same years, not the same invoices.

Step 6: check ownership before you commit

Whichever approach you pick, the accounts question is the same, and it is easier to settle at the start than to unpick later. Copyright ordinarily begins with whoever created the work, and a transfer of it must be in a writing signed by the owner of the rights being conveyed -- so "who owns the site" is several separate questions rather than one, and paying for the work does not by itself answer any of them.

Website Ownership Check

The nine areas to settle, whichever approach you choose.

  1. Area 01. Domain registration

  2. Area 02. DNS control

  3. Area 03. Website platform or hosting account

  4. Area 04. Website files and portability

  5. Area 05. Business email

  6. Area 06. Analytics and Search Console

  7. Area 07. Copy, photography, graphics and design

  8. Area 08. Customer and operational data

  9. Area 09. Cancellation, export and handoff

Scenario examples

Four situations, written to show how the questions above play out. They are illustrative: they describe a plausible starting point, not a recommendation for any real business, and a business that looks like one of these may still land somewhere else for good reasons.

A solo salon professional

Needs
Services, a portfolio, contact details, and online booking.
A reasonable starting point
A hosted builder with booking built in, or a booking tool connected to a simple site.
What to check first
Whether booking and client records can be exported, and what the deposit and payment fees are.

A local contractor

Needs
Lead generation, service areas, and quote requests.
A reasonable starting point
A builder, or a freelancer if you need many service-area pages written well.
What to check first
Where form submissions actually go. Enquiries that exist only in somebody else's inbox are the ones you lose.

A childcare centre

Needs
Trust and licensing information, tour bookings, enrolment enquiries, and regular updates.
A reasonable starting point
A freelancer, or a managed service if staff time is genuinely short.
What to check first
How enquiry data is handled and stored, and whether the site is usable with a keyboard and a screen reader.

A product business

Needs
Real ecommerce: a catalogue, payments, shipping and tax.
A reasonable starting point
An ecommerce platform, set up either by you or by a specialist in that platform.
What to check first
Transaction fees, and which parts of your store data can be exported if you move.

What to do next

You should now have one or two approaches rather than five. The next step is not to search for a product -- it is to write down what you established here: what the site must do, who will operate it, who is responsible for maintenance, and which accounts stay in your name.

That page of notes is what makes every later comparison a fair one.

Correction

  • Corrected . This page said a Wix site moves between Wix accounts as a copy. Wix also documents transferring the site itself to another Wix account. The page now describes both methods.

Sources

  1. Exporting or embedding your Wix site elsewhere (opens Wix Help Center in the same tab) Wix Help Center Supports: Wix states a site must run on Wix's servers and cannot be exported to be hosted elsewhere -- a concrete example of why portability cannot be asserted for a category. Evidence: Official source Accessed
  2. Exporting your site (opens Squarespace Help Center in the same tab) Squarespace Help Center Supports: A Squarespace export is a WordPress-compatible XML file that excludes store, album, index, info, calendar and portfolio pages, style settings and custom CSS, and only one blog page; the documentation does not claim it reproduces a working site. Evidence: Official source Accessed
  3. Duplicate or back up your store (opens Shopify Help Center in the same tab) Shopify Help Center Supports: Shopify's export covers some record types and not others -- products, customers and orders leave as CSV, while orders cannot be imported back and discount codes, issued gift cards, saved reports and traffic data do not transfer at all. Cited here as the third of three platforms giving three different answers to "can I leave", which is why this page refuses to answer it for a category. Evidence: Official source Accessed
  4. Transferring a Premium Site to Another Wix Account (opens Wix Help Center in the same tab) Wix Help Center Supports: Ownership of a Wix site can be transferred to another Wix account; for a Premium site, the plan and the domain with its mailboxes can go with it. Evidence: Official source Accessed
  5. Transferring a copy of your site to another Wix account (opens Wix Help Center in the same tab) Wix Help Center Supports: Wix can also transfer a copy of a site to another Wix account while the original stays in the sending account; contacts, orders and invoices are not copied. Evidence: Official source Accessed
  6. Roles and Capabilities (opens WordPress.org Documentation in the same tab) WordPress.org Documentation Supports: A WordPress Administrator has access to all administration features within a single site. The documentation says nothing about hosting, servers, databases, backups or security -- which is why the maintenance row on this page is editorial rather than documented. Evidence: Official source Accessed
  7. Change the site owner (opens Squarespace Help Center in the same tab) Squarespace Help Center Supports: Squarespace site ownership transfers only from the current owner to somebody already a contributor, carrying attached subscriptions and domains. Evidence: Official source Accessed
  8. Collaborator accounts (opens Shopify Help Center in the same tab) Shopify Help Center Supports: Shopify lets a merchant authorise a partner through a collaborator account scoped to particular apps and channels, which is how a hired provider can work without holding the merchant account. Evidence: Official source Accessed
  9. Managing owners, users, and permissions (opens Google Search Console Help in the same tab) Google Search Console Help Supports: Search Console requires a verified owner and allows delegated ownership, so a business can remain the verified owner of its own measurement whoever operates the site. Evidence: Official source Accessed
  10. Add, edit, and delete users and user groups (opens Google Analytics Help in the same tab) Google Analytics Help Supports: Analytics user management requires the Administrator role and identifies users by their own Google Account, so measurement access survives a change of provider. Evidence: Official source Accessed
  11. Information for Domain Name Registrants (opens ICANN in the same tab) ICANN Supports: The registrant is the party who manages the domain through the registrar, which is why domain control is listed as the business's in every arrangement on this page. Evidence: Official source Accessed
  12. Transfer Policy (opens ICANN in the same tab) ICANN Supports: A registrar must supply the authorisation code and remove the transfer lock within five calendar days of the registrant's request where the registrant cannot do it themselves. Evidence: Official source Accessed
  13. Copyright Law of the United States, Chapter 1 -- Subject Matter and Scope of Copyright (17 U.S.C. sections 101-122) (opens U.S. Copyright Office (Circular 92) in the same tab) U.S. Copyright Office (Circular 92) Supports: Section 101 defines a transfer of copyright ownership to include an exclusive licence and to exclude a nonexclusive one, which is why "who owns the site" is several questions rather than one. Evidence: Official source Accessed
  14. Copyright Law of the United States, Chapter 2 -- Copyright Ownership and Transfer (17 U.S.C. sections 201-205) (opens U.S. Copyright Office (Circular 92) in the same tab) U.S. Copyright Office (Circular 92) Supports: Copyright vests initially in the author, and a transfer must be in a signed writing -- so the answer to "do I own it" depends on the agreement, not on who paid. Evidence: Official source Accessed