narrativeflow

NarrativeFlow helps B2B marketing and sales teams build a unified narrative framework—extracting brand positioning from existing content, defining ICPs and personas, and then generating hyper-personalized outreach at scale. The platform orchestrates signal-driven campaigns that trigger based on buyer behavior (via Clay.com integration), enriching prospects with narrative context and deploying personalized sequences through HubSpot. It aims to transform scattered messaging into a consistent, value-first narrative that flows from brand positioning through to revenue generation.

Built to solve the problem of fragmented B2B messaging and generic outreach by establishing a single source of truth for narrative context that powers all customer-facing communications. The architecture documents reveal a strategic vision for a scalable "narrative-to-revenue" pipeline using domain-driven design, event sourcing, and signal orchestration—suggesting this is both a learning exercise in modern SaaS architecture patterns and an attempt to build a production-ready marketing operations tool.

Next.js 14 (App Router), TypeScript, tRPC for end-to-end type-safe APIs, Prisma ORM with PlanetScale (MySQL-compatible serverless database), Redis for caching, NextAuth.js for authentication, Tailwind CSS (recently upgraded to v4 with Tailwind Plus application shell), React with Headless UI and Heroicons. Integrations planned for Clay.com (behavioral signals), HubSpot (CRM sync), and OpenAI (content generation).

Last active Jun 28, 2025 — 11 commits across 5 active days (spanning 15 days).

Development spanned 15 calendar days in June 2025 with 11 commits across 5 active days, indicating focused sprint work—likely concentrated bursts of feature development (onboarding flow, UI shell upgrade, multi-tenant architecture) rather than sustained daily work.

The project exhibits sophisticated architectural planning with detailed strategy documents outlining event sourcing, CQRS, and saga patterns for campaign orchestration. However, the sparse commit history (11 commits, 5 active days), extensive placeholder routes (brand, campaigns, icp, personas, launch all present but implementation details not evident), and focus on infrastructure (UI shell upgrade, authentication, multi-tenant scaffolding) over core domain logic suggest this is still in early prototype/scaffolding phase. The deployed Vercel URL and production-ready tech stack indicate serious intent, but execution remains foundational.