Services
Your website project has a budget, a timeline, and a team. You might even have a CMS picked out. But nobody's answered the harder questions: How should the content be organized? Who's going to own it? What happens when five different departments need to publish to the same site?
These aren't design questions or development questions. They're strategy questions. And they need answers before anyone opens a design tool or writes a line of code.
Every website project involves hundreds of decisions — about structure, about content, about editorial workflow, about technology. Without a shared direction for those decisions, teams revisit them during design and development, which costs time, creates uncertainty, and makes it harder to stay aligned as the project moves forward.
Getting those decisions made early actually accelerates the project — the team spends less time debating and more time building. And every strategic deliverable connects directly to what comes next: a content model becomes a CMS configuration, a taxonomy becomes a search filter, a governance plan becomes an editorial calendar with named owners.
Ready to talk through your project? We're ready to hear from you. Drop us a line.
Get In Touch
Strategy at Blend starts with what discovery revealed — or, if we're entering a project mid-stream, with a focused review of what exists. From there, we work through the structural decisions that shape the entire project: how content should be organized, how the editorial experience should work, what governance structures need to be in place, and how the technology should support all of it.
We work collaboratively, not in isolation. Strategy sessions involve your stakeholders — the people who create content, approve it, manage the CMS, and set organizational priorities. The output reflects their reality, not just our recommendations.
The work is always positioned as input for what comes next. Strategy without execution is just a document — and we don't deliver documents that sit on shelves.
A strategic plan that your team has contributed to and agreed on — including content architecture, site mapping, editorial governance recommendations, and (if applicable) a platform recommendation. The deliverables vary by project, but the goal is consistent: a clear, documented set of decisions that everyone can build from.
A content strategy audit is a qualitative assessment of a website's content — not just what's there, but whether it's working.
Learn more with our content strategy audit explainer.
Before you design or build anything, understand what you're dealing with — your audiences, your content, and what your team can manage.
Choose a CMS based on how your team works — not feature lists. Platform-experienced, vendor-neutral guidance for complex organizations.
Design that works for your audience and your editors — from visual systems and prototyping to accessible, structured interfaces.
A few web strategy projects we're proud of.

Blend redesigned the SD UJS site for clarity, accessibility, and ease of use, with Umbraco CMS, better content tools, and improved document handling.

A taxonomy workshop designed to better understand both the categories and the structure of the site.

In order to better facilitate each member’s access to relevant information, a complex content model was implemented for ease of use.
Before you dive into web strategy, here's what's worth thinking through.
No. Content marketing is about creating content to attract an audience. Content strategy is about deciding what content your organization needs, how it should be structured, who owns it, and how it gets managed over time. We focus on the latter — the structural and organizational side of content that makes everything else work.
Yes. We regularly deliver strategy work as a standalone project — particularly project roadmapping, strategy-forward wireframes and tech planning, and platform evaluations. That said, the work is always positioned as input for what comes next. We'll make sure the deliverables are structured so your team (or another agency) can execute on them.
It's never too late to pause and ask the right questions. We've stepped into mid-project engagements to help align content models, rework existing design templates, or replan category taxonomy. It's more work than doing it upfront, but it's significantly less work than launching a site that doesn't function for your team.