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.
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.
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.