to select ↑↓ to navigate
Presales Playbook

Presales Playbook

Value Engineering & ROI

Value Engineering & ROI

"Klien tidak membeli teknologi — mereka membeli hasil bisnis. Tugas kita adalah menghubungkan investasi dengan outcome yang terukur."


Kapan & Untuk Siapa

Keterangan
Kapan digunakan Saat perlu membangun business case finansial untuk justify investasi, terutama untuk deal > 300M atau saat decision maker butuh angka
Siapa yang pakai Presales Consultant (penyusun), Solution Architect (input teknis), Sales Lead (presenter ke klien)
Prasyarat Discovery selesai (pain points teridentifikasi), Solution Design minimal high-level, Effort Estimation tersedia

Tujuan & Outcome

Tujuan Outcome
Membangun business case yang terukur dan credible Dokumen ROI/business case siap presentasi
Menjustifikasi investasi dengan bahasa yang dipahami CFO/CEO Decision maker mendapat angka untuk approval
Menunjukkan total value — bukan hanya cost Klien melihat investasi sebagai value, bukan expense
Membantu klien memenangkan internal approval Champion punya ammunition untuk internal selling

Definisi Istilah

Istilah Definisi
ROI (Return on Investment) Rasio antara net benefit dengan total investasi, dinyatakan dalam persentase
TCO (Total Cost of Ownership) Total biaya kepemilikan selama lifecycle solusi: acquisition + implementation + operation + maintenance
NPV (Net Present Value) Nilai sekarang dari semua future cash flows (benefits minus costs), didiskon dengan tingkat diskonto tertentu
Payback Period Waktu yang dibutuhkan agar kumulatif benefit sama dengan total investasi
Value Engineering Proses optimasi solusi untuk memaksimalkan value yang diterima klien relatif terhadap investasi
Business Case Dokumen yang menjabarkan justifikasi finansial dan strategis untuk suatu investasi
Cost Avoidance Biaya yang tidak perlu dikeluarkan karena solusi baru (berbeda dari cost savings)
Opportunity Cost Biaya "tidak melakukan apa-apa" — kerugian yang terjadi jika klien tidak invest

Konten Utama

1. Value Engineering Framework

Value Engineering adalah proses memastikan bahwa solusi memberikan maximum value untuk investasi yang dikeluarkan. Ini bukan tentang memotong harga, tapi tentang optimasi.

4 Langkah Value Engineering:

Step 1 IDENTIFY VALUE Map pain points to business outcomes Step 2 QUANTIFY VALUE Assign IDR value to each value driver Step 3 OPTIMIZE DELIVERY Adjust scope & approach utk maximize ROI Step 4 VALIDATE & PRESENT Review dgn klien, align expectations

Step 1: Identify Value Drivers

Map setiap pain point dari Discovery ke kategori value:

Kategori Value Deskripsi Contoh
Revenue Increase Solusi membantu klien menghasilkan pendapatan baru atau lebih banyak Faster time-to-market, new digital channel
Cost Reduction Solusi mengurangi biaya operasional existing Automation mengurangi manual work, reduce headcount need
Cost Avoidance Solusi menghindari biaya yang akan muncul di masa depan Avoid penalty/fine, avoid system failure cost
Productivity Gain Solusi meningkatkan output per unit input Proses yang 2 hari menjadi 15 menit
Risk Reduction Solusi mengurangi risiko bisnis Compliance, data security, business continuity
Strategic Value Solusi mendukung tujuan strategis jangka panjang Digital transformation, market positioning

Step 2: Quantify Value

Untuk setiap value driver, hitung dampak finansialnya:

Quantification Template:

Value Driver Current State Future State Improvement Annual Value (IDR)
Order processing time 2 hari/order 15 menit/order 98% faster Rp 480M (= 2 FTE saved × Rp 20M/bulan)
Error rate 5% order errors 0.5% errors 90% reduction Rp 150M (= rework cost avoided)
Reporting time 3 hari/bulan Real-time Eliminate Rp 36M (= 0.5 FTE freed)
Late delivery penalty Rp 50M/tahun Rp 5M/tahun 90% reduction Rp 45M
Total Annual Value Rp 711M

Tips Quantification:

  • Gunakan data riil dari Discovery (bukan asumsi)
  • Jika klien tidak punya data, gunakan industry benchmarks
  • Selalu conservative — better to under-promise and over-deliver
  • Bedakan antara hard savings (measurable) dan soft benefits (estimated)
  • Validasi angka dengan klien sebelum finalize

