InvoiceFlow

B2B SaaS

Get-paid-faster invoicing for freelancers and small studios.

A complete spec suite for a subscription invoicing SaaS — auth, Stripe Connect payments, a client portal, automated reminders, and a revenue dashboard, all wired to a P#S# coordinate map.

This is a complete, real InitRepo suite. Every document tags its content against the shared P#S# coordinate map in the Execution Blueprint — open context_index.json to see the machine-readable map your AI agent retrieves against.

Execution Blueprint — InvoiceFlow

The coordinate map every other document references. Each phase is a shippable milestone; each step is a unit of work an AI coding agent can pick up in isolation and trace back to the PRD, architecture, and user stories via its {P#S#} coordinate.

P1 — Foundation & Accounts

  • {P1S1} Project scaffold, CI, and environment configuration
  • {P1S2} Authentication and session management (Clerk)
  • {P1S3} Workspace + user data model and access control
  • {P1S4} Subscription billing for InvoiceFlow itself (Stripe Billing)

P2 — Invoicing Core

  • {P2S1} Client (payer) management
  • {P2S2} Invoice data model and line-item engine
  • {P2S3} Invoice editor with live preview
  • {P2S4} PDF rendering and email delivery

P3 — Getting Paid

  • {P3S1} Stripe Connect onboarding for each workspace
  • {P3S2} Hosted payment page ("Pay this invoice")
  • {P3S3} Payment webhooks, reconciliation, and status sync

P4 — Client Portal & Automation

  • {P4S1} Client portal (view + pay outstanding invoices)
  • {P4S2} Automated payment reminders
  • {P4S3} In-app + email notifications

P5 — Dashboard & Launch

  • {P5S1} Revenue dashboard and aging report
  • {P5S2} Workspace settings, branding, and tax fields
  • {P5S3} Launch hardening: rate limits, observability, legal pages

Start from this spec

Fork InvoiceFlow to open the wizard with these inputs pre-filled — then tweak the idea, the stack, and the features to make it yours. Your first brief is free.