Feasibility & Cost-Benefit Analysis

Economic Feasibility: Costs & Benefits

18 min Lesson 3 of 10

Economic Feasibility: Costs & Benefits

Before an organisation commits budget, people, and time to building or acquiring a new system, it must answer a deceptively simple question: Is this worth doing financially? Economic feasibility is the discipline of answering that question rigorously — not with gut feel or optimism, but with a structured inventory of every cost the project will create and every benefit it can realistically deliver. This lesson builds that inventory from scratch, using three running scenarios: a private clinic deploying a booking system, an online retailer adding a warehouse management system, and a logistics firm replacing its legacy dispatch platform.

Why this matters: Projects that skip or rush economic feasibility routinely underestimate costs by 30–50% and overestimate benefits by a similar margin. The resulting "optimism gap" is the single largest predictor of project failure at the funding stage.

The Two Axes of Cost: One-Time vs Recurring

Every cost in a project falls into one of two buckets. Understanding the distinction is critical because it determines when money flows out and how the investment looks over time.

One-time (capital / non-recurring) costs are paid once to bring the system into existence. They typically spike during the project phase and then stop. Examples include:

Software licences purchased outright (e.g., a one-time perpetual licence for an ERP module at $25,000)
Hardware: servers, networking switches, barcode scanners, kiosk screens
Development and customisation: paying a development team or vendor to build the system
Data migration: extracting, cleaning, transforming, and loading five years of appointment records from a paper-based system into a database — easily a six-week professional-services engagement
Training: workshops, manuals, and instructor time to bring 45 clinic reception staff up to speed
Implementation and go-live support: the professional-services hours needed to configure, test, and launch

Recurring (operational / ongoing) costs continue for the life of the system. They appear every year (or month) in the operating budget and must be covered by the organisation permanently. Examples include:

SaaS subscription fees (e.g., $3,600/year for a cloud booking platform tier)
Maintenance and support contracts (typically 15–20% of software licence cost per year)
Hosting and infrastructure: cloud compute, storage, bandwidth, SSL certificates
Ongoing staff costs: a part-time system administrator, a data analyst who queries the new reporting module
Periodic retraining: whenever the system is upgraded or staff turn over
Consumables and integration fees: SMS gateway charges per message sent, payment-processor transaction fees

Build a 3-to-5-year cost model. Decision-makers who see only year-one costs are frequently surprised when year-two and year-three bills arrive. Present both a "total project cost" and an "annualised total cost of ownership (TCO)" figure to give stakeholders the full picture.

One-time costs create a large upfront spike; recurring costs continue at a lower but permanent level each operating year.

Applying the Cost Framework: Clinic Booking System

Consider a private clinic with 8 doctors and 3 reception staff that wants to deploy an online booking system. A realistic cost breakdown might look like this:

One-time costs:
- Software development / vendor customisation: $18,000
- Data migration (3 years of paper records digitised): $4,500
- Staff training (3 days, external trainer): $2,200
- Hardware upgrade (waiting-room kiosk, receipt printer): $1,800
- Total one-time: $26,500
Recurring annual costs:
- Cloud hosting and software subscription: $3,600/year
- Maintenance and support contract: $2,400/year
- SMS reminder gateway (estimated 8,000 messages/year at $0.04): $320/year
- Total recurring: $6,320/year

Over 3 years: $26,500 + (3 × $6,320) = $45,460 total cost of ownership. That is the number the economic feasibility section must justify against benefits.

The Two Dimensions of Benefits: Tangible vs Intangible

Benefits are the positive outcomes the new system is expected to deliver. They divide into two families, and the distinction matters enormously for how you present them.

Tangible benefits can be directly measured in money. They show up in the profit-and-loss account or the operating budget. Analysts are expected to quantify them with a clear calculation methodology:

Labour savings: The clinic currently employs a part-time receptionist whose sole role is answering booking calls (5 hours/day × 5 days × 52 weeks × $18/hour = $23,400/year). If online self-booking handles 70% of bookings, that role can be eliminated or redeployed, saving approximately $16,380/year.
Reduced no-shows: The clinic has 40 appointments per day; 12% are no-shows at an average revenue loss of $85 per missed slot. Automated SMS reminders are proven to reduce no-show rates by 35–45%. If reminders cut no-shows by 40%: 40 × 0.12 × 0.40 × 85 × 250 working days = $40,800/year recovered revenue.
Error reduction: Double-bookings currently require an administrator to manually resolve 3 cases per week at 45 minutes each. Eliminating double-bookings saves 3 × 0.75 × 52 × $25 = $2,925/year in administrative time.
For the logistics firm: Automating dispatch confirmation eliminates 4 FTE data-entry positions (4 × $32,000 = $128,000/year saved), reduces fuel waste from mis-routed trucks by an estimated 8% ($44,000/year), and cuts late-delivery penalties by 60% ($27,000/year). Total tangible benefit: $199,000/year.

