Matvey Zakharov
RU

Every month starts from zero

Nothing brings past clients back on a schedule: nobody tracks when each one will need the product again, nobody contacts them then, and there is no subscription, contract or deposit that recurs. So every month's revenue has to be found or re-closed anew.

What is known about a month on its first day

The last month of each period as it looks on its first day. The number in a day is how many orders for it are already known.

Before
Mon
Tue
Wed
Thu
Fri
Sat
Sun
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Known in advance: RUB 0 of RUB 3.3M
After
Mon
Tue
Wed
Thu
Fri
Sat
Sun
18
26
38
410
54
6
7
812
96
105
115
126
13
14
158
167
178
182
197
20
21
226
235
244
257
2613
27
28
293
307
Known in advance: RUB 3.6M of RUB 6.1M
An order is known in advance when the client was reminded of his next purchase, or when it was planned together with him.

Client cards: purchases in a year

Clients who first bought in the first month of the period. Purchases per client in a year on average: 1.4 before and 2.5 after.

Before
After
A card is a client, a circle is a month after the first purchase. Grey: the first purchase; blue: a repeat one.
SOLUTION

Customer lifecycle / repeat-revenue system

  1. From your sales of recent years, I find which clients bought again and after how long: each has his own cycle.
  2. Each cycle gets a reminder: the client hears from you when it is time again, and the order goes into the plan before the month starts. Where it fits, a subscription, contract or deposit.
  3. On the first of the month you see how much of it is already known, and how much is still to be found.

What an engagement produces

  • A review of repeat purchases: who, how often, after how long
  • Reminders on each client's cycle
  • A monthly plan with the orders already known
  • Offers for regular clients: subscription, contract, deposit
  • Setup in your tools, or oversight if you set it up yourself

Rules, thresholds, scripts and automation logic are engagement deliverables and are not published here.

Find out whether this is actually your constraint.

Explore another problem