Step 3: Optimize Delivery

Setelah value teridentifikasi, optimasi solusi untuk maximize ROI:

Teknik Deskripsi Kapan
Phasing Deliver high-value items dulu Budget terbatas, mau quick win
MVP Approach Launch dengan fitur minimum viable Time-to-market penting
Scope Optimization Hapus nice-to-have, fokus must-have ROI perlu diperbaiki
Technology Substitution Ganti komponen mahal dengan alternatif Margin tipis
Resource Mix Kombinasi senior + junior untuk cost efficiency Cost optimization
Automation Automate testing/deployment untuk reduce effort Repetitive tasks

Step 4: Validate & Present

  • Review business case dengan klien (champion) sebelum formal presentation
  • Adjust angka berdasarkan feedback
  • Present ke decision maker dengan format executive
  • Link setiap angka ke data yang bisa diverifikasi

2. ROI Calculation Methodology

Basic ROI Formula

ROI = (Total Benefits - Total Investment) / Total Investment × 100%

Contoh:

  • Total Benefits (3 tahun): Rp 2,133M
  • Total Investment (implementation + 3 tahun operations): Rp 800M
  • ROI = (2,133 - 800) / 800 × 100% = 166.6%

3-Year ROI Model (Standard)

Divistant menggunakan model 3 tahun sebagai standar, karena kebanyakan IT project memiliki lifecycle 3-5 tahun.

Template 3-Year Model:

Item Year 0 Year 1 Year 2 Year 3 Total
INVESTMENT
Implementation cost (500M) (500M)
License/subscription (50M) (50M) (50M) (150M)
Support & maintenance (30M) (30M) (30M) (90M)
Internal cost (client) (50M) (10M) (10M) (10M) (80M)
Total Investment (550M) (90M) (90M) (90M) (820M)
BENEFITS
Cost reduction 300M 350M 400M 1,050M
Productivity gain 200M 250M 300M 750M
Revenue increase 100M 200M 300M 600M
Cost avoidance 50M 50M 50M 150M
Total Benefits 0 650M 850M 1,050M 2,550M
Net Benefit (550M) 560M 760M 960M 1,730M
Cumulative (550M) 10M 770M 1,730M

Key Metrics dari contoh di atas:

  • ROI: 211% (3 tahun)
  • Payback Period: ~12 bulan
  • NPV (discount rate 10%): Rp 1,285M

3. TCO Comparison

TCO comparison sangat powerful untuk melawan objeksi "vendor lain lebih murah":

TCO Components:

Kategori Components Sering Tersembunyi?
Acquisition License, setup fee Tidak
Implementation Development, customization, migration, training Sebagian
Operation Hosting, subscription, support, maintenance Sebagian
Hidden Costs Customization tambahan, upgrade, re-training, downtime Ya
Exit Costs Migration out, data export, contract termination Ya

TCO Comparison Template:

Cost Category Divistant (3yr) Alternative A (3yr) Alternative B (3yr)
License/subscription 150M 300M 0 (open-source)
Implementation 500M 400M 700M
Annual support 90M 120M 200M
Customization (est.) 100M 250M 150M
Training 50M 80M 100M
Infrastructure 100M 150M 200M
Total TCO 990M 1,300M 1,350M

4. Business Case Document Structure

  1. Executive Summary — 1 halaman: masalah, solusi, investasi, ROI headline
  2. Business Problem — Pain points dan cost of inaction
  3. Proposed Solution — Ringkasan solusi (reference proposal)
  4. Value Analysis — Value drivers dan quantification
  5. Investment Summary — Breakdown investasi
  6. ROI Model — 3-year projection, payback period, NPV
  7. TCO Comparison — Jika applicable (competitive situation)
  8. Risk Analysis — Risiko implementasi dan mitigasi
  9. Recommendation — Clear call-to-action

5. Cost of Inaction (COI)

Salah satu alat paling powerful: tunjukkan berapa biaya jika klien tidak melakukan apa-apa.

COI Formula:

Cost of Inaction = Current annual losses × Years of delay

Contoh:

  • Manual process cost: Rp 480M/tahun (2 FTE + error cost)
  • Delay 1 tahun = Rp 480M yang terbuang
  • Delay 2 tahun = Rp 960M yang terbuang
  • Investasi solusi: Rp 500M
  • "Setiap tahun menunda berarti membakar Rp 480M. Investasi Rp 500M akan membayar dirinya sendiri dalam 12 bulan."