Intangible benefits are real improvements that genuinely create value but resist precise monetary measurement. They must still be listed and described — they influence stakeholder decisions even when they cannot be put in a spreadsheet column:

Improved patient / customer satisfaction: Patients can book at midnight from their phone instead of calling during office hours. This is a real competitive advantage for the clinic, but its financial value depends on how many patients it retains or attracts — hard to pin down exactly.
Enhanced staff morale and reduced burnout: Reception staff no longer spend half their day on repetitive phone bookings. Reduced turnover has a cost saving attached (recruiting and training a replacement receptionist costs $4,000–$8,000), but the morale uplift itself is intangible.
Better management information: Automated booking generates rich data — peak-demand hours, doctor utilisation rates, cancellation patterns — that management never had before. These insights can improve scheduling and revenue, but how much is uncertain at the feasibility stage.
Brand and reputation: An online-bookable clinic appears more professional and tech-forward to younger patients. Difficult to monetise directly.
Compliance and audit readiness: Digital records are easier to audit, search, and comply with data-retention regulations than paper logs. The cost of non-compliance (fines, litigation) is real but probabilistic.

The intangible trap: Some analysts inflate intangible benefits into pseudo-tangible numbers by assigning arbitrary dollar values ("improved brand image: $50,000/year") without any calculation methodology. This destroys credibility. Keep intangibles clearly labelled as intangible, describe them qualitatively, and leave them out of the NPV or payback-period calculation. Reviewers who see inflated intangibles discount the entire document.

Benefits split into tangible (include in financial calculations) and intangible (describe qualitatively; never inflate into fabricated dollar figures).

Documenting the Cost-Benefit Inventory

The output of this analysis phase is a structured cost-benefit inventory — a table listing every identified cost and every identified benefit, their type (one-time / recurring; tangible / intangible), the year in which they occur, and the source of the estimate. This document becomes the input to the financial calculations you will perform in Lesson 4 (NPV, ROI, and Payback Period).

For the clinic example, the 3-year summary looks like this:

Total costs (3 years): $45,460 (one-time $26,500 + recurring $18,960)
Tangible benefits (annual, conservative estimate): $60,105/year (labour savings $16,380 + no-show recovery $40,800 + error reduction $2,925)
Net tangible benefit over 3 years: $180,315 − $45,460 = $134,855 net positive.
Intangible benefits (described, not monetised): patient satisfaction, staff morale, management insights, brand positioning.

That number does not yet account for the time value of money (addressed in Lesson 4), but it immediately tells a clear story: the system returns well over $3 for every $1 invested over 3 years. Even if the benefit estimates are 40% optimistic, the project still pays for itself. This is the kind of defensible, transparent analysis that earns approval from a finance committee.

Show your working. Every estimated benefit should include a one-line calculation: "40 appointments/day × 12% no-show rate × 40% improvement × $85 average revenue × 250 days = $40,800." If a reviewer challenges your numbers, you have a clear methodology to discuss and adjust, rather than a black-box figure that invites rejection.

Common Mistakes in Economic Feasibility

Scope creep blindness: Costs estimated for a tightly scoped system — but the scope expands by 30% during development, and the original cost figure was never updated. Always note the scope assumptions behind each cost estimate.
Forgetting the change cost: The old system does not simply disappear on go-live day. Running two systems in parallel for 3–6 months, converting historical data, and managing the transition all have costs that are routinely omitted.
Counting benefits before they are real: The labour saving from automating data entry exists only after the system is live and staff are retrained. Benefits begin accumulating months after project start, not on day one. Spread them correctly across the timeline.
Ignoring hidden recurring costs: Security patching, annual compliance audits, integration fees charged per-transaction, and the hidden cost of internal staff time spent administering the system. These erode the benefit picture silently.

A credible economic feasibility section does not need perfect numbers — it needs honest numbers, transparent methodology, clearly labelled assumptions, and a sensitivity check ("what if costs are 20% higher and benefits are 20% lower?"). Stakeholders and finance committees are far more likely to approve a realistic analysis with stated risks than an optimistic one that will embarrass everyone when actuals diverge.