Inspiration

As a solo founder, I’ve personally struggled with manual social media monitoring—constantly scanning X (Twitter) for relevant conversations while trying to build a product. Valuable opportunities were often missed simply because social chatter moves faster than humans can track.

Three pain points shaped this project:

  • Time Drain: Hours spent manually searching X instead of building or selling
  • Missed Opportunities: Competitors engaging prospects that I didn’t see in time
  • Tool Gap: Existing social-CRM tools were either expensive for SMBs or poorly integrated with Odoo

When I discovered the Odoo × SNS Hiring Hackathon, it felt like the right moment to build a lightweight, Odoo-native solution that automates what many teams still do manually—turning social conversations into CRM leads.


What it does

Social Radar for Odoo demonstrates an end-to-end pipeline that converts X mentions into CRM-ready lead objects aligned with Odoo’s data model.

The system:

  • Ingests social mentions (via a mock X adapter for hackathon safety)
  • Normalizes and enriches them into Odoo-compatible lead schemas
  • Prepares leads for insertion into Odoo CRM pipelines
  • Shows where and how these leads appear inside Odoo CRM

The focus is on design correctness and integration readiness, not brittle live API calls.


How we built it

  • Modular Python Architecture Six atomic modules with strict contracts:

    • X Data Fetcher
    • Lead Enricher
    • Queue Manager
    • Odoo Integrator
    • Dashboard Renderer
    • Logger / Monitor
  • Mock-First External Integration Due to recent X API monetization, the system uses a mock adapter that mirrors X v2 schemas. Switching to live data requires configuration only—no refactor.

  • Odoo-Aligned Design Lead schemas and pipeline stages match Odoo CRM expectations, ensuring smooth XML-RPC integration.

  • Clean Development Setup GitHub Codespaces, minimal dependencies, and deterministic demo runs.


Challenges we ran into

  • Paid External APIs X’s API access model required designing a safe mock-first adapter without compromising production readiness.

  • ERP Integration Boundaries Ensuring CRM logic, enrichment, and transport layers remain strictly separated.

  • Solo Development Constraints Prioritizing architecture clarity and demo reliability over feature volume.


Accomplishments we’re proud of

  • End-to-End Working MVP A complete pipeline from social mention to CRM-ready lead object.

  • Production-Grade Architecture Stable contracts allow each module to be swapped or extended independently.

  • Zero-Debt Design No hardcoded secrets, no tight coupling, no demo-only hacks.

  • Strong Odoo Fit Designed specifically around Odoo CRM concepts, not generic CRMs.


What we learned

  • How Odoo’s CRM model influences backend integration design
  • Why strict module contracts matter in ERP systems
  • How to design demos that remain reliable under hackathon constraints
  • The value of honest, mock-first integrations over fragile live calls

What’s next for Social Radar for Odoo

  • Live X API integration (when credentials are available)
  • Real-time ingestion via webhooks or queues
  • Multi-platform support (LinkedIn, Reddit, etc.)
  • AI-assisted enrichment and lead scoring
  • Packaging as an Odoo App Store addon

Built With

Share this project:

Updates