Embeddable Widgets & API

Overview

Embeddable Widgets expose Condelo's intelligence outputs as embeddable UI components and REST API endpoints for integration into external tools. Instead of requiring users to switch to Condelo, intelligence surfaces inside the tools they already use — CRM, project management, intranets, and custom applications.

This transforms Condelo from a destination application into intelligence infrastructure.

The Problem

• The #1 complaint about knowledge tools: "Search is disconnected from action" — insights live in one tool, decisions happen in another
• Context switching between tools costs knowledge workers an estimated 3.2 hours per week
• Intelligence is most valuable at the moment of decision, not when someone remembers to check a separate tool
• Integration capabilities in most knowledge management tools are limited to basic search APIs
• Organizations want intelligence embedded in existing workflows, not another tab to manage

How It Works

1. Widget SDK — Embeddable React components (iframe or web component) with authentication via API key or OAuth
2. Intelligence API — REST endpoints for retrieval, inference queries, signal status, wiki article content, and surface data
3. Webhook push — Outbound webhooks when signals fire, inferences are published, or wiki articles update
4. Context API — Pass contextual parameters (deal name, customer, product) to scope intelligence to the current workflow

Widget Types

• Competitor Context — Auto-populates with relevant battlecard content for the current deal's competitor (for CRM)
• Customer Voice — Surfaces relevant customer feedback when viewing a feature request (for project management)
• Policy Check — Flags whether proposed actions align with internal policies (for approval workflows)
• Key Metrics — Shows latest surfaces and signals on any dashboard (for intranets)

User Story

A sales team embeds a "Competitor Context" widget in Salesforce. When a rep opens a deal record, the widget automatically populates with relevant battlecard content for that deal's competitor — recent product moves, recommended talk tracks, win/loss patterns. No context switch, no manual lookup. A product team embeds a "Customer Voice" widget in Jira. When viewing a feature request, the widget surfaces relevant customer feedback and support tickets from ingested documents, helping PMs prioritize with real evidence.

Complexity & Timeline

Target Clients

• Personas: Revenue Operations, Product Operations, IT Directors, Platform Engineers
• Verticals: SaaS, Enterprise Software, Financial Services, any organization with established tool ecosystems
• Pitch: "Intelligence where you work — not in another tab."

Revenue Potential

Shifts Condelo's positioning from destination app to intelligence infrastructure — a fundamentally larger market. Supports usage-based pricing (per API call, per widget embed, per webhook). Creates adoption multiplier: users encounter Condelo intelligence without installing or learning a new tool. Opens platform play: third-party developers build on Condelo's intelligence layer. Competitive advantage: most knowledge tools offer basic APIs, not contextual intelligence widgets.

Feature Synergies

• Living Battlecard — Battlecard widgets in CRM are the highest-value integration for sales teams
• Compliance Mapper — Policy check widgets in approval workflows bring compliance intelligence to the point of decision
• Live Intelligence Feeds — Webhook push delivers real-time intelligence events to any connected system

Risks & Open Questions

• Widget SDK maintenance across different host environments (Salesforce, Jira, custom apps) is an ongoing investment
• Authentication in embedded contexts introduces security complexity (CORS, token management)
• Widget performance must be near-instant — users won't wait for intelligence to load in their primary workflow
• Scope creep risk: every team will want a custom widget, need clear widget template framework