Resources · Buyer guide

Buy the website around the job it needs to do.

Use this guide to test whether a website proposal names the real job, ownership model, boundary, content responsibility, migration risk, verification plan, and exit path.

Website buyer guidance

A proposal should tell you who owns what.

Before approving a website project, verify the scope, content responsibility, ownership, forms, analytics, migration plan, operating costs, and handoff—not only the homepage design.

Website proposal review ledger listing scope, content, domain, hosting, forms, analytics, migration, and handoff requirements with corresponding warning signs.
Boho evidence plateBuyer guidance · Not legal advice · Contract terms vary

Repair or redesign? Who owns what? What must survive the move?

Start with the website's commercial job: which services, products, locations, proof, questions, and must the site support? A redesign should solve a named weakness, not merely produce a different style.

Inventory the , , hosting, source, content, images, , , search accounts, , email dependencies, important , and existing agreements before assuming a new can replace them safely.

A credible scope makes responsibility visible.

Outcome and audience

Name the primary offers, buyers, locations, useful actions, and what should become easier when the work is complete.

Pages and content

List the routes, content responsibilities, revisions, images, product or service data, , and what is specifically excluded.

Ownership and access

State who owns the domain, source, production account, analytics, content, licenses, credentials, , and recovery path.

Hosting and support

State the platform, eligibility, third-party costs, traffic or storage limits, update boundary, , support response, exit process, and what happens when a retainer ends.

Quality and verification

Include , , , forms or fallback paths, , analytics readiness, link checks, launch checks, and documented exceptions.

Change and rollback

Explain how the current site is preserved, how URLs move, which approvals gate launch, and how the prior state can be restored if the fails.

Eligible client-owned hosting

Eligible websites may use ’s Free plan in an account controlled by the client. Leaving Boho does not by itself create a hosting charge or require the website to move.

, maintenance, technical support, paid providers, and infrastructure beyond the Free plan remain separate. Cloudflare controls its plan, terms, limits, and availability.

Buy the accountable operating system, not only the homepage mockup.

A strong proposal connects the design to content, ownership, hosting, search continuity, customer action, measurement, , and maintenance. Ask for the explanation before approving the change.