Phuriwaj

BOL 2026 Data Strategy

Planted 10 days ago

BOL 2026 Data Strategy

BOL (Business Online PCL) 9-month platform modernisation roadmap to transform from a legacy data provider into a deployable Intelligent Data Platform targeting Thai banks and government agencies.

Core Idea

The strategy leverages a 2026 convergence window — FATF mutual evaluation pressure, PDPA enforcement, and reduced AI build costs — to modernise the platform using a Strangler Fig pattern with AI-assisted code migration. Budget 50–70M THB, team of 16–18, target customers are Thai banks and government agencies needing deployable data intelligence infrastructure.

Key Points

  • Budget: 50–70M THB (needs narrowing to baseline + stretch headcount scenarios before board)
  • Team: 16–18 people; 8 new hires including critical ML/NLP roles (2–3 month lead time risk)
  • Pattern: Strangler Fig — incrementally replace legacy without a full rewrite
  • AI policy: AI-accelerated development but human review mandatory for all code; “ห้าม Trust AI Translation 100%”
  • Tech stack decision: Databricks vs Snowflake vs Iceberg+Trino — frozen by M1 Track B
  • Compliance drivers: FATF mutual evaluation 2026, PDPA enforcement, ISO 27001 extension scope
  • Key differentiators: Thai NLP (F1 ≥0.80), deployable platform model, legacy data moat

Three Execution Risks

  1. Hiring timeline — 8 critical hires at 2–3 month lead time; ramp-up gap not reflected in M6 delivery dates. Contractor/Vendor fallback should be a parallel track, not a backup plan.
  2. M6 scope volume — migrated features + new platform + pilot customer + multi-tenancy + governance + NLP in 6 months is aggressive for 16–18 people even with AI acceleration. Needs an explicit “must-have vs nice-to-have” cut line.
  3. Pilot customer LOI — hard dependency: LOI within 2 weeks of kick-off. No contingency plan documented if no pilot customer commits by week 8.

Decision Gate (M0 Blockers)

Four blockers must be resolved before the clock starts:

  1. Legacy system categorisation (migrate vs. retire)
  2. Pilot customer LOI
  3. Knowledge holder commitment (legacy system context carriers)
  4. Revenue model confirmation

Document Quality Notes

Strengths: Legacy Reuse strategy intellectually honest, “Why Now” argument sharp, AI Strategy unusually calibrated (task-type breakdown, human review workflow), Decision Required framing surfaces blockers early.

Improvement areas: RACI and approval path should be explicitly linked; budget range (40% variance on personnel) needs narrowing for board; Non-Goals section should include rationale for deferrals.

Week of 2026-W21

Full strategy document reviewed and commented on. Three execution risks identified above. Assessment: high-quality internal enterprise planning, board-ready after addressing the three risks and narrowing the budget range.

Source

Journal dates: 2026-W21 (session — “Review BOL 2026 data strategy document”)