Web design & development. The work most of our long relationships start with.
Most of what Serenity ships starts with a website. Mostly in Webflow. UX, UI, content strategy, information architecture, SEO, and development — the whole craft, kept on the same hands the whole way through. Projects range from focused redesigns to large builds that grow into ongoing partnerships.
Nine disciplines, one team.
The whole craft of a web engagement, kept inside the studio. No handoff to a development shop, no design files thrown over the wall.
Talking to actual users. Mapping the decisions they make and the moments they get stuck.
Sitemap, navigation logic, content hierarchy — organized around the audience, not the org chart.
What stays, what goes, what gets rewritten. Sometimes we write it. Always we shape it.
Component libraries, type systems, color, motion. Designed for the actual content, not the other way around.
Our default platform. CMS, interactions, ecommerce when needed. Built for editors, not for engineers.
When the brief calls for something Webflow can't do gracefully. Always alongside, rarely instead of.
Redirect maps, structured data, performance, and the care that keeps existing traffic from collapsing.
Core Web Vitals, WCAG 2.1 AA, keyboard navigation. Baseline, not optional.
Walkthroughs, documentation, ongoing care. Built so your team can keep the site healthy without us.
Brand clarity isn't a service we sell — but websites almost always need it before the build can do its job.
Sector framing. Voice. The elevator pitch the team can agree on. Most of the rebrands we've done in the last few years started as a website project — discovery surfaced that the site couldn't say what the organization did because the organization hadn't agreed on what it did.
We do that work inside the engagement when it needs doing. We don't bill it as a separate phase, we don't sell it as a deck. It happens through the execution, and the site ships on a foundation that holds. It's often the most valuable thing we ship.
Work across the long relationships.
Each one started as a website project. Each one became something larger — because the work held.
Six phases. We don't skip them.
Discovery & alignment
The first weeks are about understanding the institution, the audience, and what the brief might be missing. Most of our best work happens because we asked questions in this phase that nobody had asked in the brief.
Information architecture & content strategy
Sitemap, content audit, voice, sector framing. If brand clarity work needs doing, this is where it surfaces — and where we do it, inside the engagement.
Visual design & UI systems
Component library, type system, color, motion. Designed for the actual content, not the other way around. We work in real prototype, not static mockups.
Webflow build (or custom, if needed)
Most of our work ships in Webflow. We escape to custom code when an integration or interaction demands it — not by default.
Launch & migration
SEO continuity, redirect maps, performance check, accessibility audit. Then the public day — usually quieter than people expect, because the work was done in advance.
Stewardship
We don't disappear. Many of our web engagements roll into ongoing care — content updates, growth, the slow improvements that real sites need over time.
“They think holistically. At multiple junctures, they have raised their hand to help advise and counsel us on design decisions with other partners, never in the spirit of stealing the business, but instead trying to come up with a solution that fits our full story and brand.”~ Colby Reade· Vice President, External Affairs & Strategy · M.J. Murdock Charitable Trust
Questions that come up early.
Mostly about how we work, not what we deliver.
Why Webflow, mostly?
Because for the kind of clients we serve — foundations, healthcare, universities, mission-driven organizations — Webflow hits the right balance. Ownership, editability, performance, design fidelity. Internal teams can keep the site healthy without engineering support. We use other tools when the project calls for it. We're not religious about it.
When do you write custom code?
When the brief asks for something Webflow can't do gracefully — complex integrations, custom interactions, specialized data displays, real-time features. Custom code shows up alongside Webflow, not instead of it. Most of the time the editable site stays in Webflow and the bespoke pieces live in code.
Do you take on smaller projects?
Yes, when the brief is tight and the team is ready. We're honest about what fits a smaller scope — usually a focused redesign of a few pages, not a full rebuild — and we'd rather tell you that up front than scope-creep into trouble later.
Do you offer ongoing maintenance?
Yes. Most of our long relationships started as a website project and grew into ongoing stewardship — monthly retainers covering content, updates, and incremental improvement. We treat sites as systems that need care, not one-time deliverables.
Can you migrate an existing site?
Yes. We've done several migrations off WordPress, Squarespace, and bespoke platforms into Webflow. SEO continuity — redirect mapping, structured data preservation, performance audit — is part of the standard scope, not an add-on.
Have a web project in mind?
When you email us, you're emailing the people who'll do the work — not a business development team.
hello@serenitystudios.com