Start with the work it needs to do
List key pages, editing workflows and integrations. Standard options may be sufficient, but important custom processes need proof that the system can support them.
Templates fit when standard structures are enough
Existing systems and templates can reduce initial work, but check design flexibility, migration, domains and plan costs. Different systems have different terms.
Custom design fits when differences serve a purpose
Custom experiences, complex services or core business integrations may justify scoped design and development, with time for testing and ongoing care.
You can combine approaches
You may use an existing CMS and customise only the screens or functions needed. Agree on what can change and what remains constrained by the platform.
See the admin workflow before deciding
Let the future editor try routine tasks such as text changes, products and images. Also ask about access, backups, migration and support after handover.
A checklist to keep
- Features actually needed
- Acceptable design limitations
- Time available for content management
- Accounts and data to hand over
- Initial and recurring costs
A service related to this guide
Website design & development