PPL Spark
ProductsLabWiki

Product — RAIner & the StoryMatcher Flow

RAIner is a conversational AI companion for life and leadership orientation. A user has one ~20-minute dialogue and leaves with a growth trajectory — not a personality label. This page walks through what the product actually does today.

The user journey

  1. Entry. User arrives from a post or campaign, opens the chat.
  2. Profile integration. With consent, the agent reads the user's LinkedIn — especially the two most recent roles — to ground the conversation in real context.
  3. Story selection. The StoryMatcher agent pulls ~5 leadership stories from a vector database that's been hand-tagged against Robert Kegan's developmental stage model (S2 through S5, with half-steps). Stories are personalized to the user's LinkedIn context while preserving their developmental structure.
  4. Iterative refinement. The user picks the story that lands emotionally — "that's me" or "I want that." The system uses the score of the chosen story to retrieve the next set, deliberately mixing nearby and distant stages. This repeats 4–6 times.
  5. Insight report. Selected stories aggregate into a score range, which produces a personalized report on who the user is now and who they are becoming.
  6. Ongoing engagement. Continued conversation via WhatsApp/Telegram/Slack, stored (privacy-enabled) for future peer matching based on developmental resonance, not static type.

Full spec: User Experience and AI processing · System prompts

What makes this different

Unlike MBTI, Enneagram, DiSC, or Big Five, RAIner is:

  • Narrative-based, not trait-based — you choose stories, not answer questionnaires.
  • Evolving, not static — the output is a trajectory, not a fixed label.
  • Context-aware — grounded in your actual professional history from LinkedIn.
  • Peer-matchable — two users can be connected by developmental resonance across growth arcs, not by shared personality type.

Full comparison table: RAIner vs. typology tools

HR customer experience

On the HR side, the product is framed as a reactive-to-proactive shift. Before RAIner: a manager notices morale is off, scrambles to find a training, something generic gets deployed late. After RAIner: the platform surfaces early signals ("Mira has hidden potential — invite her to a growth conversation," "Jamal is drained — a shared lunch would help"), giving HR leverage in ~1.5 hours/week instead of a reactive grind.

Story: HR Customer Journey · Buyer-side framing: EMCC HR Buyers Guide

Sector adaptations

Underlying tech notes

The retrieval layer is a RAG system (retrieve-and-rerank is the current default). The team has mapped the trade-offs across classic, multimodal, graph, hybrid, agentic, and multi-agent RAG — see Rag Systems. Infrastructure details and platform decisions are tracked under Technology.