Custom website or CMS? Choose for the work, not the badge
By Pixit
A project does not become professional simply by changing its technology label. A CMS can meet a straightforward need well. Custom code can support a specific workflow, or add unnecessary complexity to a simple one. Pixit builds custom products; we still want that choice to have a clear reason.
Describe what makes the project different
Start with the unusual requirements: client access, specific booking rules, user permissions, connections to business software or a multi-step process. A visual preference alone does not necessarily decide the underlying technology.
A company publishing services and occasional articles has different needs from a platform where organisations manage teams and subscriptions. Write those differences down before asking for the “best stack”. A good answer should explain a trade-off, not merely name some tools.
A CMS provides an existing editing framework
A content management system offers a starting point for publishing and organising pages. Its usefulness depends on configuration, chosen extensions and maintenance. It still needs design, implementation and quality checks.
Ask for a demonstration of everyday tasks: edit a paragraph, add a project and correct a translated link. A feature-rich interface can be frustrating if it does not match your team's work. The editing experience belongs in the proposal, not in a surprise tutorial after delivery.
Custom development lets you define the rules
A purpose-built workflow gives you control over screens, permissions and integrations. It also means planning validation, error handling, administration and data migration. The invisible parts are part of the product and the estimate.
Consider a client portal containing documents. Showing a download button is only one task. The system must prevent another client from accessing that document, handle missing files and help staff publish the correct version. These requirements explain why seemingly similar screens can involve very different work.
Maintenance exists on both sides
Custom software still needs updates. A CMS is not automatically slow or insecure. What matters is the implementation, its dependencies, the monitoring and the ability to fix issues when they appear.
Clarify who owns the accounts, how backups are handled and what another supplier would need to take over. Request operating notes and a handover. Independence is not measured by how many buttons exist in the administration area; it is measured by the tasks you can confidently complete.
A practical way to choose
Give each supplier three real tasks and ask how they would support them now and change them later. Compare the initial work, running costs and handover constraints over a period you can realistically plan for.
Our preference is for technology that gives the business room to work. If a specific workflow justifies custom development, make that case clearly. If a simpler arrangement meets the need, it is better to discover that before development. The technology should carry the project, not become its main character.
