Return on IT projects: How to measure value

Introduction

"Can you build us an app?" "How much does it cost?" "1.5 million kroner." "What do we get for the money?"

This is a conversation we often have at Hyperbolic. And the right answer is not "An app with these features." The right answer is "Value that exceeds the investment."

But how do you measure the value of IT? A new CRM does not directly deliver revenue. A dashboard does not produce products. Automation is invisible when it works.

Returns on IT projects are often difficult to quantify, but they are crucial. Without a clear business case, IT investments are the first to be cut when budgets tighten.

Why returns are often ignored

"We just need to have it": Technology for technology's sake. "Everyone is using Kubernetes, so we have to as well." But why? What is the business value?

"It’s too complex to measure": Often a legitimate concern. How do you value "a better user experience"?

"We don’t have a baseline": "How long does it take now?" "I don’t know, we have never measured it."

The result: Projects approved without a solid business case, hard to justify continued funding, impossible to evaluate success.

Basic returns

Formula: Return = (Gain - Investment) / Investment × 100%

Example:

• Investment: 1 million kroner (development, implementation, training)

• Annual gain: 400,000 kroner (savings + increased revenue)

• Return in the first year: (400,000 - 1,000,000) / 1,000,000 = -60% (negative, as expected)

• Return over 3 years: (1,200,000 - 1,000,000) / 1,000,000 = 20%

• Payback period: 2.5 years

But it is rarely that simple.

Quantifiable gains

1. Direct cost savings

Easiest to measure and most convincing to stakeholders.

Examples:

• Automation: Manual process takes 40 hours a week, costs 500 kroner per hour. Automation reduces it to 5 hours. Savings: 35 × 500 = 17,500 kroner per week = 910,000 kroner per year

• License consolidation: Replaces 5 separate tools with one integrated system. Savings: 300,000 kroner per year in licenses

• Infrastructure optimization: Migration to the cloud with rightsizing. Savings: 40% on infrastructure = 500,000 kroner per year

Example from Hyperbolic: Automating invoice processing for a client:

• Before: 2 full-time employees processed 5,000 invoices monthly manually

• After: AI system processes 90%, humans only handle exceptions (500 monthly)

• Savings: 1.8 full-time employees = about 900,000 kroner per year

• Investment: 1.2 million kroner (development + implementation)

• Return: Payback in 16 months

2. Productivity improvements

Employees use time more efficiently.

Measuring:

• Time measurement before/after: Measure current time spent, compare it with after implementation

• Throughput: How many work units per time period?

• Reduced cycle time: Time from start to completion

Example - CRM implementation:

• Before: Salespeople spend 10 hours a week on administrative tasks (data entry, searching for information)

• After: CRM automation reduces it to 3 hours a week

• Team size: 20 salespeople

• Time saved: 20 × 7 hours = 140 hours a week

• Value: If salespeople can use the saved time for sales, and each hour of sales generates 2,000 kroner in margin, then 140 × 2,000 = 280,000 kroner a week

Crucial: Released time must actually be used productively. If salespeople just go home earlier, there is no business value.

3. Revenue acceleration

IT that directly affects revenue.

Examples:

• E-commerce platform: Better user experience leads to higher conversion

• Sales tools: CRM with better pipeline visibility → higher win rates

• Time-to-market: Faster product launches

Measuring:

• Improvement of conversion rate: Before: 2%, After: 2.5%. With 1 million visitors a year that’s 5,000 extra customers

• Increase in average deal size: Better insights → better targeting → higher deal sizes

• Revenue from new channels: Mobile app opens a new customer segment

Soft gains (harder to quantify)

1. Risk reduction

Improvements in compliance:

• What is the potential fine for non-compliance?

• What is the likelihood of that?

• Expected value = Potential cost × Probability

Example - Part 11 compliance project:

• Potential FDA warning letter → consent decree → production halt

• Estimated cost: 75 million kroner

• Probability without project: 15% over 3 years

• Expected value avoided: 11.25 million kroner

• Project cost: 3.5 million kroner

• Return: (11.25 - 3.5) / 3.5 = 221%

Safety improvements:

• Average cost of data breaches in the pharmaceutical industry: 35 million kroner

• Project reduces risk from 10% to 2% annually

• Expected value: 8% × 35 million = 2.8 million kroner per year

2. Improved decision making

Dashboard or analytics platform provides better insights.

How to value?:

• Faster decisions: Reduces time to decision from weeks to days. What is the cost of delay?

• Better decisions: Hard to measure directly, but can use surrogate measures

Example:

• Production dashboard identifies inefficiencies earlier

• On average, catches problems 2 weeks earlier than before

• Every week inefficiency costs 100,000 kroner

• 10 such problems identified per year

• Value: 10 × 2 weeks × 100,000 = 2 million kroner per year

3. Employee satisfaction

Frustrating IT drives employee turnover. Good IT improves retention.

Valuation:

• Cost of replacing an employee: about 100-150% of annual salary

• If better IT reduces turnover from 15% to 12%

• For 100 employees, average salary 600,000:

  • 3% × 100 × 600,000 × 1.25 = 2.25 million kroner per year

