The problems, and what actually solves them
Marketing changes require a designer with a seat.
Once the site is static in your repo, a copy change is a pull request any engineer can review and merge.
You need the marketing site and the app on one domain.
Static files sit behind the same CDN or reverse proxy as the app, so /pricing and /app share an origin without a redirect hop.
Analytics and experiments cannot be installed cleanly.
You control the HTML, so tags go in the head where they belong instead of through a builder's embed slot.
Diligence asks who controls the website.
The answer becomes 'it is in our repo, deployed by our CI' rather than 'a former contractor's design account'.
The economics
The cost that matters here is not the monthly hosting fee — it is the queue. Every marketing change that needs a seat-holder is a change that waits. Moving the site into the repo removes the queue entirely.
Next step
Export the site, deploy it to a staging URL, and check it before anything is cancelled or handed over.
Export a site