Planning Service — Roadmap & Benchmark

Last refreshed: 2026-06-16. Excerpt + summary dari Extraction Plan §5 (Benchmark) + §6 (Roadmap fitur).

Roadmap Phase 1 → Phase 2

Phase 0 (audit)        ─── 2026-06-10 DONE
       │
Phase 1 (service mandiri) ── 2026-06-11 SHIPPED
       │
       │ Open: Break-even + Pricing Sensitivity schema decision
       │ Open: Roadmap fitur (lihat §1 di bawah)
       │
Phase 2 (SaaS multi-tenant)── PARKED (tunggu tenant model)
       │
       └─ Lift ke modelary.com:
          • Standalone DB instance
          • Multi-tenant JWT auth
          • Branding final (Modelary vs Proyqo)
          • Pricing model (Polqo-style subscription?)
          • Marketing site + landing page

1. Gap Fitur Saat Ini

Saat ini Planning Service hanya cover Growth Projection. Berikut gap untuk jadi produk SaaS full:

A. Skenario yang sudah ada

• ✅ Growth Projection — input device unit, output projected revenue + payback period
• ✅ Default constants tersedia (margin/MDR/setup cost) seedable per merchant

B. Skenario yang BELUM ada (perlu schema baru)

• ❌ Break-even Analysis — kapan ROI tercapai untuk capex device
• ❌ Pricing Sensitivity / What-If — variasikan MDR/setup cost vs profit
• ❌ Cohort Retention Projection — predict churn merchant per cohort
• ❌ Cash Flow Projection — multi-month cash flow with scenarios

C. Fitur enabler SaaS (Phase 2)

• ❌ Multi-scenario comparison panel (side-by-side 2-3 scenario)
• ❌ Scenario sharing antar user (read-only link)
• ❌ Export to PDF / Excel
• ❌ Audit log per scenario edit
• ❌ Template library (industry presets: F&B, retail, jasa, dst.)

2. Benchmark — Produk Sejenis di Pasar

Excerpt dari Extraction Plan §5:

Produk	Origin	Fokus	Lesson
Causal	UK	Financial modeling for startups	Cell-based formula seperti spreadsheet, but version controlled
Mosaic	US	FP&A platform	Heavy integration ke akuntansi (Quickbooks, NetSuite)
Pry	US (acq. Brex)	Cash flow + headcount planning	Simple UI, scenario quick-switch
Vena	Canada	Enterprise FP&A	Excel-native interface
Modelary (Kesles)	Indonesia	Financial scenario untuk merchant payment	Domain-specific (MDR, device cost, transaction volume)

Diferensiasi Modelary: Domain-specific untuk industri payment/merchant — lawan generic FP&A tools. Built-in untuk skenario QRIS Plus / Coherent / device unit economics.

3. Roadmap Lanjutan (Phase 2 SaaS)

Wave 1 — Foundation (Q3 2026 target)

• Multi-tenant DB instance (lift dari shared Postgres)
• Tenant-aware JWT auth (vs API key internal sekarang)
• Domain modelary.com + landing page minimal
• Subscription billing (Polqo pattern: monthly per-user)

Wave 2 — Feature Parity (Q4 2026 target)

• Break-even + Pricing Sensitivity full implementation
• Cohort Retention Projection
• Cash Flow Projection
• Scenario template library

Wave 3 — Polish (Q1 2027 target)

• Multi-scenario comparison panel
• PDF/Excel export
• Audit log
• Team collaboration (share, comment)

Wave 4 — Integration (TBD)

• Integration dengan akuntansi populer Indonesia (Jurnal, Kledo, Mekari)
• Bank account sync (BCA, Mandiri OAuth)
• Industry preset library

4. Decision Log

Date	Decision	Status
2026-06-10	Extract Planning sebagai service mandiri (Phase 1)	✅ DONE
2026-06-10	Codename = Modelary (working name, lock TBD)	🟡 Pending final branding
2026-06-11	DB di-deploy sebagai schema di shared Postgres dulu (vs standalone instance)	✅ Decided — defer ke Phase 2
2026-06-11	DROP legacy schemas report.* + planning.* di main DB	✅ DONE (mig v1/106)
TBD	Phase 2 trigger criteria: ≥3 paying customer Phase 1 OR strategic pivot?	⏸️ Parked
TBD	Pricing model: per-user seat vs per-scenario count vs flat?	⏸️ Parked

5. Open Questions

1. Pricing: subscription per-user atau per-scenario? Polqo pakai per-user, Sqile pakai per-scenario.
2. Branding final: lock "Modelary" atau pivot ke "Proyqo" (suffix -qo selaras Polqo)?
3. Tenant migration: kalau ada existing merchant pakai planning di internal, apakah auto-migrate ke tenant SaaS atau opt-in?
4. Integration scope: standalone product atau tetap embed di dashboard Kesles?
5. Indonesian market readiness: apakah pasar SMB Indonesia bersedia bayar SaaS untuk FP&A? Need market research.

Cross-References

• Full plan: Extraction Plan
• Status: Service Status
• Architecture: Architecture
• Memory: project_planning_service.md