Case Study · Consulting
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 exactly 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.
The problem
Content scattered everywhere it landed.
Harrier is a consulting business for small businesses and small to medium nonprofits, two and a half years old and deliberately built to look and feel different from most consultancies in that space. Its founder wanted a site he could build now and know would grow with him — not one he would have to tear down the first time the business scaled. The harder problem was the content. Articles 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.
What we built
One content center, one taxonomy.
We built Harrier a website on a foundation that can grow, and a content center that takes almost any format its founder wants to publish: recorded video and near-podcast audio, short scannable articles, long written pieces, PDFs, JSON and markdown files. All of it lives in one place rather than scattered across platforms. Underneath it sits a custom taxonomy tied to pillar content, organized around the three subjects Harrier intends to be known for over the long term, a structure that makes the material 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, chosen for what scaling would cost later.
Centralise the content
Video, audio, articles, PDFs, JSON and markdown, all in one place.
Build the taxonomy
A custom structure tied to three 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.
The result
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. What he has now is a single place to publish anything he makes, in whatever form he makes it, organized around the three subjects he wants Harrier known for, and a back end that will not need tearing down the first time the business grows into it. 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.
Before
- Content spread across articles, PDFs and files with no single home
- No structure connecting any of it to a long-term subject
- A template or vibe-coded site would need rebuilding to scale
- No clear answer on the security posture a 2026 site needs
After
- One content center taking video, audio, articles, PDFs, JSON and markdown
- A custom taxonomy tied to three long-term content pillars
- A foundation built to grow rather than be replaced
- Security and architecture handled by a partner who does it daily
Managed Websites
Building something you intend to keep?
A site that grows with the business costs less than the one you rebuild in two years. Tell us where you are heading and we will tell you what it takes.
A senior engineer reads it and replies within one business day.