FLIK Strategy & Roadmap

MCA_PRODUCT_ROADMAP_2026

25 min read

Merchant Cash Advance (Bulk Purchase) Product Roadmap 2026

From Current State to Wayflyer-Level Platform

Document Version: 1.0 Date: January 6, 2026 Owner: Product & Engineering Team Vision: Transform Useflik’s Bulk Purchase product into a world-class embedded revenue-based financing platform comparable to Wayflyer

📊 Executive Summary

Current State Assessment

Strengths:

  • ✅ Production-ready recollection system with 3 strategies
  • ✅ Real-time status management and lifecycle automation
  • ✅ Seller dashboard with financial tracking
  • ✅ Flexible product-level tracking
  • ✅ Local market expertise (CLIK integration, PKP/NON-PKP handling)

Critical Gaps vs Wayflyer:

  • 🔴 No Partner Distribution Model - Direct B2B only, missing B2B2C embedded finance
  • 🔴 No Partner API - Cannot integrate with platforms/marketplaces
  • 🔴 Manual Underwriting - No automated decision engine
  • 🟡 Limited Pre-Disbursement Flow - Basic onboarding, needs credit scoring automation
  • 🟡 No OAuth Integrations - Manual data collection vs automated sync

Strategic Direction

We will separate the product into TWO MAJOR DOMAINS with a THIRD CRITICAL ADDITION:

┌─────────────────────────────────────────────────────────────┐
│                  MCA PRODUCT ARCHITECTURE                    │
├─────────────────────────────────────────────────────────────┤
│                                                               │
│  1. PRE-DISBURSEMENT (Onboarding & Underwriting)            │
│     ├─ Merchant Application                                  │
│     ├─ Credit Scoring Engine (5-factor model)               │
│     ├─ CLIK Integration                                      │
│     ├─ Holdback Calculator                                   │
│     ├─ Margin Viability Check                                │
│     ├─ Agreement Generation                                  │
│     └─ Cash Disbursement                                     │
│                                                               │
│  2. POST-DISBURSEMENT (Recollection & Monitoring)           │
│     ├─ Multi-Strategy Recollection (EXISTING)               │
│     ├─ Period Limits (PLANNED)                               │
│     ├─ Parallel Projects (PLANNED)                           │
│     ├─ Overcollect Handler (NEW)                             │
│     ├─ Buyback Handler (ENHANCED)                            │
│     └─ Revenue-Based Collection (NEW)                        │
│                                                               │
│  3. PARTNER PLATFORM (NEW - CRITICAL)                        │
│     ├─ Partner API (OAuth 2.0)                              │
│     ├─ Partner Portal & Dashboard                            │
│     ├─ White-Label Components                                │
│     ├─ Revenue Share Management                              │
│     └─ Partner Onboarding Flow                               │
│                                                               │
└─────────────────────────────────────────────────────────────┘

🎯 North Star Metrics (18-Month Targets)

MetricCurrent6 Months12 Months18 Months
Total Capital FundedUnknown$5M$20M$50M
Auto-Approval Rate0%60%75%85%
Partner Platforms02815
Active Merchants~201005001,500
Avg TAT (Application→Disbursement)2-3 days12 hours4 hours1 hour
Portfolio NPL RateUnknown<1.5%<1.3%<1.2%
Partner NPSN/A50+60+70+

🗺️ Roadmap Overview (18 Months)

Phase 1: Foundation (Month 1-6) - “Build the Core”

Theme: Automated Pre-Disbursement + Partner API MVP

Phase 2: Partner Platform (Month 7-12) - “Enable Distribution”

Theme: Partner Onboarding + White-Label + Pilot Launches

Phase 3: Scale & Optimize (Month 13-18) - “Wayflyer Parity”

Theme: ML Underwriting + Advanced Features + Geographic Expansion

📅 Detailed Roadmap

PHASE 1: FOUNDATION (Month 1-6)

Theme: “Build the Core Engine”

🎯 Phase Objectives

  1. Deploy automated credit scoring and underwriting engine
  2. Build Partner API foundation (authentication, core endpoints)
  3. Enhance post-disbursement recollection capabilities
  4. Establish monitoring and analytics infrastructure

🚀 MILESTONE 1.1: Pre-Disbursement Automation (Month 1-2)

Epic 1.1.1: Credit Scoring Engine

Priority: P0 (Must-Have) Owner: Backend Engineering + Risk Team Effort: 3 engineers × 6 weeks

User Story:

As an underwriter, I want the system to automatically score merchants so that I can focus on edge cases and approve 60%+ applications instantly.

Requirements:

  • Implement 5-factor scoring algorithm (from PRD)
    • Revenue Stability (30%): CV calculation
    • Revenue Quality (20%): Growth trend analysis
    • CLIK Score (20%): Credit bureau integration
    • Business Tenure (15%): Years in operation
    • Advance Ratio (15%): Requested vs monthly revenue
  • Score band mapping (EXCELLENT → UNACCEPTABLE)
  • GMV eligibility check automation
  • Auto-approve logic for scores ≥80
  • Manual review queue for 50-79 scores
  • Auto-decline for scores <40

Technical Tasks:

  • Create credit_score service in Go
  • Database schema: credit_scores, revenue_data tables
  • CLIK API integration (SOAP-based, NAE function)
  • API endpoints: POST /v1/underwriting/assess
  • Unit tests (80%+ coverage)
  • Integration with existing bulk purchase flow

Acceptance Criteria:

  • ✅ Credit score calculated in <500ms (p95)
  • ✅ 95%+ alignment with manual underwriter decisions
  • ✅ Complete breakdown of score components with reasoning
  • ✅ Auto-approval working for EXCELLENT/VERY GOOD bands

Deliverables:

  1. Credit Scoring Service (Go microservice)
  2. CLIK Integration Module
  3. Admin dashboard for score review
  4. API documentation

