Chase every failed payment
When a card declines, Lou reads why, pulls the customer's history, and drafts the recovery email while the charge is still warm. You approve it, or let Lou send below a threshold you set.
Ask your business anything.
Then put it to work: revenue recovery, support mail, quiet customers. You built the product. PorchOps runs the back office with you.
No card required.
Overview
APP · CUSTOMERSCustomers · 312
StripeConnected
MRR$18,420
Imported 309 customers · 14 months of history
NAMEMRRLTVSTAGEHEALTHRISKHalyard$1,180$11,120activehealthy—Tessera Studio$640$3,840activehealthy—Heron Software$420$2,300activehealthy—Fenwick Labs
$432$4,980activePayment failed—Lou · drafting the recovery noteArgosy Field Co.$86$940activehealthy—Marrow Systems$310$2,790activehealthy—Coastline Metrics$980$9,240activehealthyinvoice overdueDriftwood Analytics$215$1,860activehealthy—Kestrel Ventures$1,050$8,400activehealthy—Palmer Instruments$560$5,600activehealthy—Windward Supply$145$1,320activehealthy—Beacon Supply——trialhealthy—Thistle & Vane——trialhealthy—
Information.
Customers, payments, usage, the product itself, under one roof. Ask it anything; the answer comes with its sources.
APP · CUSTOMERSCustomers · 312
StripeConnected
MRR$18,420
309 imported · 14 months of history
NAMEMRRHalyard$1,180Tessera Studio$640Heron Software$420Fenwick Labs
Payment failed$432Lou · drafting the recovery noteArgosy Field Co.$86Marrow Systems$310
Documentation.
How you run your business, written here or anywhere, is what the crew goes by. And it helps you write down the rest.
APP · WIKIv5
Billing & dunningprocess
Updated by Dale · just now
How we bill
Monthly on the signup anniversary, card on file through Stripe. Annual folks get invoiced and left alone.
Dunning schedule
Stripe retries on its own schedule; we don't pile on. Day 1 is silence on purpose, most cards fix themselves. Day 2, one plain note from us. If the Monday retry bounces too, it goes to a human. Two notes maximum, ever. Nobody reads a third, and the fourth is how you end up in spam next to the casino mail.
Refunds
First month, it's a yes, no questions. After that we prorate. Nobody has argued with a prorate yet.
Comped accounts
Friends, early testers, anyone who found a bug before we did. A Stripe coupon, so nobody gets billed by accident.
Recovering a failed card
When a card fails, wait a day before the first note. Lead with the fix, not the failure. One retry Monday morning, then a plain reminder.
Stripe · dunning settings
Cited inHank · Quiet customer check-in
Lou · Failed payment recovery
Communication.
It runs both ways. PorchOps keeps you in the loop; the crew keeps your customers paying, happy, and taken care of.
APP · INBOXInbox
- Dana · Fenwick Labscard declined?replied
Saw the note about my card. I updated it just now, can you re-run the charge?
Reply to DanaThanks Dana. The new card looks good, and the retry is queued for Monday morning per our usual schedule. The August charge will clear then; nothing else you need to do.
Wiki · Recovering a failed cardApproved by KitSent
Action.
Describe the work once and it runs as a playbook, or just tell the team what you need. Ad hoc or structured, it’s always priced, logged, and auditable.
Failed payment recoverySaved
Run · Fenwick Labs
Done · 4 steps · 3 credits
- 04Send after approvalApproved by Kit
LLou drafted failed payment recovery for you to review
Held for your approval before anything sends.
SUBJECTQuick note about your August payment
Hi Dana. The card on file for your Fenwick Labs account didn’t go through yesterday; the August charge of $86.00 came back declined. I’ll retry Monday morning. If it’s easier to update the card now, the billing page is at foundry-labs.demo/billing.
Approved · logged in the run
Approved · sent to [email protected]
What can you offload this month?
Start with the chore you dread most. Each one is a job the crew already knows how to do. Drafts land in your queue, and nothing goes out until you say so.
Clear the support inbox
Frankie reads every inbound before you do, sorts the real asks from the noise, drafts replies in your voice, and files the bugs as issues with repro steps. The pile becomes a triaged queue.
Catch a customer before they go quiet
Hank watches for the churn tells, a login that stops, usage that dips, a support thread that spikes, and flags the account while there's still time to save it. He drafts the check-in; you decide whether to send.
Get your Monday briefing
Dale rolls up last week, revenue, churn, support volume, what shipped, and has it waiting when you sit down. The operating rhythm you keep meaning to run yourself, run for you.
Write the changelog you keep skipping
Inky reads the diff the day you ship and drafts the changelog entry in your voice, dated and ready to publish. The release note you never get around to, already written.
Close the books every month
Lou reconciles the month's transactions, flags the lines that need your eye, posts what you approve, and locks the period once it's clean. The close becomes a review, not a weekend.
A bookkeeper who chases every failed payment and closes your books, a Monday briefing, and a Friday changelog: free while you're small, no card, all five on the porch from day one. The whole crew drafts for you; you approve.
Meet the crew behind the jobs
How the work flows.
Connect your stack. The PorchOps team reviews signals automatically, on schedule, or on demand, analyzing data, classifying intent, and executing tasks in your voice.
Your connectors
- stripepayments + customers
- gmailinbound email
- slackteam mentions
- posthogusage events
- githubissues + commits
- verceldeploys
- notiondocs + briefs
5 agents
- loubookkeeper
- frankiesupport coordinator
- hankcustomer success
- dalechief of staff
- inkycommunications writer
approval gate
by defaultevery draft waits on you
auto-sendonly where you allow it
external surfaces
- gmail
- slack
- linear
internal surfaces
- changelog
- status page
Nothing sends or changes without your approval, by default. Build trust over time, and automate up to your risk tolerance. Every task is scope-controlled, testable, and audit-logged.
The five hires you didn't have to make.
Five specialists, not a chatbot wearing five hats. They share your tone and business context. They own their functions and work together to run your company the way you'd run it, if you had the time.
lou
bookkeeper
Watches your Stripe. Drafts the recovery email the moment a payment fails, matched to the decline and the customer.
read lou's profilefrankie
support coordinator
Reads every inbound email. Drafts replies in your voice. Files bug reports as Issues with reproduction steps.
read frankie's profilehank
customer success
Watches which customers have gone quiet and tells you why he thinks so. Drafts the check-in. Never sends it.
read hank's profiledale
chief of staff
Runs your rhythm. The Monday brief. A monthly read on your market. A nightly pass over what the rest of the crew noticed.
read dale's profileinky
communications writer
Drafts the changelog you keep skipping, from the week's shipped work, in your voice. You publish it.
read inky's profile
You don't teach them how to do their jobs. The agent toolkits everyone else is shipping start you at zero. Write the prompts, build the eval, work out what to say to a customer whose card just failed. The operators arrive knowing.
→ Read each agent's profile
The back office you didn't have to build.
CRM, inbox, issue tracker, changelog, status page, wiki — in your app the day you sign up. Already running your own? Plug them in — every primitive is MCP-exposed, so agents read and write through the same typed contract no matter what's behind it.
Light CRM
examplecustomerplanriskjane @ acmeproorbit labstrialmarco & co.startervault systemsteamdrafting recovery · vault systemspayments · usage · risk
Shared Inbox
exampleinbox3 unreadcathy @ blueprint2mexport still hangs at 10k rows…jane @ acme14mthanks, invoice receivedstripe alert1hsubscription past due · marco & corouting 3 escalationsasks · bugs · escalations
Issue Tracker
exampleissues · open7S0payment webhook 500s · stripeFexport CSV truncates at 10kFS2sidebar copy typo · settingsIS3dark mode flicker · safari—triaged · 2 promoted todaybugs · features · severity
Release Log
examplerelease logv0.4v0.4.4addedwebhook events for invoicesv0.4.3improvedfrankie triage confidencev0.4.2fixedcustomer search edge casedrafted v0.4.4 · pendingnew · improved · fixed
Incident Page
examplecomponentsall operationalapp.porchops.cominbound webhooksstripe syncslack relayemail digestincidents · posted and timestampedcomponents · uptime · history
Light Wiki
examplecontents· Overview· Lou· Frankie· Hank· Dale· Inkyplaybook glossary
linked · monday briefprocess · product · policies
Coming in cold? We've already decided what a CRM should record, how a status page structures incidents, what fields belong on an issue, the patterns most SaaS companies converge on.
Inside the platformGrow into your back office.
Free while you're small, with the whole crew drafting. Move up to Growth when the jobs are real and you want them sent on their own. The plan grows with the company.
free
$0
Free forever
All 5 agents, starter playbooks. Drafts only.
200 + top-up to 50/wk
Start here growth
$47/ month
Billed monthly
Auto-approval, custom playbooks
1,500 credits / mo
| Feature | free | growth |
|---|---|---|
| Drafts vs auto-send | drafts only | both |
| Custom playbook builder | — | Yes |
| BYOA (bring your own Anthropic) | — | Yes |
| Monthly credits | 200 + top-up to 50/wk | 1,500 credits / mo |
Building is easy.Selling is hard.Scaling is harder.
SaaS is a grind. Missed payments, customer comms falling through the cracks, shipping without a log, docs and specs that drift from the product. Every day a barrage of to-dos and should-dos that compete for time and attention. We're building PorchOps so it hurts a little less, and we're excited to share it with you.
Reclaim your day. We've got your back office covered.