The End of the Backlog: How AI Changes What "Delivery" Means

I just had the weirdest realisation. We are nearly at a stage where our tech products will have no backlogs or long-term roadmaps.

That's disconcerting for someone who has been delivering these backlogs for decades. I used to shock everyone by deleting everything older than three months in the backlog. Pearls were clutched! "What about that P4 bug I raised last year?!"

But here's what happened this week: Monday morning meeting, with a list of heavy lifting tasks from the last week. They were all released by lunchtime.

This changes everything.

When Capacity Stops Being the Constraint

For my entire career, the question has been "can we build it?" Product roadmaps, sprint planning, backlog grooming—all of it exists because development capacity is the bottleneck. We've built entire methodologies around managing scarcity.

When development can be completed the same day it's raised, what does that mean for product design and offerings? If we no longer have the constraints around capacity, we can now get on with the more important task of answering: just because we can, should we?

That shift—from "can we?" to "should we?"—is profound. It changes what product management means. It changes what delivery means. It changes what a product company even is.

The Old Playbook That Kept Us Small

For the past two years, we've been building an extraordinary AI-native business performance tool at Ask Astro. I still get a rush seeing a CEO's face when we show them what it can do. And it's going strong.

But here's the kicker: our clients love it, but they also need solutions for their other problems—like a custom lead pipeline or operational tools specific to their business. More importantly, they want one trusted AI partner who understands their business and can handle their sensitive data securely, rather than juggling multiple vendors.

Even though they trust us and asked repeatedly to solve these problems, we've always said no.

Why? The old playbook: build one product, own one space, stay investable. Last year, I would have agreed.

I've changed my mind.

What Changed: Seeing the Pattern

After building the Astro Stack here in Wellington—an end-to-end AI pipeline—I know we can deliver custom solutions 10x faster than what's currently available. Our capacity is far larger than I imagined, now that we are at full throttle. I just need to get out of my own way. (Ironically, even Ask Astro is telling me this.)

Then I saw this post from Y Combinator that crystallised what I was seeing:

"Agencies have always been crazy hard to scale. Low margins, slow manual work, and the only way to grow is to add more people.

But AI changes this.

Now instead of selling software to customers to help them do the work, you can charge way more by using the software yourself and selling them the finished product at 100x the price.

That's why agencies of the future will look more like software companies, with software margins. And they'll scale far bigger than any agencies that exist in these fragmented markets today."

That's exactly what we're seeing. The line between product companies and service businesses is blurring. When you can deliver custom solutions in 4-8 weeks instead of 3-6 months, when you can build what used to take a team of five with a team of two, when Monday's requirements are Tuesday's release—you're not constrained by the old categories anymore.

What This Means for Ask Astro

We're transitioning from SaaS-only to AI-leveraged services because we can. Ask Astro continues as our flagship product, but now we're also building custom solutions for specific business challenges—using the same Astro Stack as our delivery accelerator.

One trusted partner. One security model. Multiple solutions.

This aligns with our core values in ways the old model didn't:

Curiosity - We're continuously exploring new approaches to improve business leadership, not limiting ourselves to one product definition.

Challenge the Status Quo - We're questioning the traditional "one product" restriction that no longer makes sense in an AI-native world.

Accountability - We're delivering on promises consistently by solving the actual problems clients bring us, not just the ones that fit our product roadmap.

Simplicity - We're making complex AI accessible by being the one partner businesses need, not one of many vendors they're juggling.

How we work now:
→ You tell us your challenge
→ We analyse and give you a fixed price
→ We build it (4-8 weeks, not months)
→ We implement, train, and support locally
→ Fixed ongoing costs—no surprises

We're looking for companies that are operationally complex, margin-sensitive, data-rich but fragmented, under pressure to transform with AI, and can't find an off-the-shelf solution.

The Nine-Month Journey to Get Here

This didn't happen overnight. We've been AI-native from the start, building Ask Astro on an AI-first architecture for two years. But it's taken about nine months to get to this more optimised space where we can actually deliver at this pace.

Being AI-native means we're seeing these results sooner than most. Many companies are still experimenting with AI tools, trying to figure out how to integrate them into existing workflows. We built our workflows around AI from the ground up. That's the difference between using AI and being AI-native.

The first few months were about learning what AI could actually do versus what we thought it could do. Then came the phase of building the infrastructure—the Astro Stack—that would let us move fast. Then the refinement of understanding which problems AI solves brilliantly and which still need human judgement.

Now we're at the point where the system hums. Where Monday's heavy lifting is done by lunchtime. Where capacity isn't the constraint anymore.

But here's what's important: this isn't just about us. This is a pattern that's coming for every knowledge-based business. We're just seeing it first because we're AI-native.

What This Means Beyond Ask Astro

There aren't enough experienced New Zealand teams executing AI solutions for the time we all have to get on this massive shift. The gap between what businesses need and what's available is enormous.

If you're running a product company and you're still thinking in terms of annual roadmaps and quarterly releases, you're about to be disrupted by someone who can deliver in weeks what takes you months.

If you're running a service business and you're still scaling by adding people, you're competing against teams that can deliver the same output with a fraction of the headcount.

If you're a business leader trying to transform with AI and you're juggling multiple vendors, each with their own security model and integration requirements, you're making it harder than it needs to be.

The old categories—product company, service business, agency, consultancy—they're all blurring. What matters now is: can you deliver value quickly, can you do it securely, and can you do it at a price that makes sense?

The Real Question

When capacity stops being the constraint, the question changes.

Not "can we build it?" but "should we build it?"

Not "how long will this take?" but "is this the right thing to do?"

Not "how do we manage the backlog?" but "what problems actually matter?"

That's the shift. And it's both exciting and nerve-wracking.

Those who know Sam and me understand what getting back into this game means. Not our first rodeo. 🤠

But this time, we're doing it with tools that change the fundamental economics of delivery. And that changes everything.

Want to talk about what this could mean for your business? Let's chat.