Epic 1.1.2: CLIK Credit Bureau Integration

Priority: P0 (Must-Have) Owner: Backend Engineering Effort: 2 engineers × 3 weeks

Requirements:

  • SOAP API client for CLIK (based on manual v2.5)
  • NAE (New Application Enquiry) implementation
    • Entity (company) credit check
    • Owner (individual) credit check
  • Response parsing and data extraction
  • Credit quality determination logic
  • 30-day caching to reduce API costs
  • Error handling and retry logic

Technical Tasks:

  • SOAP client library setup
  • XML request/response marshaling
  • Credential management (AWS Secrets Manager)
  • Cache layer (Redis, 30-day TTL)
  • Cost tracking per query
  • Fallback to manual check on failure

Acceptance Criteria:

  • ✅ Successfully retrieve credit reports for entity + owner
  • ✅ Parse CLIK score, collectability, negative events
  • ✅ Response time <30 seconds (p95)
  • ✅ Cache hit rate >40% for repeat merchants
  • ✅ Clear error messages for all failure scenarios

Cost Estimate:

  • Setup: One-time negotiation with CLIK
  • Per query: Rp 10,000-15,000
  • Monthly (60 apps/day × 2 subjects × 30 days): Rp 36M ($2,300 USD)
  • With 40% cache hit rate: Rp 21M ($1,400 USD)

Epic 1.1.3: Holdback & Margin Calculators

Priority: P0 (Must-Have) Owner: Backend Engineering Effort: 1 engineer × 2 weeks

Requirements:

  • Holdback Calculator implementation
    • Base holdback % calculation
    • Credit score adjustment factor
    • Floor (15%) and ceiling (40%) enforcement
    • Pro-rata collection schedule generation
  • Margin Viability Checker
    • Buffer calculation (Gross Margin - Holdback)
    • Viability assessment (VIABLE-HEALTHY → NOT VIABLE)
    • Restructuring recommendations
    • Scenario modeling

Technical Tasks:

  • Calculation service in Go
  • API endpoints: POST /v1/underwriting/holdback, POST /v1/underwriting/margin
  • Unit tests with various scenarios
  • Integration with credit scoring output

Acceptance Criteria:

  • ✅ Holdback calculation <200ms
  • ✅ Pro-rata schedule accurate to 0.1% precision
  • ✅ Margin viability matches manual assessment 90%+ of time
  • ✅ Clear restructuring suggestions for tight margins

Epic 1.1.4: Underwriter Workspace

Priority: P0 (Must-Have) Owner: Frontend + Backend Engineering Effort: 2 engineers × 4 weeks

Requirements:

  • Application queue management
    • Sorted by TAT urgency
    • Filter by status, score band, amount
    • Real-time updates
  • Application review interface
    • Credit score breakdown display
    • System recommendation visibility
    • One-click approve/decline
    • Override with justification
  • Document viewer (inline PDF/image)
  • Comments and notes (internal + merchant-facing)
  • Audit trail for all actions

Technical Stack:

  • Frontend: Vue.js 3 + Nuxt 3
  • Backend: Existing Go services + new endpoints
  • Real-time: WebSockets or Server-Sent Events

Acceptance Criteria:

  • ✅ Queue refreshes automatically (5-second intervals)
  • ✅ Application review loads in <2 seconds
  • ✅ Document preview supports PDF, JPG, PNG
  • ✅ All actions logged with timestamp + user

🚀 MILESTONE 1.2: Partner API Foundation (Month 2-4)

Epic 1.2.1: Partner Authentication & Authorization

Priority: P0 (Must-Have) Owner: Backend Engineering Effort: 2 engineers × 4 weeks

Requirements:

  • OAuth 2.0 client credentials flow
  • Partner registration portal
  • API key management (generate, rotate, revoke)
  • JWT token generation (RS256 signing)
  • Scoped tokens (partner_token → company_token)
  • Rate limiting (1,000 req/min standard tier)

API Endpoints:

POST /v1/auth/partner/token
POST /v1/auth/company/token
POST /v1/auth/refresh
POST /v1/auth/revoke

Technical Tasks:

  • OAuth 2.0 server implementation (Go library)
  • Partner credentials storage (encrypted in PostgreSQL)
  • Token blacklist in Redis
  • Rate limiter middleware
  • API key rotation workflow
  • Security audit

Acceptance Criteria:

  • ✅ Partner can obtain tokens in <200ms (p99)
  • ✅ Auth success rate >99.5%
  • ✅ Tokens expire correctly (1h partner, 24h company)
  • ✅ Rate limiting enforced accurately

Epic 1.2.2: Core Partner APIs

Priority: P0 (Must-Have) Owner: Backend Engineering Effort: 3 engineers × 6 weeks

Requirements:

  • Application submission API
    • Partner submits on behalf of merchant
    • Pre-filled data from platform connection
    • Document upload support
  • Application status API
    • Real-time status tracking
    • Webhook notifications
  • Offer retrieval API
    • Get funding offer after approval
    • Transparent terms display
  • Acceptance API
    • Merchant accepts/declines offer via partner

API Endpoints:

POST /v1/applications
GET  /v1/applications/{application_id}
GET  /v1/applications/{application_id}/offer
POST /v1/applications/{application_id}/accept
POST /v1/applications/{application_id}/decline
GET  /v1/applications (list)

Technical Tasks:

  • RESTful API design (follow Stripe conventions)
  • OpenAPI 3.0 specification
  • Request/response validation
  • Idempotency support (idempotency keys)
  • Error handling and standard error codes
  • Webhook infrastructure (retry logic, signatures)

Acceptance Criteria:

  • ✅ All endpoints have <300ms p95 latency
  • ✅ Comprehensive error codes and messages
  • ✅ Idempotency prevents duplicate applications
  • ✅ Webhooks delivered with 99%+ success rate

Epic 1.2.3: API Documentation & Sandbox

