web Strategy
The system behind sites that convert, get cited, and keep improving
Most web work stops at launch. This is the system I run instead: a four-part loop of foundation, message, path, and proof, driven by data and tested rather than assumed. It’s built for B2B, SaaS, and SMB teams who already know their site needs more than a redesign and want to see how the method actually works before they hire anyone.
If you’re still narrowing down the problem
Web strategy is the ongoing management of your site’s structure, content, and technical foundation, matched to how your actual buyers or donors make decisions. It’s not a redesign project with an end date. It’s infrastructure that gets measured and adjusted the way you’d manage a pipeline or a fundraising calendar.
If that’s the piece you’re still working out, the blog has deeper breakdowns of specific symptoms: slow pages, flat organic traffic, AI tools not citing your site. If you already know you need a system and you’re evaluating who runs one well, keep reading.
Why this is different from what you’ve probably already tried
Most teams land here after one of three things hasn’t worked:
An in-house marketer stretched across too many channels
Web strategy gets the leftover hours, so it never gets the sustained attention it needs.
A traditional agency retainer
Work ships on a schedule, not on evidence. Changes get made because the contract calls for monthly deliverables, not because the data called for them.
A freelancer or contractor
Execution without a system behind it. Good at the task in front of them, with no framework tying today’s task to last quarter’s data.
I run this as an embedded, ongoing practice, an external internal team, not a vendor relationship. Every change is tied to a specific metric, and every metric feeds the next decision.
The four-part framework
Every engagement touches all four. Depth and order depend on where your site currently stands. That’s why every engagement starts with an audit, not a build.
Foundation
Core Web Vitals, schema markup, crawlability, site architecture. Checked first, because content and messaging built on a shaky technical base underperform no matter how good the copy is.
Message
What the site says, to whom, in what order. For SaaS and B2B, this usually means naming what the product does for a specific role, not the category it competes in. For SMBs, this usually means naming the specific result a customer gets, not restating the general pitch.
Path
How a visitor actually moves through the site, mapped against real behavior, not assumptions about how people should navigate.
Proof
Case studies, data points, credentials, testimonials, placed deliberately at the points where a visitor is deciding whether to trust you, not scattered across the site.
How we found a form embed was quietly costing conversions
A recent engagement with a field-service SaaS company started with a book-demo landing page that looked fine on the surface. The quantitative data told a different story: a conversion drop concentrated at one specific step. Qualitative review, reading the actual form logs, testing the flow directly, traced it to a third-party form embed failing silently for a segment of visitors. No amount of copy rewriting would have caught it. The fix was technical, not creative, and it came directly out of the four-part loop, not a hunch.
The decision loop, in practice
This is the same cycle whether the project is a homepage rebuild or a single blog post optimized for how AI answer engines cite it.
| Step | What it answers | What it looks like |
|---|---|---|
| StepQuantitative data | What it answersWhere is the problem | What it looks likeAnalytics, Core Web Vitals, funnel drop-off, search console |
| StepQualitative research | What it answersWhy is it happening | What it looks likeSales call review, support tickets, direct user testing |
| StepHypothesis | What it answersWhat specific change should fix it | What it looks likeA falsifiable statement tied to one metric |
| StepExperiment | What it answersDid it work | What it looks likeA/B test, phased rollout, or clean before/after comparison |
| StepAnalytics, ongoing | What it answersWhat’s next | What it looks likeFeeds directly back into quantitative data |
A launch is the start of the next measurement cycle, not the finish line.
Common questions
Web strategy is the ongoing alignment of a site’s technical foundation, messaging, user path, and proof points with how a specific buyer actually researches and decides, managed as infrastructure rather than a one-time project.
A redesign is a one-time project with an end date. Web strategy is a continuous loop of quantitative data, qualitative research, hypothesis-driven changes, and experimentation, applied on an ongoing basis rather than at a single launch point.
Ready to build a stronger growth system?
If your website should be doing more than sitting there, we should talk.
The right partnership turns your site into an asset that keeps improving as your strategy evolves.