Product Delivery Roadmap¶
This document defines what's in scope for each phase of Pebble Orchestrator (Pebble IQ) development. For technical requirements and kickoff preparation, see the Prerequisites & Dependencies.
Executive Summary¶
| Phase | Duration | Core Focus | Status |
|---|---|---|---|
| Phase 1 (POC) | 10 Weeks | Signal Ingest + Visual Kanban + CRM Core | Agreed |
| Phase 2 | 6 Weeks | CRM Workflow + CPQ + Costing Logic | Planned |
| Phase 3 | 6 Weeks | Tally Sync + Order Management + Tenders | Planned |
The Robustness Roadmap (1-Year Evolution)¶
To transition from "Manual Tool" to "Automated Partner," development follows an evolutionary loop:
| Stage | Focus | AI Role | Goal |
|---|---|---|---|
| Shadowing (M1-3) | Data Collection | Shadow | Observations & "Man-in-the-loop" validation to build logic baseline. |
| Thresholding (M4-8) | Confidence Score | Partner | Silent if >95% sure. Approval needed if 60-95% sure. |
| Autopilot (M9-12) | Exception Handling | Expert | 90% automation. Only interrupts for genuine "Edge Cases". |
Phase 1: POC - Visual Kanban + CRM Core (78 UCs)¶
Goal¶
Validate technical feasibility by delivering a Visual Business Workspace with Custom CRM (Core Hub) for 79 granular Use Cases, enabling users to triage emails as actionable cards (manual edit override) and manage the core company engagement records (including Product Code Master) in a native, state-driven system.
[!IMPORTANT] Kickoff Hardening: Before development starts, we will run the
plane-mcp-servertest suite against the customer's self-hosted instance to confirm API read/write stability for all 3 entities.
Customer Context (BOIS Pivot)¶
| Attribute | Detail |
|---|---|
| Core Need | CRM/ERP Action orchestration via Visual Kanban |
| CRM Strategy | Custom Django/PostgreSQL CRM (No data migration from D365) |
| ERP Strategy | Focus RT (Current) → Tally Prime (Phase 3 Target) |
| Multi-Entity | 3 legal entities, separate DBs, cumulative stock reporting |
| Validation | Auto-verify CIN/PAN/GST for all leads |
Core Capabilities¶
| Capability | Description |
|---|---|
| Visual Board | Review & Selection: Plane.so vs Taiga.io |
| Unified Inbox | Aggregates sales@, logistics@, tender@ into one view |
| AI Stream Classify | AI places cards in buckets; manual in-place state override (No Drag/Drop) |
| HOD Guided Triage | Explicit mechanism for HOD to guide/allocate/move tasks between streams |
| Keycloak Identity | Firm Integration: Single-Sign-On foundation for all integrated platforms |
| Groupware Eval | Look & Review: Nextcloud, Mayan EDMS, n8n, Guacamole |
| Custom CRM Core | Company Master (8 tabs), Product Code Master, AI Assistant, OCR |
Phase 2: CRM Workflow & CPQ (26 UCs)¶
Goal¶
Implement a SharePoint-like environment using Nextcloud and an integrated EDMS (Mayan), while automating the Lead-to-Enquiry Lifecycle.
Key Deliverables¶
| Feature | Description |
|---|---|
| CRM Workflow | Integrated state machine tracking leads from source to Enquiry |
| Response Playbook | Automated reply generation based on intent and precedence |
| Margin Control | Workflow for below-target margin approvals and governance |
| Costing Engine | Domestic vs Import price tracking (>5% delta detection) |
| KBN-003 Sync | Bidirectional Drag-and-Drop integration for Plane boards |
| Transporter RFQ | Automated inquiry to logistics partners from order cards |
Phase 3 Key Deliverables¶
| Category | Features |
|---|---|
| Tally Integration | Stock, Order, and Ledger sync via XML/HTTP |
| Operations | Dispatch Screens, Sales-to-Ops Handover, Back-to-Back Orders |
| Tender IQ | Document Screening, GEM Automation, Performance Selector |
| Intelligence | AI-Grounded Drafts with Real-time ERP context |
Future Roadmap (Post-Phase 3)¶
The following areas are identified for future expansion and are not included in the current 2,700h base scope:
- Field Sales: Geofenced visits, route planning, nearby customer discovery.
- Quality & Samples: Barcode tracking, LIMS integration, Smart COA shuffling.
- Security Hardening: Apache Guacamole VDI for secure remote access.
ARCHIVED: DMS & Deduplication¶
[!NOTE] Status: Archived per customer feedback (December 2025). Legacy modules available in the Archive-DMS folder. This includes Hash-based dedup, Semantic Search, and OCR processing of raw document dumps.