One screen for Keap recurring revenue and at risk renewals

Build me an app that is one screen for all of my Keap recurring revenue. Keap's own reporting can show me a cash forecast but it cannot tell me what is actually billing and what quietly broke, so I want a browsing surface first and a recovery workspace second.

The main view is a table of every active subscription. Load it with Keap List Subscriptions, then join each row to its plan with List Subscription Plans, to the underlying product with List Products, and to the subscriber with List Contacts. Each row shows the subscriber name and email, the plan and product name, the billing amount, the billing cycle and frequency, the next expected bill date, the normalized monthly value of that subscription, the subscription status, and the subscriber's lifetime spend. Lifetime spend comes from summing that contact's paid orders via List orders, and it sits right next to the subscriber name so I can tell at a glance which saves are worth a phone call and which are worth an email. Above the table put a summary strip with total monthly recurring revenue, active subscription count, and a breakdown of monthly recurring revenue totalled by plan, sorted with the biggest plans first. Let me search by subscriber, filter by plan and by status, and sort by any column.

A Renewals tab shows everything due to bill in the next 30 days, built from the next expected bill date on each active subscription, grouped by day with a running total of the expected billing amount per day and for the window overall. The window length should be a setting so I can change 30 days to whatever suits my billing rhythm.

An At Risk tab is the working queue. Build it by cross referencing List orders against each active subscription: a subscription is at risk when its last expected cycle date has passed and there is no successful order for that contact covering that cycle. This needs a grace window rather than flagging the instant a cycle date passes, because Keap makes three automatic charge attempts two days apart before a charge is considered failed. Default the grace window to five days so a row only surfaces once Keap's own retry sequence is finished, and expose the window as a setting. Each at risk row shows days overdue, the amount at risk, the last successful order date, lifetime spend, the plan, and the contact's applied tags. Sort the queue by amount at risk by default and let me flip to sorting by lifetime spend.

From any row I can act without leaving the app. A Retry billing action calls Invoice a Subscription to generate invoices for the due cycles of that subscription. An Apply recovery tag action calls Apply Tag with a tag I configure once in app settings. A Log what I did action opens a small composer and calls Create a Note against the contact. An Open follow up action calls Create a Task with a title, description and a date I pick. Every action confirms before it fires, shows the result inline, and refreshes the affected row.

A Slack button in the At Risk tab uses Slack Bot Send a Message to push the day's at risk list to a revenue channel I configure. The message should be readable in Slack: a headline with the count and the total amount at risk, then a line per subscription with the subscriber, the plan, days overdue, the amount, and lifetime spend, capped at a sensible number of rows with an overflow count at the bottom.

Each row also gets a Build a save play button that kicks off a background agent for that one subscription. The agent reads that contact's order history with List orders, their applied tags with List Applied Tags (Contact), and the subscription record itself, then decides whether the right move is to retry billing or to reach out to a human. It drafts a personalized card update message in my voice referencing what they actually subscribe to and how long they have been a customer. It writes its reasoning back into Keap as a note with Create a Note and opens a dated follow up with Create a Task so the thinking is on the record even if I never open the app again. It then returns the recommendation, the drafted message, and its confidence into the app, where it appears on the row as a pending save play I can read, edit and approve. Nothing customer facing and no billing retry happens off the back of the agent: a human approves in the app before anything sends.

Bake in these Keap details. Monetary amounts are decimal values in whole units of the account currency, for example 12.50, not minor units, so never divide by one hundred. Keap v2 resource IDs are strings and v1 resource IDs are integers, so never cross an ID from one version into the other. The v2 list endpoints use cursor pagination with page_size plus page_token and return a next_page_token, so page through fully when building the subscription, order and contact sets rather than reading only the first page, and cache the joined result so the tabs do not refetch everything on every switch.

The app should remember its own settings across sessions: the recovery tag, the Slack channel, the grace window, the renewals window, and the lifetime spend threshold above which a subscriber is marked as worth a call. It should also keep a local action log of what was retried, tagged, noted, tasked or approved and when, so an at risk row I already handled today shows as handled instead of nagging me again tomorrow.