Pebble Business Orchestrator¶
Welcome to the Pebble Business Orchestrator Documentation.
Your single source of truth for building an AI-powered sales orchestration system that unifies email intelligence, CRM/ERP workflows, and operational automation.
What This Documentation Covers¶
Business Modules - Pre-lead screening, email triage, visual kanban, quotation generation, tender management, quality tracking
Data Foundations - Multi-entity masters, hierarchical customer structures, product DNA, GST/CIN validation
System Integration - D365, Odoo, Zoho connectors with real-time sync
AI Capabilities - Email classification, deduplication, source attribution, negotiation tracking
Operational Safety - 11:30 AM work shifting, escalation chains, SLA governance
Quick Navigation¶
🚀 GTM & Business Pipeline¶
- Prelead Management - Excel ingestion → 3-level screening → CRM mapping
- Email Orchestration - Outlook sync → Email cards → Stream routing
- Visual Kanban - Drag-and-drop board → Status triggers → Work shifting
- Quotation & Costing - Landed cost → Supplier RFQ → Broker flows
- Sales Follow-up - Sequence automation, dialer sync, response tracking
🏭 Factory Ops & Knowledge¶
- Operations & Logistics - Quote-to-order conversion, route planning
- Tender Management - GEM screening, bid intelligence, compliance
- Quality & Samples - Barcode tracking, lab testing, COA generation
- Ops & Knowledge Overview - DevOps, MLOps, and monitoring
🏗️ Technical Foundation¶
- High-Level Architecture - Event-driven design, data flow, and scaling
- Implementation Overview - Tech stack, project structure, and live screens
- Masters & Metadata - Entity hierarchies and validation
- Workflow Engine - SLA tracking and approval chains
How to Use This Documentation¶
For Product Managers: Start with Vision & Strategy to understand the "why", then explore Use Case Overview for comprehensive requirements.
For Developers: Jump straight to Developer Use Cases for detailed specifications including business logic, scenarios, observability, and acceptance criteria. Each UC includes cross-links to related workflows.
For Architects: Review the core workflow (Prelead → Email → Kanban → Quotation) to understand data flow, then check Integrations for system connectivity.
Finding Specific Features:
- Use the search bar (top right) for keywords like "CIN validation", "11:30 AM shifting", "broker rates"
- Follow cross-reference links (e.g., [EML-013]) between related use cases
- Check module indexes for complete feature lists per functional area
Adding Documentation: - Create new use cases in the relevant module folder - Follow the narrative format: What It Does → How It Works → Edge Cases → Success Signals - Add cross-links to related UCs using markdown anchors - Keep the vault aligned with actual product capabilities
Project Status¶
Total Use Cases: 77 (Added MLOps/DevOps) Comprehensive Documentation: 8 (Prelead, Email triage, Kanban board) MVP Modules: 9 (Covering Email→Kanban→Quote critical path) Architecture: High-Level Documentation (Multi-tenant, event-driven) OSS Strategy: Leverage Wekan/Taiga for Kanban UI, focus engineering on business logic