6. Benchmark Data per Service Domain

Gunakan benchmark sebagai referensi saat klien tidak punya data internal:

Service Domain Typical ROI Range Payback Period Key Value Drivers
ERP Implementation 150-300% (3yr) 12-18 bulan Process automation, visibility, compliance
E-commerce Integration 200-400% (3yr) 6-12 bulan Revenue channel, order automation
Custom Application 100-250% (3yr) 12-24 bulan Process digitization, productivity
Data & Analytics 150-350% (3yr) 9-15 bulan Better decisions, revenue optimization
System Integration 100-200% (3yr) 12-18 bulan Eliminate silos, reduce manual work
Managed Services 120-180% (3yr) 6-12 bulan Cost predictability, reduced downtime

Note: Angka benchmark bersifat general. Selalu adjust berdasarkan konteks klien.

7. Presenting ROI ke Decision Makers

Format untuk CFO

CFO care about: financial return, risk, cash flow impact.

Key slides:

  1. Investment summary (1 slide)
  2. 3-year ROI model (1 slide)
  3. Payback period visual (1 slide)
  4. Risk quantification (1 slide)

Language: "Investasi Rp 500M menghasilkan net benefit Rp 1.7M dalam 3 tahun, dengan payback period 12 bulan dan ROI 211%."

Format untuk CEO

CEO care about: strategic alignment, competitive advantage, speed.

Key slides:

  1. Strategic value alignment (1 slide)
  2. Competitive positioning impact (1 slide)
  3. Timeline to value (1 slide)
  4. Summary recommendation (1 slide)

Language: "Solusi ini memposisikan [Perusahaan] untuk menangkap peluang digital di pasar yang bergerak cepat, dengan time-to-value 6 bulan untuk quick wins pertama."

Format untuk CTO

CTO care about: technical debt reduction, scalability, future-proofing.

Key slides:

  1. Technical debt elimination value (1 slide)
  2. Scalability roadmap (1 slide)
  3. TCO comparison (1 slide)
  4. Technical risk mitigation (1 slide)

8. BizOps CRM Integration

Track value engineering progress di Opportunity:

== VALUE ENGINEERING ==
Business Case Status: [In Progress / Completed / Presented]
Total Investment: IDR [amount]
Projected Annual Benefit: IDR [amount]
ROI (3yr): [%]
Payback Period: [months]

Key Value Drivers:
1. [driver] — IDR [value]
2. [driver] — IDR [value]
3. [driver] — IDR [value]

Client Validation: [Validated / Pending / Not Yet]
Presentation Date: [tanggal]
Decision Maker Response: [summary]

Template & Aset

📘 Know (Untuk dipelajari)

  • Value Engineering methodology (SAVE International)
  • ROI/TCO calculation best practices
  • Industry benchmark data (Gartner, Forrester, IDC)

📊 Show (Untuk digunakan)

  • ROI Calculator — Spreadsheet dengan formula ROI, NPV, Payback Period
  • TCO Comparison Template — Template perbandingan TCO multi-vendor
  • Business Case Template — Template dokumen business case
  • Value Driver Mapping Worksheet — Template untuk mapping pain points ke value
  • Executive Presentation Template — Slide deck untuk presentasi ke decision maker

📤 Share (Untuk dikirim ke klien)

  • Business Case document (PDF)
  • ROI summary (1-pager untuk champion internal selling)
  • Executive presentation deck

Skenario Umum

Skenario 1: ROI untuk ERP Implementation — Klien Manufaktur

Situasi: Klien manufaktur dengan 200 karyawan masih pakai spreadsheet. Investasi ERP Rp 500M.

Value Engineering:

  1. Identify: Manual inventory (2 FTE), order errors (5%), reporting delay (3 hari), stock-out losses
  2. Quantify:
    • FTE savings: Rp 480M/3yr
    • Error reduction: Rp 150M/3yr
    • Stock-out reduction: Rp 300M/3yr
    • Compliance (audit ready): Rp 100M/3yr (cost avoidance)
    • Total benefits: Rp 1,030M/3yr
  3. ROI: (1,030 - 600 TCO) / 600 = 71.7% (3yr)
  4. Payback: ~18 bulan

Presentasi: Focus ke CFO — payback period dan hard savings.

Skenario 2: TCO Comparison — Melawan Vendor Lebih Murah

