You built the product. Then you became the support desk, the collections department, and the usage-page refresher, while costs climbed and the roadmap waited. PorchOps is the back office for solo operators: five agents with names and jobs. Lou chases failed payments and closes the books, Frankie has your inbox, Hank notices customers drifting, Dale keeps you up to speed, and Inky writes the changelog. They work in Stripe, GitHub, Vercel, Slack, and Notion.
Hi Product Hunt, Travis here. I've been tirelessly working on PorchOps nights and weekends and it's time to go live.
I watched the need for this grow out of the chaos of the AI explosion. It seemed like everybody was racing to the bottom of AI slop: poorly written emails with no context, code documentation and project traceability captured badly or not at all, with sloppy financials lacking business context. So much of what everyone was trying to do lacked the cohesiveness of a well-trained, specialized team of people.
In the months since the AI wave started to crest, we've been building that team at PorchOps: five named coworkers (Lou on the books, Frankie on support, Hank on customer success, Dale as chief of staff, Inky on comms) who give a founder specialized back office help at a fraction of what a team costs.
Each coworker runs on playbooks you can use out of the box, build on your own, and refine as you scale. Playbooks aren't locked inside PorchOps, either. They're written in OpenPlaybook, an open format we built for this kind of work, and the reference is already public at porchops.dev. It's designed so a playbook can be written by hand, carried to another tool, or run on your own machine. Your processes belong to you, not to whoever you're paying this month.
It feels like everyone is building agents now, and we see that. When set out to build five AI coworkers, we learned fast that the coworkers are the easy part.
Anyone can wire a model to an inbox or feed Claude a report. What makes a back office work is everything around the people in it: the process they follow, a record of what got done, and a clear line on who decides. Most of the last few months went into that layer, which is less fun to demo and a lot harder to copy.
Much like the real world, you can hire and train someone to manage a spreadsheet, but a qualified and skilled person can hit the ground running and save you time, money, and client relationships.
We’re starting with failed payments on Stripe because that's where a small business leaks money first, and recovered revenue is the easiest proof there is. The payment work is one piece of something bigger: a bench for the whole back office, built the way we wish ours had worked from day one. We're not ready to show it yet, but you'll want to be following when we do.
If you run a small business on Stripe, we would love to connect. We're taking ten founding partners: the first month is free, then $47 a month, locked for as long as you stay. In return we ask for your feedback while we build, a testimonial once you've seen it work, and permission to use your real recovery numbers, redacted however you want. Details are at porchops.com/founding-partners.
Not on Stripe? Tell me the one chore you'd hand off tonight if you trusted whoever took it. The best answers we’ll codify as playbooks, and I'll tag you when yours ships. We'll post the first recovery numbers here, good or ugly, and the first look at the bench when it's ready.
All the best, and enjoy the platform.
Travis