Stop running your studio out of eight different apps.

Those are general-purpose tools you have to bend to audio work. Studio Pilot ships with the workflow already modeled: projects → sessions → revision rounds → approvals → invoices → client portal. No templates to wrangle, no custom formulas, no building your own CRM out of a database.

Each project gets a stream of deliverable cards — one per mix, with versions stacked oldest-to-newest. Attach a Dropbox or Drive file; Studio Pilot generates the waveform, measures BS.1770 LUFS + dBTP true peak, and stores them so the client portal renders the same view without re-downloading the audio. Hit Send and the client gets a single link. When they pin a note at a timestamp, you see it in your engineer card with the marker still on the waveform, click-to-seek. State-driven footers: Draft → Send; Sent → “awaiting review”; Revisions → quoted client notes + Start v(N+1); Approved → green seal with signature.

In a SQLite database inside ~/Library/Application Support/Studio Pilot on your Mac. Supabase only stores what has to be in the cloud — your login email, subscription status, and the data the client portal needs to render (projects, deliverables, revision pins, signatures, peaks, loudness). Everything else stays local. You can export the whole thing as JSON or delete your account entirely from Settings → Privacy & Data; every restore writes a `*.pre-restore-<timestamp>.db` safety backup first so a misclick is recoverable.

It has agentic tool access to your real studio data — currently 20+ tools spanning projects, calendar, clients, invoices, deliverables, analytics, and the Feed Hub. Ask “what’s slipping this week?” and it pulls your actual deadlines. Ask “block Friday for the Street Chronicles mix” and it puts real blocks on your real calendar. Ask “draft a note to Kara about the revision delay” and it knows which revision you mean. The persona is staff-not-CEO: it observes and surfaces patterns from your own data, never tells you what to do, never compares you to other engineers.

Yes. Studio Pilot is BYOK — paste an Anthropic key in Settings → AI Manager and chat goes through your account directly. No proxy, no per-message billing on our side, no quota. (A managed-AI proxy is something we may add later if there’s demand; today it’s your key, your cost, your control.)

You send the client a single link. They hear the mix, pin revision notes to specific timestamps on the waveform with @-mentions for the engineer or other team members, approve when it’s done with a real signature, and pay the invoice through Stripe — all on one page. No login required. No app to download. Works on their phone. Realtime: when they pin a note, it shows up on your engineer card without a manual reload.

Yes — a Progressive Web App at /studio on any phone. Installable to the home screen on iOS Safari + Android Chrome. Reads + writes your projects, calendar, clients, tasks, invoices, time entries. The desktop is still the heavy command center; mobile is for triage on the go.

Studio Pilot ships a partnership-level macOS Accessibility surface. Every actionable control has a stable aria-label, and a top-level “Automation” menu publishes 17 named scripting targets (Go to ▸ hub, Toggle panels, Sync to Cloud, etc.) for SoundFlow’s `sf.ui.menuBar` and `sf.ui…buttons.whoseDescription` patterns. Reference macro shipped in the repo. A separate REST API on port 9473 gives stream-deck and surface bindings 12+ endpoints for the Studio tier.

CSV import handles clients, projects, and time entries. There’s also a one-click Motion import (Motion API key → pulls your tasks). For anything else, you can run Studio Pilot alongside your existing tools during migration — there’s no forced cutover.

Yes. The core app is local — SQLite, scheduling, invoicing, PDF generation, time tracking, tax-prep CSV export — all run without internet. You only need a connection for Google Calendar sync, Dropbox file linking, AI chat (BYOK), and the client portal. Fly cross-country, work the whole flight.

Yes. Invoicing → Recurring tab. Set up weekly / monthly / quarterly / yearly cycles per client; Studio Pilot auto-issues a draft invoice on the cycle date with a guard against double-issuance. Plus outbound webhooks (Settings → Webhooks) fire HMAC-signed JSON to Zapier/n8n/your-own-server on 10 event types — invoice.sent, invoice.paid, project.completed, revision.submitted, etc.

Default: they come from Studio Pilot's address with your studio name in the From display and replies routed to your inbox. To send from your own address natively, you have two paths: (1) **Gmail / Workspace** — one-click Connect with Google in Settings → Integrations → Send From; the consent screen briefly shows an "unverified app" warning until Google completes our restricted-scope verification (in progress), then it disappears entirely; (2) **Any other provider** (iCloud, Outlook, Fastmail, Yahoo, custom domain) — paste an app password and Studio Pilot auto-verifies the connection in ~5 minutes. Credentials stay local — never sync to the cloud, never appear in backups.

Analytics gives you Cash (booked / unbilled / overdue + A/R aging buckets), Rates (effective hourly per project + per client, realization rate), Clients (revenue concentration, health scores, acquisition cohorts), and Goals (quarterly targets across revenue / hours / projects / new clients). A quarterly PDF email report auto-sends the first week of each new quarter. For tax season, Settings → Import Data → Tax-prep export dumps one CSV row per paid invoice for the year with hours-worked aggregates — hand it to your accountant.

Yes. Manage subscription, update card, pause, or cancel from Settings → Subscription — it runs through Stripe Customer Portal. If you cancel, you keep full access until your billing period ends, then degrade to the free tier. Your data stays put either way.

macOS only for now. Windows and Linux are on the roadmap but not a near-term priority — the app is built with Electron so the port is feasible, it’s a matter of signing, notarization, and testing time.