Skip to content
Now acquiring WordPress agencies Learn more
Blue Winds Media
Start a project
About Blue Winds

Fifteen years of shipping work, not pitching it.

A team of designers, engineers and marketers working almost entirely with B2B companies whose problems don't fit a template.

01Premise 02Beliefs 03Engagement
No. 01 / Premise

We've watched the web reinvent itself more than once.

Every few years something arrives that will change everything, and it changes some of it. Working out which parts — before the budget is spent — is what we're for.

2011
Brochure sites and the earliest CMS builds

Everyone wanted a site they could edit themselves. Most ended up with one they were afraid to touch.

2014
Responsive — and then responsive properly

Every layout built twice, every flow three times, and every assumption about how people browse rebuilt.

2017
Commerce arrives in B2B

Distributors and manufacturers discovered that PDF catalogues and phone quotes were costing them orders.

2020
Integration becomes the real job

The site stopped being the deliverable; the ERP, the PIM and the quoting logic behind it became the work.

2026
AI, finally in production

Easy to demo, hard to put on a working desk. The interesting question is what a team is still using six months later.

The pattern, every time
Attention Actual usefulness

The pattern rarely changes: a loud arrival, a couple of years of expensive mistakes, then the technology quietly becomes ordinary and useful. Being early isn't the skill — judging which parts are ready, and for whom, is.

No. 02 / Beliefs

Three things we'll say out loud, whether or not they win the pitch.

i.

Shipping beats announcing

Nobody ever got paid for a roadmap slide. We judge our own work on whether it survives production, holds up when volume doubles, and gives somebody their afternoons back.

ii.

The unglamorous work pays the most

The best return is almost never the thing anyone wants to demo. It's the quoting process everyone avoids, the product data nobody owns, and the workflow resting on one person's spreadsheet.

iii.

Sometimes the right answer is to do nothing

Plenty of systems are worth leaving alone, and plenty of platforms are a year away from being worth the switch. We'd rather say so and keep the relationship than bill for something that won't hold.

No. 03 / Engagement

How the work actually runs.

Most engagements begin with a single need and grow from there. The ones we're proudest of have run for years, not months.

Stage 01 / 04

Listen

We ask a lot of questions before suggesting anything. Landing on the right problem is half the value.

Stakeholder interviews Analytics forensics Time with your sales team
Stage 02 / 04

Plan

Structure, search and art direction settled on paper, while changing our minds is still cheap.

Information architecture Art direction Phased scope and budget
Stage 03 / 04

Build

Designers and engineers sit on the same calls, so nothing needs translating between them.

Design systems Production build Integrations and QA
Stage 04 / 04

Grow

Go-live is a milestone, not a finish line. The numbers only start moving in the months that follow.

Measurement Continuous testing Standing sprint cadence