He could have vibe-coded it. He chose to build it.
A consultancy two and a half years old, run by someone who works in tech and knew what the shortcut would cost him later. This is the reasoning behind choosing a foundation over a template, and the content platform we built on it.
At a glance
- Client
- Harrier
- Industry
- Consulting
- Serving
- Small business and nonprofits
- Engagement
- Website and content platform
3
content pillars the whole taxonomy is built around
Why not the shortcut
It has to scale
Growing later would mean revamping the entire back end of a vibe-coded site.
Security is a job
The posture a web developer needs in 2026 is not something you pick up on the way past.
AI changed the brief
A chaotic environment, more automation, more content, and a moving target underneath all of it.
Brian on why he chose to build it.
What he covers
- Why a vibe-coded site would not scale with the business
- The security posture he did not want to learn the hard way
- Pillar content and a taxonomy built for search and AI
Brian Birch, CEO, Harrier
Content scattered everywhere it landed.
Harrier is a consulting business for small businesses and small to medium nonprofits, deliberately built to look and feel different from most consultancies in that space. Its articles sat in one place, PDFs in another, code samples and reference material somewhere else again, with no single home a reader could be sent to and no structure holding any of it together.
I don't really understand the security posture that I need to think about as a web developer in 2026. So I'm relying on a partner like Albright to really bring all that knowledge to the table.
One content center, one taxonomy.
Everything sits on a custom taxonomy organized around the subjects Harrier intends to be known for over the long term, so the material stays navigable for readers and legible to the AI search tools that increasingly decide who gets cited.
That taxonomy is actually tied to pillar content, which is kind of a newer way to look at creating content in the AI era. And I would have had no idea how to do that on my own.
Decide the foundation
Custom build over a template.
Centralise the content
Video, audio, articles, PDFs, JSON and markdown, all in one place.
Build the taxonomy
A custom structure tied to long-term content pillars.
Make it findable
Structured so readers and AI search can both navigate it.
Albright is kind of like they're my answer to, well, I can't do that. I don't have an excuse if I've got Albright in my corner.
A platform, not a brochure.
Harrier's site is young, and its founder is candid that he did not buy it for a short-term return. He bought a foundation. The thing he was most concerned about protecting was the quality of what goes on it.
I'm passionate that any information we put out at Harrier is truthful, highly researched, and not AI slop.
Building something you intend to keep?
Tell us where you are heading and we will tell you what it takes.
A free 15-minute call. Prefer to write? Send a message.