Adjust Billing and Membership Correlation

Sudowrite is a great tool and I appreciate what the team has built, but I would like to suggest a change to how billing and memberships are handled because the current system can unintentionally shorten a user’s paid access time.

Right now, the system appears to charge on a fixed billing date (for example, the 1st of the month). If the payment does not clear immediately, Sudowrite suspends membership features. However, when the payment eventually processes, it can take several days for the system to recognize the payment, and in some cases the account does not automatically reactivate until support intervenes.

Because the billing date does not reset after the payment actually clears, the result is that users may lose multiple days of paid service. For example, last month my payment processed about two weeks after the original billing date, then support manually resynced my account to register the payment a week after that, but the next billing cycle still occurred based on the original date. This meant I effectively paid $29 for roughly a week of access instead of the full 30 days.

A few alternative billing models would solve this issue and align with how many subscription services operate:

Option 1
Pause service if payment fails, but once the payment clears, restart the subscription and begin a new 30-day billing cycle from that date.

Option 2
Allow a grace period and keep service active until the next successful payment, ensuring users always receive the full 30 days of paid access.

The key point is that if customers are paying for 30 days of service, they should reliably receive 30 days of service. Adjusting the billing cycle to start when payment actually clears would create a much more consistent and fair experience.

I hope the team will consider improving this part of the system because Sudowrite is an excellent writing tool and refining the subscription mechanics would make the overall user experience even better.