# Budgeting for IT Spend: A Finance Team's Guide

IT used to be a line item. Now it's a labyrinth: SaaS subscriptions bought by individual teams, cloud bills that swing 30% month to month, annual renewals clustered in the same quarter, and shadow tools nobody told finance about. For Indian mid-market companies, IT spend routinely grows faster than revenue — and most finance teams lack a framework to govern it.

This guide gives you one.

Start With the Right Categories

A useful IT budget has six buckets:

1. Run (keep the lights on)

Infrastructure, hosting, internet, licences for core systems (ERP, email, security). Predictable, mostly non-negotiable in-year. Typically 55–65% of total IT spend.

2. Grow (business applications)

CRM, HRMS, analytics, departmental SaaS. This is where sprawl lives and where governance pays.

3. Change (projects)

New implementations, migrations, integrations. Lumpy by nature — budget per project with named owners, not as an amorphous pool.

4. People

In-house IT salaries, contractors, managed service providers. Remember PF/ESI and TDS obligations on contractor payments.

5. Security & compliance

Audits, tooling, certifications (ISO 27001, SOC 2), DPDP Act compliance work. Underfunding this bucket is cheap until it's catastrophically expensive.

6. Contingency

5–10% reserve. Something always breaks, and something always needs buying in December.

Set Benchmarks Before You Negotiate

Typical IT spend as % of revenue (rough Indian mid-market ranges):

  • IT-light services firms: 1–2%
  • Product/tech companies: 8–15%+
  • Manufacturing: 1.5–3%

Track spend per employee too — ₹4,000–₹12,000 per employee per month is common for knowledge-work businesses once you include software, hardware amortisation and connectivity. Your trend matters more than the absolute number: rising cost-per-employee with flat output signals sprawl.

The SaaS Sprawl Problem

Ask three questions and most companies discover waste:

  1. How many tools do we pay for? (The real number is usually 2x what finance knows about.)
  2. What's our utilisation? Licences paid but unused commonly run 20–40%.
  3. When do renewals cluster? If eight contracts renew in April, that month's cash flow takes a beating.

    4. Governance fixes:

    • Central contract register: every subscription logged with owner, value, renewal date and payment terms.
    • Renewal reviews 60 days out: challenge each renewal — usage data or it doesn't auto-renew.
    • Procurement gate: any new SaaS above a threshold (say ₹50,000/year) needs finance sign-off.
    • Licence true-ups quarterly: reclaim seats from departed employees and dormant users.

    Budget the Hidden Costs

    Line items finance teams forget:

    • Implementation and integration — often 1–3x the licence cost in year one.
    • Training and change management — unused software is pure waste.
    • FX exposure — most SaaS is dollar-priced; a rupee move of 3% shifts your budget materially.
    • GST input tax credit leakage — unreconciled ITC on software invoices is money forfeited.
    • TDS on cross-border payments — software royalties from non-resident vendors can attract withholding; budget for compliance, not just the invoice.
    • Price escalations — vendors raise list prices 5–10% annually; budget renewals at +7%, not flat.

    Fix the Cash Timing, Not Just the Amount

    Here's the pattern that wrecks otherwise good IT budgets: vendors push annual contracts paid upfront. Finance gets a discount for prepayment, says yes, and then Q1 cash flow absorbs a ₹40 lakh hit while the benefit spreads across twelve months.

    Three better options, in order of preference:

    1. Monthly billing — ask for it; some vendors agree, especially at scale.
    2. Quarterly payments — a reasonable middle ground.
    3. Financing the annual contract — when the vendor insists on annual terms, platforms like KredFlow let your company pay monthly while the vendor still receives full payment upfront. You keep the annual-contract pricing; your cash flow keeps its monthly rhythm. Approval is instant via GSTIN verification, so it doesn't add procurement friction.

      4. Option 3 increasingly wins because it converts a lumpy capex-style outflow into a clean opex-shaped monthly expense — matching how the cost actually benefits the business.

      Build the Annual Budget in Five Steps

      1. Baseline actuals from the last 12 months across all six buckets.
      2. Map every contract with renewal dates and escalation clauses onto next year's calendar.
      3. Add planned projects with named owners and staged milestones (funds release on milestone completion).
      4. Apply stress assumptions: +7% vendor escalation, +3% FX buffer, 10% contingency.
      5. Review monthly against a dashboard: spend vs budget, licence utilisation, upcoming renewals, cash timing.

        6. The Bottom Line

        Good IT budgeting isn't about spending less — it's about spending deliberately. Categorise, benchmark, kill zombie subscriptions, plan renewal cash flows, and stop letting vendor payment terms dictate your treasury calendar. Companies that do this typically find 15–25% of their existing IT spend is recoverable — before negotiating a single new contract.