Sporafind Build Roadmap

Ghanaian diaspora intelligence platform. Phase A is live — each phase funds the next.

🌍 The Vision

Phase A (live): Read-only diaspora intelligence with blog, pricing, and admin tools. Syndicates, recruiters, and researchers pay to search, filter, and export. Frontend: Express + EJS on Vercel serverless. Backend: FastAPI on Vercel with Supabase (PostgreSQL). CI/CD: GitHub Actions + automated testing.
Phase B-D (future): Diaspora members claim their scraped profile, verify, and opt into paid connections. Blog & content marketing drives organic sign-ups. The platform evolves into a two-sided marketplace: intelligence data on one side, social networking with tiered pricing on the other.

◆ Data Architecture

SHIPPED

profiles (scraped)

Companies House officer records. Read-only, never modified by users. Has claimed_by FK to users — ready for Phase B.

SHIPPED

blog_posts + pricing_plans

blog_posts: published/draft posts, tags, categories, analytics, full-text search. pricing_plans: DB-driven tiers with featured flagging. Both served via FastAPI.

PHASE B

user_profiles (new table)

Diaspora members who claim their scraped profile. Stores bio, photo, interests, verified status, and connection price tiers. Linked to profiles via FK.

PHASE C

pricing_tiers + connections (new tables)

connections: tracks who paid to connect, status, Stripe payment intents. Messaging threads tied to each connection.

◆ Strategic Decisions — zero-cost until revenue

Phase A buyer: Investment syndicates, recruiters, researchers
Phase B-C buyer: Same + diaspora members seeking visibility
Phase A pricing: Free + $19/mo paid + Enterprise (per-seat)
Phase C pricing: Platform takes 15% cut on connection fees
Backend: FastAPI (Python) on Vercel
Database: Supabase Free tier (pgvector included)
Frontend: Express + EJS on Vercel serverless
Auth: session.js (client-side) → Better Auth (future)
Deploy: Vercel (frontend + backend, serverless)
LLM: Gemini free tier + open-source on Modal
Data: Companies House free API → Bright Data post-validation
Data (user): Opt-in claimed profiles + direct sign-ups
Testing: pytest (backend) + vitest (frontend) — CI via GitHub Actions