Reference: alternative-stack recommendations by use case and budget (Candid 6-tier framework)

By use case + budget — Candid Creative's recommended default stack.

Use case A — Brochure / service / contractor site, $3-8k, single editor:

  • Recommend: WordPress + Gutenberg + Kadence theme + Kadence Blocks (or Blocksy + Stackable; GeneratePress + GenerateBlocks).
  • Why: native, free, fast, accessible, no recurring license risk.

Use case B — Marketing site for established SMB, $5-15k, frequent edits:

  • Recommend: WordPress + Gutenberg + custom block theme + ACF Blocks for bespoke modules.
  • Why: structured content, designer-controlled patterns, future-proof.

Use case C — Content-heavy, SEO-critical, AI-citation-sensitive, $8-20k:

Use case D — Web app, authenticated flows, dashboard, $15k+:

  • Recommend: Next.js + headless CMS (WordPress, Sanity, or Payload) + Vercel/Cloudflare.
  • Why: SSR, app router, server actions, dynamic rendering.

Use case E — Tiny brochure, $0-1.5k, no developer access:

  • Recommend honestly: Squarespace, or WordPress + Gutenberg + Twenty Twenty-Five default theme.
  • Why: if alternative is no site at all, even Elementor Free is defensible. For new builds, default Gutenberg is now usable without a page builder.

Use case F — Existing portfolio of legacy Elementor/Divi the agency inherits:

  • Don't rebuild reflexively. Audit each: if traffic is significant and the site performs, optimize in place (Flexbox Containers, asset cleanup, image optimization). Plan migration only on the next redesign cycle or when builder breakage forces it.

This framework drives RULE: Stop quoting Elementor / Divi / WPBakery as the default for new Candid client builds. Block themes lead the pricing menu. and Candid Creative page-builder transition roadmap: 4 stages over 12 months.