Project Contracts & Procurement: Types, Risks & Financial Models

Key Concepts & Contract Types

1. Contract Basics: Definition & Purpose

A contract is a legally binding agreement between a buyer (client) and a seller (vendor) that defines:

• Scope of work (deliverables)
• Payment terms (milestones, penalties)
• Responsibilities (who does what)
• Termination clauses (force majeure, breach)

Why contracts matter in software projects?

• Reduce ambiguity → fewer disputes
• Align expectations → better delivery
• Provide legal recourse if things go wrong

classDiagram
    class Contract {
        +Scope of Work
        +Payment Terms
        +Responsibilities
        +Termination Clauses
    }
    class FixedPriceContract {
        +Total Cost Fixed
        +Risk on Vendor
    }
    class TimeAndMaterialContract {
        +Cost Based on Effort
        +Risk on Client
    }
    class CostPlusIncentiveFeeContract {
        +Cost + Fee + Incentives
        +Shared Risk
    }
    Contract <|-- FixedPriceContract
    Contract <|-- TimeAndMaterialContract
    Contract <|-- CostPlusIncentiveFeeContract

2. Three Major Contract Types (with Pros/Cons)

3. Procurement Strategies

Procurement is the process of acquiring goods/services. Common strategies:

1. Competitive Bidding: Multiple vendors submit proposals; client selects the best.
   • Example: NTC’s fiber-optic cable procurement (2023).
2. Sole Sourcing: Buying from a single vendor (e.g., proprietary software like Oracle).
3. Negotiated Contract: Direct talks between client and vendor (common for T&M).
4. Electronic Procurement: Online bidding platforms (e.g., Nepal Government’s e-Governance portal).

sequenceDiagram
    participant Client
    participant Vendor1
    participant Vendor2
    participant Vendor3
    Client->>Vendor1: Submit Proposal (Competitive Bidding)
    Client->>Vendor2: Submit Proposal
    Client->>Vendor3: Submit Proposal
    Vendor1-->>Client: Proposal (NPR 12M)
    Vendor2-->>Client: Proposal (NPR 10M)
    Vendor3-->>Client: Proposal (NPR 14M)
    Client->>Vendor2: Award Contract (Lowest Cost + Quality)
    note right of Client: Example: NTC’s fiber-optic procurement (2023)

Why procurement matters?

• Ensures value for money (not just lowest price).
• Mitigates vendor lock-in (e.g., relying on a single supplier for hardware).
• Reduces corruption risks (transparent bidding processes).

Financial Evaluation of Contracts

1. Key Metrics for Project Selection

Contracts must justify their cost. Use these financial models:

2. Worked Example: Calculating NPV, IRR, and Payback Period

Project Cash Flows (in USD):

Assumptions:

• Discount rate ($r$) = 10% (market rate for Nepalese IT projects).
• Initial investment = $50,000.

Step 1: Calculate NPV

$$\text{NPV}=\frac{-50,000}{(1+0.10{)}^0}+\frac{15,000}{(1+0.10{)}^1}+\frac{15,000}{(1+0.10{)}^2}+\frac{20,000}{(1+0.10{)}^3}+\frac{30,000}{(1+0.10{)}^4}+\frac{25,000}{(1+0.10{)}^5}$$ $$\text{NPV}=-50,000+13,636+12,397+15,026+19,399+16,061=\ast \ast 16,520\ast \ast$$ Interpretation: The project is profitable (NPV > 0).

Step 2: Calculate IRR

Use trial-and-error or financial calculators to find $r$ where NPV = 0. Answer: IRR ≈ 18.5% (higher than the 10% discount rate → accept the project).

Step 3: Calculate Payback Period

Payback Period: 3 years (fully recovered by Year 3).

Discounted Payback Period:

• Year 1: -50,000 + 13,636 = -36,364
• Year 2: -36,364 + 12,397 = -23,967
• Year 3: -23,967 + 15,026 = -8,941
• Year 4: -8,941 + 19,399 = 10,458 (recovered in Year 4).

Why discounted payback is better: Simple payback ignores the time value of money. Discounted payback accounts for inflation and opportunity costs.

