Updated: 16 October 2026
Indian enterprises buy networking under three commercial models: CapEx (asset ownership plus a service fee), OPEX (hardware and management as one 3- or 5-year subscription), and Managed-Only (a service fee applied to an existing estate). The choice turns on cash flow, balance sheet treatment, tax view, and refresh risk, making it a CFO decision as much as a CIO one.
The most common error Indian CFOs make in the networking capital allocation conversation is choosing the commercial model before understanding the estate. An enterprise decides "we are moving to OPEX because we like predictable costs" and then discovers, six months into a five-year subscription, that its existing hardware had three years of useful life left and Managed-Only would have been half the cash outlay. Or the reverse: an enterprise commits to a full CapEx refresh and then realises the site expansion plan makes OPEX's per-site pricing structurally cheaper.
Model choice is a downstream decision. Estate audit is upstream. This piece assumes the estate has been mapped and turns to the CFO's actual question: given what we own or plan to own, which model works best over five years?
The Three Models, in Cash Flow Terms
CapEx. Buy the hardware. Capitalise it. Depreciate over its useful life. Layer a separate annual service contract on top for the operational discipline. Cash flow is front-loaded in year one (the hardware buy) and flat thereafter (the service fee). The balance sheet shows an asset and a matching depreciation schedule. Refresh risk sits entirely with the customer.
OPEX. One subscription covers hardware, management, support, and refresh. Priced per site or per tier. Term is 3 or 5 years. Cash flow is flat across the term (fixed subscription instalments). The hardware sits on the vendor's books, not yours. Refresh is handled at term end or as part of the bundle. Refresh risk transfers to the vendor.
Managed-Only. No hardware transaction. An annual or multi-year service fee on the estate you already own. Cash flow is the smallest of the three (no hardware cost, just management). Best fit when the existing hardware has useful life remaining, and the pain point is operations, not equipment.
Take a hypothetical fifty-site Indian enterprise refreshing its network estate. Hardware cost under a straight CapEx purchase would run at approximately Rs.2 crore. All numbers illustrative.
| Year | CapEx Model | OPEX Model | Managed-Only Model |
|---|---|---|---|
| Year 1 | Rs.2.0 cr hardware + Rs.40 lakh service | Rs.90 lakh subscription | Not applicable (assumes fresh hardware) |
| Year 2 | Rs.40 lakh service | Rs.90 lakh subscription | Not applicable |
| Year 3 | Rs.40 lakh service | Rs.90 lakh subscription | Rs.50 lakh service (existing estate) |
| Year 4 | Rs.40 lakh service | Rs.90 lakh subscription | Rs.50 lakh service |
| Year 5 | Rs.40 lakh service | Rs.90 lakh subscription (refresh included) | Rs.50 lakh service |
| 5-year total cash | Rs.4.0 cr | Rs.4.5 cr | Rs.1.5 cr on the existing estate |
| Year-1 cash burden | Rs.2.4 cr | Rs.90 lakh | N/A |
Three observations from the table.
First, OPEX is not automatically cheaper over five years. In headline totals, it is often marginally more expensive than CapEx because the vendor is carrying the refresh risk and the working capital cost. The trade is not cheaper cash; it is smoother cash and less refresh exposure.
Second, Managed-Only is materially the cheapest if the hardware side is already sunk. This is why it dominates for enterprises with a recently-refreshed Cisco estate.
Third, the year-one cash burden is the single largest gap between models. CapEx puts Rs.2.4 crore on the year-one P&L (before capitalisation and depreciation smoothing). OPEX puts Rs.90 lakh. For a growth-stage enterprise or a business unit inside a capital-rationed group, that difference decides the model.
Under Ind AS 116 (aligned with IFRS 16), a subscription that bundles an identified asset the customer controls the use of may be classified as a lease. That means the OPEX model, despite its name, can end up on the balance sheet as a right-of-use asset with a matching lease liability, rather than a fully off-balance-sheet operating expense.
Whether a specific OPEX contract triggers Ind AS 116 lease accounting turns on the fine print: whether the hardware is identified, whether the customer controls the use, and whether the service and asset components are separable. Contracts vary. Your auditor is the definitive voice on classification.
CapEx capitalises the hardware as plant and machinery, depreciated over useful life. The service fee sits as an operating expense.
OPEX, depending on classification, either sits fully as operating expense or partially as a right-of-use asset with a lease liability (present-valued) and finance cost recognition. Under lease accounting, the balance sheet is not "clean" in the way sales pitches often suggest.
Managed-Only is a pure service contract, fully expensed as it accrues. No balance sheet impact beyond payables timing.
For a CFO planning to a specific balance-sheet ratio target (net debt to EBITDA, return on capital employed), the accounting treatment of the OPEX contract can matter as much as its cash pattern.
Direct tax under India's Income Tax Act:
CapEx. Hardware depreciates. Computer hardware (including switches and routers commonly) attracts a 40 per cent written-down-value depreciation rate under the Income Tax Rules; specific classifications may differ. Depreciation reduces taxable income each year of the asset's life. Service fees are fully expensed in the year of accrual.
OPEX. If treated as a pure service contract, the subscription is fully expensed in the year of accrual. If lease-classified under Ind AS 116 for accounting purposes, the tax treatment may still follow the substance of the contract; typically the entire subscription is treated as service expense for tax, with book-tax reconciliation for the lease accounting.
Managed-Only. Fully expensed as service in the year of accrual. Straightforward.
GST at 18 per cent applies to service fees under both OPEX and Managed-Only, and to the service component of a CapEx contract. Hardware GST varies by tariff heading. Input tax credit is available for the service GST where the customer is a registered entity making taxable outward supplies.
TDS applies to service fees under Section 194J (professional or technical services) or Section 194C (contractual work), depending on the nature of the service under the contract. Your tax team's classification governs.
Four decision questions, applied in order.
1. What is the age of the existing estate? Under three years remaining useful life: Managed-Only, extended by an eventual refresh conversation. Three to five years remaining life: Managed-Only for now, refresh conversation deferred. Over five years old or end-of-life: refresh unavoidable, so the choice is between CapEx and OPEX.
2. What is your year-one capital availability? Constrained capital points to OPEX. Comfortable capital and a preference to own points to CapEx. If capital availability is fine but the group has a hard EBITDA-to-capex ratio target, either can work; check the accounting classification first.
3. What is your site-add rhythm? Frequent new sites (retail expansion, branch openings, new plants) suit OPEX because per-site pricing is transparent and additions do not require a fresh capital cycle. Stable footprint suits CapEx or Managed-Only.
4. What is your governance rule on asset ownership? Public sector, BFSI and regulated pharma often require asset ownership on the books; CapEx or Managed-Only fit. Growth enterprises and consumer businesses often prefer OPEX for the predictability.
Most Indian enterprises land on a mix. OPEX for new site rollouts, CapEx at the corporate HQ where governance requires ownership, Managed-Only for legacy branches until the next refresh window.
CapEx risks. Technology obsolescence. Refresh discipline (an estate ageing past useful life quietly becomes unsupportable). Working capital tied up in depreciating assets. Skills risk (owning the estate means owning the ability to run it, unless a Managed-Only service is layered on top).
OPEX risks. Vendor lock-in over the term (exit before term end typically triggers cancellation charges). Accounting misclassification (contracts that turn out to be leases surprise the year-end audit). Escalation clauses inside multi-year contracts (verify the price flexibility on adds, moves and changes). Refresh scope (verify what "refresh" means in the contract: like-for-like, upgrade, or new SKUs).
Managed-Only risks. The estate remains the enterprise's problem to refresh; only operations are outsourced. If the estate is old, the enterprise may find itself locked into an escalating support cost as the hardware ages toward end-of-life. Suitable when the hardware side is healthy; risky when it is not.
Different RFPs. Different question sets.
For a CapEx bid:
Line-item BoQ: hardware SKUs, licences, SI services, ongoing management scope, spares.
Annual service fee as a defined percentage of hardware value, banded by SLA tier.
Refresh trigger conditions and pricing for the next cycle.
Exit and offboarding provisions.
For an OPEX bid:
Subscription price per site or per user, per tier, with defined reference hardware.
SLA schedule (response and restoration by priority).
Refresh commitment inside the term (what is refreshed, when, and at whose cost).
Price treatment for adds, moves and changes during the term.
Exit clause and data-return provisions.
Ind AS 116 classification note (the bidder's stated position, subject to customer audit review).
For a Managed-Only bid:
Estate audit as a mandatory first step, with output shared before final commercial commitment.
Coverage tier definitions with SLA schedule.
Scope inclusions and exclusions (what is not the managed operator's problem).
Handling of end-of-life devices and any refresh recommendations.
Exit and offboarding provisions.
Given our estate age, our year-one capital picture, our site expansion plans and our governance stance, which model gives us the best combination of cash flow, balance sheet treatment and operational quality over the next five years?
The answer is almost never one model. It is usually a mix, allocated by site type or by business unit, tied to a costed five-year rolling plan. That rolling plan is a shared artefact, not an IT paper or a finance paper. Enterprises that build it once and revisit annually make better networking decisions than those that treat every refresh cycle as a fresh negotiation.
For a costed five-year comparison across the three models for your actual footprint, we run a Commercial Fit Session: two hours with your CFO or Financial Controller and your CIO or IT lead in the same room. Output is a walkthrough of the five-year cash flow under each model, the accounting treatment we would expect (subject to your auditor), and a recommended allocation across site types. Written within ten working days.
Proactive is a Cisco Penta-Preferred Partner under the Cisco 360 Partner Program, running Managed Services engagements under all three commercial models across BFSI, manufacturing, ITeS, GCC and pharma customers in India.
Disclaimer: Cash flow figures, tax treatment, GST rates and Ind AS 116 classification points in this piece are indicative and drawn from typical Indian enterprise contracts as of publication. Actual accounting classification, tax treatment and commercial terms vary by contract and by the customer's audit position. This is operational guidance; your chartered accountant, tax adviser and auditor are the definitive voices on accounting and tax treatment. Not a substitute for professional advice.
We'll get back to you shortly.