Platform cost by user segment

Free · Individual · Pro · Premium · Ultimate · Jan → 28 Aug 2026
Free accounts
302,880
99.80% of all accounts
Paid accounts
608
345 Pro · 201 Premium · 62 Ultimate
Monthly active on voice
~1,700
0.6% of the free base
New paid, Jan → Aug
33 → 10
per month, down 70%

Signups month on month free is flat, paid is collapsing

MonthFree signupsProPremiumUltimatePaid totalFree per paid
January4,772226533145 : 1
February4,114416222187 : 1
March3,5991120233109 : 1
April5,312513725212 : 1
May4,06389623177 : 1
June4,1021214834121 : 1
July4,49456819237 : 1
August (to 28th)4,60642410461 : 1
Total35,0625110642199176 : 1

Free acquisition is healthy and steady at ~4,400 a month. Paid conversion has fallen 70% — from 33 new paid accounts in January to 10 in August. Premium is the worst hit: 26 in January, 2 in August. The free-to-paid ratio has widened from 145:1 to 461:1. Nothing about the free tier changed; what changed is the rate at which we convert off it.

Who consumes the AI voice agent the only cost line we can attribute per user

MonthActive usersTotal callsPaid-user callsFree-user callsFree shareTalk hrsTotal costFree-user cost
January2183862136594.6%20$125$113
February29269932437553.6%26$141$82
March5573,3333003,03391.0%71$413$368
April9085,4283195,10994.1%114$632$591
May1,56315,70848215,22696.9%154$908$839
June1,75826,33636925,96798.6%166$984$920
July1,91018,33529318,04298.4%207$1,315$1,251
August (to 28th)1,47010,37211810,25498.9%157$1,062$1,041
Total80,5972,22678,37197.2%915$5,580$5,205

Free users take 97.2% of AI calls and 93.3% of the AI spend, and the free share has climbed every month since February. But keep the magnitude honest: the entire eight-month AI voice bill is about $5,580 — roughly ₹4.9 lakh, against ₹94.5L of sales in the same period. This is a ~5% cost line, not an existential one.

Consumption trend free-user AI calls per month

Free-user AI calls Paid-user AI calls

Is there a heavy-user problem? last 30 days · 1,723 users active on voice

Calls taken in 30 daysUsersCallsTalk hrsCostCost per user
127227230$167$0.62
2–333881539$228$0.67
4–73882,16649$331$0.85
8–156267,13853$407$0.65
16–31991,78711$88$0.89

There is no abuse problem. The heaviest free user in the last 30 days took 29 calls and cost $1.26. The single most expensive free user cost $4.20. Cost per active user is flat at roughly $0.65–0.89 across every usage band, so no gating threshold would recover meaningful money. All 25 of the top consumers are on the FREE plan — but that is unremarkable when 99.8% of accounts are free.

Note the direction of causation: these are outbound calls we place to them, not a service they pull on demand. Heavy AI usage is us dialling repeatedly, not a user consuming a free resource. A usage cap would be capping our own outreach.

Assistant / LLM chat volume the other consumption surface

MonthJanFebMarAprMayJunJulAug
Assistant messages79,72563,53960,79493,13666,58059,27746,21740,500

509,768 assistant messages since January, and the trend is falling — down 49% from the April peak. Whatever the free tier is costing in LLM inference, it is shrinking, not growing. Per-message cost is not stored, so this cannot be converted to rupees from the database. That number has to come from the provider bill.

Chat / LLM cost — measured, not modelled provider export · 29 Jul → 28 Aug 2026

This replaces the estimate I refused to make. The provider export gives 31 days of actual organisation-level LLM spend, so the text side of the platform now has a real number attached to it.

MeasureValueNote
Total, 31 days$747.2529 Jul – 28 Aug 2026, organisation-wide
Daily average$24.10range $5.33 – $65.74
30-day run rate$723≈ ₹63,600 per month
Annualised at this rate$8,798≈ ₹7.7 lakh a year
Assistant turns in window27,180plus 18,887 user turns
Cost per assistant reply$0.0275≈ ₹2.42 per Anika message
Cost per user message answered$0.0396≈ ₹3.48 per inbound text handled

The trend inside the window is sharply down

WeekSpendPer day
29 Jul – 4 Aug$230.09$32.87
5 – 11 Aug$241.36$34.48
12 – 18 Aug$113.78$16.25
19 – 25 Aug$123.90$17.70
26 – 28 Aug$38.13$12.71