Priority: P0 (Must-Have) Owner: Technical Writer + Backend Engineering Effort: 1 writer + 1 engineer × 3 weeks

Requirements:

  • OpenAPI/Swagger documentation
  • Sandbox environment with test data
  • Postman collection
  • Code examples (Node.js, Python, Go)
  • Integration guide (step-by-step)
  • Quickstart tutorial (<10 minutes)

Deliverables:

  1. API docs site (hosted on docs.useflik.com/partners)
  2. Sandbox environment (sandbox.useflik.com)
  3. SDKs: Node.js, Python (initial release)
  4. Postman workspace (public)

Acceptance Criteria:

  • ✅ Documentation covers all endpoints
  • ✅ Sandbox has 20+ test merchants
  • ✅ Code examples work without modification
  • ✅ Integration guide validated by 3 beta partners

🚀 MILESTONE 1.3: Post-Disbursement Enhancements (Month 3-5)

Epic 1.3.1: Period Limits (Daily/Weekly/Monthly Caps)

Priority: P1 (Important) Owner: Backend Engineering Effort: 2 engineers × 3 weeks

Context: From bulk-purchase-config-improvement-2025 requirements - enable merchants to cap collection frequency to protect cash flow.

Requirements:

  • Configuration schema extension 
    {
  "period_limits": {
    "enabled": true,
    "daily_limit": 500000.0,
    "weekly_limit": 2000000.0,
    "monthly_limit": 7000000.0
  }
}
  • Collection aggregation by period
  • Limit enforcement in recollection calculation
  • Spillover handling (defer to next period)
  • Dashboard visualization of limits

Technical Tasks:

  • Update recollection_config schema
  • Implement period aggregation logic
  • Modify recollection service to check limits
  • Add spillover queue mechanism
  • UI components for limit configuration
  • Analytics dashboard for limit tracking

Acceptance Criteria:

  • ✅ Limits enforced in real-time during order processing
  • ✅ Spillover deferred correctly to next period
  • ✅ Dashboard shows current vs limit accurately
  • ✅ No performance degradation (<50ms added latency)

Epic 1.3.2: Parallel Bulk Purchases (Priority-Based Selection)

Priority: P1 (Important) Owner: Backend Engineering Effort: 2 engineers × 3 weeks

Context: From bulk-purchase-config-improvement-2025 requirements - allow multiple active projects with priority routing.

Requirements:

  • Priority field in bulk purchase configuration 
    {
  "priority": 1,  // 1 = highest, 10 = lowest
  "allow_parallel": true
}
  • Selection algorithm for overlapping projects
    • Check priority first
    • Check remaining balance
    • Check product match (for SPECIFIC_PRODUCTS)
  • Proportional splitting (optional)
  • Dashboard showing active projects

Technical Tasks:

  • Update bulk purchase schema with priority
  • Implement priority-based selection algorithm
  • Handle edge cases (equal priority, zero balance)
  • Add “allow_parallel” toggle in UI
  • Update recollection logic to iterate projects
  • Performance testing with 5+ parallel projects

Acceptance Criteria:

  • ✅ Highest priority project selected first
  • ✅ Fallback to next priority if primary exhausted
  • ✅ Performance acceptable with 10+ parallel projects (<100ms)
  • ✅ Clear UI showing which project collected from

Epic 1.3.3: Overcollect & Buyback Handlers

Priority: P1 (Important) Owner: Backend Engineering Effort: 2 engineers × 2 weeks

Requirements:

  • Overcollect Handler
    • Detect when collected > target
    • Auto-complete status transition
    • Option to refund excess or apply to new project
  • Buyback Handler
    • Trigger when end_date passed + collected < target
    • Generate buyback invoice
    • Calculate remaining quantity
    • Notification to merchant and client

Technical Tasks:

  • Enhanced status transition logic
  • Overcollect detection algorithm
  • Buyback invoice generation
  • Email/SMS notifications
  • Dashboard alerts
  • Reconciliation workflow

Acceptance Criteria:

  • ✅ Overcollect detected within 1 hour of occurrence
  • ✅ Buyback triggered on end_date + 1 day
  • ✅ Invoices generated automatically
  • ✅ Notifications sent within 5 minutes

Epic 1.3.4: Revenue-Based Collection (Wayflyer-Style)

Priority: P2 (Post-Launch) Owner: Backend Engineering Effort: 2 engineers × 4 weeks

Context: Wayflyer collects a fixed % of monthly revenue (10-20%) rather than transaction-level. This is more predictable for merchants.

Requirements:

  • New recollection target: MONTHLY_REVENUE
  • Monthly revenue calculation
    • Aggregate all orders in calendar month
    • Apply collection percentage (e.g., 15%)
    • Single ACH debit on month-end
  • Pro-rata schedule based on months
  • Failed payment retry logic

Technical Tasks:

  • New target type in recollection config
  • Monthly aggregation job (cron)
  • ACH integration (Stripe or local bank API)
  • Retry mechanism (3 attempts over 7 days)
  • Dashboard for monthly payments

Acceptance Criteria:

  • ✅ Monthly revenue calculated accurately
  • ✅ ACH debit initiated on last day of month
  • ✅ Failed payments retried with exponential backoff
  • ✅ Merchant sees clear monthly schedule

🚀 MILESTONE 1.4: Monitoring & Analytics (Month 5-6)

Epic 1.4.1: Operational Dashboards

Priority: P0 (Must-Have) Owner: Frontend Engineering + Data Team Effort: 2 engineers × 3 weeks

Requirements:

  • Portfolio Dashboard (Risk Team)
    • Total capital funded
    • Portfolio NPL rate (real-time)
    • Operating mode status
    • Collection performance
    • Top 10 merchants by exposure
  • Underwriting Dashboard
    • Applications/day
    • Auto-approval rate
    • Average TAT by routing level
    • Manual review queue depth
  • Partner Dashboard
    • Applications per partner
    • Funded volume per partner
    • Revenue share calculations
    • Partner NPS scores

