rekap analyzes the customer history you already have and shows you who's due soon, who's overdue, who's slipping away, and who is most worth bringing back.
A regular customer does not announce that they are drifting. Their normal return pattern simply breaks. rekap is designed to surface that change while there is still something useful to do about it.
Provide recent customer and transaction history from your existing system. Six to twelve months is preferred.
We clean the file, model normal return cadence, suppress customers already booked, and prioritize meaningful exceptions.
You receive a Recovery List and a concise Monthly Rekap showing who deserves attention and why.
The first job of rekap is not to impress you with analytics. It is to surface the customers who deserve attention.
| Customer | Status | Normal cadence | Days since | Trailing value | Future booking | Priority |
|---|---|---|---|---|---|---|
| Sarah M. | Overdue | 42 days | 61 | $780 | None | High |
| Jennifer R. | Due soon | 35 days | 33 | $510 | None | Watch |
| Michelle T. | Lapsed | 30 days | 74 | $940 | None | High |
| Alex P. | On track | 28 days | 21 | $620 | Booked | No action |
New, On Track, Due Soon, Overdue, Lapsed, and Recently Recovered customers.
Separate lifecycle risk from economic value so high-value customers get the right priority.
Customers with known future bookings should not appear as recovery targets.
Focus on the few customer groups and specific names that deserve action now.
The first pilot is intentionally hands-on. We will validate every high-priority flag, compare the model against what you know about your customers, and measure what actually happens next.