Daily chat spend has fallen 61% inside a single month — $34.48/day in early August to $12.71/day by the 28th. That tracks the message-volume decline on the row above (Anika's replies are down ~45% since April). Whatever is driving it is worth understanding before it is treated as a saving: a quieter assistant is cheaper, but the Spaces engagement data says text is one of the few things paying users actually do.

Chat is not a small line — it roughly equals voice

AI cost linePer monthPer month ₹Basis
Voice (all segments, all directions)$698₹61,400$5,580 over 8 months, measured per call
Chat / LLM$723₹63,600provider export, 31 days
Total AI$1,421₹1.25 lakh≈ ₹15 lakh a year at this rate

Splitting chat cost by segment

SegmentNew threads in windowShareAllocated chat cost
Free3,06497.1%$726 · ₹63,900
Individual services792.5%$19
Pro60.2%$1.4
Premium30.1%$0.7
Ultimate40.1%$0.9
Total3,156100%$747

Treat this split as an upper bound on free, not a precise allocation. The export carries no user_id, project_id or line_item — every row is organisation-total — so cost has to be allocated by an activity proxy. The proxy used here is threads created in the window, which is the only per-segment signal the indexes support. It overstates free: a paying user typically continues an existing thread rather than opening a new one, so their ongoing message volume is invisible to this measure. A proper split still needs the single-field index on assistant_thread.gameplayerId, or an export with user_id populated.

The five segments defined once, used throughout

SegmentDefinitionUsersShare
FreeNo entitlement of any kind. Signed up, never bought anything.302,44299.66%
Individual servicesBought a one-off service — ₹299 consultation, SoP review, visa filing — but no plan.4380.14%
Pro₹2,499 plan3410.11%
Premium₹34,999 plan2000.07%
Ultimate₹69,999 plan550.02%
Total303,476100%

Plan segment from entitlements.activePlan.planName; individual-service buyers are entitlement holders with no plan. Free is the remainder of platform_subscriptions. A user is counted in their highest tier only.

Inbound vs outbound — the whole voice picture Jan → 28 Aug 2026 · provider-reported USD

DirectionCallsShareTalk hrsAvg callCostShare of cost
Outbound — we dial them75,14393.2%68833 s$4,35478.0%
Inbound — they call us (WhatsApp voice)4,4885.6%180145 s$94016.8%
Other / untagged9691.2%47174 s$2865.2%
Total80,600100%91541 s$5,580100%

An inbound call lasts 4.4× longer than an outbound one — 145 seconds against 33. Inbound is 5.6% of call volume but 16.8% of the cost, because when someone rings us they actually talk. Outbound is cheap per call precisely because most of it never connects.

Voice cost by segment who generates which kind of call

SegmentUsersOutbound callsOutbound $Inbound callsInbound $Other $Total $$ per user
Free302,44274,033$4,2042,612$684$163$5,051$0.017
Individual438727$72255$54$29$154$0.35
Pro34120$4142$20$28$51$0.15
Premium200220$421,172$152$49$243$1.21
Ultimate55143$33307$30$18$81$1.48
Total303,47675,143$4,3544,488$940$286$5,580$0.018

The direction of the call tells you which segment it is. Free users take 98.5% of outbound — we chase them. Paying users generate 41.8% of inbound from 0.34% of the accounts — they ring us.

Inbound calls per user, over eight monthsRatevs Free
Free0.009
Pro0.4248×
Individual services0.5867×
Ultimate5.58646×
Premium5.86678×

A Premium user calls in 678 times more often than a free user. That is the clearest engagement signal in the entire dataset — and it costs $1.21 per user across eight months against ₹34,999 of revenue. Inbound volume is a retention asset, not a cost problem. Premium alone accounts for 26% of all inbound calls from 200 accounts.

Human coach calls the genuinely expensive channel

DirectionCallsConnectedTalk hoursShare of hours
Outbound29,60114,14095194.3%
Inbound5,2281,580585.7%
Total34,82915,7201,009100%

1,009 counsellor hours in eight months — this is the real cost line, and it dwarfs the AI. At a fully loaded ₹400/hour that is roughly ₹4.0 lakh of human time, against ₹4.9 lakh of AI voice. Comparable in rupees, but the AI number covers 80,600 calls and the human number covers 34,829. Per connected conversation, a counsellor costs roughly 20× what the AI does.

Only 45% of coach dials connect. Inbound coach calls connect at 30% — worse than outbound at 48% — which suggests missed inbound calls are being logged. That is a service-level problem worth its own look. Per-segment attribution of coach hours is not computed here: argonaut_counsellors_call_history keys on lead_id while segments key on gamePlayerId, and the bridge is not indexed for a platform-wide join.

Text — Anika in the Spaces volume is measurable, cost is not

MonthJanFebMarAprMayJunJulAugTotal
Space messages — human & system50,09843,02145,49365,99964,83881,55870,17552,414473,596
Anika replies30,83123,80527,42136,51414,33619,67718,25516,812187,651
Assistant LLM turns79,72563,53960,79493,13666,58059,27746,21740,500509,768

Anika wrote 187,651 replies in 2026 — 28% of everything in the Spaces. Volume peaked in April and has roughly halved since; Anika's share of the conversation dropped sharply after April, which looks like a deliberate change worth confirming with engineering.

Why there is no rupee figure on this row

assistant_conversation stores the message text but no token counts and no cost. Only the voice collection carries a metadata.cost field. Estimating from character length would undercount badly, because the billed prompt re-sends the system context and full history on every turn — none of which is stored per call. Any number produced that way would be wrong by a multiple, so I have not produced one.

Per-segment text volume also could not be computed. assistant_thread.gameplayerId is only indexed compound with createdAt, so a segment-wide join times out. A single-field index on gameplayerId, or a one-off export, unblocks it.

Cost against revenue, per segment the only comparison that matters

SegmentUsersVoice cost / user
8 months
Plan priceVoice cost as % of revenue
Free302,442$0.017₹0undefined — no revenue
Individual438$0.35₹299–15,000< 10%
Pro341$0.15₹2,4990.5%
Premium200$1.21₹34,9990.3%
Ultimate55$1.48₹69,9990.2%

Voice cost is a rounding error against every paid tier — under 0.5% of revenue in all four. The heaviest users of the platform are also the most profitable ones by a wide margin. Nothing here supports throttling a paying segment, and the free segment costs $0.017 a head over eight months.

The one genuine exposure is free outbound: $4,204 spent dialling people who have never paid, producing 78% of total voice spend for the segment with no revenue attached. That is the line to manage — not by closing the platform, but by dialling fewer, better-qualified people, which is exactly what the ₹299 cohort analysis argues for.

What this means for closing the platform

The premise does not survive the data. "We can't keep the platform too open for too long" assumes open access is costing us. Three findings say otherwise:

  • 99.4% of free accounts are dormant. ~1,700 of 302,880 are active on voice in a month. Gating a dormant account saves nothing — there is no marginal cost to an account that never logs in.
  • The heavy tail is trivially cheap. The most expensive free user in 30 days cost $4.20. Cost per active user is flat across every usage band, so no cap or paywall threshold recovers meaningful money.
  • Free "consumption" is mostly us calling them. 97% of AI voice is outbound dialling we initiate. Restricting free users would restrict our own outreach — and the ₹299 analysis shows outreach is exactly what converts.

The real finding on this page is the conversion collapse — 33 new paid accounts in January against 10 in August, with Premium down from 26 to 2. That is a monetisation problem sitting on top of a healthy and stable top of funnel, and closing the platform would treat the symptom we do not have while making the one we do have worse.

If the goal is to gate something, gate the expensive human, not the cheap software. Counsellor time and G-Meets are where real money goes, and the companion ₹299 analysis shows they are already being rationed — just arbitrarily rather than deliberately.

Data we do not have — the ask

To close this properly, the following is needed from engineering — none of it is in the database today

  1. Actual infrastructure cost per active user. Hosting, storage and bandwidth are not attributed per account anywhere. Without it, "cost of a free user" is unanswerable beyond the AI line.
  2. LLM inference spend — received, partially resolved. The 31-day provider export gives organisation totals ($747.25). What is still missing is the breakdown: the export's user_id, project_id and line_item columns are all empty, so chat cannot be separated from the voice agent's own LLM calls, program-finder, or SoP generation — nor split by user. Ask for the same export with those dimensions populated.
  3. Login / session activity. There is no reliable last-login on the account record, so "dormant" here is inferred from voice and chat activity only. A true MAU needs session events.
  4. Document and storage footprint per user — SoPs, uploads, dashboards. Row counts exist; bytes do not.
  5. Free-tier feature entitlements as configured. What a free account is actually permitted to do today is not represented in the data, so we cannot model what gating would remove.
  6. An index on assistant_thread.gameplayerId (single-field). Today it exists only compound with createdAt, which makes per-segment text attribution time out. This is a five-minute change that unlocks the text-cost analysis.
  7. A gamePlayerId on argonaut_counsellors_call_history, or a maintained lead↔player bridge table. Without it, counsellor hours — the largest cost line on this page — cannot be split by segment.

Sourcesplatform_subscriptions (plan and signup month), ai_voice_conversation (metadata.cost, durationSeconds; paid users identified by joining gamePlayerId), assistant_conversation (message volume). Costs are provider-reported USD for the AI voice stack only and exclude telephony, infrastructure and LLM chat. Months are IST; August runs to the 28th. Pulled 28 Aug 2026 — a snapshot, not live.