We Deleted Most of Our Agents. Everything Got Faster
Picture: Web Directions

Meetup In 6 weeks

December
Monday
to Tue 8 December 2026 · Sydney time

We Deleted Most of Our Agents. Everything Got Faster

Where
AI Engineering room 488 George Street, 2000, Sydney
Host
Web Directions
Entry
Not stated
Sign-up
On the host's page
Open on webdirections.org

All Sydney events

You sign up with the host. foundercal only links to it.

Who you meetThe people on the listing, and what the host tells us about the room.

  • Khang Nguyen Hoang Speaker
Investors Not stated The listing does not say
The format Talks, then talking Meetup
Sign-up On the host's page Price not stated

AboutIn the host's words.

Speakers: Khang Nguyen Hoang (Hello Clever)

Track: AI Engineering

The default advice is to add agents: specialised roles, an orchestrator, handoffs between them. We built that. It was a genuinely useful way to explore the problem space, and under real production traffic it was slow and expensive.

When an agent system is slow, the instinct is to reach for a faster model. That was the wrong lever. Our latency wasn't dominated by inference — it was dominated by round trips. Every handoff re-serialised context, every planner turn burned tokens producing nothing a user would ever see, and the overhead compounded per hop. It's the N+1 query problem wearing a different hat: hundreds of small calls where one would do.

So we started deleting. Collapsing to a single agent holding multiple toolkits cut cost per resolved task by roughly two-thirds and latency by about half — same model, no infrastructure change. A caching layer over the repeated-question tail took a further ~30% off the already-reduced figures, on the same principle: the cheapest model call is the one you never make.

I'll show what we measured at each hop to identify round trips as the real cost driver, what broke when we consolidated — tool-selection accuracy, eval attribution, the loss of per-subtask model tiering — and how we handled each. The patterns for managing large toolkits are already known: retrieval over tool definitions, hierarchical grouping, progressive disclosure. What isn't documented is which ones survive production, and where each quietly stops working. Figures are directional and normalised. Includes a side-by-side trace replay of both architectures on an identical task.

https://data.webdirections.org/ai-engineer-sydney/sessions.json#34cbdd7a-0d15-4c99-b1fe-190b17e5f9a5

Full text on webdirections.org .

Where

AI Engineering room

488 George Street, 2000, Sydney

Open in Maps ↗

Same week in Sydney All 139 events

Dec
to 5 Dec
Hackathon

AI Engineer Hackathon

Founders pitch

Web Directions Free
Dec
to 13 Dec
Conference

AI Week

Web Directions
Dec
to 12 Dec
Conference

NeurIPS 2026

One of the year's big ones

NeurIPS Foundation
Dec
to 8 Dec
Meetup

Lessons from Economics for the Human / Agent Software Workforce

Leadership room
Web Directions
Dec
to 8 Dec
Meetup

Ontologies

AI Engineering room
Web Directions
Dec
to 8 Dec
Meetup

Shipping together in an AI native team

Software Engineering room
Web Directions
Dec
to 8 Dec
Meetup

Dependency hell is back. This time it's your agent's config.

Software Engineering room
Web Directions
Dec
to 8 Dec
Meetup

Your website is a terrible API

AI Engineering room
Web Directions
Dec
to 8 Dec
Meetup

Sovereignty Is an Inference Problem

Leadership room
Web Directions
Dec
to 8 Dec
Meetup

My Agents broke APIs

AI Engineering room
Web Directions
Open on webdirections.org Mon 7 Dec ↗