Exercise 2: Why the SaaS Startup Needs Custom Development, Not Just Site Ownership — Possible Solution
====================================================================

WHAT WORDPRESS FUNDAMENTALS-LEVEL OWNERSHIP ACTUALLY COVERS
------------------------------
WordPress Fundamentals covers using WordPress as a site owner with no
PHP required - managing content, installing existing themes and
plugins, and working entirely within what's already built and
available off the shelf.

WHY THIS ISN'T ENOUGH FOR THIS SPECIFIC SCENARIO
------------------------------
Per this capstone's own table for Scenario 3, the real ceiling risk was
assessed as "High - real chance of needing custom integrations
(analytics, CRM, A/B testing) no page builder supports." This is
explicitly a need for functionality that doesn't already exist as an
installable, off-the-shelf theme or plugin - custom integrations
specific to this company's own tools and workflows aren't something a
site owner can simply install and configure through the dashboard the
way WordPress Fundamentals covers.

WHY THIS SPECIFICALLY POINTS TO WORDPRESS INTERMEDIATE/ADVANCED
------------------------------
Per this chapter's own recommendation, "given genuine growth plans and
the real chance of needing custom functionality (Chapter 6's own
ceiling material), this is a strong candidate for real custom theme
and plugin development, exactly the territory WordPress Intermediate/
Advanced covers." Building genuinely custom integrations - the kind
this scenario's own ceiling assessment flagged as likely needed -
requires real PHP development: custom plugin code (per that course's
own actions/filters material) or custom theme functionality, not
dashboard-level configuration of existing tools.

WHY "HIGH CEILING RISK" IS THE SPECIFIC TRIGGER HERE
------------------------------
Per Chapter 6's own ceiling material, WordPress's real strength over
hosted platforms is that "real PHP development... is always available
as a genuine escape hatch" once a project's needs exceed what
off-the-shelf tools provide. A scenario with a genuinely high, expected
ceiling risk is precisely the case where that escape hatch needs to be
actively used, not just available in the abstract - which is exactly
why this scenario points toward real custom development rather than
stopping at WordPress Fundamentals-level ownership.

WHY THIS WORKS AS AN ANSWER
------------------------------
It distinguishes precisely what WordPress Fundamentals-level ownership
covers from what this scenario's own stated needs require, cites this
chapter's own explicit reasoning connecting the high ceiling-risk
assessment to real custom development, and explains why the "escape
hatch" language from Chapter 6 becomes actively relevant rather than
merely theoretical here.