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.
Your back office,on autopilot.
The team and tools to run your operations. Recover revenue, prevent churn, grow accounts, and keep customers close.
Drafts by defaultAuto-approve anythingAudit everything
No card required.
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.
A bookkeeper who chases every failed payment, 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
pending review3
auto-sent · 24h12
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 when a payment fails. Tracks renewals. Flags expansion when usage spikes.
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 who's logging in and who isn't. Flags churn risk before they cancel. Nudges trial users on day 1, day 7, and day 14.
read hank's profiledale
chief of staff
Runs your rhythm. Weekly briefs. KPI snapshots. Status page narration. Incident comms when something goes wrong.
read dale's profileinky
communications writer
Drafts your changelog the day you ship. Writes your lifecycle email, your newsletter, your social posts. Calibrated to your voice over time.
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, define what a dunning email even looks like. 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
customermrrriskjane @ acme$4,800orbit labs$480marco & co.$1,200vault systems$2,400drafting recovery · vault systemspayments · usage · risk
Shared Inbox
inbox3 unreadcathy @ blueprint2mexport still hangs at 10k rows…jane @ acme14mthanks, invoice receivedstripe alert1hsubscription past due · marco & corouting 3 escalationsasks · bugs · escalations
Issue Tracker
issues · open7S0payment webhook 500s · stripeFexport CSV truncates at 10kFS2sidebar copy typo · settingsIS3dark mode flicker · safari—triaged · 2 promoted todaybugs · features · severity
Release Log
release logv0.4v0.4.4addedwebhook events for invoicesv0.4.3improvedfrankie triage latency · 40%v0.4.2fixedcustomer search edge casedrafted v0.4.4 · pendingnew · improved · fixed
Incident Page
componentsall operationalapp.porchops.com82msinbound webhooks146msstripe sync204msslack relay112msemail digest62ms99.99% · 30dlast incident · 18d agocomponents · uptime · history
Light Wiki
contents· 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 platformpricing · annual saves 33%
Grow 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.
1,000 + top-up to 100/wk
Start here growth
$31/ month
Billed yearly · save $192/yr
Auto-approval, custom playbooks
10,000 credits / mo
| Feature | free | growth |
|---|---|---|
| Drafts vs auto-send | drafts only | both |
| Custom playbook builder | — | Yes |
| BYOA (bring your own Claude) | — | Yes |
| Monthly credits | 1,000 + top-up to 100/wk | 10,000 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.