NISM Professor

Investment efficiency KPI

Also written Investment Efficiency · Investment efficiency · Cost per beneficiary KPI

The cost-per-unit-of-outcome measure in a project's KPI set — in the workbook's housing case study, total project cost divided by the number of families benefited.

In plain language

A project can report that it helped many people and still be poor value. The missing number is what each unit of help cost.

The investment efficiency KPI is that number. In the workbook's housing case study it is defined in one line: cost per family for providing housing facilities.

Its formula is equally plain. Total project cost divided by the number of families benefited.

Its target is unusual, and worth noticing. The workbook does not set a rupee ceiling. It says the aim is to optimise cost while ensuring quality housing. So the measure is not "make it as cheap as possible". Driving cost down by building worse houses would score well on this KPI and fail the project.

That is why it never travels alone. In the same case study it sits beside a quality of housing improvement KPI and a stakeholder satisfaction KPI. Read together, the three stop an organisation optimising one at the expense of the others.

This is the same idea that Acumen Fund's BACO Ratio and the Robin Hood Foundation's Benefit-Cost Ratio apply at portfolio level — cost against outcome, in one figure.

How it works

Where it comes from (Chapter 8, the Niwas Project housing case study). The project's KPI set runs to eight items, and investment efficiency is the second:

#KPIMeasureTarget
1Number of families benefitedTotal families given better housing1,265 families, as stated in the project objectives
2Investment efficiencyCost per familyOptimise cost while ensuring quality housing
3Project timeliness(Families benefited on time ÷ total families) × 100100% completion within the specified period
4Stakeholder satisfactionSurvey or feedback from beneficiaries, contractors and local authoritiesHigh satisfaction ratings
5Quality of housing improvement(Families with significantly improved housing ÷ total families) × 100Substantial improvement in living conditions
6Water and sanitation improvement(Families with improved facilities ÷ total families) × 100Enhanced water supply and sanitation
7Transparency and communicationClarity and accessibility of project information to the publicOpen and transparent reporting
8Social inclusionExtent of social inclusion in the project

Note the pattern. KPI 1 is a count. KPI 2 is a cost per count. KPIs 3, 5 and 6 are percentages of the same denominator. So the whole set is anchored on one number — the 1,265 families — and investment efficiency is what converts money into that same unit.

Why "optimise", not "minimise". A cost-per-unit measure is the easiest KPI in any set to game: cut specification, cut supervision, and the ratio improves. The workbook's target wording guards against exactly that by pairing cost with quality housing, and the KPI set adds independent quality and satisfaction measures on the same denominator. An organisation reporting a falling cost per family and a falling quality percentage has not become efficient.

Where the same logic appears elsewhere in the paper. The ICDR minimum disclosures for an NPO require its past social impact to highlight trends in key metrics including the number of beneficiaries, cost per beneficiary and administrative overheads. Chapter 7 names cost effectiveness and the benefit cost ratio among the measures organisations use, and warns that because different organisations pick different ones, programmes in the same sector become incomparable. So a cost-per-unit KPI is only comparable where two projects define the unit the same way.

The formula

Investment efficiency = Total project cost ÷ Number of families benefited

The workbook states this as the formula for the Niwas Project's investment efficiency KPI. The general form is total cost divided by the number of units of outcome delivered, with "unit" defined by what the project actually produces — families housed, patients operated, farmers trained.

Target: optimise cost while ensuring quality. The workbook sets no rupee ceiling for it.

A worked example

The 1,265-family target and the formula are the workbook's; the rupee figures are illustrative.

The Niwas Project repairs and upgrades housing for slum families in Mumbai. Target: 1,265 families.

Year-end position. Total project cost ₹9,48,75,000; families benefited 1,265.

Investment efficiency = ₹9,48,75,000 ÷ 1,265 = ₹75,000 per family.

Now read it against the rest of the KPI set.

KPIResult
Families benefited1,265 of 1,265 → target met
Investment efficiency₹75,000 per family
Project timeliness1,140 of 1,265 on time → 90.1%
Quality of housing improvement1,190 significantly improved → 94.1%
Water and sanitation improvement1,015 with improved facilities → 80.2%

The comparison that gives the number meaning. A second contractor bid the same work at ₹58,000 a family — total ₹7,33,70,000, a saving of ₹2,15,05,000. On investment efficiency alone, that bid wins by a wide margin.

Suppose it had been accepted and the outcome had been: quality improvement 61%, water and sanitation 44%, satisfaction low. Cost per family falls 23% and two of the project's stated purposes fail. The workbook's target — optimise cost while ensuring quality housing — is what rules that trade out.

Why the unit definition matters. A different NPO reports ₹31,000 per family for "housing support" and looks three times as efficient. Read the unit: its work is roof-sheet replacement only, not water and sanitation. Same words, different denominator, and the two figures cannot be compared. This is the incomparability problem Chapter 7 warns about, in one line of a KPI table.

Why NISM asks about it

Chapter 8 (Social Impact Assessment Case Studies, 15% weightage and the heaviest chapter in the paper) sets out the Niwas Project's eight KPIs with their formulas and targets, and investment efficiency is the one with an explicit division formula attached. Chapter 9's ICDR minimum disclosures require cost per beneficiary among the past-impact metrics an NPO must show, and Chapter 7 discusses cost effectiveness and benefit-cost ratios as sector measures.

Chapter 8's questions read the case tables. Expect: what is the formula for the investment efficiency KPI (total project cost ÷ number of families benefited), what was the family target (1,265), and which KPI a given formula belongs to — the percentage formulas for timeliness, quality and sanitation all share the same denominator and are easy to confuse with each other.

Common exam traps

  • The formula is total project cost ÷ families benefited. Not cost ÷ target, and not cost ÷ population of the settlement. The denominator is families actually benefited.
  • The target is to optimise cost, not minimise it. The workbook pairs it with "ensuring quality housing". A question offering "lowest possible cost per family" as the target is wrong.
  • It is one of eight KPIs and cannot be read alone. Timeliness, quality of housing improvement, water and sanitation improvement, satisfaction, transparency and social inclusion are measured on the same project, several on the same denominator.
  • 1,265 is the family target, from the project objectives — attached to KPI 1, not to this one.
  • Cost per family here, cost per beneficiary in Chapter 9. The ICDR disclosure requirement names cost per beneficiary and administrative overheads among the trend metrics. Same idea, different unit; keep the wording of each straight.
  • Cost-per-unit figures are comparable only where the unit is defined the same way. Chapter 7 lists exactly this as a challenge: different organisations use different measures, which makes programmes in the same sector incomparable.
  • Do not confuse it with the BACO Ratio or the Benefit-Cost Ratio. Those are named methodologies of Acumen Fund and the Robin Hood Foundation for comparing options at portfolio level. This is a single project's own KPI.

Where this is taught

Free preparation for NISM Series XXIII

Related terms

← All terms
Something look wrong? Report it