On this page
The project existed because Routing decisions, trunk capacity, and IVR performance affected billing accuracy and contract economics at scale, but there was no central analytics layer. Source data was fragmented across email bodies, email attachments, CSV, tab-delimited files, and direct database tables — formats that didn't agree with each other. The platform had to run reliably enough to support billing-grade reporting, since gaps would show up in financial and contract decisions. The source summary is: Built the billing and capacity data warehouse for a telecom routing operation where routing, trunk, and IVR performance directly drove cost and revenue at large scale. The core engineering problem was ingestion: the data arrived in five inconsistent formats from 1,000+ devices, with no central system to reconcile it. Delivered the platform solo in about six months, then backfilled five years of history so trend analysis worked from day one. The role was: Sole owner across every phase — requirements, project management, systems and database architecture, ETL engineering, application development, deployment, and production operations. Title was Capacity Analyst; the actual function was architect, engineer, and owner of the platform. The work sat squarely inside the existing business, so the goal was never to add complexity for its own sake.
Operating flow
- Map the current system and the constraint first.
- Choose the smallest change that can hold the load.
- Build against the real workflow instead of a toy case.
- Roll it out with enough monitoring to catch the edge cases.
This series follows the build in the order it happened: discovery, the solution direction, the implementation steps, and the operational result. Each post stays on one decision or one build step so the reader can see how the system moved from the initial constraint to a working result.
The details come from the project files and the company context, not from a generic template. That keeps the story grounded in the mechanics of the work: what was built, what it replaced, and what changed when it shipped.
The implementation stayed close to PostgreSQL, MySQL, Python, Perl because the new system still had to live inside the same operating environment as the old one. That kept the work from drifting into a clean-room exercise that would look better on paper than it would in production. The practical question was always whether the implementation could hold up under the real workflow and the real users. If it could not do that, it was not finished.
The constraint behind the step was that Routing decisions, trunk capacity, and IVR performance affected billing accuracy and contract economics at scale, but there was no central analytics layer. That is why the work had to trade one kind of cost for another instead of trying to eliminate cost altogether. In almost every case, the useful move was to spend a little more effort on clarity, validation, or control so the business would spend less effort on repeated manual work later. That is the pattern the project files keep pointing to.
The role in the work was Sole owner across every phase — requirements, project management, systems and database architecture, ETL engineering, application development, deployment, and production operations. That meant the implementation could not stop at the code boundary because the operating model, handoff, and support path were part of the outcome. The relevant outcome was Supported an estimated $50M+/day in billing operations (estimate — frame it as such). The build only earns its place if the new result is visible in the way the business works after launch.
The specific step in this article was Built the billing and capacity data warehouse for a telecom routing operation where routing, trunk, and IVR performance directly drove cost and revenue at large scale. That is the piece that moves the story from analysis into execution. It is also the part that shows the difference between a conceptual fix and a system people can actually use. That distinction matters more than style or novelty.
The point is to show how the system works, not to turn the project into a slogan or a summary stub.
When the architecture changes, the real question is what the new system allows the business to do that the old one could not. That shows up here in throughput, reliability, operating cost, turnaround time, and how much manual work disappears once the workflow is redesigned.