A lot of the businesses that reach out to us don't have a steady month. A wedding venue's phone is nearly silent in July and doesn't stop ringing in November. A tax consultant is quiet for nine months and underwater for three, chasing the annual return-filing deadline that concentrates a huge share of a year's work into a few weeks. An AC repair business lives and dies by how hot April gets. A festive-season retailer does half its year's business in six weeks around Diwali. None of these businesses has an "average month" in any meaningful sense — and a flat monthly software fee is, structurally, a bet that they do.
What a flat fee assumes
Subscription pricing works cleanly when usage is roughly constant — the same volume of activity, month after month. The flat fee is a reasonable approximation of a reasonable average.
Seasonal businesses break that assumption on both ends. In the slow months, you're paying full price for a service you're barely touching — the wedding venue paying the same fee in July that it pays in November, for a fraction of the calls. In the peak months, if the plan has any kind of cap or seat limit, you either hit it right when you need headroom the most, or you're stuck negotiating an upgrade under time pressure during the busiest weeks of your year.
Seasonality isn't a business being inconsistent. It's the business working correctly. The pricing model should be the thing that adapts — not the business.
Why usage-based pricing fits the shape of the problem
AIVA has no monthly fee and no seat limit. You draw from one balance — ₹4 a minute for voice, ₹2 a conversation for web chat, ₹1 a message for SMS — and it moves with whatever's actually happening on your phone line and your website that month.
For a seasonal business, that means the bill in July looks like July, and the bill in November looks like November, without anyone having to notice, request a downgrade, or negotiate a temporary upgrade. There's no plan to right-size twice a year. There's no conversation with a vendor about whether this quarter counts as "peak." The pricing already reflects it, automatically, because it was never estimating your month in the first place — it was just pricing what happened.
A worked year, for one seasonal business
Take the AC repair example from the top, and put real numbers to it. Say the business gets 8 calls a day in its quiet stretch — August through February, seven months — at an average 3 minutes each (diagnostic calls tend to run longer than a quick booking question). That's 208 calls a month, or 8 × 26 × 3 × ₹4 = ₹2,496 a month, roughly ₹17,470 across the seven quiet months.
Then March and July, the shoulder months either side of peak heat, see call volume roughly triple to 25 calls a day — 650 calls a month, ₹7,800 a month, ₹15,600 across both months.
Then April through June, peak heat, call volume more than doubles again to 60 calls a day as ACs across the city start failing at once — 1,560 calls a month, 1,560 × 3 × ₹4 = ₹18,720 a month, ₹56,160 across the three-month peak.
Add it up: roughly ₹89,230 for the year, unevenly spread exactly the way the business's real year is unevenly spread — about 63% of the annual spend concentrated into the three hottest months, because that's also where 63% of the actual work is happening.
Now compare that to two flat-fee scenarios. A flat fee sized to comfortably cover the peak — say ₹8,000 a month, close to what April through June actually costs — would charge ₹96,000 for the year, more than the usage-based total, because it's charging peak-level pricing for the quiet months too. A flat fee sized to be affordable in the quiet months — say ₹3,000 a month, ₹36,000 for the year — would be cheaper on paper, but it wouldn't remotely cover peak volume: ₹8,000-plus worth of actual April usage against a ₹3,000 bucket means either a steep overage charge or a service that caps out during the exact three months the business depends on it most. There's no flat number that's simultaneously fair in February and sufficient in May. That's not a pricing failure specific to any one vendor — it's what a flat fee structurally cannot do for a business shaped like this one.
The specific problem of an unpredictable peak
Wedding venues and tax consultants know their peak dates almost to the week — the calendar tells them. An AC repair business doesn't have that luxury. Its peak is triggered by weather, not a calendar, which means the exact week volume tsunamis in is genuinely uncertain until a heatwave actually arrives. That's a harder planning problem than a predictable seasonal business faces, and it's exactly the case auto-recharge is built for — instead of trying to guess the week to manually top up, the balance recharges itself once it drops below a threshold you set, so a sudden, weather-driven spike in calls never runs the account dry in the middle of the first heatwave week of the year.
The honest edge case
It would be misleading to claim usage pricing wins in every single comparison, so here's the honest version: in a shoulder month rather than a true peak one, a flat fee sized around ₹8,000 and a real usage bill can land close together — March and July above cost about ₹7,800 each, not far off that hypothetical flat rate at all. The case for usage pricing isn't that it wins every individual month — it's that it wins the year, because the same flat fee that looks roughly competitive in a shoulder month is wildly overpriced against the ₹2,496 of a quiet one, and badly undersized against the ₹18,720 of a true peak one. There's no single flat number that avoids that trade-off for a business with real seasonal swings.
The other honest edge case runs the opposite direction: a business with high, genuinely consistent volume nearly every month — not seasonal at all — is exactly the case where a negotiated flat rate can outperform the standard per-unit price. That's what custom pricing and invoicing is for, and it's a fair option for the businesses it fits. It's just a different case from the seasonal one this post is about.
The part that's easy to miss
The fairness argument is the obvious one, but there's a second effect that matters just as much: usage-based pricing removes the incentive to under-deploy during your slow season out of fear of the fixed cost. A wedding venue on a flat monthly plan has a reason to think about turning things off in the off-season to save money — which is exactly the season when a missed inbound call, someone planning eight months out, calling around, is disproportionately valuable, because there are so few of them to begin with. Usage pricing removes that trade-off entirely. There's no reason to turn anything off, because the off-season barely costs anything to keep running.
What this actually means at recharge time
In practice, this shows up as recharge packs, not invoices: ₹500 to start, ₹2,000 or ₹5,000 when you need more headroom, topped up whenever your balance runs low — sized to however your year is actually shaped, not to a calendar the vendor picked. A seasonal business ends up recharging more in its two busy months and barely touching its balance the rest of the year, which is exactly what a fair price for a seasonal business should look like. Full details on the packs and how the balance draws down are on the pricing page, and every account starts with ₹500 of it free to test against your own actual seasonal pattern before you commit to anything.
We built it this way because most of our own customers don't have flat years, and we didn't want our pricing to be the one part of their business that pretended they did. If you want the fuller reasoning behind ditching a monthly fee entirely, that's covered in more depth in why AIVA has no subscription tier at all.