Buyer guides

Decisions competitors skip.

Most agency pages list Next.js, portals and billing. These notes start from a named failure: a theme that indexed spam, a portal the firm abandoned, a product nobody paid for. Written by SiteMivo for founders who already have a brief. None of them promise a ranking.

By SiteMivo. Drafted with research assistance and checked against the sources on each page. Updated 10 October 2026.

• Website vs client portal vs SaaS ↗

  Which thing to build before anyone names a framework.

• Custom website vs template ↗

  When a theme is enough, and when hand-coded is the longer-lived choice.

• Website redesign without losing search equity ↗

  URLs, redirects and content that already earns enquiries.

• Headless CMS: when you need one ↗

  Sanity, Payload or Contentful only when editors need a model files cannot express.

• Agency, freelancer, or a small studio ↗

  Who writes the code, who owns it, and what happens if one person is away.

• What belongs in a SaaS MVP ↗

  One paid workflow, tenancy, billing and entitlements. The rest stays written down.

• Custom portal vs off-the-shelf ↗

  Buy when the workflow is standard. Build when the forms stop fitting.

• Technical SEO in the website build ↗

  Titles, canonicals, sitemap and rendered HTML. Not a plugin, not a ranking promise.

• Accessibility in the website build ↗

  WCAG 2.2 AA as requirements. A badge only when a dated audit exists.

• Code ownership and project handoff ↗

  Repository, domain and deployment in your name. A note your team can follow.