From a blank repo to a live, billing SaaS in 60 days - solo.
Sociovox is a full-stack SaaS platform for independent content creators and creator management agencies - combining a content calendar, brand deal CRM, Gmail-powered brand inbox, auto-republish workflows, and Stripe billing under one dashboard.
Sole founder and PM. Owned the entire product surface: discovery, roadmap, UX decisions, feature specs, and release sequencing. Used an AI-assisted coding tool (Antigravity) as the engineering execution layer - making every architectural and product call myself.
Live at sociovox.in with three billing tiers (Free, Pro, Agency) powered by Stripe. All 6 core modules are feature-complete and deployed on Vercel.
While managing my own LinkedIn presence and tracking brand outreach manually across spreadsheets and Gmail threads, I realized the same problem was universal for any creator or agency at scale: the operational overhead of content management is invisible until it breaks.
Existing tools solve one piece - scheduling, or CRM, or analytics - but force creators to stitch 4-5 products together. The context-switching cost and data fragmentation across those tools is the actual productivity killer. Sociovox is the single pane of glass.
This wasn't a spec exercise. Every feature decision had a direct cost consequence - API bills, Vercel limits, Stripe fees - which meant prioritisation was forced, not academic.
Growing 10k-500k followers, juggling brand outreach via DMs and emails, missing deals because of no system, posting inconsistently due to no calendar.
Managing 10-50 creators simultaneously with no unified view of deal status, content pipeline, or per-creator performance. Drowning in client WhatsApp threads.
Tools like Hootsuite solve scheduling. HubSpot solves CRM. Notion solves notes. None of them speak "creator" - no brand deal pipeline, no per-platform analytics mapped to deal ROI, no inbox purpose-built for inbound sponsorship. Sociovox is the first tool that connects content output to commercial outcome in one view.
"When I get a brand collaboration inquiry in my Gmail, I want to track it from first contact
to payment - but I'm stuck copy-pasting between Gmail, a spreadsheet, and my posting tool,
losing deals in the chaos."
The Workflow Cost
Every feature had to answer one question: does this help a creator earn more or spend less time on admin? Features that didn't pass this test didn't ship in V1.
Shipped in trust-building order: Calendar first (immediate value, low risk), then Analytics (data confidence), then Brand CRM + Gmail Inbox (monetization-adjacent), then Auto-Republish + Billing (retention and revenue).
"The operating system for creator businesses - not another scheduling tool."
Next.js 14 App Router for SSR and route-level auth. Supabase for database and auth. Stripe for billing with webhook-driven entitlement. Gmail API (OAuth) for the brand inbox. Vercel for deployment.
Each feature went through a micro-PRD (problem → acceptance criteria → edge cases) before any code was written. This prevented the most common solo-founder trap: building the wrong thing fast. Spec discipline over speed.
OAuth scope management for Gmail. Getting read-only inbox access without triggering Google's security review required careful scope scoping - fetching only unread threads tagged with sponsorship keywords rather than full inbox read. Took 3 iterations to pass OAuth verification.
Deliberately cut the social scheduling (auto-post to Instagram/YouTube) feature from V1 despite user demand - the API approval timelines from Meta and Google would have delayed launch by 6+ weeks. Shipped the calendar as a planning tool first, with publish integration queued for V2.
Drag-and-drop post planning with platform tags, status tracking (Draft → Scheduled → Published), and per-creator views for agency accounts.
Aggregated performance metrics across platforms - engagement rate, reach, post frequency - mapped to content type and publishing cadence.
Kanban pipeline (Contacted → Negotiating → Contracted → Paid) for tracking sponsorship deals from first contact to invoice. Per-deal notes, value, and deadline tracking.
OAuth-connected inbox view filtered for brand outreach - surfaces unread sponsorship threads without exposing personal email. One-click push from inbox to CRM pipeline.
Workflow engine that re-queues evergreen content based on performance thresholds - if a post hit above-average engagement, it auto-schedules a re-share at optimal timing.
Free / Pro / Agency tiers with Stripe Checkout and webhook-driven feature entitlement. Upgrade prompts triggered contextually when a user hits a tier limit mid-workflow.
Ran 15 async interviews with independent creators (5k-200k followers) and 4 small creator agencies before writing a line of code. Used a Notion-based "painted door" - a fake product page with a waitlist - to gauge interest before committing to the build.
I assumed the calendar would be the most-requested feature. It wasn't. The brand inbox was. Every creator I talked to described missing or losing brand deals in their personal Gmail as their #1 pain point. This moved the Gmail integration from "Phase 2" to a V1 core module.
Early feedback showed creators didn't want another scheduling tool - they wanted revenue clarity. This shifted the product's identity from a "content tool" to a "creator business OS," which also changed how I wrote the landing page and pricing positioning.
Agency users needed a fundamentally different view - multi-creator dashboards, not single-creator flows. This drove the Agency tier design: same modules but with a "client switcher" layer on top rather than duplicating the entire product.
Content-led, founder-driven: LinkedIn posts documenting the build journey drove the waitlist. Positioning myself as a "Technical PM building for creators" attracted both early users and PM community attention simultaneously.
Free tier is deliberately generous on the calendar and analytics - the features that create habit. The paywall sits at Brand CRM and Gmail Inbox, which are the features creators need once they start getting paid. Upgrade intent is highest at the moment of deal arrival.
Creator communities on Discord and Reddit (r/NewTubers, r/CreatorEconomy) were higher-intent than LinkedIn for product feedback. LinkedIn drove awareness; Discord drove signups.
The CRM Kanban creates a "deals in progress" state that makes churning psychologically difficult - users with active deals in the pipeline have a strong reason to stay even before they've paid.
% of signups who connect Gmail and create their first CRM deal within 7 days - the core activation event.
Tracked by cohort. Triggered upgrade prompts at natural friction points (deal limit reached, inbox quota hit).
How quickly a new user moves a brand deal from inbox to CRM pipeline - the single metric that predicts retention.
% of eligible posts that trigger the auto-republish workflow - signals that the content engine is embedded in the creator's routine.
The product is live, billing is active, and the core loop (inbox → CRM → calendar → analytics) works end-to-end. Every technical and product decision was mine - this is the closest thing to proof-of-PM-execution I have.
Every time I skipped the acceptance criteria step and went straight to building, I ended up rebuilding. A 30-minute micro-PRD saved an average of 4 hours of rework. This is the lesson I'll carry into every PM role - engineering time is the most expensive resource, even when it's AI-assisted.
The order you ship modules changes user behavior permanently. Shipping calendar before CRM meant users built a posting habit before a deal-tracking habit - which created the right mental model. If I'd shipped CRM first, the product would have felt like a business tool, not a creative one.
The social auto-publish feature (direct posting to Instagram/YouTube) was the most-requested item. I cut it from V1 entirely. The right call - Meta API approval alone would have taken 8+ weeks and stalled everything. A useful product that ships beats a perfect product that doesn't.
Google's OAuth verification process is not just an engineering problem - it's a trust and positioning problem. How you describe your app's use of Gmail data to Google is essentially a product brief. Framing it wrong (even technically correctly) gets you flagged for security review. Writing that brief taught me more about product clarity than any PRD template.
I can take a product from zero - no team, no funding, no existing codebase - to a live, billing, multi-module SaaS with real users in 60 days. Every decision from database schema to upgrade prompt copy was a product decision I owned.
Scale. Sociovox is early. The real test - retention past 30 days, paid conversion at volume, agency expansion - is still being run. But the foundation is solid, the loop works, and the product is live at sociovox.in.
This isn't a case study about a feature I helped ship inside a large company. This is what happens when a PM has no one to hand off to - every tradeoff, every scope cut, every user conversation, every technical constraint is navigated alone. That's the sharpest PM training available.
Every tool, library, and service used
Key architectural decision: Keeping the entire backend inside Next.js API routes (rather than spinning up a separate Express/FastAPI server) reduced deployment complexity to zero - one Vercel project, one environment, one set of environment variables.
The spec that drove the most complex module
Creators receive brand collaboration inquiries via Gmail but have no way to separate them from personal email, track their status, or move them into a deal pipeline without manual copy-paste.
Where Sociovox sits vs. existing tools
Strong on scheduling. No brand deal management. No Gmail integration. Priced for marketing teams, not individual creators. The UX assumes you already know what you want to post - no help with the business side of being a creator.
Built for brands to manage creators, not for creators to manage their own business. Expensive, enterprise-focused, and require the brand to onboard you - a creator can't self-serve.
Flexible but blank-slate. High setup cost for each creator. No Gmail connection. No analytics. No billing. Creators use these as workarounds, not solutions - which means they're building their own Sociovox manually, piece by piece, every month.
The gap Sociovox fills: A tool built specifically for creators to manage their own business - combining scheduling, deal tracking, inbox, and analytics in one product, at creator-friendly pricing, with self-serve onboarding. No brand sponsor required, no agency needed, no spreadsheet required.
What ships next and why (ranked by user demand × retention impact)
Why: Most-requested feature. Currently the calendar is planning-only. Closing the loop to actual publish removes the last reason to keep a separate scheduling tool.
Blocker: Meta API approval. Already in application. ETA: Q2 2026.
Why: When a creator moves a Gmail thread to the CRM, they still have to write the pitch response manually. An AI-generated deal brief (based on their niche, rates, and past deal history) closes this gap.
Approach: Prompt templating via Anthropic API. No fine-tuning required for V2.
Why: Agency tier users need to manage 10+ creators in one dashboard. Currently each creator has a separate account - there's no roll-up view across clients.
Design approach: Workspace model with client-switcher, not separate accounts. Same modules, parent-level analytics aggregation.
Decision rule for V2 scope: Any feature that reduces churn or drives upgrade is in. Any feature that only improves activation for new users is deferred until retention is solved.
How the tiers were designed and why
The paywall was placed deliberately at the features that creators use after they've built a habit - not at onboarding. Free tier creates the habit. Pro tier serves the creator who's actively monetizing. Agency tier serves the operator.
Pricing insight: INR pricing (not USD) was a deliberate call for the India-first launch. ₹999 vs $12 feels meaningfully different to an Indian creator even though the actual conversion is similar. Price anchoring matters more than currency math.