Technical Stack:

  • Frontend: Vue.js + Chart.js
  • Backend: PostgreSQL + materialized views
  • Real-time: WebSockets for live updates

Acceptance Criteria:

  • ✅ Dashboards load in <3 seconds
  • ✅ Data refreshes every 5 minutes
  • ✅ Export to PDF/Excel
  • ✅ Mobile-responsive design

Epic 1.4.2: Alerting & Notifications

Priority: P1 (Important) Owner: Backend Engineering Effort: 1 engineer × 2 weeks

Requirements:

  • Email notifications (SendGrid or AWS SES)
    • Application status updates
    • Approval/decline notifications
    • Disbursement confirmations
    • Collection alerts
  • SMS notifications (Twilio or local provider)
    • Critical alerts only (high-priority approvals)
  • In-app notifications
    • Push notifications to mobile app (future)
    • Banner alerts in web dashboard
  • PagerDuty integration for ops team
    • P0: API down, payment processing failure
    • P1: NPL threshold breach, TAT exceeded

Acceptance Criteria:

  • ✅ Email delivery rate >98%
  • ✅ SMS delivery rate >95%
  • ✅ Notifications sent within 30 seconds of trigger
  • ✅ Users can configure notification preferences

📊 Phase 1 Success Criteria

Quantitative Metrics:

  • ✅ Auto-approval rate ≥60%
  • ✅ Average TAT <12 hours (auto) / <8 hours (manual)
  • ✅ 2 pilot partners signed LOIs
  • ✅ 50 merchants funded via pilot
  • ✅ Portfolio NPL <1.5%
  • ✅ API uptime >99.5%

Qualitative Milestones:

  • ✅ Credit scoring engine validated against historical data
  • ✅ Partner API passes beta testing with 2 partners
  • ✅ Underwriters report 50%+ time savings
  • ✅ Zero critical security vulnerabilities
  • ✅ All core services deployed to production

Deliverables:

  1. ✅ Automated Credit Scoring Engine
  2. ✅ CLIK Integration (Production)
  3. ✅ Holdback & Margin Calculators
  4. ✅ Underwriter Workspace (Web App)
  5. ✅ Partner API v1.0 (OAuth, Core Endpoints)
  6. ✅ API Documentation Site
  7. ✅ Sandbox Environment
  8. ✅ Period Limits Feature
  9. ✅ Parallel Projects Feature
  10. ✅ Operational Dashboards

PHASE 2: PARTNER PLATFORM (Month 7-12)

Theme: “Enable Distribution at Scale”

🎯 Phase Objectives

  1. Launch partner portal and onboarding
  2. Onboard 5-8 pilot partners
  3. Deploy white-label UI components
  4. Implement revenue share management
  5. Scale to 300+ merchants via partners

🚀 MILESTONE 2.1: Partner Portal (Month 7-9)

Epic 2.1.1: Partner Registration & Onboarding

Priority: P0 (Must-Have) Owner: Full-Stack Engineering Effort: 3 engineers × 6 weeks

Requirements:

  • Partner registration flow
    • Company information (name, registration, address)
    • Business model description
    • Merchant base size and GMV
    • Integration requirements
    • Contract signing (DocuSign integration)
  • KYC verification for partners
  • Partner approval workflow (internal)
  • Welcome email with onboarding guide
  • Developer account creation
  • API credential generation

User Journey:

1. Partner fills out inquiry form → 2. Sales call (discovery) →
3. Contract negotiation → 4. Sign partnership agreement →
5. Receive API credentials → 6. Read documentation →
7. Integrate in sandbox → 8. UAT testing →
9. Production launch

Acceptance Criteria:

  • ✅ Partner can self-register in <10 minutes
  • ✅ Approval process completes in <5 business days
  • ✅ API credentials generated instantly after approval
  • ✅ Onboarding guide reduces time-to-integration by 50%

Epic 2.1.2: Partner Dashboard

Priority: P0 (Must-Have) Owner: Frontend Engineering Effort: 2 engineers × 4 weeks

Requirements:

  • Portfolio analytics
    • Total applications submitted
    • Approval rate (trending)
    • Funded volume (daily/weekly/monthly)
    • Active funded merchants
  • Revenue share tracking
    • Tier status (Bronze/Silver/Gold/Platinum)
    • Earnings to date
    • Projected earnings (next month)
    • Invoice history
  • Merchant funnel visualization
    • Applications → Approvals → Funded
    • Drop-off analysis
  • API usage metrics
    • Request volume
    • Error rate
    • Latency (p50, p95, p99)
  • Support ticketing
    • Integration support requests
    • Bug reports

Acceptance Criteria:

  • ✅ Dashboard loads in <2 seconds
  • ✅ Data refreshes in real-time (WebSocket)
  • ✅ Export reports to CSV/PDF
  • ✅ Mobile-responsive design

Epic 2.1.3: Revenue Share Management

Priority: P0 (Must-Have) Owner: Backend Engineering + Finance Effort: 2 engineers × 3 weeks

Requirements:

  • Tiered revenue share model 
    Bronze (<$1M/month): 20%
Silver ($1-5M/month): 25%
Gold ($5-10M/month): 28%
Platinum (>$10M/month): 30%
  • Automatic tier upgrades based on volume
  • Revenue share calculation
    • Per merchant: (Fees + Interest) × Partner %
    • Monthly aggregation
  • Invoice generation (automated)
  • Payment processing (ACH or wire transfer)
  • Reconciliation dashboard

Technical Tasks:

  • Revenue share calculation engine
  • Tier upgrade logic (cron job)
  • Invoice generation (PDF)
  • Payment integration (Stripe or bank API)
  • Reconciliation workflow
  • Audit trail

