Biro

I've spent most of my career in the awkward space between agencies and engineering. Close enough to agencies to understand how they sell and what clients actually expect from them. Deep enough into infrastructure, hosting, legacy systems, and operational disasters to know what happens after the sales pitch is over and somebody has to keep things running for years.

After watching this long enough, you start to realize something. Most agencies don't actually want to run a development department. They think they do, because clients keep asking for websites, landing pages, integrations, analytics, SEO fixes, maintenance, hosting. "Full service" sounds attractive. Recurring revenue sounds attractive. Bigger retainers sound attractive. Everything sounds attractive right up until the moment the agency accidentally becomes responsible for production infrastructure.

Then suddenly somebody is debugging DNS records at 11PM because email stopped working after a domain migration nobody documented properly in 2021. A WordPress plugin auto-updated itself into oblivion thirty minutes before a campaign launch. Analytics numbers stopped matching because a tracking script disappeared during a redesign. Forms silently died months ago and nobody noticed, because submissions were supposed to forward into a mailbox that no longer exists. One client's nephew "knows SEO" and installed six optimization plugins that are now fighting each other like raccoons in a trash can.

And at some point everybody collectively asks:

"How did we end up maintaining all this?"

Fair question.

Agencies and developers run at different speeds

Agencies and developers operate at completely different rhythms, even when everybody involved is competent and well-intentioned. Agencies optimize for momentum, communication, presentation, shipping visible work quickly. Developers optimize for stability, maintainability, edge cases, and avoiding future disasters that nobody else can see coming yet.

Which means the agency says "it's just a small change," while the developer quietly realizes the "small change" touches authentication, analytics, caching, three third-party integrations, production infrastructure, and some horrifying legacy plugin written during what appears to be the fall of the Byzantine Empire.

Now everybody's frustrated for understandable reasons. The client thinks developers are slow. Developers think everybody else is reckless. The agency owner sits in the middle wondering why running Facebook campaigns somehow evolved into discussing SPF records and PHP memory limits.

I've seen this cycle so many times now that it barely surprises me anymore.

The expensive part isn't salaries

Agencies usually focus on salary numbers because they're easy to measure. The real cost is operational instability. Some months there's too much work and everybody's overloaded. Other months developers sit idle while payroll quietly burns in the background. Then one senior developer leaves, and suddenly nobody really knows how deployments work anymore, where production credentials are stored, why cron jobs randomly fail, or which client website still contains "temporary" fixes that became permanent three years ago.

Most agencies aren't trying to become software companies. Development is supportive infrastructure for the real business: branding, campaigns, strategy, creative work, client relationships. So technical processes often evolve organically instead of intentionally. And "organically" in web development usually means:

"A lot of things somehow work, but nobody wants to touch them anymore."

AI didn't fix this

Now AI enters the picture and somehow makes all of this simultaneously better and more dangerous. The productivity gains are real. I use AI constantly. It's genuinely useful. But it also created this strange illusion that software engineering is now basically a solved problem, because code generation got dramatically easier.

It didn't.

Generating code snippets was never the hard part. The hard part is operating real systems long-term without slowly descending into chaos. Keeping websites online. Keeping analytics accurate. Keeping SEO intact during redesigns. Managing hosting costs before they quietly spiral. Maintaining integrations between systems that were never really designed to talk to each other in the first place. Making sure backups actually restore properly instead of just existing theoretically. Handling infrastructure migrations without causing outages. Solving ugly production problems quickly when clients are stressed and losing money.

That's the real work. Ironically, AI probably increases the value of experienced technical operators, because there's about to be an enormous amount of generated software held together by optimism and half-understood abstractions. Somebody still needs to understand what happens when things go sideways.

And things always go sideways eventually.

The boring partnership

Which is probably why I've come to appreciate boring technical partnerships more over the years. Not boring as in uninspired. Boring in the operational sense. Calm communication. Stable infrastructure. Predictable delivery. No ego, no drama, no disappearing acts. No trying to "own the client." No startup-founder theater where everybody pretends they're changing the world while a WooCommerce plugin update takes down checkout on a Friday afternoon.

Just solid work, quietly done. Problems solved before they become bigger problems.

If the technical side of a client relationship feels invisible most of the time, that's usually a sign everything is functioning properly.

That's basically why Biro exists

Not to become another loud agency competing for attention on LinkedIn with AI-generated thought leadership posts about disruption and innovation. There's already plenty of that.

Biro exists because a lot of agencies are genuinely excellent at branding, strategy, campaigns, storytelling, and client relationships, but don't want the operational burden of running a full engineering organization internally just to support the technical side of those services.

So the idea is pretty simple. Be the technical backbone. Quietly. Reliably. Without turning into the center of attention.

Because after enough years doing this work, I've realized something surprisingly unglamorous:

Most clients don't actually want "innovation."

They want things to work.

Where to find it

Biro is live at biro.works. WordPress hosting, custom development, AWS infrastructure, ongoing maintenance, all the unsexy work that keeps client engagements alive between campaigns.

If you run an agency and the technical side of your client work has started feeling heavier than it should, that's the conversation worth having.

• 12-projects