RFP & RFI Response
"Jangan hanya menjawab pertanyaan RFP — gunakan setiap jawaban sebagai kesempatan untuk menunjukkan pemahaman dan differensiasi."
Kapan & Untuk Siapa
| Keterangan | |
|---|---|
| Kapan digunakan | Saat menerima dokumen formal RFI, RFP, atau RFQ dari klien atau calon klien |
| Siapa yang pakai | Response Lead / Presales Consultant (koordinator), Solution Architect (teknis), Sales Lead (komersial), SME (domain) |
| Prasyarat | Dokumen RFI/RFP/RFQ diterima, Bid/No-Bid decision sudah diambil |
Tujuan & Outcome
| Tujuan | Outcome |
|---|---|
| Memberikan respons yang lengkap, compliance, dan persuasif | Dokumen respons yang memenuhi semua mandatory requirements |
| Menunjukkan diferensiasi Divistant dari kompetitor | Masuk shortlist / memenangkan tender |
| Membangun hubungan dengan procurement/evaluation team | Akses ke decision maker untuk presentasi/klarifikasi |
| Mengumpulkan intelligence tentang kebutuhan klien | Input untuk future engagement meskipun tidak menang |
Definisi Istilah
| Istilah | Definisi |
|---|---|
| RFI (Request for Information) | Dokumen eksplorasi dari klien untuk mengumpulkan informasi tentang vendor dan kapabilitas — belum tentu ada project konkret |
| RFP (Request for Proposal) | Dokumen formal yang meminta proposal lengkap dengan solusi teknis, approach, tim, dan harga |
| RFQ (Request for Quotation) | Dokumen yang fokus pada harga/penawaran — biasanya scope sudah jelas |
| Bid/No-Bid | Keputusan internal apakah akan merespons RFP/RFI atau tidak |
| Compliance Matrix | Tabel yang memetakan setiap requirement RFP ke bagian respons yang menjawabnya |
| Incumbent | Vendor yang saat ini sudah melayani klien — biasanya punya advantage |
| Evaluation Criteria | Kriteria yang digunakan klien untuk menilai respons (biasanya ada di dokumen RFP) |
| Shortlist | Daftar vendor terpilih yang akan di-invite untuk presentasi/klarifikasi |
| BAFO (Best and Final Offer) | Penawaran terakhir yang diminta setelah negosiasi awal |
Konten Utama
1. RFI vs RFP vs RFQ — Perbedaan & Pendekatan
| Aspek | RFI | RFP | RFQ |
|---|---|---|---|
| Tujuan klien | Explore opsi vendor & solusi | Pilih vendor terbaik | Dapatkan harga terbaik |
| Formalitas | Low-Medium | High | Medium |
| Scope klien | Belum jelas | Cukup detail | Sudah fix |
| Response time | 5-10 hari kerja | 10-20 hari kerja | 3-7 hari kerja |
| Effort respons | Low (5-15 halaman) | High (30-100+ halaman) | Medium (10-20 halaman) |
| Fokus respons | Kapabilitas & experience | Solusi lengkap + harga | Harga + T&C |
| Win strategy | Stand out, get on radar | Best solution + value | Competitive price + quality |
| Follow-up | Biasanya ada RFP setelahnya | Presentasi / BAFO | PO / contract |
2. Bid/No-Bid Decision Framework
Sebelum menginvestasikan effort untuk merespons, lakukan assessment terstruktur:
Bid Criteria (Scoring 0-10 per item)
| Kriteria | Bobot | Score Guide |
|---|---|---|
| Kapabilitas match | 20% | 10 = core expertise; 5 = bisa tapi stretch; 0 = di luar kapabilitas |
| Win probability | 20% | 10 = strong position; 5 = competitive; 0 = long shot |
| Budget realistis | 15% | 10 = budget jelas & sesuai; 5 = tidak jelas; 0 = unrealistic |
| Timeline achievable | 10% | 10 = comfortable; 5 = tight; 0 = impossible |
| Relationship/access | 15% | 10 = established relationship; 5 = some contact; 0 = blind bid |
| Strategic value | 10% | 10 = flagship account; 5 = nice to have; 0 = no strategic value |
| Resource availability | 10% | 10 = team ready; 5 = need to hire/partner; 0 = no resource |
Decision Matrix:
| Total Score | Decision | Action |
|---|---|---|
| ≥ 70 | BID | Full response, invest maximum effort |
| 50 - 69 | CONDITIONAL BID | Respond with caveats, manage effort |
| 30 - 49 | LEAN BID | Minimal response, fokus ke differentiator saja |
| < 30 | NO-BID | Decline formally, maintain relationship |
No-Bid Red Flags (auto No-Bid jika ≥2 terpenuhi):
- Requirement di luar core expertise dan tidak ada partner
- Incumbent advantage sangat kuat + kita tidak punya inside track
- Timeline respons < 5 hari untuk RFP complex
- Budget sudah ditetapkan di bawah minimum margin kita
- RFP ditulis dengan spec yang jelas mengarah ke vendor lain
No-Bid Response Template
Meskipun No-Bid, selalu kirim respons formal untuk menjaga hubungan:
Dear [Nama],
Thank you for including Divistant in your [RFP/RFI] process for [nama project].
After careful evaluation, we have decided not to submit a response at this time
as [pilih alasan yang diplomatik: current resource commitments / scope alignment].
We remain interested in future opportunities and would welcome the chance to
support [nama perusahaan] in areas such as [sebutkan 1-2 area relevan].
Please keep us in mind for upcoming initiatives.
Best regards,
[Nama]
3. Response Framework — 5-Step Process
Step 1: Kickoff & Planning (Hari 1-2)
Aktivitas:
- Baca seluruh dokumen RFP/RFI secara menyeluruh
- Identifikasi semua mandatory requirements dan evaluation criteria
- Buat compliance matrix: requirement → section → owner
- Assemble response team dan assign sections
- Set internal deadlines (minimal 2 hari sebelum submission deadline)
- Identifikasi pertanyaan klarifikasi untuk klien
Compliance Matrix Format:
| # | RFP Requirement | Section | Mandatory? | Owner | Status | Compliance |
|---|---|---|---|---|---|---|
| 1 | System must support 1000 concurrent users | 4.2 | Ya | SA | Draft | Full |
| 2 | 24/7 support SLA | 5.1 | Ya | PM | Pending | Partial |
| 3 | ISO 27001 certified | 6.3 | Ya | QA | Done | Full |
| 4 | On-premise deployment option | 4.5 | Tidak | SA | Draft | Non-comply |
Compliance Levels:
- Full — Fully compliant, bisa memenuhi sepenuhnya
- Partial — Bisa memenuhi sebagian, perlu explain workaround
- Non-comply — Tidak bisa memenuhi, perlu explain alternatif
- Exceed — Melebihi requirement, gunakan sebagai differentiator
Step 2: Clarification (Hari 2-3)
- Kirim pertanyaan klarifikasi ke klien dalam format terstruktur
- Tanyakan: ambiguitas requirement, evaluation criteria weighting, budget range, incumbent info
- Gunakan kesempatan bertanya untuk menunjukkan depth of understanding
- Catat semua jawaban klarifikasi — ini jadi input penting
Step 3: Draft Response (Hari 3-12)
Struktur Respons RFP Standard:
| Section | Konten | Owner |
|---|---|---|
| Cover Letter | Ringkasan value proposition | Sales Lead |
| Executive Summary | PESO format (lihat Proposal Writing) | Presales Consultant |
| Company Overview | Profile, credentials, relevance | Presales Consultant |
| Understanding of Requirements | Bukti pemahaman kebutuhan | Presales Consultant |
| Technical Solution | Architecture, technology, approach | Solution Architect |
| Methodology & Project Plan | Approach, timeline, milestones | Presales Consultant |
| Team & Experience | Proposed team, CVs, case studies | Presales Consultant |
| Pricing | Detailed pricing breakdown | Sales Lead + Finance |
| Compliance Matrix | Requirement-by-requirement response | Semua |
| Appendices | Supporting documents | Semua |
Writing Tips untuk RFP Response:
- Jawab persis apa yang ditanya — jangan mengarang soal sendiri
- Setiap jawaban = requirement addressed + value added
- Gunakan framing: "Compliant. Additionally, Divistant provides..."
- Bold key phrases yang menjawab evaluation criteria
- Konsisten dengan terminology RFP (jangan ganti istilah mereka)
- Jika non-comply, jelaskan alternatif yang lebih baik beserta alasannya
Step 4: Review & Quality Check (Hari 13-15)
Review Layers:
| Review Type | Reviewer | Focus |
|---|---|---|
| Compliance Review | Response Lead | Semua requirement terjawab? Compliance matrix complete? |
| Technical Review | Solution Architect | Akurasi teknis, feasibility, consistency |
| Commercial Review | Sales Director | Pricing competitive, margin OK, terms acceptable |
| Quality Review | Peer (bukan penulis) | Grammar, formatting, readability, brand consistency |
| Red Team Review | Senior/MD (untuk deal besar) | Baca dari perspektif evaluator — apakah kita menang? |
Red Team Review Questions:
- Apakah executive summary cukup kuat untuk masuk shortlist?
- Apakah differentiator kita terlihat jelas di setiap section?
- Apakah pricing competitive dan well-justified?
- Di mana weakness kita? Sudahkah kita address?
- Jika kita jadi evaluator, apakah kita pilih respons ini?
Step 5: Finalize & Submit (Hari 16-18)
- Final formatting dan brand check
- Generate PDF (non-editable)
- Verifikasi semua lampiran lengkap
- Submit sesuai format yang diminta (portal, email, hardcopy)
- Submit minimal 24 jam sebelum deadline — hindari risiko teknis last minute
- Update BizOps CRM: attach respons, update stage, log submission date
4. Win Strategy untuk RFP
Competitive Positioning
| Situasi | Strategy |
|---|---|
| Kita incumbent | Highlight track record, continuity, institutional knowledge |
| Kita challenger | Highlight fresh perspective, innovation, competitive pricing |
| Blind bid (no relationship) | Focus on credentials, methodology, case studies |
| Multiple incumbents | Emphasize integration capability, single-vendor simplicity |
| Budget-sensitive client | Value engineering, phasing, TCO comparison |
Ghost Competitor Strategy
"Ghosting" = mengatasi kelebihan kompetitor tanpa menyebut nama mereka.
| Competitor Strength | Our Ghost Response |
|---|---|
| Brand name besar / global | "Divistant menawarkan dedicated local team yang memahami konteks bisnis Indonesia, bukan template global yang perlu diadaptasi" |
| Harga lebih murah | "Investasi kami mencakup end-to-end support termasuk hypercare, menghindari hidden cost yang sering muncul di kemudian hari" |
| Teknologi proprietary | "Solusi open-source kami menghindari vendor lock-in dan memberikan fleksibilitas jangka panjang" |
| Tim lebih besar | "Tim Divistant yang dedicated dan senior memastikan quality over quantity, dengan single point of contact yang konsisten" |
5. Response Team & Roles
| Role | Tanggung Jawab | Alokasi Waktu |
|---|---|---|
| Response Lead | Koordinasi keseluruhan, compliance tracking, final review | 40-60% selama response period |
| Presales Consultant | Non-technical sections, executive summary, methodology | 60-80% selama response period |
| Solution Architect | Technical solution, architecture, integration | 40-60% selama response period |
| Sales Lead | Commercial sections, pricing, cover letter | 20-30% selama response period |
| SME (Subject Matter Expert) | Domain-specific content, case studies | 10-20% as needed |
| Finance | Pricing validation, margin check | 5-10% review only |
| Quality Reviewer | Grammar, formatting, consistency | 10% during review phase |
6. Timeline Management
Standard Timeline (RFP 20 hari kerja):
| Phase | Hari | Aktivitas |
|---|---|---|
| Kickoff & Planning | 1-2 | Read RFP, compliance matrix, team assembly |
| Clarification | 2-3 | Submit questions, gather answers |
| Drafting | 3-12 | Write section by section |
| Review | 13-15 | Multi-layer review |
| Revision | 16-17 | Address review comments |
| Final & Submit | 18 | Format, PDF, submit |
| Buffer | 19-20 | Emergency buffer |
Compressed Timeline (RFP 10 hari kerja):
| Phase | Hari | Adaptation |
|---|---|---|
| Kickoff + Clarification | 1 | Parallel — assign sections same day |
| Drafting | 2-6 | All writers parallel, daily check-in |
| Review | 7-8 | Single review layer (Response Lead + SA) |
| Revision + Submit | 9 | Same-day revision and submission |
| Buffer | 10 | Emergency only |
7. BizOps CRM Integration
Stage Updates:
| RFP Milestone | CRM Action |
|---|---|
| RFP diterima | Create/update Opportunity, attach RFP document |
| Bid/No-Bid decision | Log decision di Notes dengan scoring |
| Response submitted | Update stage → "Proposal Sent", attach response |
| Shortlisted | Update stage → "Negotiation/Review" |
| Presentation/BAFO | Log di Notes |
| Won/Lost | Update stage, log win/loss reason |
Notes Format:
== RFP STATUS ==
RFP Title: [judul]
Client: [nama klien]
Received: [tanggal terima]
Deadline: [tanggal deadline]
Bid/No-Bid: [BID / NO-BID] (Score: xx/100)
== RESPONSE STATUS ==
Response Lead: [nama]
Status: [Drafting / Review / Submitted / Shortlisted / Won / Lost]
Submission Date: [tanggal kirim]
Competitors: [yang diketahui]
== EVALUATION ==
Shortlist Announced: [tanggal]
Presentation Date: [tanggal]
BAFO Requested: [Ya/Tidak]
Result: [Won/Lost] — [alasan]
Template & Aset
📘 Know (Untuk dipelajari)
- APMP (Association of Proposal Management Professionals) Body of Knowledge
- Shipley Capture & Proposal Guide
- Government procurement regulations (jika applicable)
📊 Show (Untuk digunakan)
- Bid/No-Bid Scorecard — Spreadsheet scoring template
- RFP Response Template — Template dokumen respons standar
- Compliance Matrix Template — Template tracking requirement-by-requirement
- RFP Timeline Planner — Gantt template untuk planning respons
- No-Bid Letter Template — Template surat decline
📤 Share (Untuk dikirim ke klien)
- Final RFP response (PDF format)
- Clarification questions (email/document)
- No-Bid response letter
- Presentation deck (untuk shortlist presentation)
Skenario Umum
Skenario 1: RFI dari BUMN — Eksplorasi Vendor
Situasi: BUMN energi mengirim RFI ke 10 vendor untuk eksplorasi solusi digitalisasi operasional. Response time 7 hari.
Pendekatan:
- Bid decision: BID (strategic account, strong capability match)
- Fokus: company profile, relevant experience di sektor energi, kapabilitas end-to-end
- Include 2-3 case study yang relevan
- Jangan berikan pricing detail — ini baru RFI
- Tujuan: masuk shortlist untuk RFP yang akan menyusul
- Sertakan request untuk meeting/presentasi langsung
Hasil: RFI response 12 halaman. Di-invite ke RFP stage bersama 4 vendor lainnya.
Skenario 2: RFP Kompetitif — Melawan Incumbent
Situasi: Perusahaan telekomunikasi issue RFP untuk modernisasi billing system. Incumbent adalah vendor besar multinasional. Deadline 15 hari kerja.
Pendekatan:
- Bid score: 62 (Conditional Bid — strong technical, weak relationship)
- Ghost strategy: emphasize local support, flexibility, no vendor lock-in
- Win theme: "Modern, open-source based, dengan dedicated local team"
- Pricing: competitive, include phasing option
- Differentiator: live demo offer sebagai bagian dari respons
- Red Team review oleh MD (deal >500M)
Hasil: Masuk shortlist 3 besar. Di-invite untuk presentasi dan live demo.
Skenario 3: RFQ Cepat — Staff Augmentation
Situasi: Klien existing kirim RFQ untuk 5 developer selama 6 bulan. Deadline 3 hari.
Pendekatan:
- Bid decision: BID (existing client, straightforward scope)
- Response: rate card, CV ringkas per candidate, availability date
- Tidak perlu compliance matrix formal — langsung tabel requirement vs capability
- Include value-add: free Technical Lead oversight
- Submit dalam 2 hari
Hasil: RFQ response 8 halaman. PO diterima dalam 1 minggu.
Skenario 4: No-Bid Decision — Kapan Menolak
Situasi: Perusahaan fintech issue RFP untuk AI/ML platform. Bid score: 25 (di luar core expertise, no relationship, spec mengarah ke vendor lain).
Pendekatan:
- Bid decision: NO-BID
- Kirim No-Bid response letter yang profesional
- Tawarkan area lain yang bisa dibantu (misalnya integration layer)
- Minta tetap di-include di future RFP
- Log di CRM sebagai "Lost" dengan reason "No-Bid: capability mismatch"
Hasil: Relationship maintained. 3 bulan kemudian, klien kirim RFP untuk integration project yang sesuai expertise.
Checklist
RFP Response Submission Checklist
Pre-Writing:
- RFP dibaca menyeluruh oleh Response Lead
- Bid/No-Bid decision documented dengan scoring
- Compliance matrix dibuat dan di-share ke team
- Response team assembled dan section assigned
- Internal timeline ditetapkan (min 2 hari buffer sebelum deadline)
- Clarification questions dikirim ke klien
During Writing:
- Semua mandatory requirements terjawab (full/partial/non-comply)
- Win theme konsisten di seluruh respons
- Setiap section mengandung differentiator
- Pricing validated oleh Finance
- Case studies dan references relevan
- Technical solution reviewed oleh SA
Pre-Submission:
- Compliance review passed — 100% requirements addressed
- Technical review passed — no inaccuracies
- Commercial review passed — margin OK, pricing competitive
- Quality review passed — grammar, format, brand
- Red Team review (untuk deal > 500M)
- All attachments complete (CVs, case studies, certificates)
- PDF generated (non-editable)
- Submission format sesuai requirement (portal / email / hardcopy)
- Submitted min 24 jam sebelum deadline
- BizOps CRM updated: response attached, stage updated, notes logged
Tanggung Jawab (RACI)
| Aktivitas | Response Lead | Presales Consultant | Solution Architect | Sales Lead | Sales Director |
|---|---|---|---|---|---|
| Bid/No-Bid assessment | R | C | C | C | A |
| Compliance matrix | R | C | C | I | I |
| Clarification questions | R | C | C | I | I |
| Executive Summary | C | R | C | C | I |
| Technical Solution section | I | C | R | I | I |
| Methodology section | C | R | C | I | I |
| Pricing section | I | I | C | R | A |
| Team & Experience section | C | R | C | I | I |
| Compliance review | R | C | C | I | I |
| Red Team review (>500M) | C | I | I | C | R |
| Final approval & submit | I | R | I | A | I |
| Post-submission follow-up | C | I | I | R | I |
Legenda: R = Responsible, A = Accountable, C = Consulted, I = Informed
Referensi
- Internal: Qualification & MEDDIC Framework, Proposal Writing, Service Catalog
- Framework: APMP Body of Knowledge, Shipley Capture & Proposal Guide
- Standard: Perpres 16/2018 (Pengadaan Barang/Jasa Pemerintah — jika applicable)
- Tools: BizOps CRM (Opportunity tracking), Compliance Matrix template
Last updated 3 months ago
Was this helpful?