Acceptance Criteria:

  • ✅ Revenue share calculated accurately (verified by finance)
  • ✅ Invoices generated on 1st of month
  • ✅ Payments processed within 5 business days
  • ✅ Zero discrepancies in reconciliation

🚀 MILESTONE 2.2: Pilot Partner Launches (Month 9-11)

Epic 2.2.1: Partner Integration Support

Priority: P0 (Must-Have) Owner: Partner Engineering + DevRel Effort: 2 engineers × 8 weeks

Requirements:

  • Dedicated integration engineers (1 per partner)
  • Weekly sync calls during integration
  • Custom integration support (platform-specific)
  • UAT environment for each partner
  • Bug fixes and optimizations
  • Go-live checklist

Pilot Partner Targets (2-3 partners):

  1. eCommerce SaaS Platform (~5,000 merchants)
  2. Payment Processor (~10,000 SMB merchants)
  3. Marketplace Platform (~2,000 sellers)

Partner Integration Phases:

WeekMilestone
1-2Contract signed, credentials issued
3-4Developer account setup, API docs read
5-6OAuth integration, sandbox testing
7-8Application submission flow implemented
9-10UAT with 5-10 beta merchants
11-12Production launch

Acceptance Criteria:

  • ✅ 2 partners successfully integrated
  • ✅ 50+ merchants funded via partners
  • ✅ Integration time <6 weeks (from contract to launch)
  • ✅ Partner NPS ≥50 at Day 60

Epic 2.2.2: Co-Marketing Campaigns

Priority: P1 (Important) Owner: Marketing + Partnerships Effort: 1 marketer × 12 weeks

Requirements:

  • Joint webinars (partner + Useflik)
  • Co-branded email campaigns
  • In-app placement (banners, widgets)
  • Case studies and success stories
  • Press release for partnership announcement

Campaigns:

  1. Webinar: “How to Grow Your Business with Fast Capital” (partner audience)
  2. Email: “Introducing Capital from [Partner Name]” (merchant base)
  3. In-App Banner: “Get up to $500K in 24 hours” (partner dashboard)

Acceptance Criteria:

  • ✅ 1 webinar per partner (100+ attendees)
  • ✅ Email open rate >25%
  • ✅ In-app banner CTR >5%
  • ✅ 20+ merchants apply within first week of launch

🚀 MILESTONE 2.3: White-Label UI Components (Month 10-12)

Epic 2.3.1: Embeddable Application Form

Priority: P1 (Important) Owner: Frontend Engineering Effort: 2 engineers × 4 weeks

Requirements:

  • React component library (or framework-agnostic Web Components)
  • Pre-styled for common platforms (Shopify, WooCommerce)
  • Customizable branding (colors, logo, fonts)
  • Responsive design (mobile/tablet/desktop)
  • Form validation and error handling
  • OAuth connection reuse (if merchant already connected)

Embed Code Example:

<script src="https://cdn.useflik.com/v1/widgets/application.js"></script>
<div id="useflik-application"
     data-partner-id="partner_123"
     data-theme="light"
     data-primary-color="#007bff">
</div>

Acceptance Criteria:

  • ✅ Widget loads in <500ms
  • ✅ Works on 5+ major platforms (tested)
  • ✅ Branding customization in <5 minutes
  • ✅ Mobile conversion rate >70%

Epic 2.3.2: Offer Display Widget

Priority: P1 (Important) Owner: Frontend Engineering Effort: 1 engineer × 3 weeks

Requirements:

  • Display funding offer with transparent terms
    • Funding amount
    • Payback total (1.1-1.4x)
    • Repayment %
    • Estimated term
    • Effective APR
  • Repayment calculator (interactive slider)
  • Accept/Decline buttons
  • DocuSign integration (embedded signing)

Acceptance Criteria:

  • ✅ Widget renders in <300ms
  • ✅ Calculator updates in real-time
  • ✅ Accept rate >50% (merchants who see offer)
  • ✅ Signing flow completes in <3 minutes

Epic 2.3.3: Merchant Dashboard Widget

Priority: P2 (Nice-to-Have) Owner: Frontend Engineering Effort: 1 engineer × 3 weeks

Requirements:

  • Balance display (remaining amount)
  • Payment history (last 10 payments)
  • Next payment date and amount
  • Early payoff calculator
  • Support chat integration

Acceptance Criteria:

  • ✅ Widget embeds in partner platform
  • ✅ Real-time balance updates
  • ✅ Payment history loads in <1 second
  • ✅ Merchant satisfaction score ≥4/5

📊 Phase 2 Success Criteria

Quantitative Metrics:

  • ✅ 5-8 active partners
  • ✅ 300+ merchants funded via partners
  • ✅ Partner-driven CAC <2,000 direct)
  • ✅ Partner NPS ≥60
  • ✅ Merchant NPS ≥50
  • ✅ Revenue share payments processed without errors

Qualitative Milestones:

  • ✅ Partner portal rated 4.5/5 by partners
  • ✅ Integration time reduced to <4 weeks
  • ✅ White-label widgets adopted by 80%+ of partners
  • ✅ Co-marketing campaigns generate 100+ applications
  • ✅ Zero partnership churn

Deliverables:

  1. ✅ Partner Portal (Registration, Dashboard, Support)
  2. ✅ Revenue Share Engine
  3. ✅ 5-8 Pilot Partners Live
  4. ✅ White-Label UI Components (3 widgets)
  5. ✅ Co-Marketing Campaign Toolkit
  6. ✅ Partner Success Playbook

PHASE 3: SCALE & OPTIMIZE (Month 13-18)

Theme: “Wayflyer Parity + Geographic Expansion”

🎯 Phase Objectives

  1. Deploy ML-based underwriting (80%+ auto-approval)
  2. Scale to 15+ partners
  3. Launch advanced recollection features
  4. Geographic expansion (Malaysia, Philippines)
  5. Achieve $50M funded capital

🚀 MILESTONE 3.1: ML-Based Underwriting (Month 13-15)

