How We Work The Lab Thinking Proof About
Start a Conversation
Thinking

Opinions from thirty years of building things that didn't exist yet.

This isn't corporate content. No committee approved it. No marketing team softened the edges. It's what I actually think about software, AI, business, and why most companies are pointing technology in the wrong direction.

DO
The Founder
Lead Platform Architect & CTO, Developer Office · 30 years in a discovery market · Zero security breaches
Featured Essay

The software industry has been pricing the wrong thing for thirty years. AI just made it obvious.

Here's what nobody in this industry wants to say out loud.

Software development was never the hard part. Understanding the business — deeply enough to know what to build, and what not to — was always the hard part. But for thirty years, the industry priced the hard part at zero and charged for the easy part. Because writing code was visible and expensive, and understanding the business was invisible and therefore assumed to be free.

AI just made the easy part nearly free. Which means the entire industry's revenue model — billing for developer hours, charging for lines of code, pricing by sprint — just lost its foundation. They were charging for the commodity. The thing that actually determined whether a project succeeded or failed — whether anyone in the room truly understood the business — was never on the invoice.

Think about the procurement chain that every software project goes through. Idea. Approval. Requirements. Revisions. Costing. Negotiation. Procurement. Point of no return. Then — finally — someone writes code.

Every step in that chain exists for one reason: development was expensive and invisible. You couldn't see the software before you paid for it, so you needed layers of process to manage the risk of buying something you couldn't touch. Requirements documents, proposals, procurement reviews — none of them exist to ensure the software is right. They exist to manage the financial risk of the software being wrong.

When development costs collapse — when you can build working software during the conversation about whether to build it — the reason for the entire procurement apparatus disappears. The requirements document is replaced by the software itself. The negotiation changes because you're pricing a reality, not a promise. Procurement becomes a formality that ratifies what everyone's already tested.

This isn't a process improvement. This is the end of a business model.

The companies that survive this shift will be the ones that were always selling understanding. They just happened to deliver it as code. The companies that don't survive will be the ones that were selling code and hoping nobody noticed the understanding was missing.

We know this because we've lived it. Every system we've built over thirty years succeeded not because we were faster coders, but because we understood the domain — the languages, the law, the regulations, the business. We've always been in the business of understanding. We just used to deliver it slowly because development was the bottleneck.

Now that the bottleneck is gone, we can prove we understood your business during the conversation itself. The software appears as a side effect of the understanding. That's not a sales trick. That's the new economics of the industry — and every software company on earth is about to discover which side of it they're on.

The question every business should be asking its technology partners right now isn't "how fast can you build it?" It's "do you actually understand my business well enough to know what to build?" Because that question is now the only one that determines whether you get value.

If your vendor is still billing you by the sprint, they're charging you for the commodity. The expensive part — the part that decides everything — isn't on the invoice.

Series — 11 Parts

Data Protection in Paradise

A practitioner's guide to Sri Lanka's Personal Data Protection Act — examining the PDPA through the lens of enterprise software, behavioural economics, and business reality.

Part 1
Sri Lanka made history in March 2022 by becoming the first South Asian country to enact comprehensive data protection legislation. And almost nobody in the business community truly understands it.
Read
Part 2
The Authority exists. The Board is constituted. But the core obligations are still waiting for a commencement date. Schrödinger's Regulation.
Read
Part 3
A section-by-section breakdown of every change in the amendment. The reference document you'll want to bookmark.
Read
Part 4
You have just provided consent. It is freely given. It is technically informed. It is unambiguous. And it is completely, utterly meaningless.
Read
Part 5
Your simple question has become seven overlapping regulatory instruments, administered by four different regulators. Welcome to data protection compliance in Sri Lanka.
Read
Part 6
Sri Lanka's IT sector earned $1.6 billion in 2025. Every one of those operations involves cross-border data flows. The rules just changed dramatically — and it's good news.
Read
Part 7
Two words added. The entire accountability landscape for AI in Sri Lanka, transformed. The amendment quietly created one of the most progressive frameworks in the region.
Read
Part 8
The PDPA requires most organisations to appoint a Data Protection Officer. Sri Lanka's first batch of certified DPOs numbered a few dozen. The gap is a canyon — and an opportunity.
Read
Part 9
Open your phone. Count the messages you didn't ask for. Part IV will be the single most disruptive provision of the entire Act for consumer-facing businesses.
Read
Part 10
The DPIA is the single most useful exercise an organisation can perform to understand where its data risks actually are. This is the guide I wish existed when I started.
Read
Part 11
Ten million rupees per non-compliance. That's the headline. But is Rs. 10 million actually scary? The answer is yes — but not for the reasons most people think.
Read
Essays
March 2026
Silicon Valley has money, talent, and infrastructure. Sri Lanka has something the Valley lost years ago: the necessity to build things that work with constraints. And in the AI era, constraints breed the kind of discovery that abundance never produces.
Coming soon
March 2026
Every company is hiring AI engineers. Almost none of them are hiring people who understand the business well enough to know what the AI should do.
Coming soon
February 2026
The Request for Proposal was designed for a world where you couldn't see software until it was built. We can now show you working software during the sales conversation.
Coming soon
January 2026
The ones that failed had one thing in common: the people who designed them never spoke to the people who'd use them.
Coming soon
January 2026
Every time someone says "user error," what they actually mean is "we designed this badly and we'd rather blame the person than fix the interface."
Coming soon
December 2025
The moment an organisation outsources its understanding of its own systems, it loses the ability to make strategic decisions about its own future.
Coming soon
November 2025
The agents that are actually making money for businesses aren't particularly smart. They're just deeply contextual.
Coming soon