Business Websites and Web Platforms

A template fixes structure and features first, and the business adapts. Custom work starts from your requirements — pages, flows and connections are defined around your business, not the other way around.

Often the public site does not match how work actually runs — it can display information, but enquiries, records, status or admin work still happen elsewhere by hand. Custom work builds the online parts you specify so they can run as you need.

When a template cannot cover your flows, fields, permissions or integrations — or when forcing the template costs almost as much as rebuilding. If you only need a standard brochure with editable text and images, a template is often enough.

At least: who it is for, which tasks it must complete, which pages or features are required, whether an admin is needed, whether it must connect to existing tools, and what belongs in phase one. Clearer inputs make scope and timing clearer.

Typical path: discuss requirements → confirm scope → design and build → you confirm key checkpoints → delivery. Each step follows what you confirmed, not a fixed package.

Complexity of features, number of integrations, whether materials are ready, and how quickly confirmations come back. Small, clear scope is faster; large mid-project changes extend the timeline.

Usually: how the work should run, necessary copy or assets, access for integrations if any, and confirmation of scope, key screens and acceptance criteria. Build follows what you confirm.

Treat new needs as a new scope: state what to change and how far to go, then re-estimate time and fee before continuing. Delivery is not a hard stop — changes are re-aligned first.