Start with the people who maintain the content
If a marketing team regularly edits pages and publishes articles, an established CMS may be helpful. If a site supports a specialised workflow, a custom application may fit better. Neither choice removes the need for a considered editing experience.
Map the requirements before comparing tools
List the content types, integrations, permissions and transactions. Mark each as essential or optional. A simple presentation site usually does not need the same infrastructure as a customer portal.
Ask about the lifetime cost
Development is one cost. Hosting, updates, backups, paid extensions and ongoing support also matter. Ask who owns the accounts and what happens if you change providers. Make comparisons against the same operational requirements.
Keep portability in view
Request a clear explanation of where the site can run and how content can be exported. A custom build should come with source and deployment instructions if that is part of the agreement. WordPress needs database and media backups as well as theme files.
Make the final decision with a real brief
Share your expected content updates, business processes and team skills. We can recommend an approach after reviewing those needs rather than assume every project needs the same stack.