CTO & VP Engineering Advisory Vancouver · Global

AI is shipping code faster.
Your architecture is paying the bill.

I help engineering leaders at AI-accelerated companies restore what AI quietly erodes: confidence that what you ship will hold. Faster delivery. Fewer incidents. Architecture that bends instead of snapping.

Book a 30-Minute Diagnostic → Watch the Devoxx talk ↗
Alex Bunardzic speaking at Devoxx Belgium
Devoxx Belgium Closing talk · Europe's largest developer conference

Peer Validation

Trusted where mistakes get audited.

Senior operators in regulated industries — workplace safety, financial services, agile leadership — vouch for the judgment behind the work.

His hands-on approach and deep technical expertise made him the go-to person when our teams needed innovative solutions to complex problems. His strong opinions are always backed by solid reasoning and real-world experience.

Andre Kaminski Director, Advanced Technology Solutions WorkSafeBC

Alex was successful in capturing my vision and solving countless problems to deliver programs that always exceeded my expectations. I always appreciated his out-of-the-box thinking and his can-do attitude.

Sandy Martin Senior Compliance Executive Raymond James Ltd

He has a gift for making complex ideas feel accessible while still challenging you to think more broadly. Every interaction has been thought-provoking and energizing. His presence is invaluable.

Woody Zuill Agile Guide & Senior Consultant Agile Expertise & Coaching

The Problem

Welcome to the Velocity Trap

Your sprint metrics look great. AI is shipping code faster than ever. Engineers are busy, boards are happy. And yet — release confidence is quietly collapsing. Reviews take longer. Incidents take longer to contain. Refactors feel dangerous. The system is speeding up and stiffening at the same time.

This is the Velocity Trap: AI dramatically increases output but also amplifies every existing weakness in your delivery system. Teams generating technical debt at AI speed, with no systematic way to keep their architecture healthy.

The standard fixes — more code review, more testing, better tooling — don't solve it. They address the symptom. The real problem is that engineers are simultaneously deciding where to go and managing how the system stays correct. At AI speed, that coupling doesn't hold.

Velocity without navigation is not progress. It's acceleration in an unknown direction with a degrading map.

You may be in the trap if…

  • → AI is generating code faster than your team can review it
  • → Refactoring feels risky enough that it doesn't happen
  • → Sprint velocity is up but release confidence is down
  • → Technical debt is growing, disguised as productivity
  • → Your best engineers spend more time reacting than thinking
  • → Architecture decisions are made by whoever moves fastest
If 3 or more of these land —
we should talk.

The Exit

What it looks like on the other side

Organizations that have worked through this transition describe the same set of changes — in roughly the same order.

⟳
Delivery becomes measurable

Instead of "it feels slow," there are clear signals — cycle time, defect escape rate, refactor frequency — that tell you how the system is actually performing.

⬡
AI becomes a force multiplier

Not a chaos source. Engineers navigate. AI executes. The split is clean enough that AI speed becomes real speed, not disguised risk.

↯
Refactoring becomes routine

When the guardrails are in place, changing the system stops being a special project and becomes something that happens continuously, safely.

◈
Quality regressions surface early

Problems are caught before they compound. Small failures are welcome — they're cheap to fix. Large incidents stop being inevitable.

△
Engineers think like architects

The shift isn't about hiring senior people. It's about changing what your existing team is being asked to do moment-to-moment.

→
Architecture serves the business

The codebase stops being a record of past decisions and becomes a living system that reflects current strategy. It bends instead of snapping.

"Alex introduced TDD to the team and set up structures that resulted in significant improvement in delivery time and quality — literally eliminated bugs in our product while meeting all requirements and deadlines." — Eugene Lin, Engineer (fintech)

The Method — Test-Driven Navigation

Humans navigate. AI executes. Tests are the boundary.

Without that boundary, AI speed becomes a liability. With it, AI becomes a precision instrument. The framework that establishes it is Test-Driven Navigation (TDN), introduced in my closing talk at Devoxx Belgium and at the International Software Quality Days in Vienna.

