---
title: "How we use AI to ship faster without technical debt"
description: "AI made our developers faster, from no gain on some tasks to 18× on others. Our guardrails keep your platform easy to change while it happens."
url: https://www.pivale.co/blog/ai-development-without-technical-debt/
date: 2026-11-09
author: "Barry Fisher"
tags: ["AI", "Advice", "Choosing an agency", "Integrations"]
publisher: Pivale (https://www.pivale.co)
---

# How we use AI to ship faster without technical debt

## The real gains

We've measured what AI changes in our work: from no gain on some tasks to around 18× faster on others. Overall, we get more done than we did three years ago.

In May 2023, our [Engineering Excellence](https://www.pivale.co/blog/engineering-excellence/) article predicted that AI would change how websites are built, and that people would still need to make the decisions and answer for them. Both predictions held.

The question to ask an agency using AI is whether today's work makes your platform easier or harder to change tomorrow.

## The risk: speed now, debt later

AI-written code raises fair worries: hidden technical debt, missed edge cases, features that don't match each other and security gaps. Left alone, an AI tool builds whatever feature it's asked for next. Kent Beck, one of the original signatories of the Agile Manifesto, calls this being "feature drunk": prompt after prompt, until nobody can change the system without a rebuild.

That approach can delight a client for a quarter. Your website has to last far longer: we look after most of the sites we build for six to eight years, and many for longer.

## Features versus futures

In his talk [Features vs. Futures](https://youtu.be/K7Z8Wa83Wgo), Beck describes two kinds of value in software. **Features** are what it does today: visible and easy to celebrate. **Futures** are what you could make it do tomorrow: invisible until they run out.

Beck's word for futures is optionality. In practice, it means that as your system grows, you don't get backed into a corner and left regretting decisions made years ago. That's a form of technical debt we see often in legacy systems.

Each new feature uses up some of those options. Building it locks in decisions: where your data lives, how your systems connect and how your workflows run. Each decision can make later changes slower or more expensive.

AI speeds up both: you get features sooner, and you use up options sooner too. It can also keep your options open, as long as we build that step into how it works. So we work in a staircase: after each feature, we restore futures with tests, tidying and making sure the team understands what we built.

[Graph of futures against features delivered: the features with futures line climbs in steps, the feature drunk line falls and flattens out](#figure-features-and-futures "figure")
*Our aim: futures keep rising as features are added. After Kent Beck's features vs. futures graph.*

Our rule: every piece of work delivers the feature and leaves your futures at least as healthy as it found them.

## Six guardrails that keep the speed safe

Our AI tools work inside the [Engineering Excellence](https://www.pivale.co/blog/engineering-excellence/) principles we published in 2023, now at a faster pace:

1. **Proven design patterns.** New work follows patterns we've already proven, so every integration logs, fails and recovers the same way.
2. **Automated tests.** Tests define what the system must do and run on every change, catching AI mistakes now and for years to come.
3. **Quality gates.** We write our standards as checks that AI tools test their own work against. A developer still reviews every change.
4. **A shared language.** Your stakeholders and our developers agree what words like "order", "customer" and "consent" mean, so the meaning survives from workshop to code and tests.
5. **Safe releases.** We test every change on staging first, and can roll any change back.
6. **Your data stays private.** The AI sees our code and nothing else: on every project, we keep credentials and personal data out of its reach.

### The surprise: AI can increase your futures

With these guardrails in place, we can change existing code with less risk than ever. Good test coverage gives our developers, and you, the confidence to make large changes: if a change breaks something that already works, the tests tell us straight away. So we can revisit decisions made years ago instead of working around them.

Coverage only helps if the tests check what matters to your business: the workflows your teams rely on and the integrations between your systems. With each new feature or change, we pay close attention to what the tests need to protect. Used this way, AI adds features faster and makes your platform easier to change.

<aside class="aside">

## Case study: one request, nine requirements beneath it

A B2B client with a multisite asked us to send Meta a purchase event whenever a customer completes an order. The request was one line. Underneath it sat nine more requirements. That's normal: most requests carry requirements that only surface once the work starts.

[Diagram: the one request, send Meta the purchase event, above a waterline, with nine requirements underneath it](#figure-meta-requirements "figure")
*One request, nine more requirements underneath.*

- **Consent.** Nothing goes to Meta unless the customer has accepted marketing cookies.
- **Measurement.** A matching GA4 event carries the same ID, so the client can reconcile the two.
- **Compliance.** The client approved new wording for their privacy policy.
- **Reliability.** We log every call to Meta, success or failure, as we do for all our integrations.
- **Pricing rules.** Should the order value include promotions, delivery or VAT? We settled this with the client during the build.
- **Testing.** Automated tests for the hashing of personal data and for the whole feature, then a developer stepping through it on staging.

Three years ago, this would have taken at least a week. This time we logged six hours, end to end.

### Building got fast. Deciding didn't.

Our developers directed Claude Opus 5.5 to write the code, and that was the quick part. The value was in the decisions: consent rules, VAT and policy wording. That's where the time goes now, and where an experienced partner proves their worth.

For the client, that meant a compliant feature live within the week, for about a sixth of the hours. It sits in its own module with separate settings for each site, so they can switch it off or change it without touching anything else. **Their futures went up.**

> **Under the bonnet: how the integration works**
>
> - Purchase events go server to server through Meta's Conversions API, gated by a check on the customer's marketing cookie consent.
> - The server event and the GA4 browser event share an event ID.
> - Customer identifiers are hashed (SHA-256, as Meta requires) before they leave the site, with unit tests covering the hashing.
> - Every call to Meta runs through Drupal's Advanced Queue module using a custom job type, giving an audit trail of successes and failures.
> - Kernel tests exercise the module inside Drupal, so a future change that breaks it fails the tests.
> - It's packaged as a standalone custom module with per-site configuration across the multisite.

</aside>

## The expert stays in the loop

Six hours is one example, and the gains vary from task to task. A hard-to-find bug that once took three hours can now take ten minutes. But AI also misses things an experienced developer would spot at a glance, and sometimes needs babysitting, rolling back or redoing by hand.

[Bar chart of speed-ups: a task needing babysitting about 1 times, the Meta feature 6 times, a hard-to-find bug 18 times](#figure-ai-speed-ups "figure")
*AI speed-ups on three real tasks. The bug and Meta figures come from logged time; the babysitting case is approximate.*

The gains come from experienced people using AI. Our developers decide what to ask for, notice when the answer is wrong, and know when to stop and restore futures.

A speed-up on its own says little about what happens to the software after launch, when technical debt can start to cost you within months.

> **Five questions to ask any agency using AI**
>
> 1. Who reviews the AI's work before it reaches you?
> 2. Which automated tests protect each change, now and in future?
> 3. Can you show an audit trail for every external integration?
> 4. How do you keep our data and credentials away from AI models?
> 5. How will you keep our platform easy to change in three years' time?

## Fast, with futures protected

In 2023 we sat top left: sound engineering, but each feature took the time it took. AI without guardrails moves a team bottom right: fast, but spending your futures to do it. We moved straight across the top.

[Two-by-two of speed of delivery against futures protected: Pivale moves from careful but slow in 2023 to fast and future-proof today, while AI without guardrails sits in fast but fragile](#figure-where-we-sit "figure")
*Where Pivale sits: fast delivery with futures protected.*

You won't see the cost of the bottom row on the first invoice. You see it later, in slower changes, bigger quotes and, in the end, a conversation about a rebuild.

## The difference for you

Working this way gives you:

- **More of your roadmap delivered** for the same budget, with the gains depending on the work.
- **Results sooner**, so you hit your targets earlier and can answer competitors faster.
- **Better decisions**, because the time we save on code goes into consent, compliance and edge cases.
- **A platform that stays changeable**, with no surprise rebuild in three years' time.

Every agency now has AI, but they don't all use it the same way. Whether your system is an information website or mission-critical, you should stay in control of it. We care about the quality of what you're left with years from now, and how many options it leaves open. We won't trade your tomorrow for a quick win today.

Our [website systems audit](https://www.pivale.co/services/audits/) shows how much room to change your platform has left, and where AI could speed up your roadmap safely. To talk it through, [book a 30-minute call](https://www.pivale.co/contact/) with one of our friendly experts, with no obligation.

## Further watching and reading

- Kent Beck, [Features vs. Futures: Software Design in the Age of AI](https://youtu.be/K7Z8Wa83Wgo) (video)
- Kent Beck, [Kudzu to Garden: Sustainable Augmented Development](https://videos.itrevolution.com/watch/1122001849) (video and transcript)
- Pivale, [Engineering Excellence](https://www.pivale.co/blog/engineering-excellence/) (May 2023)

---

Source: https://www.pivale.co/blog/ai-development-without-technical-debt/. Pivale is a UK digital consultancy. Book a 30-minute call at https://www.pivale.co/contact/ or email hello@pivale.co.