Trust Begins With What You Put on the Bill

A customer should not have to finance the argument that their service provider is doing a good job.

That sounds like a question for utility regulators. I believe it is also a design principle for enterprise technology: when people cannot easily leave a system, that system owes them greater transparency-not less.

A report by Inside Climate News describes Alabama regulators asking Alabama Power to voluntarily stop recovering advertising expenses through customer rates before a statutory prohibition takes effect in 2029. The utility currently may recover half its non-public-safety advertising costs; the request would accelerate the change, subject to its consent.

The immediate issue is advertising. The deeper issue is how institutions distinguish the cost of delivering a service from the cost of protecting their own position.

Cost Allocation Is a Governance Decision

In enterprise architecture, we often treat cost allocation as an accounting exercise performed after the system is built.

It is not.

The way we structure billing, shared infrastructure, vendor contracts and internal chargebacks determines who subsidises whom. Those decisions encode institutional priorities just as surely as access-control policies do.

Consider a shared cloud platform. Should a business unit pay for the resources it consumes? Usually. Should it also absorb an experimental initiative that primarily benefits another division? Perhaps-but that subsidy should be explicit.

The same question applies to generative AI. A customer-facing assistant may reduce service costs, support sales, collect feedback and generate promotional recommendations within a single interaction.

Which purpose should bear which cost?

If the architecture cannot distinguish those activities, “operational expenditure” becomes a convenient umbrella for expenses with very different beneficiaries.

A precise invoice can still rest on an unfair allocation model.

Make Policy Traceable Through the System

My architectural takeaway is straightforward: material billing decisions need a traceable chain from policy to transaction.

That means connecting:

• Purpose: What activity did the expenditure support?
• Beneficiary: Who received the primary benefit?
• Authority: Which rule or agreement permits recovery?
• Evidence: What records allow someone else to verify the decision?

These are not simply dashboard fields. They require consistent classifications, ownership, versioned rules and an audit trail across procurement, finance and operational systems.

There is a trade-off. Detailed attribution adds implementation cost and administrative work. Excessive granularity can create false precision, particularly when infrastructure genuinely serves multiple purposes.

The goal is not to meter every keystroke. It is to make consequential allocations explainable and contestable.

Compliance Should Not Require a Rebuild

The Alabama report also highlights a familiar gap: a policy can be agreed today while its mandatory implementation remains years away.

For technology leaders, that raises an important question: how quickly can your systems implement a changed obligation?

If a new billing restriction requires rewriting application code, reconstructing historical data and negotiating incompatible vendor exports, the organisation has accumulated governance debt.

Versioned, effective-dated allocation rules can reduce that debt. So can clear data lineage and controlled approval workflows. But configurability must come with testing: changing a rule quickly is useful only if the resulting bills remain correct.

What Founders and CTOs Should Take Away

Three principles deserve attention:

• Separate service delivery from institutional promotion. Shared budgets should not erase meaningful differences in purpose.
• Design for challenge, not merely disclosure. Users need a practical route to question a charge and obtain a reasoned answer.
• Treat switching barriers as a responsibility multiplier. The harder your service is to leave, the stronger its accountability should be.

For young entrepreneurs, this matters before regulation arrives. Transparent economics are easier to establish early than to retrofit after customers lose confidence.

The most trustworthy systems do more than calculate what someone must pay. They can explain why that person should pay it.

---

About the Author: Sanjeev Sarma is the Founder Director and Chief Software Architect at Webx Technologies. With a core focus on Generative AI integration, Cloud-Native Scalability, and Enterprise Software Architecture, he has spent over two decades driving digital transformation across Northeast India and beyond. Beyond his corporate leadership, Sanjeev is deeply invested in shaping the future of the IT industry. He serves as an Industry Expert on the Board of Studies for Assam Don Bosco University’s School of Technology, advises state technology committees, and actively mentors emerging tech startups at STPI. He brings a unique, dual perspective of high-level enterprise execution and future-ready academic curriculum development.