What the feature entails:
A limited rollover system for the Basic plan’s monthly search allotment: unused searches are added to the next month’s allowance up to a fixed rollover cap (for example, base 300 searches + up to 100–150 rolled-over searches).
Purpose: Increase user value and satisfaction for intermittent users without creating open-ended liability for Kagi.
(Context: many providers use one-month rollover or “banking” models for allowances)
How it affects existing workflows / UX:
Users keep their current workflow; they perform searches as usual. The change is purely in quota accounting and UI visibility.
Billing & quota display: Account pages and the usage meter will show: base allowance, rolled-over amount, and remaining total for the month (e.g., “300 base + 100 rolled over = 400 total”).
Notifications: Optional notifications (e.g., “You have 80 rolled-over searches available this month”) guide users to use rolled-over searches before they expire.
Edge cases & enforcement: Rollover would be limited to a capped (e.g., 150 max) to preserve predictability and minimize revenue risk. This keeps backend accounting simple and avoids long-term accumulation. This mirrors common telco rollovers.
Minimal friction for support/engineering: Implementation requires: quota-tracking for the previous month, a cap parameter per plan, UI updates, and a small change to billing/usage logic. The user-facing experience remains straightforward and familiar.
Typical uses: cover a busier month after a light one (e.g., unused 200 → roll 100 with a 100 cap), cover searches after vacation, improve perceived value at renewal.
UI interactions: dashboard shows rolled-over amount and expiry; optional alert like “You have 50 rolled-over searches that expire in 7 days.”
Implementation pattern: consume rolled-over quota first; cap and single-month expiry keep liability bounded — similar to mobile data rollover practices.
