Skip to article
ecomservices.io
Subscriptions · How to run this
EconomicsCalculatorApprovalCalculatorDunningCalculatorAccount updaterCalculatorIdeasCalculatorImplementationNot on this page yetOptimisationNot on this page yetProjected cashNot on this page yet

Library · Subscriptions · How to run this

Winback flow must beat the next MIT

How to run thisSubscriptions3 steps
CalculatorKlaviyo flow vs rebill clock · Calculator lives in the articleOpen

Cancel-save and winback flows run on email hours. The CRM next MIT runs on a different clock. If the charge fires first, the save never had a chance. Type hours to flow and hours to rebill. Save % is optional.

Pair: Klaviyo flow vs rebill clock on Subscriptions. Save EV: cancel-save offer. SMS capacity: SMS cap vs rebill cohort.

What you type

Hours to flow — from cancel / trigger to the first save send that can still stop the MIT (your flow schedule, not a blog).

Hours to rebill — from the same trigger to the next CRM MIT.

Save % (optional) — your closed-book save share on that flow. Blank is fine.

If hours to flow < hours to rebill, the flow lands first (gap = rebill − flow). Otherwise MIT wins (miss = flow − rebill). Move the send earlier — do not invent a save chip to paper a miss.

What not to do

Do not invent a save percent. Do not treat SMS daily cap as this clock. Do not leave the next MIT inside the flow delay. Do not mix winback for churned-out profiles into a still-billing MIT cohort without saying so.

Related: Subscriptions, cancel-save offer, SMS cap vs rebill cohort, pause vs skip vs cancel.

Procedure

  1. Type hours to the first save send.
  2. Type hours to the next MIT from the same trigger.
  3. Optional: type closed-book save %. Read overlap or miss.

Failure modes

  • Inventing a save percent.
  • Treating SMS daily cap as this clock.
  • Leaving the next MIT inside the flow delay.

Worked example

None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.

Glossary

Flow vs MIT clock
Whether the first cancel-save / winback send lands before the next CRM MIT. Save % does not move the clock.

Work with us — We run this job on your accounts. Services

FAQ

Is this SMS send cap vs rebill cohort?
No. [SMS cap vs rebill cohort](/manuals/sms-cap-vs-rebill-cohort) is daily send capacity. This page is whether the email flow fires before the next MIT hour.
Is this cancel-save EV?
Related price. [Cancel-save offer](/manuals/cancel-save-offer) prices leftover LTV. This page is the clock — flow before charge, or miss.
What save percent should I paste?
None from a slide. Leave blank, or type your closed-book save %. We invent none.