Start with the people who update it
WordPress can suit teams that want a familiar content editor. Custom development can suit a more specific product experience or business workflow. Both approaches still need thoughtful design and maintenance.
Define the moving parts
List content types, forms, user roles and integrations before choosing a stack. A custom interface does not automatically require a custom backend.
Think beyond launch
Discuss backups, updates, support and who owns the source, accounts and content. The right choice is the one your business can operate comfortably.