Project Specifics

What the Content Engagement POC is, why it's being built, and the strategy as currently understood.

Official name Decided

Content Engagement is the official name of this new motion, not a working label for this conversation. It refers to Algolia powering engagement via content, using Algolia's core strengths: AI Retrieval, Configuration, and Scale. This name should be used consistently in any internal or external reference to this work.

What is the Content Engagement POC Decided

A proof of concept for moving Algolia from a search/discovery platform for eCommerce, Retail, and product search into ContentSearch, and from ContentSearch into a machine for Content Engagement.

The core idea: engagement, not just answers. A visitor asking a question on a website shouldn't just get an answer back. The agent should discover intent, understand context, and engage the way a human companion would: proactively, contextually, across a journey, not confined to a single chat box.

Named flavors of engagement:

• Conversational discovery — chat that answers and discovers. Builds on discovery/NLP/grounding work already invested in this project.
• Journey-embedded engagement — embedded through different algolia.com journeys (case study, pricing, homepage), each engaging differently depending on where the visitor is.
• Context and personalization — knowing what page/context the visitor is in and offering something relevant to that specific moment, not a generic chat widget.
• Conversion-oriented — the point of engagement is to bring the visitor into the fold: book a call, start building, ask something deeper. Engagement is instrumental to a business outcome, not a UX nicety on its own.

Why this is being built Decided

In Arijit's own framing: this could define Algolia's next business strategy. It is described as work that will "dictate and define the future" of this initiative, not a routine feature build. The stakes are explicitly strategic and company-level, not a single customer pitch.

Strategy Decided

Dimension	Answer
Backend	Algolia (the search/data layer)
Delivery layer	Agent Studio agents (Algolia's own product)
Target journeys (parallel, not sequential)	Case study pages, pricing page, homepage/landing page
POC deployment	Standalone demo environment simulating those page types. Not injected into live algolia.com. Lower risk, faster iteration, no production exposure while the concept is unproven.
Success bar	System ready to demo to the internal team and to external audiences (Algolia partners), and adopted as the starting point for POCs with Algolia. Concrete and checkable, not a vague sentiment.

Audience for this document Decided

Currently Arijit's own bible. Being documented so it can also become an external, Algolia exec-facing bible without a rewrite. Consequence: language and structure must work in layers, an executive summary layer first, supporting detail underneath, not one flat wall of internal shorthand. Every chapter going forward should keep that layering (big picture, then action items, then full detail), the same pattern already used in Chapter 2's three sub-sections.

Relationship to the existing AC2 build Decided

Grounding work completed so far Decided

Item	Status
Analytics API pull (queries, CTR, conversion, no-results) on the live algolia.com search index	Done. See Chapter 2.1.
Full index x-ray (all 17,138 records, every field)	Done. See Chapter 2.1 (baseline) and 2.2 (enriched copy).
Screenshot sweep of representative case study / pricing / homepage pages	Not started. See Tracker.
GA / Looker Studio export (traffic and behavioral data, separate from Algolia's own query analytics)	Not started. Looker Studio dashboard is not reachable via plain fetch, needs Arijit's export or an authenticated browser session.
Joint UI/UX brainstorm (where engagement should surface, what it should say)	Not started. Waiting on the screenshot sweep and GA data first.

Decisions log

Date	Question	Resolution
2026-07-12	Timeline	Full demo-ready POC by Tuesday this week.
2026-07-12	Audience for this document	Arijit's bible today, structured to also serve as an Algolia exec/external-facing bible without a rewrite. Layered presentation required.
2026-07-12	Success criteria	Demo-ready for internal team and external Algolia partners, adopted as the starting point for Algolia POCs.
2026-07-12	Project naming	"Content Engagement" is the official name of the motion.
2026-07-12	Resourcing / relationship to AC2	Not parallel. Content Engagement is the AC2 work.

Open questions