Epic 3.1.1: ML Model Development

Priority: P0 (Must-Have) Owner: Data Science + ML Engineering Effort: 1 data scientist + 1 ML engineer × 8 weeks

Requirements:

  • Data collection and labeling
    • 6-12 months of historical applications
    • Label: approved/declined, default/repaid
    • Feature engineering (100+ features)
  • Model training (XGBoost or similar)
  • Feature importance analysis
  • A/B testing (rule-based vs ML)
  • Model monitoring dashboard

Features (Sample):

  • Revenue growth rate (30-day, 90-day, 180-day)
  • Revenue volatility (coefficient of variation)
  • CLIK score (entity, owner)
  • Business age (years)
  • Industry (categorical)
  • Order frequency (orders/month)
  • Average order value
  • Customer concentration (top customer % of revenue)
  • Repeat purchase rate
  • Refund rate
  • Debt-to-revenue ratio (from CLIK)

Model Performance Targets:

  • Precision: >85% (approved loans that repay)
  • Recall: >80% (good loans approved)
  • AUC-ROC: >0.85
  • False positive rate: <2%

Acceptance Criteria:

  • ✅ Model outperforms rule-based by ≥10% in approval rate
  • ✅ NPL rate maintained or improved (<1.3%)
  • ✅ Model inference <2 seconds (p95)
  • ✅ Explainability dashboard for underwriters

Epic 3.1.2: Production Deployment

Priority: P0 (Must-Have) Owner: ML Engineering + DevOps Effort: 1 ML engineer + 1 DevOps × 4 weeks

Requirements:

  • Model serving infrastructure (TensorFlow Serving or similar)
  • Shadow mode (ML scores in parallel, not used for decisions)
  • Gradual rollout (10% → 50% → 100%)
  • Fallback to rule-based if ML fails
  • A/B testing framework
  • Real-time monitoring (Prometheus + Grafana)

Rollout Plan:

Week 1-2: Shadow mode (log predictions, no impact)
Week 3-4: 10% traffic (ML decides, track NPL)
Week 5-6: 50% traffic (expand if NPL stable)
Week 7-8: 100% traffic (full rollout)

Acceptance Criteria:

  • ✅ Shadow mode runs for 2 weeks without errors
  • ✅ NPL stable during 10% → 50% rollout
  • ✅ Auto-approval rate increases to 80%+
  • ✅ Model monitoring alerts on drift or degradation

🚀 MILESTONE 3.2: Advanced Recollection Features (Month 14-16)

Epic 3.2.1: Tiered Recollection

Priority: P1 (Important) Owner: Backend Engineering Effort: 2 engineers × 3 weeks

Requirements:

  • Dynamic recollection % based on thresholds 
    {
  "target": "TIERED",
  "tiers": [
    {"threshold": 5000000, "percentage": 0.10},
    {"threshold": 10000000, "percentage": 0.15},
    {"threshold": 20000000, "percentage": 0.20}
  ]
}
  • Real-time tier calculation
  • Dashboard showing current tier and next threshold
  • Merchant notification on tier change

Example:

  • Collected 0-5M: 10% recollection
  • Collected 5M-10M: 15% recollection
  • Collected 10M+: 20% recollection

Acceptance Criteria:

  • ✅ Tier transitions accurate
  • ✅ Performance <50ms added latency
  • ✅ Dashboard shows tier progress
  • ✅ Notifications sent within 5 minutes

Epic 3.2.2: Category-Based Recollection

Priority: P2 (Nice-to-Have) Owner: Backend Engineering Effort: 1 engineer × 2 weeks

Requirements:

  • Recollection based on product category 
    {
  "target": "CATEGORY",
  "categories": ["Electronics", "Apparel"],
  "percentage": 1.0
}
  • Category matching logic
  • Dashboard for category performance

Acceptance Criteria:

  • ✅ Category matching accurate
  • ✅ Support 10+ categories
  • ✅ Performance acceptable (<100ms)

🚀 MILESTONE 3.3: Geographic Expansion (Month 15-18)

Epic 3.3.1: Multi-Currency Support

Priority: P1 (Important) Owner: Backend Engineering Effort: 2 engineers × 4 weeks

Requirements:

  • Support IDR, MYR, PHP (Malaysia, Philippines)
  • Currency conversion (real-time exchange rates)
  • Multi-currency reporting
  • Currency-specific underwriting parameters

Technical Tasks:

  • Currency field in database schema
  • Exchange rate API integration (e.g., Fixer.io)
  • Currency formatting in UI
  • Multi-currency reconciliation

Acceptance Criteria:

  • ✅ Support 3 currencies initially
  • ✅ Exchange rates update hourly
  • ✅ Reporting accurate across currencies
  • ✅ No currency conversion errors

Epic 3.3.2: Regional Operating Modes

Priority: P1 (Important) Owner: Risk + Engineering Effort: 1 risk analyst + 1 engineer × 2 weeks

Requirements:

  • Operating mode per country
    • Indonesia: Conservative/Standard/High-Growth
    • Malaysia: Conservative/Standard (initially)
    • Philippines: Conservative (initially)
  • Country-specific underwriting parameters
    • Min revenue threshold
    • Max facility amount
    • CLIK equivalent (Malaysia: CTOS, Philippines: CIC)

Acceptance Criteria:

  • ✅ Operating modes configurable per country
  • ✅ Underwriting parameters adapt automatically
  • ✅ Dashboard shows mode per country

🚀 MILESTONE 3.4: Partner Scaling (Month 16-18)

Epic 3.4.1: Partner Marketplace

Priority: P2 (Nice-to-Have) Owner: Product + Engineering Effort: 2 engineers × 4 weeks

Requirements:

  • Public marketplace for partners
    • List of integrated partners
    • Partner profiles (description, industries served)
    • Apply to join as partner
  • Partner referral program
    • Refer other partners, earn bonus
  • Partner leaderboard (gamification)

