The first time an IT services company asked me to help them measure CSR impact, I thought it would be straightforward.
They had the data. They had the dashboards. They had teams whose entire job was tracking metrics. If any sector could measure impact properly, it would be IT services.
I was completely wrong.
Over the years at Marpu Foundation, we have worked with several IT services companies across India. Large multinational firms. Mid-sized Indian companies. Niche technology consultancies. Each engagement revealed something new about why impact measurement is so difficult in this sector.
And more importantly, what actually works.
Here is what I have learned.
The Headcount Trap
IT services companies have massive employee bases. Tens of thousands of people. Sometimes hundreds of thousands spread across cities and countries.
This creates a peculiar problem for CSR impact measurement.
When you have 50,000 employees, even a small percentage participating in volunteering looks impressive in absolute numbers. “5,000 employees volunteered this quarter” sounds like a major achievement. But that is only 10% participation.
I have seen companies celebrate volunteer hours in the millions while actual community impact remains shallow. The metric becomes the goal. And once that happens, everything distorts.
Companies start optimising for participation numbers rather than outcomes. A one-hour webinar on sustainability gets counted the same as a full-day hands-on project. An employee watching a recorded video becomes a “volunteer.” The numbers look good. The impact is questionable.
The first lesson I learned is that headcount-based metrics are almost always misleading in IT services. They tell you about employee engagement, not community change.
Why IT Services Companies Struggle More Than Others
This is not a criticism. It is an observation about structural challenges unique to this sector.
The project-based workforce problem. Most IT services employees are assigned to client projects. Their time is billed. Their calendars are not their own. Taking a day for volunteering means someone else covers their work or the client waits.
This makes sustained engagement nearly impossible. Employees participate when they can, which is unpredictable. Building long-term relationships with communities becomes difficult when volunteer groups change every time.
The geographic spread challenge. A manufacturing company has employees concentrated around its plants. An IT services company has employees scattered across dozens of cities and often working from home.
Running a unified CSR programme across this footprint is genuinely hard. What works in Bangalore may not work in Bhubaneswar. Local contexts differ. NGO partners differ. Community needs differ.
The delivery pressure reality. IT services operates on tight deadlines. Client deliverables do not wait for volunteering activities. When project timelines clash with CSR events, the project always wins.
I have seen beautifully planned volunteering activities cancelled at the last minute because a client escalation happened. This is not a values problem. It is a business reality.
The Metrics That Get Reported vs The Metrics That Matter
Here is a pattern I have noticed across almost every IT services company I have worked with.
The metrics that get reported to leadership and in annual reports are easy to collect but hard to interpret. Number of volunteers. Total volunteer hours. Amount spent on CSR. Number of beneficiaries reached.
These numbers fill slides and satisfy compliance requirements. But they answer the wrong question.
The question is not “how many people did we reach?” The question is “what changed because we reached them?”
A company might report reaching 10,000 students through career guidance sessions. But how many of those students actually changed their career trajectory? How many made better decisions because of that interaction? How many even remember what was discussed?
At Marpu Foundation, we have learned to push for outcome metrics even when they are harder to collect. Did the student enrolment improve? Did the health indicators change? Did the family income increase? Did the water quality get better?
These metrics require follow-up. They require baseline data. They require patience. But they tell you whether your CSR actually worked.
The Quarterly Reporting Pressure
IT services companies report quarterly. Revenue, margins, utilisation, attrition. Everything moves in 90-day cycles.
This rhythm gets imposed on CSR as well. And it creates problems.
Some CSR outcomes take years to materialise. A tree planted today shows its environmental impact in five years. A girl educated today changes her family’s trajectory over a decade. A community health intervention today prevents diseases that would have appeared years later.
Quarterly reporting forces teams to show progress every three months. This pushes CSR towards activities with immediate, visible outputs rather than interventions with deeper, delayed outcomes.
I have seen companies choose a one-day tree plantation over a year-long watershed development project because the plantation shows up in this quarter’s numbers. The watershed project would create more impact but the results would appear in some future leader’s tenure.
The lesson here is that companies serious about impact need to decouple CSR measurement from quarterly cycles. Annual or multi-year assessments capture real change better.
What Actually Works for Measuring Impact
After years of trial and error, here is what I have seen work in IT services companies.
Cohort-based tracking. Instead of measuring all beneficiaries as one blob, track specific cohorts over time. The 200 students who received scholarships in 2024. The 50 women who completed livelihood training in 2025. Follow their progress. Document changes.
Baseline plus endline design. Before starting any CSR intervention, measure current conditions. After completion, measure again. The difference is your impact. Without baselines, you are guessing.
Beneficiary voice inclusion. Numbers tell part of the story. Beneficiary testimonials tell the rest. What do the people you are trying to help actually say? Did their lives change? How?
Third-party verification. Internal teams have incentives to show positive results. External evaluators do not. Periodic third-party assessments add credibility and catch blind spots.
Comparison groups when possible. If you provided computers to 20 schools, what happened in similar schools that did not receive computers? The comparison helps isolate your impact from general trends.
None of this is easy. But it separates CSR that creates change from CSR that creates reports.
The Employee Volunteering Measurement Trap
Employee volunteering deserves special mention because IT services companies invest heavily in it.
The standard measurement is volunteer hours. Employee X contributed 8 hours. The company contributed 100,000 hours this year. This number is easy to track and looks impressive in sustainability reports.
But volunteer hours measure input, not output.
Eight hours of an employee’s time could result in massive impact or zero impact depending on what they did, how well it was organised, and whether the activity was actually needed.
I have seen companies count “volunteering” that beneficiaries did not want or need. Tree plantations in places where trees were not the priority. Teaching sessions to students who needed food more than lectures. The hours were logged. The impact was absent.
Better measurement asks different questions. Did the volunteering solve a problem the community identified? Did the beneficiaries value what was provided? Would they want it again?
At Marpu Foundation, we design volunteering activities based on community needs assessment, not corporate calendars. This alignment is what makes volunteer hours translate into actual outcomes.
The Skills-Based Volunteering Opportunity
IT services companies have one massive advantage that most do not leverage properly.
Their employees have valuable skills. Coding. Data analysis. Project management. Process design. Communication. Training.
When these skills are applied to social sector problems, the impact multiplies far beyond what generic volunteering achieves.
I have seen a team of developers build a beneficiary tracking system for a rural health programme in one weekend hackathon. That system saved hundreds of hours of manual work every month for years afterwards.
The measurement challenge here is attribution. How do you quantify the value of a donated system? How do you track its long-term benefit?
The best approach I have seen is to estimate equivalent cost. What would the NGO have paid for this service commercially? That gives a baseline for value created. Then track usage and outcomes over time to understand actual benefit.
Skills-based volunteering is underdeveloped in most IT services companies. When it works, its impact far exceeds traditional volunteering. The measurement systems just need to catch up.
What I Wish More IT Services Companies Would Understand
After years of working in this space, here is what I wish every CSR leader in IT services would hear.
Measurement is not overhead. It is how you learn what works. Companies that treat impact measurement as a compliance burden miss the opportunity to improve their programmes.
Fewer deeper beats many shallow. Running CSR activities in 100 locations creates impressive geography. Deep engagement in 10 locations creates actual change. Measurement becomes easier and more meaningful when programmes are concentrated.
Time horizons matter. Some impacts take years. Build measurement systems that can wait. Quick wins are fine for employee engagement but not for community transformation.
Partner capability matters. Your NGO partner’s ability to track and report impact determines what you can measure. Invest in partners with strong monitoring systems rather than just low costs.
Stories complement numbers. The best impact reports combine quantitative metrics with qualitative narratives. Numbers show scale. Stories show meaning.
The Bigger Lesson
Working with IT services companies taught me that measurement is never neutral.
What you choose to measure shapes what you choose to do. Measure volunteer hours, and you get activities that maximise hours. Measure lives changed, and you get interventions that change lives.
IT services companies have the analytical capability to measure almost anything. The question is whether they have the courage to measure what actually matters, even when those metrics are harder to collect and slower to show results.
The companies that get this right build CSR programmes that create genuine impact. The companies that do not end up with impressive decks and empty outcomes.
At Marpu Foundation, our work with IT services companies has made us better at impact measurement across all sectors. The rigour these companies demand has pushed us to build better systems, collect better data, and think more carefully about what success actually looks like.
If you are leading CSR at an IT services company and wrestling with impact measurement, I would be happy to share more specifics about what has worked and what has not.
Write to me at hi@kadiriraghuvamsi.com.
