A site that represents
a business.

The common failure is designing a site page by page. Every comp looks considered in isolation, and then someone needs a page nobody drew — a policy update, a new location, a role that has to be advertised this week — and it gets assembled from whatever is nearest. Six months later the site is visibly two sites.

So the deliverable is a system rather than a set of pages: a type scale, a spacing rhythm, a colour set with stated contrast behaviour, and components that already answer the questions a new page will ask. Templates cover what you have and what you will plausibly add.

Whether a CMS belongs in the build is a real decision, not a default. Content that genuinely changes — posts, listings, a team that grows — earns one. Content that changes twice a year does not, and a database nobody writes to is a liability with a maintenance cost and a security surface attached.

Performance and accessibility are build requirements here rather than a later pass, and the site ships with its repository, deployment pipeline and written documentation. Taking it in-house afterwards should be a decision you make freely, not one the stack punishes.

What you get

• Design system: type scale, spacing, colour, components
• Page templates for the pages you have and the ones you will add
• Responsive build, tested on real devices rather than a simulator
• CMS wiring where content genuinely changes
• Repository, deployment pipeline and written handover

Not included

• Copywriting and photography
• Paid media and ad management
• Ongoing content updates unless retained