Charter: Freelance Developer Client Portal & Project Delivery Platform

The Idea

Charter is a client management and project delivery platform purpose-built for freelance software developers. It connects to your GitHub repos, maps commit activity to milestones, generates plain-English weekly progress summaries for non-technical clients, handles milestone-based Stripe payments, and produces scope-change alerts when projects drift — replacing the chaotic mix of Notion + DocuSign + PayPal + Slack that most freelance devs cobble together today.

The Problem You Solve

Freelance developers are terrible at "making progress visible" to clients. Generic freelance tools (Bonsai, HoneyBook, Wave) understand dollars but not code deliverables. Clients ask "how's it going?" in Slack because there's no portal. Scope creep happens in silence. Milestone invoices are awkward to justify. The result: client trust erodes, disputes happen, and the developer looks disorganized despite doing great work.

Charter gives freelance devs a professional layer that generic tools can't: a portal that shows actual technical progress in terms clients understand, linked to payment milestones both sides agreed on upfront.

Core Features (MVP)

• Project intake + scope definition — structured scope document with acceptance criteria per milestone; client signs off via email link (no DocuSign account needed)
• GitHub repo connection — OAuth link to one or more repos; commit activity auto-tagged to active milestone
• Client portal — shareable link (no client login required); shows milestone status, active commit feed translated to plain English via Claude API, and payment schedule
• AI progress summaries — weekly auto-generated "this week in plain English" email to client, pulled from commit messages and issue closures; developer reviews before send
• Milestone-based Stripe payments — each milestone has a defined payment; client pays via Stripe Checkout link embedded in portal; Charter takes 0% (developer pays Stripe fees only)
• Scope change alerts — when GitHub issues/PRs are opened outside the original milestone definitions, Charter flags a scope change and generates a one-click change order for the client to approve and pay
• Project close + case study export — at project end, generates a shareable portfolio card: timeline, tech used, outcome summary, commits count — turn every project into a work sample

Pricing

• Solo — $59/month: up to 5 active projects, unlimited clients
• Studio — $149/month: up to 5 developers (team accounts), 15 active projects, white-label portal subdomain
• Annual discount — 2 months free (Solo $590/year, Studio $1,490/year)
• No per-project fee; no percentage of developer revenue (key differentiator vs. platforms that take a cut)

Tech Stack

• Frontend/Backend: Next.js + TypeScript on Vercel
• Database: Supabase (projects, milestones, clients, payment events)
• Payments: Stripe Checkout + Webhooks (milestone payment links)
• GitHub integration: GitHub OAuth App + REST API (commit feed, issue tracking)
• AI summaries: Claude API (claude-haiku-4-5 for cost efficiency on weekly digests)
• Email: Resend (weekly summaries, payment receipts, scope change alerts)
• E-signature: Email-based confirm link (no third-party required for MVP)

How to Build MVP

Week 1–2: Core data model + auth

• Supabase schema: users, projects, milestones, clients, commits_cache
• GitHub OAuth flow, repo selector, basic commit sync job (nightly cron)
• Project + milestone creation UI

Week 3–4: Client portal + payments

• Shareable client portal page (no auth, UUID-based URL)
• Milestone status display with commit feed
• Stripe Checkout link per milestone; webhook updates milestone to "paid"

Week 5–6: AI summaries + scope change detection

• Weekly cron: pull commits since last summary, send to Claude API for plain-English digest, queue for developer review before sending
• Scope change heuristic: new GitHub issues opened with no milestone tag → flag in dashboard + generate change order email draft

Week 7–8: Polish + case study export

• Project close flow, PDF/shareable case study card
• Onboarding flow for first 10 beta users
• Stripe billing for Charter subscription itself

How to Get First Customers

1. Post in freelance dev communities — Hacker News "Ask HN: Who's freelancing?", /r/freelance, /r/webdev, Indie Hackers — lead with "I built this for my own freelance work" (authentic founder story)
2. GitHub-adjacent distribution — write a blog post: "How I stopped losing client trust mid-project" with Charter as the solution; target SEO: "freelance developer client portal," "how to manage freelance dev clients"
3. Twitter/X build-in-public — document building it, target audience already follows dev-side creator accounts
4. ProductHunt launch at 60 days with a "built by a freelance dev for freelance devs" angle
5. Direct outreach — find GitHub profiles with public freelance indicators (portfolio sites, "available for hire"), DM 50 of them with a free beta invite

Revenue Math

• Month 3 (post-launch): 30 Solo customers × $59 = $1,770/month
• Month 6: 80 Solo + 15 Studio = $4,720 + $2,235 = ~$7,000/month
• Month 9: 140 Solo + 30 Studio = $8,260 + $4,470 = $12,730/month
• Retention lever: developers who land a new client use Charter on day one — the client portal becomes the professional handshake; high switching cost once clients are used to the portal format

Why This Is Different

Generic freelance tools (Bonsai, HoneyBook, AND, AND) are designed for photographers, consultants, and creatives — they understand hours and invoices, not code. The only tools that understand GitHub are project management tools (Linear, Jira), but those are internal, not client-facing. Charter is the only tool that sits in the developer → client communication layer with GitHub as the source of truth. The AI translation layer (technical commits → client-readable updates) is the core defensible feature — competitors would need both GitHub expertise and AI integration to replicate it.

Path to Quitting Day Job

At $12k MRR (Month 9), if day job pays ~$10k/month net, Charter alone covers it. The Studio tier is the growth lever — one freelance agency or dev shop with 3–5 developers paying $149/month is worth more than 2.5 Solo subscribers and has much higher retention (team adoption is sticky). After $10k MRR, hire one part-time customer support/growth person via revenue, then focus on Studio tier and agency partnerships.

Risks & Mitigations

• "I'll just use Notion" — freelancers who use Notion have no GitHub integration, no payment automation, no scope change alerts; Charter's pitch is 3 hours/project saved, not "another tool to configure"
• GitHub dependency — GitLab and Bitbucket integrations are 2-day additions after MVP; roadmap them publicly to not lose non-GitHub users
• AI summary quality — Claude's commit message translation is high quality even on terse messages; developer review before send is the safety valve; bad summaries get edited, not blamed
• Niche too small — there are 1M+ freelance developers in the US alone; even 0.1% of that market at $59/month = $5.9M ARR; this is not a small niche

Why This Works for You Specifically

You have used GitHub APIs (Patchwork, StackPulse, multiple prior ideas), Stripe (all payment ideas), Claude API, Next.js, and Supabase — this is your exact stack. More importantly, you are the target user: a software engineer who can instantly see why a freelance dev client portal with GitHub integration is 10x better than Bonsai. You can run your own (hypothetical or real) freelance work through Charter and dog-food it authentically. The founder-market fit is unusually strong.

First Action

Spend 2 hours this week: (1) Sign up for a Bonsai or HoneyBook trial and write down the 5 things that feel wrong for a developer; (2) post in the Indie Hackers "Ask IH" forum: "Freelance devs — what's your current client management stack?" — collect 10+ real workflow descriptions before writing a line of code. Validate the pain is real, then build Week 1.