Human — Navigates
  • What should happen next
  • Business intent & priorities
  • Architectural tradeoffs
  • Where the system should go
Tests define the boundary
AI — Executes
  • How to implement safely
  • Refactoring mechanics
  • Maintaining consistency
  • Enforcing constraints at scale
Human IN the loop

Inspector inside the loop.

  • Audits every step the AI takes
  • Attention spent on how the code reads
  • Capped by what one pair of eyes can absorb
vs
Human ON the loop

Director above the loop.

  • Sets the boundary as failing tests
  • Attention spent on business outcomes
  • Scales with however many agents you run

Same loop, different altitude — and that is the whole distance between supervising AI and steering it. See the full diagram ↗

◯
Tests aren't a checklist. They're a navigation instrument.

Failing tests are hyper-specific instructions: they tell AI exactly where to go next and prove when it has arrived safely. Not more tests — strategic intent separated from mechanical execution.

Watch the Devoxx Talk → Read the full TDN framework ↗ See it argued live with the Guild →

Honest Filter

Is this a fit?

My work is high-context and high-effort. Not every organization needs it or is ready for it. Here's a direct read.

✓  Good fit
  • ✓ CTO or VP Engineering at a 50–300 person SaaS
  • ✓ Using or seriously planning to use AI in software delivery
  • ✓ Want to move faster without sacrificing predictability
  • ✓ Accountable for both speed and quality — not just one
  • ✓ Willing to have a frank conversation about what's actually slowing you down
✗  Not a fit
  • ✗ Want AI to go faster with zero constraints
  • ✗ Looking for developer training or certification
  • ✗ Optimizing only for short-term velocity
  • ✗ Need a large firm with project managers and decks
  • ✗ Not using AI in delivery and not planning to
Find out in 30 minutes →

How We Work

Three ways to engage

Every engagement begins with a diagnostic. If there's a fit, we decide together what comes next. No boilerplate proposals. No multi-month ramp.

Start here · The only way in

The Diagnostic

A focused 2-week assessment of your codebase, AI usage patterns, and delivery risks. You leave with a clear roadmap and the data to make the internal case for change. This is the only way any deeper engagement starts.

I sometimes call myself a software delivery midwife — not entirely a joke. Nothing shows up in these two weeks that your team was not already carrying. My part is to keep the delivery safe, name what I can spot and you cannot, and hand you the findings. There is no squad. Nothing gets embedded. What you do with the roadmap afterward is your decision, not my sales target.

$7,500 – $15,000  ·  2 weeks Fixed scope. Fixed price. No lock-in beyond. Book the diagnostic call →

If there's a fit, next steps

Prove it works

Pilot Accelerator

Hands-on TDN implementation with one high-impact team. The goal is a measurable, internal lighthouse project that builds momentum for broader adoption and gives you something concrete to show leadership.

$35,000 – $50,000  ·  6–8 weeks Learn more →
Ongoing counsel

Strategic Advisor

A retainer for leaders who need a trusted external perspective on complex technical decisions, AI strategy, or system evolution — without the overhead of a full-time engagement.

$8,000 – $12,000 / month Start a conversation →

Longer programs — pilot teams, scaling across groups, stabilizing delivery under pressure — are laid out in detail on the full engagements page ↗. They all still start with the diagnostic.

About Alex

Three decades. One consistent obsession.

I didn't set out to create a framework. I set out to solve a problem that kept showing up everywhere I worked: brilliant engineering teams drowning in technical debt they couldn't safely fix.

Over three decades on the job I watched organizations spend millions on digital transformation that left them slower than before. Teams paralyzed by fear of breaking production. Then in 2023, generative AI arrived — and I watched the same pattern repeat, only faster. Teams generating debt at AI speed with no systematic exit.