Acceptance Criteria:

  • ✅ Marketplace lists 15+ partners
  • ✅ 5+ partner referrals in first 3 months
  • ✅ Leaderboard drives 20%+ increase in partner engagement

Epic 3.4.2: API v2.0 (Advanced Features)

Priority: P2 (Nice-to-Have) Owner: Backend Engineering Effort: 2 engineers × 4 weeks

Requirements:

  • Batch application submission
  • Merchant scoring trends API
  • Portfolio analytics API
  • Custom webhooks (partner-defined events)
  • GraphQL support (in addition to REST)

Acceptance Criteria:

  • ✅ Batch API processes 100+ applications in <10 seconds
  • ✅ GraphQL queries match REST performance
  • ✅ Webhooks support 10+ custom events
  • ✅ 5+ partners adopt v2.0 within 6 months

📊 Phase 3 Success Criteria

Quantitative Metrics:

  • ✅ Auto-approval rate ≥80%
  • ✅ 15+ active partners
  • ✅ 1,500+ merchants funded (cumulative)
  • ✅ $50M total funded capital
  • ✅ Portfolio NPL <1.2%
  • ✅ Partner NPS ≥70
  • ✅ Merchant NPS ≥55

Qualitative Milestones:

  • ✅ ML model in production, outperforming rules
  • ✅ Geographic expansion launched in 2 countries
  • ✅ White-label widgets reduce partner integration time to <2 weeks
  • ✅ Partner marketplace drives organic partner acquisition
  • ✅ Wayflyer parity achieved in core features

Deliverables:

  1. ✅ ML-Based Underwriting Model
  2. ✅ Model Monitoring Dashboard
  3. ✅ Tiered Recollection Feature
  4. ✅ Multi-Currency Support
  5. ✅ Regional Operating Modes
  6. ✅ Partner Marketplace
  7. ✅ API v2.0 (Advanced Features)
  8. ✅ 15+ Partners Live
  9. ✅ $50M Funded Capital

🔄 Cross-Cutting Initiatives (Ongoing)

Security & Compliance (All Phases)

  • SOC 2 Type II certification (Month 12)
  • Penetration testing (quarterly)
  • GDPR compliance audit (Month 18)
  • PCI-DSS compliance (if handling card data)
  • Encryption at rest and in transit
  • Regular security training for engineers

Performance Optimization (All Phases)

  • Redis caching for hot data (Month 3)
  • Database query optimization (ongoing)
  • CDN for static assets (Month 6)
  • Load testing (quarterly)
  • Auto-scaling policies (Month 6)
  • API rate limiting (Month 2)

Documentation & Training (All Phases)

  • API documentation (Month 4, updated continuously)
  • Partner onboarding guide (Month 7)
  • Internal runbooks (Month 3)
  • Video tutorials (Month 9)
  • FAQ and knowledge base (Month 6)
  • Quarterly training for underwriters

Monitoring & Observability (All Phases)

  • Application metrics (Datadog or Prometheus)
  • Error tracking (Sentry)
  • Log aggregation (ELK stack or CloudWatch)
  • Uptime monitoring (Pingdom or UptimeRobot)
  • PagerDuty integration (Month 3)
  • Custom dashboards (Grafana)

💰 Investment & Resource Requirements

Engineering Team (18 Months)

RoleHeadcountDurationCost Estimate
Backend Engineers5-618 months$600K-750K
Frontend Engineers318 months$300K-400K
Data Scientist16 months (M13-18)$75K-100K
ML Engineer16 months (M13-18)$75K-100K
DevOps Engineer118 months$120K-150K
Product Manager118 months$150K-200K
Partnerships Lead112 months (M7-18)$100K-150K
Technical Writer16 months (M4-9)$40K-60K
Total Team13-1518 months1.91M

Technology & Infrastructure

ItemCost (Annual)Notes
Cloud Infrastructure (AWS)$80K-120KAuto-scaling, multi-region, high availability
CLIK API (Credit Bureau)$50K-75K~Rp 750M-1.1B (~7,200 queries/month with caching)
Email/SMS Services$20K-30KSendGrid, Twilio for notifications
Payment ProcessingVariableDepends on volume (ACH fees, bank charges)
Security & Compliance$40K-60KSOC 2 audit, penetration testing
Monitoring & Observability$25K-40KDatadog, Sentry, PagerDuty
DocuSign$15K-25KE-signature for contracts
Total Infrastructure$230K-350K/year

Total Investment (18 Months)

Engineering Team: $1.46M-$1.91M
Infrastructure (18 months): $345K-525K
-------------------------------------------
Total: $1.81M-$2.44M

Mid-Range Estimate: ~$2.1M for 18-month transformation

Return on Investment (ROI)

Assumptions:

  • Average merchant borrows: $80K (Rp 1.2B)
  • Payback multiple: 1.2x
  • Revenue per merchant: $16K (Rp 240M)
  • Cost of capital: 8%
  • Operating expenses: 30% of revenue

18-Month Projections:

MetricMonth 6Month 12Month 18
Merchants Funded1005001,500
Capital Deployed$8M$40M$120M
Revenue (Fees)$1.6M$8M$24M
Gross Margin (70%)$1.12M$5.6M$16.8M
Cumulative NPL (2%)-$160K-$800K-$2.4M
Net Profit$960K$4.8M$14.4M

ROI Calculation:

  • Investment: $2.1M
  • Net Profit (18 months): $14.4M
  • ROI: 585% over 18 months
  • Payback Period: ~3 months (Month 6 breakeven)

🚨 Risk Management

Critical Risks & Mitigations

