Identify what is standard
Service pages, articles and straightforward enquiries may fit established publishing patterns. Unusual workflows, permissions or integrations may justify custom development. Separate the customer-facing website from any application requirements.
Desktop and mobile design review
Review desktop and mobile layouts together before implementation.
Compare the full ownership model
Ask who updates the platform, manages dependencies and supports the editors. A custom site still needs maintenance. A CMS still needs disciplined implementation. Include the cost and availability of future support in the decision.
Validate the priority journey
Build or inspect a representative content-editing and customer workflow. Check performance with actual content. Choose the approach that meets the important requirements with a clear handover and manageable operating burden.
Put the guidance to work
Capture your starting point, assign an owner to the next action, and decide what evidence will confirm that it worked.
Discuss this with us