That's when Test-Driven Navigation crystallized. It's the synthesis of everything learned across fintech, healthcare, and regulated industries — applied specifically to the AI era.

Alex Bunardzic on stage at Devoxx Belgium
  • 2026
    International Software Quality Days, Vienna Invited talk: AI and the Future of Refactoring
  • 2025
    Devoxx Belgium — Closing Talk Introduced Test-Driven Navigation to Europe's largest developer conference
  • 2021
    First International TDD Conference Organizer and host
  • —
    WorkSafeBC · Raymond James · Healthcare & Fintech Engineering Practice Lead, transformation engagements across regulated industries
  • 1990
    First line of professional code Still writing them with the same intent: software should be soft enough to evolve

What rework is costing you

Put your own numbers in.

Every figure below is yours. I supply no uplift, no benchmark, and no industry average — you enter what your delivery actually looks like and decide for yourself how much of the rework is recoverable.

Example values — replace with your own

Rollbacks, hotfixes, and follow-up fixes that were not planned work.
Engineering hours, delay, incident response, and review time combined.
Your assumption, not my promise. Move it to whatever you think is defensible.
Reworked releases per year —
Annual cost of that rework —
Recovered per quarter —
Recovered per year —

Illustrative only. This arithmetic multiplies the figures you entered — it is not a forecast, a guarantee, or financial advice. Its purpose is to tell you whether the problem is large enough to be worth two weeks of anyone's attention.

Proof of Thinking

See the work before you commit

Serious buyers don't hire on a headline. These are the places to pressure-test the thinking before booking a call.

Field Note · AI Craftspeople Guild

A green build is no longer evidence

Agents are aimed at a passing test run, not a correct one — and will edit the expectation to get there. Five unedited minutes from a Guild working session, plus what follows for anyone whose assurance story rests on green.

Read the field note →
Conference Talk · Devoxx Belgium

AI and the Future of Refactoring

The closing talk that introduced Test-Driven Navigation to a live audience of thousands. If this resonates, we should talk.

Watch on YouTube →
Writing · Essays & Articles

Published work on software craft and AI-assisted delivery

Articles on Opensource.com and Medium covering TDD, mutation testing, AI-assisted development, and the discipline of shipping small, safe steps.

Browse published work →
Community · AI Craftspeople Guild

A code of conduct for engineers using AI

A manifesto and growing community for engineers who believe AI-assisted development demands higher professional standards, not lower ones.

Explore the Guild →
Talk · Domain-Driven Design

Permaculture by Succession

Rich domain models cannot take root in barren soil. A pattern for growing bounded contexts the way an ecologist restores a forest: pioneer patterns first, climax architecture last.

Read the abstract →

Pioneer Program

Shape how TDN evolves in your industry

A small cohort of organizations working directly with me to validate TDN across different industries and tech stacks. This is not a discount program — it's a genuine co-creation partnership.

  • Priority access to all TDN tools, frameworks, and resources
  • Co-creation input — help shape how TDN evolves in your specific context
  • Lifetime advisory access (4 hours per quarter)
  • Conference case study feature (anonymous or named, your choice)
Start a Pioneer conversation →
1:1 Every engagement is mine, start to finish Direct, hands-on involvement — no delegation, no subcontractors, no junior bench

Free · No call required

The AI Code Assurance Checklist

The questions an auditor, a regulator, or a new board member will eventually ask about the code your AI tooling is writing — and what a defensible answer to each one looks like.

  • What you are expected to be able to evidence, and who typically asks first
  • Where AI-assisted delivery most often breaks a review trail
  • The signals that tell you rework is growing before the metrics do
  • A short self-assessment you can run with your own leads this week

The download opens on the next page. I will not add you to a sequence, and I will not pass your address to anyone.

Your biggest competitor isn't
another company.
It's the drag in your own system.

A 30-minute diagnostic. No pitch. No hard sell. No obligation. Just a frank conversation about what's slowing you down and whether there's a fit.

Book the 30-Minute Diagnostic →