.webp)
We sell SaaSFrame licenses on Gumroad, a secured online selling platform for creators.
SaaSFrame gets updated all the time! Every new update and version will immediately be made available to all SaaSFrame users.
The licence key required to create your SaaSFrame account is send by Gumroad once you made your purchase. If this email is blocked by your email client, send me an email at antoine[at]unmake[dot]io so I can resend the licence key.
You can generate an invoice on Gumroad once you purchased SaaSFrame. You will find the link in the order confirmation email.
If you're not satisfied, you can ask for a refund within 7 days. Just send me an email at antoine[at]unmake[dot]io
A SaaS retention email invites a user to return for a relevant reason or explains a consequential account state. Its design should distinguish optional re-engagement from an operational notice rather than treating every inactive user as the same campaign audience.
The Asana reference uses an improvement-oriented message and a try-now action for an inactive recipient. Its illustration supports the return invitation.
A changed capability can be a relevant reason to revisit the product. The captured performance claim is historical marketing content, not independently verified evidence or a current specification.
Avoid assuming inactivity means dissatisfaction. A user's work may be seasonal, completed, or dependent on another task.
The Help Scout reference combines an inactivity message with a scheduled account-removal warning, a login route, assistance, and a trial-related option.
A consequential state requires accurate timing and a clear preservation or recovery route under the actual product rules. It should not be disguised as ordinary promotional urgency.
Do not copy another product's retention period or imply deletion when the account model does not establish that consequence.
Return to work, inspect a new capability, get help, and preserve account access are different actions. Label the actual destination.
Preserve relevant workspace or task context through authentication. A generic homepage may not help a user understand why they returned.
If access has already changed, show the actual state and available recovery rather than an obsolete invitation.
A short help route can uncover a blocker, but it should reach a process able to respond. Do not imply an individual reviewed the account unless that occurred.
Avoid guilt or unsupported assumptions about the user's priorities. Explain relevant value and let the recipient decide.
Keep essential consequences and instructions in text, with a useful experience when images are blocked.
A returning user should not continue receiving the same inactive-account prompt. Change targeting when the product establishes new activity or another relevant state.
Review timing, recipient scope, destinations, and any account consequence with responsible owners.
Use SaaSFrame's retention-email references to compare improvement-led invitations and account-state notices. Design around a truthful reason to act.
No. Use the actual context rather than assuming a single reason for absence.
Keep consequential state, timing, and action explicit. Do not obscure them inside a generic campaign.
Update the sequence so its inactivity claim no longer contradicts known activity.
