Ikhtisar: Client Onboarding & Delivery
Ringkasan Chapter
Chapter ini membahas 6-step delivery system untuk onboarding client dan mendelivery proyek automation secara profesional. Selling hanya menghasilkan uang sekali — onboarding yang baik menghasilkan uang berulang kali.
6-Step Delivery System
┌───────────────────────────────────────────────────────────────┐
│ 6-STEP DELIVERY SYSTEM │
│ │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ 1. DISCOVERY │──▶│ 2. PROPOSAL │──▶│ 3. STAGING │ │
│ │ CALL │ │ DOCUMENT │ │ BUILD │ │
│ │ │ │ │ │ │ │
│ │ Pahami │ │ One-page │ │ Jangan │ │
│ │ domain & │ │ proposal + │ │ eksperimen │ │
│ │ ekspektasi │ │ deliverables │ │ di production│ │
│ └──────────────┘ └──────────────┘ └──────────────┘ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ 4. END-TO- │──▶│ 5. HANDOFF │──▶│ 6. RETAINER │ │
│ │ END TESTING │ │ & DOCS │ │ & MAINTENANCE│ │
│ │ │ │ │ │ │ │
│ │ Happy + │ │ Loom video + │ │ Low-touch │ │
│ │ unhappy + │ │ SOP + runbook│ │ atau │ │
│ │ edge cases │ │ + credentials│ │ high-touch │ │
│ └──────────────┘ └──────────────┘ └──────────────┘ │
│ │
└───────────────────────────────────────────────────────────────┘Peta Video
| # | Video | Fokus Utama |
|---|---|---|
| 1 | Onboarding & Delivery | Mengapa onboarding lebih penting dari sales; overview 6-step system |
| 2 | Dokumen Proposal | One-page proposal, requirement doc, melindungi scope |
| 3 | Build di Staging | Dev → staging → production; testing paralel minimal 2 minggu |
| 4 | Menghindari Kegagalan | End-to-end testing; happy/unhappy/edge cases; credential migration |
| 5 | Dokumentasi = Delivery | 5 komponen delivery; Loom → 3 aset; runbook |
| 6 | Retainer Setelah Delivery | Low vs high touch; batch changes; retainer dari trust |
| 7 | Pitfall & Takeaway | 5 common pitfalls; 50% advance; speed vs quality |
Prinsip Utama
| # | Prinsip | Detail |
|---|---|---|
| 1 | Selling = paid once, onboarding = paid repeatedly | Client menilai saat onboarding, bukan saat sales call |
| 2 | Never price without discovery | Multiple discovery calls itu normal |
| 3 | Proposal = perlindungan | Client greedy itu alami — requirement doc jaga batasan |
| 4 | Staging dulu, production belakangan | Minimum 2 minggu testing paralel |
| 5 | Test end-to-end, bukan per node | Happy + unhappy + edge cases WAJIB lulus |
| 6 | Dokumentasi = delivery | Workflow invisible, dokumentasi yang membuat value terlihat |
| 7 | Retainer dari trust | Deliver well → maintenance natural → recurring revenue |
Flow Delivery End-to-End
Lead masuk
│
▼
Discovery Call(s) ── Pahami domain, proses, ekspektasi
│
▼
One-Page Proposal ── Problem, solution, deliverables, timeline, harga
│ Client sign-off + 50% advance payment
▼
Build di Staging ── Development → Staging → Testing paralel (2 minggu)
│
▼
End-to-End Testing ── Happy cases + unhappy cases + edge cases
│ Credential migration ke client
▼
Handoff & Docs ── Loom video + SOP + runbook + credentials doc
│ Delivery email + final payment
▼
Retainer ── Low-touch (monitoring) atau high-touch (improvement)
│ Batch changes, jangan endless tweaks
▼
Referral + New Projects ── Trust → lebih banyak client5 Pitfall yang Harus Dihindari
| Pitfall | Dampak |
|---|---|
| No staging | Satu kesalahan di production = trust hancur |
| Poor documentation | Client bingung, tidak bisa maintain |
| Over-technical | Client tidak peduli cara, mereka peduli hasil |
| Unclear expectations | Scope creep dan konflik |
| Rushing delivery | Speed tanpa quality = reputasi rusak |
Formula Emas
Automation = produk. Onboarding = pengalaman. Pengalaman = yang client bayar.