Situasi: Kompetitor menawarkan Rp 350M vs Divistant Rp 500M. Klien condong ke harga murah.

Value Engineering:

  1. Build TCO 3 tahun untuk kedua vendor
  2. Divistant TCO: Rp 500M + Rp 120M (3yr support) = Rp 620M
  3. Competitor TCO: Rp 350M + Rp 300M (customization) + Rp 200M (support premium) = Rp 850M
  4. Hidden costs competitor: limited integration (tambahan Rp 150M), re-training (Rp 50M)
  5. Adjusted competitor TCO: Rp 1,050M

Presentasi: "Investasi awal kami memang lebih tinggi, tapi total 3-year cost Anda dengan Divistant Rp 430M lebih hemat. Dan itu belum termasuk risiko vendor lock-in."

Skenario 3: Business Case untuk Internal Approval — Bantu Champion

Situasi: Champion (IT Director) perlu approval dari Board untuk budget Rp 800M. Board sangat financial-oriented.

Value Engineering:

  1. Build comprehensive business case document
  2. ROI: 211% (3 tahun), Payback: 12 bulan
  3. Cost of Inaction: Rp 650M/tahun hilang (manual process + lost opportunity)
  4. Sediakan 1-pager executive summary untuk Board deck
  5. Offer untuk co-present dengan IT Director (jika diizinkan)
  6. Prepare FAQ untuk anticipated Board questions

Hasil: Board approve. Champion berterima kasih karena business case mempermudah approval.

Skenario 4: Value Engineering untuk Reduce Scope — Budget Constraint

Situasi: Klien tertarik tapi budget hanya 60% dari proposal. Tidak mau financing.

Value Engineering:

  1. Prioritasi value drivers: rank by annual value / implementation cost
  2. Identify Phase 1 (60% budget) yang deliver 80% value:
    • Core ERP: finance + inventory (highest value drivers)
    • Skip: HR module, advanced reporting (lower priority)
  3. Phase 2 roadmap untuk remaining scope
  4. New ROI Phase 1: masih >100% karena fokus ke high-value items
  5. Present sebagai smart phasing, bukan scope cut

Hasil: Klien approve Phase 1. Phase 2 dianggarkan tahun depan berdasarkan Phase 1 success.


Checklist

Business Case Development Checklist

Data Collection:

  • Pain points teridentifikasi dan terkuantifikasi dari Discovery
  • Current costs terdokumentasi (FTE, error cost, penalties, lost revenue)
  • Client data divalidasi (bukan asumsi sepihak)
  • Industry benchmarks disiapkan sebagai supporting evidence
  • Competitive pricing data tersedia (jika TCO comparison)

Analysis:

  • Value drivers mapped ke kategori (revenue, cost, productivity, risk)
  • Each value driver quantified dalam IDR per tahun
  • Investment breakdown lengkap (implementation + ongoing)
  • 3-year ROI model calculated
  • Payback period calculated
  • NPV calculated (discount rate agreed)
  • TCO comparison built (jika competitive)
  • Cost of Inaction calculated
  • Conservative assumptions used throughout

Presentation:

  • Business case document drafted
  • Executive 1-pager prepared
  • Presentation deck customized per audience (CFO/CEO/CTO)
  • Key numbers validated dengan klien champion
  • FAQ prepared untuk anticipated questions
  • BizOps CRM updated with value engineering data

Tanggung Jawab (RACI)

Aktivitas Presales Consultant Solution Architect Sales Lead Sales Director Managing Director
Identify value drivers R C C I I
Quantify value (financial) R C C I I
Build ROI model R C I I I
Build TCO comparison R C C I I
Value engineering optimization C R C I I
Write business case document R C C I I
Validate numbers with client C I R I I
Present to CFO/CEO C I R C I
Present to CTO C R C I I
Support champion internal selling C I R C I
Log value engineering di CRM R I C I I

Legenda: R = Responsible, A = Accountable, C = Consulted, I = Informed


Referensi

  • Internal: Discovery Process, Solution Design, Effort Estimation, Proposal Writing
  • Framework: SAVE International (Value Engineering), Forrester TEI (Total Economic Impact)
  • Standard: ISO 31000 (Risk Management), PMBOK Cost Management
  • Benchmark: Gartner IT Spending Benchmarks, Forrester ROI studies, IDC MarketScape
  • Tools: BizOps CRM (Opportunity tracking), ROI Calculator (spreadsheet)
Last updated 3 months ago
Was this helpful?
Thanks!