RiskLikelihoodImpactMitigation
Partner Acquisition FailureMediumCriticalStart partner outreach in Month 1, sign 2 LOIs before building Partner API
ML Model UnderperformsMediumHighShadow mode testing for 1+ months, fallback to rule-based, gradual rollout
NPL SpikeMediumCriticalConservative operating mode by default, margin viability checks, monthly portfolio reviews
Technical DelaysHighMediumAgile sprints with bi-weekly reviews, MVP approach, cut scope if needed
Regulatory ChallengesMediumHighLegal review before launch, engage with OJK early, compliance-first design
CLIK API IssuesLowHigh30-day caching, fallback to manual check, SLA monitoring, backup credit bureau (if available)
Partner ChurnLowMediumDedicated partner success team, revenue share guarantees (first 3 months), co-marketing support

Dependency Risks

DependencyRiskMitigation
CLIK Credit BureauService downtime, price increaseCache scores, negotiate SLA, evaluate alternative bureaus (CTOS, CIC)
Cloud Provider (AWS)Regional outageMulti-AZ deployment, DR plan, regular backups
Payment GatewayDisbursement delaysPartner with 2-3 gateways, manual fallback
Third-Party APIsBreaking changesVersion pinning, monitoring, quick migration plan

📈 Success Metrics Dashboard

North Star Metric: Total Capital Funded

Target Trajectory:

Month 3:  $1M   (pilot)
Month 6:  $5M   (Phase 1 complete)
Month 9:  $12M  (pilot partners scaling)
Month 12: $25M  (partner platform live)
Month 15: $40M  (ML + geographic expansion)
Month 18: $60M  (15+ partners, 1,500+ merchants)

Leading Indicators (Monthly Tracking)

MetricTarget (M6)Target (M12)Target (M18)
Applications/Month3001,0002,500
Auto-Approval Rate60%75%85%
Approval→Funding Time<12h<4h<1h
Partner NPS50+60+70+
Merchant NPS45+50+55+
API Uptime99.5%99.7%99.9%

Lagging Indicators (Quarterly Review)

MetricTarget (Q2)Target (Q4)Target (Q6)
Total Funded Capital$5M$25M$60M
Active Partners2815
Portfolio NPL<1.5%<1.3%<1.2%
Revenue (Fees)$1M$5M$12M
LTV/CAC Ratio8:112:115:1

🎓 Lessons from Wayflyer (Apply to Our Roadmap)

What Wayflyer Got Right:

  1. API-First Design → We prioritize Partner API in Phase 1
  2. Fast Approvals (<24h) → We target <12h in Phase 1, <1h in Phase 3
  3. Transparent Pricing → We display APR equivalent, clear terms
  4. Partner Distribution → We focus on partners from Phase 2 onward
  5. Revenue-Based Repayment → We add MONTHLY_REVENUE target in Phase 1
  6. White-Label UI → We build embeddable widgets in Phase 2
  7. Data-Driven Underwriting → We deploy ML model in Phase 3

Where We Differentiate:

  1. Local Market Expertise → CLIK integration, PKP/NON-PKP handling, IDR focus
  2. Flexible Recollection Strategies → 3 strategies (ALL, SPECIFIC_PRODUCTS, VOUCHER) vs Wayflyer’s single revenue %
  3. Adaptive Risk Management → Operating modes (Conservative/Standard/High-Growth) dynamically adjust
  4. Product-Level Tracking → Bulk purchase products with SKU/quantity/COGS/margin
  5. Southeast Asia Focus → Multi-currency (IDR, MYR, PHP), regional partnerships

🚀 Getting Started (Next 30 Days)

Week 1-2: Strategic Alignment

  • Executive review and approval of roadmap
  • Secure budget ($2.1M for 18 months)
  • Identify 3-5 pilot partner targets
  • Conduct partner discovery calls
  • Legal review (embedded finance regulations in Indonesia)

Week 3-4: Team Formation & Kickoff

  • Hire/assign engineering team (5-6 backend, 3 frontend)
  • Hire product manager (embedded finance experience preferred)
  • Hire partnerships lead
  • Kickoff meeting (entire team)
  • Sprint planning for Month 1-2
  • Set up project management tools (Jira, Confluence)
  • Architecture review and tech stack finalization

Month 2: Development Sprint 1

  • Credit Scoring Engine (initial implementation)
  • CLIK Integration (SOAP client, NAE function)
  • Partner API design (OpenAPI spec)
  • Database schema updates
  • CI/CD pipeline setup

📚 Appendix

A. Key Documents Reference

  1. Gap Analysis Report - Current vs Wayflyer comparison
  2. Wayflyer PRD - Reverse-engineered product requirements
  3. Onboarding PRD - Pre-disbursement specifications
  4. Existing Flow Analysis - Current recollection system

B. Glossary

  • MCA: Merchant Cash Advance - Alternative financing based on future revenue
  • NPL: Non-Performing Loan - Loan past due >30 days
  • AMR: Average Monthly Revenue - 6-month average
  • TAT: Turnaround Time - Application submission to decision
  • CLIK: Credit bureau in Indonesia (similar to Experian/Equifax)
  • PKP/NON-PKP: Indonesian tax categories (VAT registered vs non-registered)
  • B2B2C: Business-to-Business-to-Consumer (platform partners serving merchants)

C. Competitive Landscape

  • Wayflyer: $1.6B funded, Europe/US, strong brand
  • Clearco: $2B+ funded, struggled with defaults (2022)
  • Stripe Capital: Integrated with Stripe payments, US-focused
  • Our Advantage: Southeast Asia focus, local partnerships, flexible recollection

✅ Approval & Sign-Off

RoleNameSignatureDate
CEO________________________________
CFO________________________________
CTO________________________________
CRO (Risk)________________________________
Product Manager________________________________

Document Status: Draft for Review Next Review: Q2 2026 (after Phase 1 completion) Version Control: This is a living document, updates will be versioned and communicated to all stakeholders

END OF ROADMAP

Generated: January 6, 2026 Prepared by: Product & Engineering Team Confidence Level: High (based on comprehensive gap analysis and Wayflyer reverse engineering)

Graph View