SociallyMe
AI-powered Social CRM, CMS & Prospecting Platform
An AI-powered growth platform combining CRM, lead generation, prospect research, content management, social engagement, and personalized AI assistance into one system.
01 / CONTEXT
The problem
Founders, consultants, sales professionals, creators, and growth teams frequently have to combine separate tools for CRM, prospecting, content management, social publishing, research, and AI writing. More importantly, generic AI-generated outreach can lack the context and personal voice required to build genuine relationships.
02 / APPROACH
How I built it
Prospect information and CRM state are stored centrally. Research workflows enrich leads with web context, after which a VoiceProfile layer conditions AI generation so that replies and content suggestions reflect both the user's style and the specific relationship context.
03 / CONSTRAINTS
What had to hold
Multiple social platforms Large amounts of prospect context Need for personalized communication CRM state synchronization Web research and enrichment Avoiding generic AI-generated outreach
04 / OBJECTIVES
Definition of done
• Centralize prospect research • Build an integrated social CRM • Manage content through a headless CMS • Learn and preserve the user's writing voice • Generate context-aware replies • Connect research with CRM state • Reduce repetitive prospecting work
05 / THE SYSTEM
Architecture
Reactive application A modern client application provides CRM, content, and prospecting workflows. Central collection runtime QuestPie provides centralized entity and collection management. Research pipeline Firecrawl-powered workflows gather relevant web context around prospects. Voice profile engine Writing samples are analyzed to build a reusable representation of the user's communication style. AI task orchestration Background tasks handle lead discovery, voice extraction, content curation, and generation. CRM-aware generation AI suggestions incorporate prospect history and pipeline context rather than generating generic messages.
06 / DECISIONS
Key decisions
Combine CRM context with AI generation Why: Personalization requires relationship history and prospect context, not just a language model. Use web research before generation Why: Relevant external context produces more informed prospecting and engagement suggestions. Build a VoiceProfile layer Why: AI-generated communication should reflect the user's established writing patterns and positioning. Unify CRM and CMS Why: Relationship-driven growth requires content and prospecting workflows to share the same context.
07 / SHIPPED
Deliverables
• Lead generation (delivered) — Core capability of the product (see features). • Prospect discovery (delivered) — Core capability of the product (see features). • Lead enrichment (delivered) — Core capability of the product (see features). • Influencer discovery (delivered) — Core capability of the product (see features). • Decision-maker discovery (delivered) — Core capability of the product (see features).
08 / LESSONS
What I'd keep
• Lead generation is not enough if outreach feels automated. • CRM context and authentic voice are critical to relationship-driven prospecting. • AI becomes more valuable when it operates on rich business context rather than isolated prompts. • Research, CRM, content, and engagement should share a common data model when they are part of the same growth workflow.
What changed
4 → 1
Core growth tools consolidated
to date
70%+
Prospect research and engagement time reduction
to date
// START A PROJECT
Building something with similar constraints?
If it's in your critical path and you'd rather not learn its failure modes live, let's talk about it.