Project: Build an enterprise-grade AI-powered recommendation and commerce module for a white-label health intelligence platform
Proposal Deadline: End of Day (EOD), Thursday 18 December 2025
Preferred Timezones: UTC-8 to UTC+4 (we do not work with agencies operating primarily in UTC +5 as it’s too difficult with meeting times)
Deployment Preference: Azure-first (with well-justified alternatives accepted)
Who We’re Looking For:
We are seeking a highly capable digital delivery agency or systems integrator with proven experience in building AI-driven, cloud-native, multi-tenant, production-grade systems using modern technology stacks. You must be able to:
✔ Design and deliver backend services, APIs, and data pipelines
✔ Deliver highly scalable systems with minimal ongoing human-ops burden
✔ Integrate AI/ML into real-time workflows
✔ Think modular, reusable, secure, and extensible
✔ Work with large catalogs, personalization, and dynamic ranking
We value engineered solutions over knee-jerk low-code choices, clarity over ambiguity, and scalable patterns over one-off hacks.
Why This Engagement Matters
You will be helping shape a core revenue-driving module in a platform that will power AI-driven product and diagnostic recommendations, personalized to individual health contexts.
This module will:
-Ingest large product catalogs (starting with JSON from a commercial source)
Rank and serve personalized recommendations (contextual + health signal aware)
Power both static UI lists and AI chat experiences
Integrate with a commercial storefront (via deep links/WebView)
Support multi-tenant white-label deployments (SaaS, API licensing, and IaC/IaaS)
What You Must Demonstrate
Your proposal must include the following:
1. Technical Delivery Approach
- Architecture design & stack recommendations (Azure-first preferred)
- Multi-tenant design for SaaS, API licensing, and customer-hosted deployments
- AI-enabled recommendation/ranking strategy
- Integration with existing AI chat and health signal systems
- Handling of commerce links/purchases via external provider
2. Technology Stack
- Azure services (App Services, AKS, Azure AI Search, Azure OpenAI, Service Bus, PostgreSQL, Key Vault, etc.)
- API-first, IaC-packaged modules (Terraform + Helm)
- Justification for any non-Azure components
3. Team & Resourcing
- Roles & seniority
- Plan for parallel resourcing
- Ability to scale on demand
4. Timeline & Milestones
- Phase breakdown with deliverables
- Effort estimates
- Dependencies and assumptions
5. Cost
- Total cost with breakdowns
- Assumptions, exclusions, and risk buffers
6. Relevant Experience
- Case studies showing:
- AI-based personalization/recommendation systems
- Multi-tenant, modular architecture delivery
- Azure managed services deployments at scale
- Health or sensitive data domains (privacy/security considerations)
Timeline & Submission Details
Proposal Deadline:
📅 End of Day — Thursday, 18 December 2025
(Please account for UTC timestamps; submit your package as a PDF or Google Doc link)
Required Format:
Executive Summary (1–2 pages)
Technical Proposal
Architecture Diagrams
Resource Plan
Costing & Assumptions
Risks & Mitigations
Timeline / Gantt chart (ideal)
Clarifications & Q&A:
We will provide a short, scheduled Q&A window for agencies to ask clarifying questions. Questions must be submitted in writing by EOD Wednesday 5pm UTC +8.
Timezone & Collaboration Expectations
We explicitly do not engage with agencies whose primary operational hours are in Indian or Pakistani timezones as working hours do not overlap. Do not apply if your development team, management or QA team are located in those timezones.
We expect regular touchpoints, clear escalation paths, and demonstrable progress — async work is fine, but delivery accountability requires overlap.
What Success Looks Like
✔ Production-ready, stable, scalable APIs
✔ Recommendation outputs aligned with contextual and health signals
✔ Clear, documented integration contracts for UI + chat
✔ IaC that empowers customer-hosted deployments
✔ Minimal ongoing ops overhead (self-healing, automated monitoring/alerting)
✔ Clear analytics around usage, performance, and errors
Final Notes
This is not a research project — we require production engineering plans and delivery cost estimates. Proposals must demonstrate “done, in production, with observability and support strategy” thinking.
We reward clear architecture thinking, operational reality, and robust trade-off analysis.
We look forward to reviewing your proposal by EOD Thursday, 18 December 2025.