Part 1: Becoming Agent Native.

📍 Post 1 of 8 · Becoming Agent-Native

An 8-part series on going from delivery team to agent-native organization – lessons earned, not borrowed.
→ Genesis · Anxiety · Names Matter · Proof of Value · The Pivot · Co-Creation · The Garage · The Flywheel

We Started in Our Worst Quarter. On Purpose. Q4. Our busiest quarter. The one where we’re all running flat out and nobody has margin for anything extra.

That’s when we decided to pull a small group off delivery and dedicate them to building AI agents.

People thought we were crazy. The timing was bad. But here’s the thing about timing: there’s never a good quarter to change how you work. If you wait for a slow moment, you’re waiting forever.

Three decisions made Phase 1 work. They’re worth naming clearly, because we got all three right (and had gotten them all wrong in an earlier attempt).


Decision 1: Delivery resources. Not new headcount.

The instinct is to hire specialists. Build a separate AI team. Find people with “AI” in their title.

We did the opposite.

We took people already doing the work – people who knew exactly where the friction was, who understood what “a bad Monday looks like” in our workflow – and we gave them dedicated time. Not 10% time. Not a side project. A real squad with a real mandate.

The people who know the pain are the ones motivated to build the cure.


Decision 2: Low-code or nothing.

We made it a mandate: no code-based solutions. No Foundry builds. No MCP servers. No deep engineering.

Partly practical; code means maintenance, and we didn’t have a team to own that. But mostly strategic. The platforms were moving faster than we ever could. Our edge wasn’t engineering. It was application. Low-code kept us in our lane.


Decision 3: Start embarrassingly small.

We had tried the big project approach before. A large-scale agent initiative run as a hobby by people with other jobs to do.

It failed. Not because the vision was wrong. Because nobody owned it, nobody had real time for it, and the scope was too big to make rapid, visible progress.

This time: small agents. Single tasks. The thing you do six times a day that shouldn’t require a human.

Not a meta-agent. Not a platform. Just: let’s automate that one thing that people hate doing.


Out of Phase 1, we had a handful of agents doing small, specific, daily automations. Unimpressive on a slide. Genuinely useful in a workday.

That was enough to move to Phase 2.

The biggest barrier to starting isn’t technology or budget. It’s the belief that you need a huge, perfect project to justify the investment. You don’t.

Next: What happened when those agents met the broader delivery team, and why it didn’t go the way we expected.