4. Customer satisfaction

Better IT can improve the customer experience.

Measurements:

• Improvement of Net Promoter Score

• Customer retention rate

• Customer lifetime value

Example - Customer portal:

• Customers can retrieve information themselves instead of calling

• Reduces support calls by 40%

• Support cost down 200,000 kroner per year

• Plus: Customer satisfaction up, retention improves by 5%

• 5% improvement in retention on a customer base worth 10 million kroner annually = 500,000 kroner per year

• Total value: 700,000 kroner per year

Building a business case

Template we use at Hyperbolic:

1. Executive summary

• Problem description

• Proposed solution

• Required investment

• Expected return and payback period

• Key risks

2. Current state analysis

• How do things work today?

• What are the pain points?

• Quantify current costs/inefficiencies

• Baseline measurements

3. Proposed solution

• What will we build/implement?

• How does it address pain points

• Overall scope

4. Financial analysis

• Investment: Development, licenses, hardware, training, ongoing maintenance

• Gains: Year-over-year breakdown

• Return calculation: Multiple scenarios (best/expected/worst)

• Payback period

• Net present value: Taking into account the time value of money

5. Risks and mitigations

• Technical risks

• Business risks

• Mitigation strategies

6. Success measures

• How do we measure if the project was successful?

• Specific, measurable KPIs

7. Implementation plan

• Overall timeline

• Resource needs

• Dependencies

Real-life example: ERP replacement business case

Problem: Outdated ERP, 15 years old, high maintenance cost, limited functionality, blocking growth.

Investment:

• Software licenses: 2 million kroner (3-year)

• Implementation: 3 million kroner

• Training: 300,000 kroner

• Data migration: 500,000 kroner

• Total: 5.8 million kroner

Gains (annual):

• Reduced maintenance cost: 800,000 kroner per year (old system had high support costs)

• Eliminated manual workarounds: 2 full-time employees saved = 1.2 million kroner per year

• Reduced inventory holding costs: Better planning = 500,000 kroner per year

• Faster month end close: Finance department efficiency = 200,000 kroner per year

• Total: 2.7 million kroner per year

Return analysis:

• Year 1: (2.7 - 5.8) / 5.8 = -53% (expected, payback period)

• Year 3: (8.1 - 5.8) / 5.8 = 40%

• Payback period: 2.2 years

• 5-year net present value (8% discount rate): 4.2 million kroner

Intangible benefits (noted but not financially quantified):

• Better data for decision making

• Improved customer service (faster order processing)

• Platform for growth (scalable, supports expansion)

Outcome: Project approved, implemented, achieved 95% of expected savings.

Common pitfalls

Pitfall 1: Overstating benefits

Optimism bias is real.

Mitigation:

• Use conservative estimates

• Build in contingencies

• Multiple scenarios (best/expected/worst)

• Historical data where possible

Pitfall 2: Underestimating costs

Especially ongoing costs can be overlooked.

Hidden costs:

• Maintenance and support

• Training for new employees

• Future upgrades

• Integration with future systems

Mitigation: Include 5-year total cost of ownership, not just up-front.

Pitfall 3: Ignoring opportunity cost

Resources (people, money) used for Project A cannot be used for Project B.

Question: Is this the best use of resources, or would another project yield better returns?

Pitfall 4: No post-implementation review

Many projects have a business case, but no follow-up on whether benefits were actually realized.

Best practices:

• 6-month check: Early indicator, chance to adjust

• 1-year review: Comprehensive evaluation

• Document experiences: Which assumptions were right/wrong?

Measuring ongoing value

Return is not a one-time calculation at project start. Track continuously.

Dashboard of key metrics:

• Cost savings realized vs expected

• Productivity measures

• User adoption (if benefits require use)

• Business KPIs affected by the system

Example - After automation project:

• Monthly dashboard shows:

  • Transactions processed automatically (goal: 90%)

  • Time saved (goal: 35 hours per week)

  • Error rate (goal: under 1%)

  • Return to date vs expected

If measurements underperform:

• Investigate why (technical issues? User adoption? Incorrect assumptions?)

• Take corrective action

• Adjust future projections

Beyond return: Strategic value

Not everything can be reduced to return calculations.

Strategic imperatives:

• Regulatory compliance: Must have, regardless of return

• Competitive parity: If competitors have capability, need to match

• Platform for the future: Enables future innovation

But: Even strategic projects must have clear value articulation. "Strategic" cannot be an excuse for wasteful spending.

Framework:

• Acknowledge that it is strategic

• Quantify what can be quantified

• Clearly articulate non-quantifiable value

• Define success measures

Conclusion

Returns on IT projects are not about perfect precision. It’s about:

1. Rigour in thinking: Understand costs and benefits

2. Realistic expectations: Conservative estimates

3. Clear value proposition: Why is this worth the money?

4. Accountability: Track and report on realized value

At Hyperbolic, we help customers build robust business cases for IT investments. We combine technical expertise with business understanding to ensure projects deliver real value.

Contact us for help evaluating and maximizing returns on your IT projects.