lou · recovery
Drafts cause-matched recovery emails when Stripe payments fail.
Recovered $4,200 for porchops in March.
Porchops · Powered by Beer
You built the product. We run the business.
Porchops connects your Stripe and email, then runs the operational stuff with a crew of eight named AI coworkers — recovering failed payments, watching for silent churn, drafting your changelog, keeping the porch lit.
Built by founders. Running on porchops since March. We never train AI on your data.
How it works ↓If two of these are keeping you up at night, the porch is for you.
Am I a real business?
Customers showing up, but you're answering support from Gmail with no status page, no changelog, no audit trail.
→ The crew handles real-business operations.
Silent churn — customers vanishing
Stripe says you have 1,200 subscriptions. You have no idea who's actually using it, who's quietly leaving, or who's about to.
→ Hank watches for it.
Money leaking — failed payments
Five to nine percent of MRR walks out the door every month to dunning, and you don't have time to chase it manually.
→ Lou drafts the recovery emails.
Support backlog
Customer email lands in personal Gmail between newsletters and dentist reminders. Some get answered, some don't.
→ Frankie triages every inbound.
How it works
Connect your tools.
Stripe is required. Email (Gmail or Resend) is highly recommended. OAuth in two clicks. We read what we need, nothing more.
Meet your crew.
Pre-built playbooks turn on with one toggle. Configure thresholds, approval rules, dollar caps. Lou drafts your first recovery the same day.
Approve and ship.
Drafts land in your inbox. Send with one click, or set guardrails and let Lou auto-send below your threshold.
Eight on the porch. One job each.
cleo · renewals
Watches usage; preps renewal touchpoints; flags expansion signals.
Watching renewals across porchops's own subscribers.
maggie · onboarding
Nudges trial users on day 1, day 7, and day 14 toward activation.
Nudging porchops's trial users toward activation daily.
frankie · inbox
Triages inbound mail, drafts replies, escalates real customers.
Triaging the porchops support inbox every morning.
bug · issues
Turns customer support emails into filed Issues with repro steps.
Filing Issues from inbound mail in Linear.
hank · watcher
Names what's slipping — silent customers, dropping usage — before churn.
Watching for quiet customers on porchops's own porch.
inky · scribe
Drafts the changelog. Publishes to your-name.porchops.com daily.
Writing the porchops changelog every week since March.
dale · briefer
Sends the Monday business brief and the daily ship-log digest.
Sending the Monday brief to all five porchops founders.
Failed payment recovery, in detail.
Every SaaS loses 5–10% of monthly revenue to failed payments. Most founders don't have time to chase them manually, and the customer experience is awful either way — silent churn or generic, robotic dunning emails. This is real money walking out the door.
Stripe fires a webhook when a payment fails. Porchops reads the customer's full history — tenure, MRR, prior issues, lifecycle stage — and drafts a contextual recovery email matched to the failure cause. The founder reviews and sends with one click, or sets a configurable auto-send threshold (for instance, auto-send for attempts under $500 if the customer is in good standing). Every recovery is logged, every email is auditable, every action is explainable.
Revenue you'd have written off. Time you weren't going to spend chasing it manually. Visibility you'd otherwise build by hand — a real audit trail of who paid late, who came back, and which emails recovered the most.