Back to all articles
The Shared PlatformPart 03
Technical debtEngineering leadershipPrioritisationPayments

The Shared Platform, Part 3: Tech Debt or Time to Market

Janahan Thavendran4 min read

TL;DR

  • Debt on a shared path is charged to someone else later; a double partial refund found in monthly reconciliation is the example.
  • Price both sides: the cost of delay that sales brings, and the cost of carrying the shortcut. Deliberate debt gets a ticket, an owner and a payback date.
  • Protect a 15 to 20% platform health budget, replace legacy systems piece by piece, and describe fixes as outcomes the business can weigh.
In this article

The Shared Platform, Part 3 of 7 · Making the call between shipping fast and building it right on a shared platform.

A customer asked for a partial refund. The AI digital worker we had built for refunds and chargebacks sent it to the payment gateway. The gateway didn't execute it, because the balance wasn't there. The refund was marked successful anyway. The customer asked again and received a second partial refund. We found it in monthly reconciliation.

The fix was simple once we saw it. A refund is not marked successful until the balance clears, and every new request checks the status of earlier ones first.

Nobody chose that bug as a shortcut. But it shows how debt behaves on a shared path. The cost doesn't land on the team that created it. It lands later, somewhere else, often in finance, at month end.

That's worth remembering the next time someone says, "We need this by Friday or we lose the deal."

Not all debt costs the same

Executives understand financial debt, so I use the same language. Some technical debt is a cheap loan. Messy code in a service that nothing else depends on can sit for a year without hurting anyone.

Other debt charges high interest. Anything shared that touches money, identity, or data other products trust falls into this group. A shortcut there is paid for by every team that builds on top of it, every release, until someone fixes it.

So the useful question is what rate you're borrowing at.

Price both sides of the delay

Cost of delay is what the business loses each week a feature isn't live. Sales usually arrives with that number, and they should. A lost deal is a real cost.

The platform team rarely brings the other number: what the shortcut will cost to carry. Put both on the table in the same terms. For example: "We can ship a custom version for this client in two weeks, but it will cost us about three months of maintenance over the next two years. Or we can spend three weeks on a configuration option that lets this client and the next two do it themselves. Let's compare what three weeks of waiting costs in revenue with two years of maintaining code only one client uses."

Sometimes two weeks is the right answer. That's fine, as long as it's a decision and not an accident.

Write the loan down

Deliberate debt gets a ticket, an owner and a payback date before the shortcut ships. If nobody will put their name on paying it back, treat it as a write-off you haven't admitted yet.

Unrecorded debt hurts most, because nobody knows it's there until it fails.

Keep a budget for platform health

Set aside a fixed share of every sprint, typically 15 to 20%, for platform health and debt reduction. Then protect it.

The budget changes the conversation with sales. Instead of the platform team saying no, the trade-off becomes visible: "We can do it, but it uses this quarter's platform health budget. Here's what that budget was going to fix."

Don't pay off legacy debt with a rewrite

When the debt is a whole legacy system, the temptation is a big-bang rewrite. Those stall, because the old system keeps changing while the new one is being built.

Wrap the legacy system behind a stable interface and replace it piece by piece, the same strangler pattern that protects partners during an acquisition. Each piece is a small win the business can see, and the old system can be switched off once nothing calls it.

Speak in outcomes

Never tell the business "we need to refactor." Nobody outside engineering can weigh that sentence.

For the refund bug, the fix wasn't "rework the refund state handling." It was "a refund is never marked paid until the money has actually moved." Anyone in the company can weigh that.

Ship fast when the deal is worth it. Just price the debt first, say out loud what you're borrowing, and name who will pay it back.