The Founder's Problem
Loopr
You’re a solo founder running outbound. Your leads are spread across a spreadsheet, your inbox, and sticky notes. Enterprise CRMs overwhelm you with features designed for sales teams of 20. You don’t need a pipeline manager, you need someone to tell you who to email today and why.
Timeline
17 days
Solo sprint · full ownership
Target User
Solo founders & Outbound sellers
Performance
Pipeline interactions in <1 second, analytics updates in real-time
Why Alternatives Fell Short
- Traditional CRMs are designed for enterprise sales teams. Solo founders drown in unused features.
- Lead context lives everywhere: sheets, notes, emails. Finding a single conversation history takes 5 minutes.
- No tool combines CRM tracking with daily AI guidance. You get notifications, not direction.
- Most products add gamification and noise. You need fewer pings, not more.
What I Built
Dual pipeline views: spreadsheet mode for fast edits, Kanban mode for stage-based movement
AI daily briefing that tells you exactly who to follow up with and why, every morning
Signal Score: each lead rated 0 to 100 based on reply patterns, engagement, and timing
Reply analyzer that detects sentiment and suggests next steps from message content
Tech Stack & Why
React 19 + TypeScript
Strong typing caught state management bugs before they reached users. CRM state is complex.
Vite + Tailwind CSS v4
Sub-second hot reload. Built the neobrutal design system in days.
TanStack Query
Automatic cache invalidation, request dedup, and background refetching for analytics.
Supabase
Auth, Postgres, Edge Functions, and RLS in one SDK. Single-tenant isolation built in.
Groq API
Configurable AI layer for briefings and reply analysis. Llama 3.3 70B at 800 tokens/second.
The 3-Week Process
Pipeline schema + auth + RLS foundation, sheet/kanban UI architecture
AI briefing + reply analyzer integration, signal scoring logic + lead workflows
Analytics layer + polish + deployment hardening
Lessons Learned
Solo founders value clarity over features. Removing noise increased daily active usage.
AI briefings only work when tied to specific next actions. ‘Here’s what’s happening’ isn’t enough.
Signal scoring must be transparent. Users don’t trust a black-box number telling them who to call.
Dual views (sheet + kanban) served both speed editors and strategic thinkers. One view alienated half the users.
Would Do Differently
I'd show the math behind every score. Users don't trust a black-box number telling them who to call, so scoring transparency isn't optional, it's the product.