
The Operational Controls That Prevent Revenue Leakage at Its Source
Revenue leakage in fiber networks is not a sporadic accounting glitch. It is a systemic outcome of operational gaps between commercial commitments and financial realization. Part 1 outlined where cash can drain through seams in sales, activation, billing, and enforcement. Part 2 explains the controls that intercept leakage at each of those seams—turning latent risk into executable discipline.
This is not a checklist of tactical fixes. It is a framework of controls that aligns order-to-cash integrity with real-time operations, eliminating the need for finance to chase discrepancies after the fact.
1. Activation-Driven Revenue Triggers
Revenue must be recognized on delivery of service, not at arbitrary billing cycles. Billing triggers should be automatically derived from network activation events:
-
Provisioning systems emit events when ONTs/GPON ports are confirmed live.
-
Billing engines consume those triggers to create invoices with zero lag.
-
Proration rules adjust charges precisely for mid-cycle activations.
When the start of revenue recognition is tied to the actual service state, unbilled delivered value is eliminated. Systems that defer billing until manual review ensure leakage persists.
2. Embedded Pricing and Promotion Rules
Pricing and promotions must be enforced at the transaction boundary, not patched retrospectively:
-
All commercial offers, discounts, and temporary rates are encoded as system rules, not spreadsheet attachments.
-
The customer portal validates pricing and promotions up front against these rules.
-
Billing engines reference the same pricebook to compute charges.
This prevents pricing drift, expired promotions, and inconsistent application across retail, wholesale, and anchor tenant contracts. Controls anchored in system logic eliminate human dependency for rate enforcement.
3. Contract-Driven Billing Logic
Contracts define revenue terms, not free-text notes. Controls include:
-
Machine-readable contract terms captured at signature.
-
Automatic mapping of contract milestones (e.g., escalators, term changes) into billing rules.
-
Enforcement of minimum term commitments and early-termination charges.
When contract economics are systemically enforced, billing remains aligned with agreed commercial terms without manual intervention.
4. Unified Data Backbone Across Systems
Revenue assurance requires a single operational truth across customer portal, provisioning, OSS, and billing:
-
A shared customer and address identity eliminates mismatches between activation, billing, and collection.
-
Inventory of service endpoints is synchronized across systems so that every active service has a corresponding billing record.
-
Discrepancies are flagged automatically instead of detected through periodic reconciliation.
Disconnected data is a root cause of silent leakage; a unified data model prevents that vulnerability.
5. Automated Exception Monitoring and Reconciliation
Controls must detect and resolve exceptions in real time:
-
Automated reconciliation between provisioning events and billing triggers ensures no order slips through unbilled.
-
Exception dashboards highlight missing invoices, contract non-compliance, and pricing mismatches.
-
Rules-based alerts notify operations when revenue triggers fail, enabling immediate correction.
Periodic batch reconciliation is necessary but insufficient; real-time exception handling is what prevents leakage.
6. Usage and Service Assurance Controls
Fiber networks are not static; redundancy, usage patterns, and service changes must be captured:
-
Usage records (whether flat-rate, metered, or hybrid) are fed into billing engines to ensure overage and usage-based charges are captured.
-
Failover and backup traffic attribution is controlled to prevent underbilling in complex delivery scenarios (e.g., multiple LAG/BGP/secondary links) .
-
Service changes mid-cycle prorate revenue rather than creating gaps or manual adjustments.
Without these controls, delivered value escapes the revenue cycle.
7. Integrated Fraud and Service Theft Prevention
Revenue leakage is not only an accounting issue; it includes unmonitored service usage and misuse:
-
Network events indicative of unauthorized activations or theft are logged and correlate to billing logic.
-
Automated workflows suspend or reclassify such usages until validated by business rules.
-
Controls prevent billing bypass due to mis-provisioned or circumvented service paths.
Such safeguards preserve both customer value and financial integrity.
8. Audit-Ready Operational Workflows
Finance teams should not be forced into firefighting:
-
Every transaction through the order-to-cash cycle should be audit-ready and traceable.
-
Embedded workflows provide a clear trail: quote → order → service activation → billing issuance → collection.
-
Discrepancies are not reconciled retroactively; they are prevented through traceable controls.
Auditable operations allow finance to steer performance instead of repairing failures.
Why Operational Controls Matter More Than Growth
Unchecked growth compounds leakage. Each new customer, promotion, service variant, or wholesale partner introduces complexity. Without embedded controls—activation triggers, unified data, real-time reconciliation—operator finance will always be on the back foot. The net effect is the same regardless of scale: cash conversion lags delivered service, margins erode, and forecasting loses fidelity.
The Path Forward: Control Embedded in Systems
The operational controls described here are not manual tasks; they are discipline encoded into systems and workflows. They move finance from post-hoc reconciliation to real-time assurance. When revenue triggers align with network events and contract terms, revenue leakage becomes a solvable engineering problem, not a perpetual accounting challenge.
In Part 3, we will examine how these controls change forecasting, capital allocation, and partner economics in fiber networks. In Part 4, we will consider what it means to operationalize finance-led network operations.
P.S. If you missed it, go back and read Where Cash Leaks in Fiber Networks (and Why Growth Doesn’t Fix IT)
Coming next: Board-Ready Metrics That Expose Revenue Leakage Early
ISP and Fiber Finance, Part 4
Provisioned = Paid
Why Activation-Linked Billing Is Becoming a Non-Negotiable Control in Fiber Networks
Broadband investors increasingly scrutinize not just subscriber growth, but the reliability of cash conversion. Networks can scale homes passed and activations quickly, yet still underperform financially if billing is not structurally aligned with what the network actually delivers.
One control is emerging as decisive: activation-linked billing. Operators that treat network activation as the single source of truth for invoicing convert service delivery into cash with far less friction. Those that do not accumulate free riders, pricing drift, and disputes—quietly at first, then materially.
This is not a billing feature. It is a control architecture.
The Core Thesis: Billing Must Follow the Network
In fiber networks, value is created when a service becomes active at the ONT or CPE. If billing is triggered by anything else, manual approval, scheduled cycles, spreadsheet reconciliation, cash leakage becomes structural.
Activation-linked billing applies a simple rule:
No exceptions. No retroactive clean-up.
Provisioning events flow directly into invoicing. The network, not back-office interpretation, determines when revenue begins and ends. This collapses the gap between delivered service and recognized revenue.
Dual Contracts: How Control Is Enforced
Activation-linked billing depends on separating commercial intent from network execution—and then keeping them synchronized.
The commercial contract defines the economic agreement: product, price, promotions, term, and fees. This is what the customer buys.
The network contract defines what the network must deliver: speed profile, ONT assignment, VLANs, QoS parameters, and service state.
Install, ONT activation, service activation, and billing are treated as a single workflow. When both contracts align, revenue flows automatically. When they diverge, the system surfaces the mismatch immediately.
Typical exceptions include:
Each represents either free service or incorrect billing, and each is detectable in real time when the network contract and commercial contract are continuously compared.
Why This Matters Financially
From a finance and investor perspective, activation-linked billing produces four material outcomes:
Free riders are eliminated
Active service without an invoice becomes visible and actionable immediately.
Pricing discipline is enforced
The billed plan always reflects the provisioned plan. Promotions start and stop based on activation timestamps, not memory.
DSO compresses structurally
Fewer disputes originate from billing errors, and fewer manual adjustments are required downstream.
ARPU stabilizes
Revenue leakage from expired discounts, mismatched speeds, and missed fees declines without adding operational overhead.
These effects compound as scale increases. Operators that delay this control often see the opposite: growth magnifies leakage.
Core Controls That Make It Work
Activation-linked billing is not achieved by policy alone. It requires a small number of enforceable controls embedded in systems:
Activation event → invoice start
First bill and proration are triggered directly by the activation timestamp.
Deactivation event → invoice stop
Final invoices and applicable recovery fees are triggered on service stop.
Device-to-address binding
ONT/CPE scans at install bind hardware to a service location. Billing blocks if the binding breaks.
Continuous contract synchronization
Commercial terms are compared against live network parameters, with red and amber exceptions for operations and finance.
Role-based overrides
Any manual change to price, speed, or discount requires an approved reason code and leaves an audit trail.
Wholesale and open-access settlement from activations
Partner statements are generated from actual network activations at agreed rates, not spreadsheets.
Together, these controls convert provisioning truth into financial truth.
Board-Level Indicators
Boards do not need to understand provisioning workflows. They need to see whether control exists. Operators typically track the following weekly:
Targets are unambiguous: near-zero free service, sub-day lag, and zero no-order activations.
The Investment Implication
Activation-linked billing is no longer an operational optimization. It is becoming a baseline expectation for scalable fiber economics. Networks that treat provisioning as the arbiter of billing demonstrate control, predictability, and discipline. Networks that do not carry latent risk that only appears under scale or scrutiny.
Provisioned must equal paid. Anything else is a bet against your own network.
P.S. If you missed it, go back and read
Controls That Stop Revenue Leakage, Fraud, and Service Theft
Board-Ready Metrics That Expose Revenue Leakage Early
Where Cash Leaks in Fiber Networks (and Why Growth Doesn’t Fix IT)
Learn More and Contact Us Today
ISP and Fiber Finance, Part 3
Board-Ready Metrics That Reveal Revenue Leakage Early
Revenue leakage does not require forensic analysis to detect. It requires a small number of structurally correct indicators that show whether delivered service is being converted into cash with discipline.
Boards do not need operational exhaust. They need early-warning signals tied to the predictability of cash, margin, and partner settlement. The eight metrics below form a minimum viable control set. Together, they expose leakage before it reaches the income statement.
Each metric answers one question: Is delivered value being converted into revenue without friction or loss?
1. Active-but-Unbilled Rate
What it tells the board: Whether free service exists in the network.
Definition:
(Active services − billed services in current cycle) ÷ active services
Target: <0.25%
Alert: ≥1%
This is the cleanest indicator of leakage. If this metric is red, revenue assurance is broken regardless of growth.
2. Activation-to-Invoice Lag
What it tells the board: Whether order-to-cash is under control.
Definition:
Median days from service activation to first invoice
Target: ≤1 day
Alert: >3 days
Lag converts directly into lost cash, credits, and DSO inflation. Growth amplifies the damage.
3. Pricing Policy Exception Rate
What it tells the board: Whether pricing discipline exists.
Definition:
Invoices with non-catalog pricing or unauthorized discounts ÷ all invoices
Target: <1%
Alert: ≥2%
This single metric replaces multiple discount and override indicators. Boards care about policy enforcement, not discount taxonomy.
4. Credit and Refund Velocity
What it tells the board: Whether defects or abuse are accelerating.
Definition:
(Credits + refunds) ÷ billed revenue (rolling 30 days)
Target: <1.5%
Alert: ≥3%
This metric functions as a canary. Sustained elevation indicates structural failure, not customer behavior.
5. No-Charge Operational Rework Rate
What it tells the board: Whether margin is leaking in operations.
Definition:
Jobs reopened within 14 days with zero charge ÷ completed jobs
Target: <5%
Alert: ≥8%
Missed billable work is invisible to finance unless explicitly measured. This metric makes it visible.
6. Wholesale / Open-Access Settlement Variance
What it tells the board: Whether partner economics are stable.
Definition:
|Expected − actual settlement| ÷ expected settlement
Target: ≤0.5%
Alert: >1%
Persistent variance ties up cash, creates disputes, and erodes partner trust.
7. Dispute-Adjusted Days Sales Outstanding
What it tells the board: True cash discipline versus noise.
Definition:
Standard DSO plus DSO excluding disputed balances
Target: Stable or improving trend
Alert: >10% quarter-over-quarter increase
Boards should always see both numbers. The delta reveals whether DSO drift is operational or structural.
8. Data Quality Failure Rate
What it tells the board: Future leakage risk.
Definition:
Orders failing validation (address, plan, tax, duplication) ÷ all orders
Target: <1%
Alert: ≥2%
Bad data compounds silently. This metric predicts downstream billing errors before they surface.
P.S. If you missed it, go back and read The Operational Controls That Prevent Revenue Leakage at Its Source
Coming next: Why Activation-Linked Billing Is Becoming a Non-Negotable Control in Fiber Networks
Learn More and Contact Us Today
ISP and Fiber Finance, Part 2
The Operational Controls That Prevent Revenue Leakage at Its Source
Revenue leakage in fiber networks is not a sporadic accounting glitch. It is a systemic outcome of operational gaps between commercial commitments and financial realization. Part 1 outlined where cash can drain through seams in sales, activation, billing, and enforcement. Part 2 explains the controls that intercept leakage at each of those seams—turning latent risk into executable discipline.
This is not a checklist of tactical fixes. It is a framework of controls that aligns order-to-cash integrity with real-time operations, eliminating the need for finance to chase discrepancies after the fact.
1. Activation-Driven Revenue Triggers
Revenue must be recognized on delivery of service, not at arbitrary billing cycles. Billing triggers should be automatically derived from network activation events:
Provisioning systems emit events when ONTs/GPON ports are confirmed live.
Billing engines consume those triggers to create invoices with zero lag.
Proration rules adjust charges precisely for mid-cycle activations.
When the start of revenue recognition is tied to the actual service state, unbilled delivered value is eliminated. Systems that defer billing until manual review ensure leakage persists.
2. Embedded Pricing and Promotion Rules
Pricing and promotions must be enforced at the transaction boundary, not patched retrospectively:
All commercial offers, discounts, and temporary rates are encoded as system rules, not spreadsheet attachments.
The customer portal validates pricing and promotions up front against these rules.
Billing engines reference the same pricebook to compute charges.
This prevents pricing drift, expired promotions, and inconsistent application across retail, wholesale, and anchor tenant contracts. Controls anchored in system logic eliminate human dependency for rate enforcement.
3. Contract-Driven Billing Logic
Contracts define revenue terms, not free-text notes. Controls include:
Machine-readable contract terms captured at signature.
Automatic mapping of contract milestones (e.g., escalators, term changes) into billing rules.
Enforcement of minimum term commitments and early-termination charges.
When contract economics are systemically enforced, billing remains aligned with agreed commercial terms without manual intervention.
4. Unified Data Backbone Across Systems
Revenue assurance requires a single operational truth across customer portal, provisioning, OSS, and billing:
A shared customer and address identity eliminates mismatches between activation, billing, and collection.
Inventory of service endpoints is synchronized across systems so that every active service has a corresponding billing record.
Discrepancies are flagged automatically instead of detected through periodic reconciliation.
Disconnected data is a root cause of silent leakage; a unified data model prevents that vulnerability.
5. Automated Exception Monitoring and Reconciliation
Controls must detect and resolve exceptions in real time:
Automated reconciliation between provisioning events and billing triggers ensures no order slips through unbilled.
Exception dashboards highlight missing invoices, contract non-compliance, and pricing mismatches.
Rules-based alerts notify operations when revenue triggers fail, enabling immediate correction.
Periodic batch reconciliation is necessary but insufficient; real-time exception handling is what prevents leakage.
6. Usage and Service Assurance Controls
Fiber networks are not static; redundancy, usage patterns, and service changes must be captured:
Usage records (whether flat-rate, metered, or hybrid) are fed into billing engines to ensure overage and usage-based charges are captured.
Failover and backup traffic attribution is controlled to prevent underbilling in complex delivery scenarios (e.g., multiple LAG/BGP/secondary links) .
Service changes mid-cycle prorate revenue rather than creating gaps or manual adjustments.
Without these controls, delivered value escapes the revenue cycle.
7. Integrated Fraud and Service Theft Prevention
Revenue leakage is not only an accounting issue; it includes unmonitored service usage and misuse:
Network events indicative of unauthorized activations or theft are logged and correlate to billing logic.
Automated workflows suspend or reclassify such usages until validated by business rules.
Controls prevent billing bypass due to mis-provisioned or circumvented service paths.
Such safeguards preserve both customer value and financial integrity.
8. Audit-Ready Operational Workflows
Finance teams should not be forced into firefighting:
Every transaction through the order-to-cash cycle should be audit-ready and traceable.
Embedded workflows provide a clear trail: quote → order → service activation → billing issuance → collection.
Discrepancies are not reconciled retroactively; they are prevented through traceable controls.
Auditable operations allow finance to steer performance instead of repairing failures.
Why Operational Controls Matter More Than Growth
Unchecked growth compounds leakage. Each new customer, promotion, service variant, or wholesale partner introduces complexity. Without embedded controls—activation triggers, unified data, real-time reconciliation—operator finance will always be on the back foot. The net effect is the same regardless of scale: cash conversion lags delivered service, margins erode, and forecasting loses fidelity.
The Path Forward: Control Embedded in Systems
The operational controls described here are not manual tasks; they are discipline encoded into systems and workflows. They move finance from post-hoc reconciliation to real-time assurance. When revenue triggers align with network events and contract terms, revenue leakage becomes a solvable engineering problem, not a perpetual accounting challenge.
In Part 3, we will examine how these controls change forecasting, capital allocation, and partner economics in fiber networks. In Part 4, we will consider what it means to operationalize finance-led network operations.
P.S. If you missed it, go back and read Where Cash Leaks in Fiber Networks (and Why Growth Doesn’t Fix IT)
Coming next: Board-Ready Metrics That Expose Revenue Leakage Early
Learn More and Contact Us Today
ISP and Fiber Finance, Part 1
Where Cash Leaks in Fiber Networks
Fiber network operators frequently report robust subscriber growth while cash conversion underperforms forecasts. Receipts arrive later than projected, collections require disproportionate reconciliation effort, and finance teams are absorbed in backward-looking fixes rather than shaping strategic investment cycles. These symptoms are not ephemeral execution hiccups. They are structural finance and operational disconnects.
At the core, most broadband CFOs do not lose money through an identifiable failure. Instead, revenue leaks through a network of process and system seams between commercial commitments and financial realization. Each gap, in isolation, appears tractable. Collectively, they create persistent leakage that erodes cash flow and distorts profitability.
The principal leak vectors share a common root: finance, network operations, and commercial systems do not operate on a unified control framework. In fiber ventures—the capital intensity of last-mile infrastructure amplifies this risk—static silos between sales, fulfillment, billing, and contract enforcement inevitably erode financial discipline.
Six Common Structural Revenue Leaks
When billing triggers are not tightly coupled to service activation events, invoicing lags delivered value. Days or weeks of unbilled service consume working capital. The financial impact is not hypothetical; every hour between activation and first invoice reduces project IRR and extends payback periods.
Reconciling orders, activations, and contracts after the fact forces finance into a cycle of corrections and credits. Manual reconciliations increase cycle times, inject errors, and obscure true performance. Systems with post-hoc reconciliation loops will always underperform systems with real-time control.
Without standardized pricing enforcement embedded in operational workflows, errors persist. Promotions fail to expire; contract terms are not reflected in daily operations. Over time, these policy drifts distort ARPU and margin forecasts.
When wholesale and retail revenue streams are consolidated without granular economic separation, finance teams cannot attribute performance accurately. This opacity inhibits pricing discipline and distorts investment decisions.
Billing and revenue assurance are only as accurate as the underpinning data. Inconsistent address or customer records propagate downstream errors, inflate collections cycles, and increase dispute volumes.
When the customer portal, provisioning system, and billing engine do not share a common operational backbone, revenue capture becomes contingent on human handoffs. Revenue leakage often resides in these transition points between systems, not in a single failed transaction.
Growth Without Control Amplifies the Problem
Operators often assume that subscriber growth will naturally generate cash. This belief disregards the non-linear impact of operational friction. Growth amplifies complexity faster than cash inflows—if billing, contract governance, and activation are not controlled at the transaction level. Manual processes and disconnected systems scale poorly; without embedded controls, growth increases hidden leakage.
Slower order-to-cash cycles, recurring credits, and noisy month-end closes are not merely symptoms. They are the financial consequence of control gaps between commercial commitments and revenue realization.
The Path to Financial Control
Stopping revenue leakage does not require more headcount. It requires tighter operational control, embedded into the core systems that execute the customer life cycle:
These controls ensure that revenue is recognized as services are delivered, not after finance discovers a gap.
Why This Matters
When finance, operations, and commercial systems share a common operational backbone, finance stops chasing discrepancies and starts steering the business. That shift—from reconciliation to control—is central to making fiber economics sustainable at scale. COS Business Engine embodies these principles, supporting wholesale, retail, and Open Access models without fragmenting finance operations. When systems share a unified data and control framework, leakage declines and financial performance becomes predictable.
Coming next: Controls That Stop Revenue Leakage, Fraud, and Service Theft
Learn More and Contact Us Today
U.S. Fiber Network Utilization:
The Investment Strategy Reshaping Broadband Infrastructure
By Mikael Philipsson | January 16, 2026
Part of the Broadband Investment Series
Why Network Utilization Is Now the Core Fiber Investment Thesis
Everyone says fiber wins. Investors are asking a sharper question: where, and under what model, does fiber win sustainably? The answer explains both the scale of recent U.S. broadband investments and why capital has become more selective about which operators and architectures it backs.
Investors are not just funding fiber. They are rethinking how digital infrastructure creates durable value.
For years the U.S. broadband playbook was straightforward: own the network, own the customer. That model is breaking down. The real shift is not about faster speeds. It is about network utilization at scale: build fiber once, operate and automate it as infrastructure, open it to multiple service providers, and complement it with open-access-ready fixed wireless to extend reach, accelerate time to revenue, and compound returns without overbuilding.
How the New Model Works
The legacy single-operator model is giving way to investor-backed structures that maximize network utilization from day one. The shift fits infrastructure capital’s requirements: long-life assets, diversified revenues, and repeatable expansion logic.
The structure works as follows. The NetCo owns and finances the physical network and sells wholesale access to service providers. It secures anchor-tenant commitments, operates on open access economics, and clusters market expansions to ramp take-rates without ramping risk. NetCos concentrate on layer 1 build pace with economies of scale, layer 2 automation with defined SLAs, and network utilization as the long-life compounding yield driver.
Three Case Studies
Brookfield / Intrepid Fiber / T-Mobile
Intrepid’s open access builds in Colorado and Minnesota continue to scale with T-Mobile as the retail ISP anchor. Public updates point to eight additional communities in each state and a plan exceeding 400,000 locations passed across both. The thesis is build once, add tenants.
AT&T + BlackRock / GigaPower
Marketed as the largest commercial open access fiber platform in the U.S., the JV is live in approximately 70 communities across six states and is preparing a second ISP. Adding that second provider is the utilization multiplier that boosts yields without duplicating physical plant.
AT&T Wholesale Fiber Expansion
Beyond GigaPower, AT&T signed agreements with four open access providers — Boldyn, Digital Infrastructure Group, PRIME FiBER, and Ubiquity — to extend serviceable footprint. This is capital-light coverage: scale reach via wholesale rather than owned and financed build.
Why This Model Is Structurally Disruptive
Service Providers
Asset-light expansion becomes viable. ISPs can enter new markets and add bundling options at scale over third-party fiber without carrying the capital cost of the network.
Communities and Municipalities
Active partnership with infrastructure builders accelerates permits and reuses existing assets. Communities gain future-proof connectivity for schools, healthcare, and public services, with standardized open access technology that ensures additional providers can be added over time.
Investors and NetCos
Infrastructure-profile returns with long-term secure cash flows and a diversified revenue base from multiple tenants added progressively. Risk is structurally lower than single-operator models.
What This Means for Each Operator Type
ISPs: The retail game is becoming operator-light. You can enter new geographies on other operators’ fiber and still own the customer experience. Modern OSS/BSS with API certification is required to interconnect cleanly across wholesale catalogs in open access networks.
Municipal and community networks: Partner actively with infrastructure companies or build your own and partner with credible service providers. Open access technology is no longer experimental. It is the operating standard in markets where this model is most advanced.
Investors: Utilization is your primary lever. Secure an anchor tenant first, then curate a second and third ISP to lift yield without overbuilding. Standardized onboarding makes each additional ISP incrementally cheaper to add.
Three Shifts That Will Reshape the National Landscape
Utilization Is the Strategy
The debate between owning the customer and owning the network misses the point. What matters is how well each role drives utilization of the asset it controls.
Investor-backed NetCos are demonstrating that fiber becomes true infrastructure when it is built once, operated at scale, and opened to multiple service providers through standardized technology. The most effective rollouts increasingly combine fiber with open-access-ready fixed wireless to extend reach, accelerate time to revenue, and improve utilization without overbuilding.
The operators who win will not be defined by who builds the most. They will be defined by who utilizes best, across fiber and complementary access layers.
Talk Strategy
COS Systems works directly with fiber network operators, NetCos, and municipal broadband providers across North America and Europe.
Get in Touch
Meet the latest addition to our team – Zack Mitchell
Meet Our Team – Quick Q&A with Zack
We’re excited to welcome Zack to our growing US team at COS Systems. Based in Wake Forest, NC, he’ll be working closely with our North American customers and partners to help assess and summarize issues, along with assisting in the implementation of new features. Get to know him in this quick Q&A.
Tell us a little bit about yourself – who are you, and what is your background?
A results-driven expert in the fiber industry, I bring nearly 8 years of experience, from field operations to data analytics. This background provides a comprehensive understanding of customer needs in a Field Service Management Tool.
You’re joining our growing (US) team – what will you be working on, and how does your role strengthen COS Systems in North America?
I will serve as a liaison, working closely with our developers to translate end-user needs. This will enable the development team to focus more time and energy on feature construction.
What caught your interest in COS Systems?
The Software and the Culture
What are your goals for the coming months in your new role?
To support our customers with increased documentation, release notes, and demos
What are you most excited about when it comes to working with COS customers and partners in the US?
I’m excited to build strong relationships and further understand the needs of our customers
Tell us a fun fact about yourself.
I used to race dirtbikes when I was in grade school
What’s your go-to productivity hack when things get busy?
Stop and recalibrate. I find it super helpful in times of busyness to stop, take a deep breath, and reshift focus to the highest priority items.
If you could instantly become an expert in one new skill, what would it be?
Carpentry. Imagine being able to build any piece of furniture you want, completely custom to you.
What’s your favorite way to unwind after a long workday?
Watching trashy reality tv shows with my fiancé and laughing at the absurdity.
Lastly, what’s one word your friends or colleagues would use to describe you?
Confident
Connect with Zack!
Meet the latest addition to our team – Nicholas Gerrer
Meet Our Team – Quick Q&A with Nick
We’re excited to welcome Nick to our growing US team at COS Systems. Based in Deerfield Beach, FL, he’ll be working closely with our North American customers and partners to drive product development and provide local support. Get to know him in this quick Q&A.
Tell us a little bit about yourself – who are you, and what is your background?
I’m Nick, and I come from a background in software engineering across a variety of business domains, including domain and hosting resellers, legal technology, and managed home repair. I’ve spent the past 10 years working in engineering departments, where I focused on leading technology initiatives and architecting business-critical systems. Originally from New York, I’ve always been passionate about leveraging the latest technology to solve real-world problems.
You’re joining our growing (US) team – what will you be working on, and how does your role strengthen COS Systems in North America?
I’ll be focusing on developing our Wholesale Engine application. My background in architecting business-critical systems will help strengthen the product as we grow, and being US-based means I can work more closely with our North American customers and partners to ensure they feel fully supported.
What caught your interest in COS Systems?
A few things stood out to me. First, the company culture—it was clear from my conversations that COS Systems values its people and fosters a collaborative environment. I was also excited about the autonomy I’ll have as an engineer to make meaningful contributions. On the technical side, the opportunity to work within the Laravel framework and ecosystem was a big draw. And ultimately, I wanted to join a company that genuinely cares about innovation—not just as a buzzword, but as part of how they operate.
What are your goals for the coming months in your new role?
In the short term, I want to get up to speed on the COS product offerings, build relationships with key customers, and understand the US market landscape. Long-term, I’m aiming to become a go-to resource for our products and contribute to technical decisions that shape their future.
What are you most excited about when it comes to working with COS customers and partners in the US?
I’m most excited about learning a business domain that’s new to me, helping solve real challenges for customers, seeing the impact of our solutions firsthand, and building long-term partnerships. The US market has so much opportunity for growth, and I can’t wait to be part of it.
Tell us a fun fact about yourself.
I’ve recently started prioritizing international travel with the goal of visiting a new destination at least once a year. I love learning about new cultures and ways of life—last year was Thailand, and next up is Italy. I also play ice hockey weekly in recreational adult leagues.
What’s your go-to productivity hack when things get busy?
I throw on classical music or electronic dance music when I want to focus on writing code or developing architectural solutions.
If you could instantly become an expert in one new skill, what would it be?
Speaking another language fluently. I’d choose this because of my love for international travel.
What’s your favorite way to unwind after a long workday?
Playing video games, watching sports, and catching up on TV.
Lastly, what’s one word your friends or colleagues would use to describe you?
Adaptable
Connect with Nick!
Updated UI Tools for Faster Daily Operations in Business Engine
Over the past year, our team has delivered a series of thoughtful UI improvements designed to make your daily work smoother, faster, and more intuitive.
In this update, Spencer walks through several key enhancements. First, the streamlined navigation: daily operational tools are now placed front and center on the left side, while deeper configuration menus move to a separate section, making everything easier to find. Up top, the notification center now includes release notes and improved alerts to keep you informed at a glance.
We’ve also added better visibility into integrations, allowing operators to quickly check system status and run syncs when needed. Search has been upgraded across the platform—from multi-order lookups to clearer default filters—making it quicker to find the exact data you need. The super search now highlights “perfect matches,” meaning one keystroke brings you straight to the right customer, order, or location.
Finally, fly-ins and customer/location cards have been redesigned to show more information on a single screen, reducing unnecessary clicks and helping you access diagnostics, history, and services faster than ever.
These changes may look simple, but together they create a smoother, more powerful user experience—one that helps you stay efficient and focused in your day-to-day operations. We hope you enjoy this sneak peek behind today’s advent calendar door and look forward to hearing your feedback as the UI continues to evolve.
Case Study: Kitsap PUD – Expanding Broadband with Open-Access Infrastructure
From Planning to Monetization: How Integrated Workflows Accelerate Broadband Success