Back to forecast
Revenue Intelligence Report

Konnekt Revenue Forecast

Generated 8 May 2026  ·  Forecast horizon 31 days  ·  Model Holt-Winters Additive  ·  Source Splynx ISP OSS

What we are seeing

Konnekt is collecting between KES 33,000 and KES 125,000 per day in subscription and hotspot payments, with a clear weekly rhythm. Payments tend to cluster mid-week and around month boundaries when most billing cycles renew. The model has trained on 90 days of complete payment history and is projecting forward for the next 31 days.

Last 30 days
KES 2.15M
Actual collected
May — to date
KES 602K
1 – 7 May actual
May — projected
~KES 3.25M
Full month estimate
June — projected
~KES 1.14M
Next month estimate
The projected May figure of ~KES 3.25M reflects the model's expectation for the full month, including the historically large mid-month and month-end billing clusters that spike daily revenue significantly above the daily average observed so far.

The model

The forecast uses the Holt-Winters Additive method — a classical time series model well-suited to subscription and billing data because it explicitly separates three signals present in payment flows.

L
Level
Baseline daily revenue, recalculated every day as new payments arrive
T
Trend
The gradual upward or downward direction in the baseline over time
S
Seasonality
Repeating weekly payment patterns driven by billing cycles

The forecast for any day h periods ahead is computed as:

Forecast(h) = Level + (h × Trend) + Seasonal index(h)

Each component is updated daily using exponential smoothing — meaning recent observations carry more weight than older ones, but the model never discards historical context entirely.

Level smoothing (α)
0.30
Trend smoothing (β)
0.10
Seasonal smoothing (γ)
0.20
Seasonal period (L)
7 days

The smoothing parameters are deliberately conservative. A low β of 0.10 means the model does not overreact to short-term shifts in trend — important for subscription revenue which grows gradually rather than in sudden jumps. A moderate α of 0.30 balances responsiveness to recent payment volumes against stability in the baseline estimate.

Data collected

The model trains on payment records fetched directly from the Splynx ISP platform via its REST API. Every payment transaction is retrieved, aggregated to a daily total, and passed to the model. No manual data entry or intermediate spreadsheets are involved.

Data source
Splynx — admin/finance/payments
Training window
90 complete days
Date range
7 Feb – 7 May 2026
Transactions processed
12,553

Days with no payments are filled with KES 0 to preserve the continuity of the time series. Today's date is always excluded from training because the current day is incomplete — including a partial day's total would understate the level estimate and distort the seasonal index for that weekday.

The training window begins in early February 2026. Any structural changes to the business before that date — pricing revisions, customer migrations, or service launches — are not visible to the model and do not influence the forecast.

Key considerations

Payment method All 12,553 transactions are M-PESA payments processed via Safaricom. The model implicitly captures M-PESA timing behaviour — customers tend to pay in bursts around salary dates (end of month) and service renewal reminder messages, which creates the weekly spikes the seasonal component detects.

Coverage The forecast includes all revenue streams: residential subscriptions, business accounts, and hotspot top-ups. This ensures projected totals match exactly what the Payments section of the operations dashboard reports for any given date range.

Seasonality assumption The model uses a weekly (7-day) seasonal period — the dominant cycle in ISP billing data. Monthly seasonality such as concentrated month-end spikes is partially captured because it recurs at weekly-adjacent intervals. A longer seasonal period (L=30) would require significantly more data to initialise reliably and is best revisited once 6+ months of history are available.

Trend lag With β set to 0.10 the model responds slowly to trend shifts. If Konnekt onboards a large batch of new customers or experiences significant churn, the forecast will lag behind the new reality for several weeks before the trend component fully adjusts to the changed baseline.

Forecast horizon Confidence degrades with distance. The 31-day table is most reliable for the first 7–10 days ahead. Beyond two weeks the forecast reflects the model's expectation of continued pattern repetition — treat it as a planning range, not a hard target. Month-level projections carry wider uncertainty than the daily figures suggest.

Non-recurring events Public holidays, M-PESA system outages, promotional campaigns, bulk activations, or sudden churn events cannot be predicted by this model. A day of near-zero payments caused by an outage would reduce the level estimate for several subsequent days. Such anomalies should be noted and the forecast reviewed manually when they occur.

This report is generated automatically from live Splynx payment data. As more complete days accumulate the model self-corrects and forecast accuracy improves. Smoothing parameters (α, β, γ) are candidates for optimisation through backtesting once 6+ months of data are available.  ·  ← Return to forecast dashboard