The problem this solves
Websites designed in a vacuum and then forced into a CMS come out compromised: layouts that break the moment a marketer edits them, one-off pages that cannot be reproduced, and every small change routed back through an agency. The prettiest mockup is worthless if the live site drifts away from it within a quarter of real-world editing.
How we work
We design for HubSpot CMS from the first sketch, not as an afterthought. That means designing a system rather than pages: a layout grid, typography and color tokens, and a library of reusable sections - heroes, feature grids, proof strips, CTAs - that combine into any page your team will need, including ones nobody has thought of yet.
Every module is designed with its editable fields in mind: what the marketer can change, what stays locked, and how the design degrades gracefully when someone writes a headline twice as long as the mockup. Responsive behavior is specified per module, not left for the developer to improvise.
The handoff to development is a specification, not a picture: modules, fields, states, and breakpoints documented so the built site matches the designed one. We designed and run our own site on this exact system.
Deliverables
- Page architecture and sitemap for the new site
- Design system: grid, typography, color, and spacing tokens
- Reusable module designs with editable fields specified
- Responsive behavior specification per module
- Key page designs assembled from the module library
- Developer handoff documentation