Hybrid pricing (base + usage)

Hybrid pricing is a combination of a fixed base fee and usage-based payment: the customer pays a base (for which they get an included volume/features), and above the limit — by actual usage. It is a compromise between a predictable subscription (1028) and a usage model (1033). The goal is to give the customer a predictable base while fairly pricing usage growth. Honestly about complexity, this is key: hybrid is more complex than both a subscription and pure usage. It is harder for the customer to understand how the bill is calculated (base + overage) and harder for you to set up, explain and maintain. The complexity is justified only if it solves a real problem (e.g. both predictability is needed and usage varies greatly between customers). If the task is solved by a simple subscription or simple usage — hybrid is excessive. We will honestly assess whether you need it rather than offer 'trendy' complexity. Honestly about the same requirements as usage: hybrid inherits the usage-model requirements (1033) for its variable part — an honest usage metric correlating with value and accurate reliable metering are needed. Without them the variable part will be unfair and disputable. Honestly about residual unpredictability: the base adds predictability, but the overage payment can still surprise the customer. Limits, forecasting and alerts on overage usage are needed — otherwise the same bill-shock risk as in usage. We build in transparency. Honestly about balancing base and usage: the key is correctly setting the base size, included volume and overage price so it is fair both for the customer and for you. This requires understanding usage patterns. Honestly about the effect: in a suitable situation it gives both predictability and fairness of price growth, but it is not a revenue guarantee and adds complexity. Honestly about access: a usage metric, accurate metering, billing (1028), an understanding of patterns are needed. An important boundary: this is hybrid; pure usage — 1033; subscription/base — 1028; tier structure — 1032. Picture this: instead of 'either a fixed fee or unpredictable usage' — a predictable base plus honest payment for growth when it is genuinely needed. The base price starts from 55,000 ₽ (depends on the model and metering).

• A fixed subscription is unfair with widely varying usage.
• Pure usage is too unpredictable — customers need a base.
• A past hybrid model turned out too complex and unclear.
• Overage payment surprises customers (no transparency).

• Implementing a hybrid model (base + payment for usage above the limit)
• An honest assessment: is hybrid needed or is something simpler enough (subscription/usage)
• Setting the base, included volume and overage price
• An honest usage metric + accurate metering (as in usage 1033)
• Overage transparency: limits, forecasting, alerts
• Honest boundaries (more complex than simple models; metric/metering needed; residual unpredictability; no guarantee)
• A link with usage (1033), billing (1028), plans (1032)
• Handover and review with you

• A predictable base + honest payment for usage growth
• A balance of predictability and fairness
• Overage transparency (no bill shocks)
• Honest boundaries (not always justified; metric/metering needed; no revenue guarantee)

• We assess whether hybrid is justified (vs subscription/usage)
• We set the base, volume, overage price by usage patterns
• We set up metering and transparency, honestly set boundaries with you

• Is hybrid better than a simple subscription or usage?

  Not always, honestly: hybrid is more complex than both models — harder for the customer to understand the bill, harder for you to set up and maintain. It is justified only if it solves a real problem (both base predictability and fairness with widely varying usage are needed). If a simple subscription or simple usage solves the task — hybrid is excessive. We will honestly assess the need rather than offer complexity for a 'trendy model'.

• Won't overage payment lead to bill shocks?

  There is a risk, and we close it, honestly: the base adds predictability, but the overage payment can still surprise the customer. Limits, forecasting and alerts on overage usage are needed — otherwise the same bill-shock risk as in usage (1033). We build in transparency so the customer controls spending above the base rather than getting a surprise.

• What is needed for hybrid to work honestly?

  The same requirements as usage, plus balance, honestly: a usage metric honestly correlating with value and accurate reliable metering for the variable part (as in 1033). Plus it is important to correctly set the base size, included volume and overage price to your real usage patterns — so it is fair both for the customer and for you. Without this the model will be unfair or disputable — we honestly build that in.