Porchops is the AI back office for solo founders running software businesses. We built it because we were the people who needed it.
We met working on software people had heard of, then watched a generation of solo founders ship products on Lovable, Replit, v0, Bolt, and Cursor without the operational software the rest of the industry takes for granted.
Porchops is what we wished we had — built for the founder running a $5K to $500K ARR business with no engineering team, no operations team, and a customer base that's growing faster than the back office can keep up with.
The horizontal AI layer is commoditizing. OpenAI Workspace Agents, Anthropic Claude, Google Gemini — the model layer is becoming a utility. What still doesn't exist for solo SaaS founders is the operational layer: real CRM, real support inbox, real changelog, real status page, real failed-payment recovery, real silent-churn watcher. Pre-configured, opinionated, and run by an AI crew with names you can talk to.
That's what we're building. The brand bet is that vertical wins when horizontal commoditizes — and that the eight-Op crew is how a small team actually feels when the back office is running itself.
Porchops uses Porchops. Our Stripe webhook fires Lou. Our customer graph is the customer graph. Our changelog is written by Inky and reviewed by whoever shipped. Our silent-churn watcher is Hank. The receipts you see at /we-run-on-porchops are real events from our own porch.
The day Porchops stops running on Porchops is the day the brand stops being honest. We treat that as a non-negotiable architectural commitment.
Powered by Beer
Cofounder and CEO at Porchops. Sets the bet, writes the canon, and does the customer-facing storytelling. Started Porchops because every solo founder he met was running their business across five tabs, and the back office layer for them didn't exist yet. Reply to any of his welcome emails and he'll write back — he reads everything.
Cofounder and COO at Porchops. Operations, go-to-market, and the founder voice you'll hear most in the changelog and the weekly newsletter. Cares whether the prose reads like a real person wrote it — you can usually tell which side wins. If you email hello@porchops.com about a tactical question, this is the founder who probably writes back.
Cofounder and CTO at Porchops. Owns the AI playbook runtime, the customer graph, and the eight-Op orchestration. Believes in typed contracts and explaining things twice rather than shipping them half-explained. The reason every event in the receipts feed is reproducible — and why nothing trains a model on your data. Also the founder you'd call about an architecture question.
Founding engineer at Porchops. Ships the product surface — the receipt-style Today panel, the customer pages, the inbox view, the Stripe connector — at the rate that lets the rest of the team make promises. If you've used something on Porchops, Dylan probably built it. Lurks in the Lovable, v0, and Cursor Discords most evenings.
Founding engineer at Porchops. Owns the infrastructure, data schemas, and the parts of the system that don't have a face. Keeps the lights on, the typed contracts honest, and the deploy pipeline boring. The reason your data is encrypted at rest and in transit and your audit logs are queryable. The founder you'd never see on stage but whose work you'd notice the moment it stopped.