Develop a Configurable Digital Operations Platform
Guru.com project description for the Winder platform backbone, SK Financial first vertical, Tumaini Orchard second vertical, and future vertical onboarding.
PROJECT OVERVIEW
We are seeking an experienced backend platform developer or small team to build the configurable Digital Operations Platform backbone for the Winder project.
This is not a single one-off dashboard build. The platform must be designed as a reusable operating backbone that can support multiple verticals through configuration, shared services, integrations, reporting, automation, role-based access, audit logs, and management dashboards.
The first vertical is SK Financial. The second vertical is Tumaini Orchard. Additional verticals are expected to follow, so the platform should be modular, documented, and reusable from the start.
PROJECT READINESS
The front-end and Odoo configuration work have already been completed. The remaining work is backend platform development, integration, reporting, automation, alerting, dashboard setup, testing, deployment support, and handover documentation.
A detailed implementation runbook and private GitHub starter environment have already been prepared. These will be shared with the selected contractor after award and confidentiality confirmation.
PLATFORM-FIRST DELIVERY SEQUENCE
1. Build the configurable Digital Operations Platform backbone.
2. Define vertical configuration conventions for source systems, workflows, dashboards, KPIs, roles, alerts, and reporting marts.
3. Configure SK Financial as the first vertical for financial operations, workflow automation, client/account visibility, Odoo 17 reporting, Superset, Asterisk VOIP, WhatsApp Cloud API, alerts, and management dashboards.
4. Configure Tumaini Orchard as the second vertical for ERP/orchard operations, Odoo 17 reporting, Superset, Asterisk VOIP, WhatsApp Cloud API, alerts, and management dashboards.
5. Document the onboarding pattern so future verticals can be added without redesigning the platform.
CORE PLATFORM SCOPE
- Design the Digital Operations Platform architecture and deployment structure.
- Create a configurable vertical module pattern for business-specific workflows, KPIs, dashboards, roles, alerts, integrations, and reporting datasets.
- Set up a reporting database pattern with raw, staging, mart, and audit schemas.
- Build ETL/integration jobs for APIs, database extracts, webhooks, flat-file imports, and scheduled refreshes.
- Create mart tables, indexed reporting tables, or materialized views for dashboard performance.
- Configure Superset or an approved dashboard layer with role-based access.
- Implement audit logs, data quality checks, reconciliation checks, unmatched-record review, and ETL health reporting.
- Implement alerting and notification conventions for operational exceptions and management summaries.
- Document deployment, secrets handling, backup, monitoring, and handover procedures.
INITIAL VERTICALS
SK Financial:
- Configure the platform for financial operations, workflow automation, client/account visibility, Odoo 17 reporting, Superset dashboards, Asterisk VOIP reporting, WhatsApp Cloud API integration, alerts, management dashboards, and future operational workflows.
- Confirm source systems, Odoo 17 reporting needs, VOIP/SIP requirements, WhatsApp requirements, data access methods, sensitive fields, refresh frequency, dashboard roles, and reconciliation rules before implementation.
Tumaini Orchard:
- Configure the platform for Odoo 17 Community ERP reporting and backend integrations across accounting, CRM, inventory, sales, customer communication, VOIP, WhatsApp, alerts, and management dashboards.
- Use a PostgreSQL reporting database so Superset does not query the live Odoo production database directly.
- Support Apache Superset dashboards, AWS-hosted Asterisk with Airtel Kenya SIP/VOIP, Meta WhatsApp Cloud API MVP integration, SMTP alerts, Nginx/HTTPS/SSL, and ETL reporting pipelines.
- Normalize Kenyan phone numbers to E.164 format, for example +2547XXXXXXXX, before matching calls, WhatsApp messages, CRM leads, and Odoo contacts.
IMPORTANT ARCHITECTURE REQUIREMENTS
- The platform must be reusable across multiple verticals.
- Analytics dashboards should not place heavy query load on live production systems.
- Dashboard datasets should come from reporting tables, mart tables, indexed views, or materialized views.
- Each ETL run should log start time, finish time, source counts, target counts, failures, and last successful refresh.
- Key dashboards should show last refresh time and reconcile to the relevant operational system of record.
- Secrets, credentials, tokens, production data, accounting data, VOIP records, and customer data must be handled securely.
EXPECTED DELIVERABLES
- Digital Operations Platform architecture and implementation plan
- Configurable vertical module pattern and documentation
- Backend environment setup and deployment structure
- Reporting database schemas, marts, views, or materialized views
- ETL/integration scripts with scheduler configuration and run logging
- Superset datasets, charts, dashboards, roles, and alerting where required
- SK Financial vertical configuration and dashboard foundation
- Tumaini Orchard vertical configuration and backend integration foundation
- Security/secrets handling approach
- Backup, monitoring, and operational support recommendations
- Updated GitHub repository with clean implementation files and documentation
- Handover checklist, deployment notes, and test results
IDEAL CONTRACTOR EXPERIENCE
- Backend platform architecture for multi-tenant, multi-business, or configurable operations platforms
- Python ETL scripting, PostgreSQL schema design, SQL views, indexing, data marts, and materialized views
- Apache Superset or comparable BI/dashboard tooling
- Workflow automation, alerting, audit logs, reconciliation checks, and role-based access control
- Linux/AWS administration, Docker or Docker Compose, Nginx, SSL, backups, monitoring, and secure deployments
- Odoo 17 Community integration, XML-RPC or JSON-RPC, Odoo accounting/sales/CRM/inventory data, and custom Odoo modules
- Asterisk PBX, SIP/VOIP, CDR/CEL reporting, and call analytics
- Meta WhatsApp Cloud API, webhooks, idempotency, and customer communication reporting
- Secure handling of credentials, production systems, customer data, financial data, and GitHub workflows
PROPOSAL REQUIREMENTS
When applying on Guru.com, please include:
- Examples of similar backend platform, reporting, ERP, or workflow automation projects
- Your recommended architecture for the configurable Digital Operations Platform backbone
- How you would support SK Financial as the first vertical and Tumaini Orchard as the second vertical
- How you would design the platform so additional verticals can be added later
- Your approach to ETL, reporting database design, mart tables, Superset performance, and reconciliation
- Your approach to security, secrets handling, production credentials, and sensitive data
- Your proposed milestone breakdown, timeline, and actual bid amount
- Any assumptions or questions that must be answered before starting
Note: this is a lumpsum project when bidding. Please provide one lumpsum amount.
CONFIDENTIALITY AND ACCESS
The selected contractor must treat all system access, business data, customer data, accounting data, credentials, VOIP records, WhatsApp messages, and implementation details as confidential.
Production credentials must not be stored in GitHub, shared in chat, or placed inside source code. Environment variables, secure server-side files, GitHub secrets, or a managed secret store must be used.
A GitHub implementation playbook and more detailed vertical documentation will be shared with the selected contractor after award and confidentiality confirmation.
... Show more