Funding IT Operations
IT funding models determine how technology costs are classified, allocated, and recovered across an organisation. The choice of funding model affects which cost centres bear IT expenses, how grants and programmes contribute to shared infrastructure, and whether IT capacity can be maintained between funding cycles. Mission-driven organisations face a distinctive challenge: most funding arrives through restricted grants tied to specific programmes, yet IT infrastructure serves the entire organisation and persists beyond individual project timelines.
- Core costs
- Expenses that support the organisation as a whole rather than specific programmes. IT infrastructure, enterprise software licences, and IT staff salaries represent core costs when they serve multiple functions.
- Programme costs
- Expenses directly attributable to delivering a specific funded activity. A mobile data collection deployment for a single project represents a programme cost.
- Indirect cost rate
- A percentage applied to direct costs that recovers a share of organisational overheads including IT. Also called overhead rate, facilities and administration rate, or cost recovery rate.
- Cost pool
- A grouping of similar costs that share an allocation basis. IT costs might form a single pool or divide into infrastructure, applications, and support pools.
- Allocation base
- The measure used to distribute pooled costs to benefiting units. Common bases include headcount, revenue, direct costs, or floor space.
- Modified total direct costs
- A calculation of direct costs that excludes certain items before applying the indirect rate. Equipment over a threshold and subgrants often receive this treatment.
Funding model structures
Three primary structures exist for funding IT operations, each with distinct mechanisms for cost flow and recovery. The structures differ in where IT costs initially reside, how they transfer to consuming units, and what visibility budget holders have into technology expenses.
Centralised funding
Under centralised funding, IT costs reside entirely within a single IT cost centre funded from unrestricted or core organisational revenue. Programmes and departments consume IT services without direct charges; their budgets contain no IT line items. The IT budget competes with other organisational functions for core funding during annual budget cycles.
+------------------------------------------------------------------+| CENTRALISED FUNDING MODEL |+------------------------------------------------------------------+| || +------------------------+ || | CORE REVENUE | || | (unrestricted) | || +----------+-------------+ || | || v || +----------+-------------+ || | IT COST CENTRE | || | | || | - Staff salaries | || | - Infrastructure | || | - Software licences | || | - Support contracts | || +----------+-------------+ || | || | Services provided (no charge) || v || +----------+-------------+-------------+-------------+ || | | | | | || v v v v v || Prog A Prog B Prog C Finance HR || (£0 IT) (£0 IT) (£0 IT) (£0 IT) (£0 IT) || |+------------------------------------------------------------------+This model simplifies programme budgets and ensures IT investment decisions consider organisational rather than departmental interests. Programmes cannot under-invest in IT to maximise direct programme spending, and the IT function maintains stable funding across the programme portfolio lifecycle. The mechanism works well when unrestricted revenue is sufficient and predictable.
The limitation appears when unrestricted revenue shrinks. If 85% of organisational income arrives through restricted grants, only 15% remains available for core functions including IT. An organisation with £10 million total revenue and £1.5 million unrestricted funding must cover executive leadership, finance, HR, facilities, governance, and IT from that £1.5 million. IT budgets in this scenario typically range from £150,000 to £400,000 depending on organisational priorities.
Cost recovery funding
Cost recovery funding charges IT costs to consuming departments and programmes based on usage or allocation formulas. The IT function operates as an internal service provider, recovering its costs through transfers from other budget holders. Programme budgets include IT line items, and IT revenue depends on the volume and nature of services consumed.
+------------------------------------------------------------------+| COST RECOVERY FUNDING MODEL |+------------------------------------------------------------------+| || Programme A Programme B Programme C Finance || Budget Budget Budget Budget || +--------+ +--------+ +--------+ +--------+ || | IT: £8k| | IT:£12k| | IT: £6k| | IT: £4k| || +---+----+ +---+----+ +---+----+ +---+----+ || | | | | || +-------+-------+-------+-------+ | || | | | || v v v || +----+---------------+---------------+-------+----+ || | IT COST CENTRE | || | | || | Revenue: £30,000 (sum of charges) | || | Expenses: £30,000 (breaks even) | || | | || +-------------------------------------------------+ || |+------------------------------------------------------------------+Cost recovery creates direct accountability between IT spending and consuming units. Budget holders see technology costs within their budgets and can influence consumption. The IT function receives funding proportional to services delivered, creating incentive alignment between IT investment and organisational demand.
The allocation mechanism determines how costs distribute. Simple approaches use headcount: if Programme A has 20 staff out of 100 total, it bears 20% of IT costs. More sophisticated approaches weight by intensity of IT use, applying different rates to field staff with basic email needs versus data analysts requiring substantial compute resources.
A headcount-based example for an organisation with £300,000 annual IT costs and 150 staff:
| Unit | Headcount | Percentage | Annual IT charge |
|---|---|---|---|
| Programme A | 45 | 30% | £90,000 |
| Programme B | 30 | 20% | £60,000 |
| Programme C | 25 | 17% | £51,000 |
| Programme D | 20 | 13% | £39,000 |
| Finance | 15 | 10% | £30,000 |
| HR and Admin | 15 | 10% | £30,000 |
Cost recovery introduces friction. Programme managers receiving unexpected IT charges may resist, particularly when charges derive from infrastructure investments that benefit the whole organisation. New programmes must budget for IT from inception, requiring IT cost estimates during proposal development. If a major programme ends, the IT cost pool must redistribute across fewer units, increasing per-unit charges and potentially creating budget shortfalls.
Hybrid funding
Most mission-driven organisations operate hybrid models combining centralised and cost recovery elements. Core infrastructure receives central funding while programme-specific technology charges to programmes. The boundary between core and programme-specific requires careful definition.
+------------------------------------------------------------------+| HYBRID FUNDING MODEL |+------------------------------------------------------------------+| || +------------------------+ || | CORE REVENUE | || +----------+-------------+ || | || v || +----------+------------------+ || | IT CORE INFRASTRUCTURE | || | (centrally funded) | || | | || | - Network and internet | || | - Core servers | || | - Email and collaboration | || | - IT management staff | || | - Security infrastructure | || | | || | Annual cost: £180,000 | || +-----------------------------+ || || Programme A Programme B Programme C || Budget Budget Budget || +--------+ +--------+ +--------+ || |IT:£25k | |IT: £40k| |IT: £15k| || +---+----+ +---+----+ +---+----+ || | | | || v v v || +---+----+ +--+-----+ +-+------+ || |Mobile | |GIS | |Data | || |data | |platform| |analysis| || |collect | |+ server| |tools | || +--------+ +--------+ +--------+ || (programme-specific technology) || |+------------------------------------------------------------------+The hybrid model protects essential infrastructure while ensuring programmes fund technology specific to their needs. Boundary disputes arise at the margins: does a case management system serving three programmes belong to core infrastructure or split across those programmes? The classification matters for budget planning and determines whether the system survives if one programme ends.
A practical boundary definition places infrastructure serving five or more programmes, or infrastructure essential to organisational operations regardless of programme count, into the core category. Programme-specific systems serving four or fewer programmes charge to those programmes proportionally.
Grant-funded IT mechanics
Grants fund the majority of programme activity in development, humanitarian, and many charitable organisations. Understanding how grants handle IT costs determines whether technology receives adequate investment.
Direct charging
Grants permit direct charging of IT costs when those costs benefit the grant exclusively or when a reasonable allocation methodology exists. A laptop purchased for a project officer working solely on one grant charges directly to that grant. A server hosting data for multiple projects requires allocation.
Grant budgets typically include IT line items in several categories:
Equipment represents capital items for project use. Donor policies specify capitalisation thresholds; items over the threshold (often £1,000 to £5,000) may require depreciation rather than full expensing in year one. A £3,000 laptop for a two-year project might charge £1,500 per year under straight-line depreciation if the donor requires this treatment.
Software and licences cover project-specific tools. Annual licence costs for mobile data collection platforms, GIS software, or specialist applications charge to the grants using them. Multi-year licences require allocation across the grant period.
Connectivity costs for project locations charge directly when identifiable. Internet service at a field office serving one project is a direct cost; internet at headquarters serving all projects is indirect.
IT services from external providers, including cloud hosting, development contractors, and support agreements, charge directly when serving specific projects.
Indirect cost recovery
Indirect cost recovery provides the primary mechanism for funding core IT through grants. Donors permit grantees to apply an indirect rate to recoverable costs, generating revenue that covers organisational overhead including IT infrastructure.
The indirect rate calculation divides the indirect cost pool by the allocation base. If an organisation has £500,000 in annual indirect costs (including £150,000 for IT) and £2,000,000 in modified total direct costs, the indirect rate is 25%:
Indirect cost pool: £500,000Allocation base (MTDC): £2,000,000Indirect rate: £500,000 / £2,000,000 = 25%Each grant then contributes to indirect costs proportionally. A £400,000 grant with £320,000 in allowable direct costs (after excluding equipment and subgrants from the MTDC calculation) generates £80,000 in indirect recovery:
Grant direct costs: £400,000Less: equipment over £5,000 (£20,000)Less: subgrants (£60,000)Modified total direct costs: £320,000Indirect rate: 25%Indirect recovery: £80,000The IT function receives its share of indirect recovery based on its proportion of the indirect cost pool. If IT represents 30% of indirect costs (£150,000 of £500,000), IT receives 30% of each grant’s indirect recovery. From the £80,000 above, IT receives £24,000.
Donor rate limitations
Donors impose caps on indirect rates that constrain IT funding. Common limitations:
| Donor | Typical indirect rate cap |
|---|---|
| USAID | 10% de minimis; negotiated rates accepted |
| FCDO | Varies by mechanism; often 8-13% |
| European Commission | 7% flat rate common |
| UN agencies | 7% for UN partners; varies for others |
| Private foundations | 10-20% typical; some at 0% |
When the organisation’s actual indirect rate exceeds donor caps, the difference comes from unrestricted funds or remains unfunded. An organisation with a 25% actual rate receiving a grant capped at 10% recovers only 40% of the indirect costs that grant generates. The remaining 60% must come from elsewhere or represents unfunded overhead.
The IT funding gap under rate limitations compounds across the portfolio. Consider an organisation with £3 million in grant revenue:
| Grant source | Amount | Rate cap | Recovery | Shortfall at 25% |
|---|---|---|---|---|
| USAID | £1,200,000 | 10% | £120,000 | £180,000 |
| FCDO | £800,000 | 12% | £96,000 | £104,000 |
| EU | £600,000 | 7% | £42,000 | £108,000 |
| Foundation | £400,000 | 15% | £60,000 | £40,000 |
| Total | £3,000,000 | £318,000 | £432,000 |
The organisation needs £750,000 in indirect recovery (25% of £3 million) but receives only £318,000 due to rate caps, leaving £432,000 unfunded. If IT represents 30% of indirect costs, the IT funding gap is £129,600 annually.
Building sustainable IT funding
Sustainable IT funding requires mechanisms that persist across grant cycles and accommodate portfolio volatility. Several approaches reduce dependency on any single funding source.
Indirect rate negotiation
Organisations can negotiate indirect rates with major donors, particularly the US government. A negotiated indirect cost rate agreement (NICRA) with USAID establishes an approved rate based on audited cost data. The negotiation process examines the organisation’s cost structure, validates the allocation methodology, and sets a rate that applies across all grants from that donor.
Negotiated rates typically exceed de minimis rates. An organisation with audited indirect costs supporting a 22% rate can recover that full amount from USAID grants rather than accepting the 10% de minimis. Over a £1 million USAID portfolio, the difference between 10% and 22% represents £120,000 in additional annual recovery.
The negotiation requires documentation of indirect costs by category, allocation methodologies, and historical cost data. IT costs must be clearly identifiable within the indirect cost pool, with supporting documentation for major expenditures. The process takes 6-18 months for initial negotiation.
Cost pool optimisation
IT costs should flow into the indirect pool in a manner that accurately reflects organisational consumption patterns. Misclassification reduces recovery potential.
Consider an organisation that classifies IT staff salaries as programme costs because those staff support programme technology. If IT staff spend 60% of their time on infrastructure and 40% on programme-specific systems, only the 40% should charge to programmes. The 60% belongs in the indirect pool where it contributes to the indirect rate and generates recovery from all grants.
A practical allocation methodology for IT staff time:
IT Manager annual cost: £55,000Time analysis: - Infrastructure (30%) £16,500 --> indirect pool - Shared applications (25%) £13,750 --> indirect pool - Programme A support (20%) £11,000 --> Programme A direct - Programme B support (15%) £8,250 --> Programme B direct - Programme C support (10%) £5,500 --> Programme C directThe £30,250 reaching the indirect pool generates recovery across all grants. The £24,750 in direct charges provides visibility to programmes about their IT support consumption.
Programme-embedded technology
Strategic placement of IT costs within programme budgets ensures technology receives funding regardless of indirect rate limitations. This approach requires IT involvement during proposal development.
When designing a programme requiring mobile data collection, the budget should include:
Hardware and devices as direct equipment costs. Tablets for enumerators, solar chargers for field use, and protective cases charge to the programme. These costs fall outside MTDC calculations (if over threshold) and do not consume indirect capacity.
Platform subscriptions as direct programme costs. Annual KoBoToolbox subscriptions, data hosting fees, and SMS gateway costs charge directly. These appear as programme supplies or contractual services.
Implementation support as direct personnel or consultant costs. Time for IT staff to configure systems, train users, and provide ongoing support charges to the programme. This may require IT staff time allocation across grants or consultant engagement.
Infrastructure uplift as programme costs where justified. If a programme requires network upgrades at field offices, those costs charge to the programme rather than indirect. The upgrade serves the programme and becomes part of the programme’s direct cost base.
Reserve fund accumulation
Organisations with variable indirect recovery benefit from IT reserve funds that smooth year-to-year fluctuations. The mechanism sets aside a portion of above-target recovery during strong years and draws down during weak years.
An IT reserve fund policy might specify:
Target IT budget: £200,000 annuallyReserve fund target: £60,000 (30% of annual budget)Maximum reserve: £100,000 (50% of annual budget)
Accumulation rule: When indirect recovery exceeds target, transfer 50% of excess to reserve until maximum reached
Drawdown rules: When indirect recovery falls short, draw from reserve to maintain minimum £160,000 operating budget (80% of target)
Reserve below £30,000 triggers budget reduction planningThe reserve provides 3-6 months of operating capacity during funding gaps and prevents abrupt IT service reductions when major grants end.
Cost allocation mechanisms
Allocating IT costs to benefiting units requires a methodology that is defensible to auditors, understandable to budget holders, and practical to administer. The methodology comprises cost pools, allocation bases, and calculation procedures.
Single pool allocation
The simplest approach aggregates all IT costs into one pool and allocates using a single base. Headcount serves as the most common base because it correlates broadly with IT consumption and is easy to verify.
+------------------------------------------------------------------+| SINGLE POOL ALLOCATION |+------------------------------------------------------------------+| || +-----------------------------+ || | IT COST POOL | || | | || | Infrastructure: £80,000 | || | Applications: £45,000 | || | Staff: £120,000 | || | Support: £35,000 | || | ---------------------- | || | Total: £280,000 | || +-------------+---------------+ || | || v || +-------------+---------------+ || | ALLOCATION BASE | || | Total headcount: 140 | || | Rate: £2,000 per person | || +-------------+---------------+ || | || +--------+--------+--------+--------+ || | | | | | || v v v v v || Prog A Prog B Prog C Finance Other || 40 staff 35 staff 30 staff 15 staff 20 staff || £80,000 £70,000 £60,000 £30,000 £40,000 || |+------------------------------------------------------------------+Single pool allocation works when IT consumption patterns are roughly uniform across the organisation. It fails when significant variation exists: a data-intensive programme using advanced analytics consumes more IT resources than a capacity-building programme with basic email needs, yet both pay the same per-person rate.
Tiered allocation
Tiered allocation addresses consumption variation by applying different rates to different user categories. The organisation defines tiers based on IT intensity, assigns users to tiers, and applies tier-specific rates.
A three-tier model:
| Tier | Definition | Annual rate |
|---|---|---|
| Basic | Email, documents, basic web applications | £1,200 |
| Standard | Basic plus programme applications, moderate data use | £2,400 |
| Intensive | Standard plus analytics tools, development access, high storage | £4,800 |
Applying these rates to an organisation:
Tier distribution: Basic users: 60 x £1,200 = £72,000 Standard users: 50 x £2,400 = £120,000 Intensive users: 30 x £4,800 = £144,000 Total: 140 users £336,000 recoveredThe tiered approach recovers costs more equitably but requires governance to assign and maintain tier classifications. Users and managers will dispute tier assignments, particularly when budget implications are significant. Annual review of assignments prevents classification drift.
Service-based allocation
The most granular approach allocates costs by service consumption. Each IT service has a defined unit cost, and units charge based on actual usage. This model requires robust service cataloguing and consumption tracking.
Service-based rates for selected services:
| Service | Unit | Unit cost | Measurement method |
|---|---|---|---|
| User account | Per user per month | £45 | Active directory count |
| Per mailbox per month | £8 | Exchange/M365 count | |
| File storage | Per GB per month | £0.15 | Storage system reports |
| Virtual server | Per vCPU per month | £25 | Hypervisor inventory |
| Application hosting | Per application per month | £150 | Application register |
A programme’s monthly IT charge under service-based allocation:
Programme B - Monthly IT consumption:
User accounts: 35 users x £45 = £1,575Email: 35 mailboxes x £8 = £280File storage: 500 GB x £0.15 = £75Shared server: 4 vCPU x £25 = £100Programme app: 1 application x £150 = £150 -------Monthly total: £2,180Annual total: £26,160Service-based allocation provides transparency and creates consumption awareness. Programmes can reduce costs by optimising storage or consolidating applications. The administrative overhead is substantial: tracking consumption, calculating charges, and managing disputes requires dedicated effort.
Implementation considerations
Organisations with minimal IT capacity
Organisations without dedicated IT staff face the challenge of funding technology without a distinct IT function to receive those funds. Technology costs distribute across other budget lines: the finance manager’s laptop appears in finance, the programme database in programme costs, internet under facilities.
The invisible distribution obscures total technology spending and prevents strategic investment decisions. A consolidation exercise identifies technology costs wherever they reside. Review expense categories including equipment, subscriptions, software, internet and telecommunications, repairs and maintenance, and consultants. Tag technology-related expenses to create a virtual IT cost pool.
Once total technology spending is visible, apply informal cost recovery principles. When developing programme budgets, include technology line items based on the consolidated cost analysis. If historical data shows £300 in annual technology costs per staff member, new programme budgets should include £300 per position per year.
Organisations with grant-dependent portfolios
When 80% or more of revenue comes through restricted grants, indirect rate limitations dominate IT funding discussions. The strategies involve maximising allowable direct charging, negotiating rates where possible, and building unrestricted reserves.
Review grant agreements for direct charging opportunities. Some donors permit IT equipment, software, and connectivity as direct costs without affecting indirect capacity. Others allow direct charging of allocated IT support time with appropriate documentation. The 20% of IT costs that can shift from indirect to direct reduces pressure on the constrained indirect rate.
Pursue unrestricted funding deliberately. Individual giving, corporate partnerships, and flexible institutional grants provide unrestricted revenue that funds core IT without rate limitations. Even modest unrestricted revenue, perhaps £50,000 annually, can fund the gap between actual IT needs and what indirect recovery provides.
Organisations with federated structures
Federated organisations with autonomous country offices or affiliates face IT funding decisions at multiple levels. Each entity may have its own indirect rate, cost structure, and donor relationships. Central IT services serving the federation require funding mechanisms that cross entity boundaries.
A federation IT funding model might include:
Membership fees funding shared services. Each affiliate pays an annual fee based on size, covering shared platforms, security services, and coordination. A small affiliate with £500,000 annual revenue might pay £5,000; a large affiliate with £10 million might pay £50,000.
Consortium arrangements for major donors. When a federation receives a multi-country grant, the consortium agreement specifies how IT costs allocate. The lead entity might recover IT costs through its indirect rate and transfer contributions to affiliates providing IT support.
Shared service pricing for optional services. Affiliates choosing to use centrally-provided services, such as a shared CRM or hosted infrastructure, pay consumption-based fees. Affiliates preferring local solutions opt out and bear their own costs.
The governance complexity increases substantially. Decision rights must clarify what IT decisions rest with the centre versus affiliates, how shared investments are approved, and how cost disputes are resolved.
Organisations in rapid growth
Growth strains IT funding when revenue scales faster than the infrastructure to support it. A programme portfolio that doubles in two years requires IT capacity to double, but indirect recovery lags as new grants ramp up and the denominator catches up with the numerator.
Pre-fund growth where forecasts are reliable. If secured grants will bring 50 new staff over 18 months, invest in infrastructure ahead of arrivals. Use unrestricted reserves or bridge funding from organisational reserves with a payback plan from future indirect recovery.
Negotiate IT budget escalation into multi-year grants. A three-year grant should include year-over-year IT budget increases reflecting growth, inflation, and technology refresh. If year one includes £40,000 for IT, years two and three might include £44,000 and £48,000 to accommodate expansion and rising costs.
Avoid the false economy of deferring IT investment during growth. Inadequate infrastructure creates productivity losses, security incidents, and staff frustration that cost more than the deferred investment. The short-term budget saving converts to long-term operational debt.