In the Real World

1. eSewa’s Payment Gateway Contract (Fixed-Price)

• Scenario: eSewa needed to upgrade its payment gateway for NPR 12 million.
• Contract Type: Fixed-Price (vendor: F1Soft, Nepal).
• Why?
  • Scope was well-defined (PCI-DSS compliance, API integrations).
  • eSewa wanted to avoid cost overruns (critical for financial stability).
• Risk: If F1Soft underestimated work, they bore the cost (not eSewa).

2. Daraz’s AI Recommendation System (Time & Material)

• Scenario: Daraz hired a global AI firm to build a recommendation engine.
• Contract Type: Time & Material (T&M).
• Why?
  • Scope was uncertain (exploratory ML models).
  • Daraz wanted flexibility to pivot based on early results.
• Risk: Costs ballooned to $250,000 (vs. initial $150,000 estimate).

3. Ncell’s 5G Network Procurement (CPIF)

• Scenario: Ncell partnered with Ericsson for 5G rollout.
• Contract Type: Cost Plus Incentive Fee (CPIF).
• Why?
  • High risk (new technology, regulatory hurdles).
  • Shared risk: Ncell paid actual costs + 5% fee + bonuses for on-time delivery.
• Outcome: Project completed 6 months early, saving Ncell NPR 800 million.

Procurement Risks & Mitigation

1. Common Risks in Software Procurement

2. Contract Clauses to Watch For

1. Intellectual Property (IP) Rights:
   • Who owns the code? (e.g., open-source vs. proprietary).
   • Example: If you hire a freelancer to build a mobile app, ensure you own the IP.
2. Confidentiality (NDA):
   • Protects trade secrets (e.g., eSewa’s fraud detection algorithms).
3. Termination Conditions:
   • Can either party walk away? (e.g., if vendor breaches SLA).
4. Liability Limits:
   • Caps on damages (e.g., "vendor liable for up to $50,000 in losses").

Exam Tip

What Examiners Want to See

1. For calculations (NPV, IRR, ROI, Payback):

   • Show all steps (even intermediate cash flows).
   • Use clear tables for cumulative cash flows.
   • Label units (e.g., "in USD" or "in NPR").
   • Example: In the NPV question, break down each year’s discounted cash flow.

2. For contract types:

   • Compare pros/cons in a table (like above).
   • Link to real-world examples (e.g., "Fixed-price is used by eSewa because...").
   • Explain why a contract failed (e.g., "T&M contracts can fail if scope isn’t controlled").

3. For procurement risks:

   • Name the risk + give an example + suggest mitigation.
   • Example:

     "Scope creep is a risk in T&M contracts. For example, Daraz’s AI project cost more because the client kept adding features. Mitigation: Use a change control board to approve new scope."

4. For financial models:

   • Know when to use each:
     • NPV/IRR: For comparing multiple projects.
     • Payback: For quick risk assessment.
     • ROI: For simple profitability checks.
   • Discuss limitations:
     • "NPV assumes reinvestment at the discount rate (may not be realistic)."

5. Diagrams:

   • Draw a precedence network if asked about critical paths (use Mermaid).
   • Show a contract type decision flowchart (e.g., "If scope is uncertain → T&M").

Common Mistakes to Avoid

• Ignoring the discount rate in NPV/IRR calculations.
• Mixing up fixed-price and T&M (e.g., calling T&M "fixed-cost").
• Forgetting to compare IRR with the discount rate (must be > to accept).
• Not explaining assumptions (e.g., "We assume a 10% discount rate based on Nepal’s IT sector average.").

Final Checklist Before the Exam

✅ Can you calculate NPV, IRR, and payback from cash flows? ✅ Do you know when to use fixed-price vs. T&M vs. CPIF? ✅ Can you identify risks in procurement and suggest fixes? ✅ Have you linked concepts to real companies (eSewa, Daraz, Ncell)? ✅ Are you comfortable drawing a precedence network or contract type table?

Where contracts meet hardware: Ncell’s 5G servers run under CPIF agreements (Image: Federal Bureau of Investigation, Public domain, via Wikimedia Commons)