A seat is an individual learner account with its own ongoing experience in the platform, not just a one-time login.
Each seat gets a personal account, persistent AI Tutor context, quiz and progress history, and access to targeted courses.
Beyond the per-seat licence, the only other fee is an optional one-time setup fee in some enterprise deals. There are no separate metered charges passed to the customer for GB, tokens, or videos.
For a 600-employee company, it depends on scope:
Broad internal learning (e.g. all managers or knowledge workers): start with seats roughly equal to your target population (typically 300-600 seats in Year 1).
Tightly scoped rollout (e.g. only L&D plus a few pilot cohorts): 25-150 seats with a clear path to scale up as you expand programs.
Seats are reassignable when people leave or move roles, and we charge on concurrent active learner accounts, not every person who has ever worked at the company.
We typically map the organization into three groups - all count as seats:
We use per-seat pricing because it matches how value is delivered, how the category buys, and it keeps procurement simple - while our internal model already accounts for variable usage and underlying infra costs.
Matches how value is delivered. The product does not just "store videos." It builds an individualized learning graph per person over time: which courses they have completed, how they perform on assessments, what they ask the AI, where they are stuck. That is the level at which managers and HR care about outcomes.
Standard in the LMS and LXP category. Most modern learning platforms (LMS, LXP, LinkedIn Learning for Business) price on some version of "₹X-₹Y per learner/seat/user per year" rather than per video or per GB. Some offer variants like "per active user" or separate creator vs learner seats, but they are all user-based licensing models.
Keeps procurement simple. "We plan to support 400 learners this year at ₹X per seat per month" is much easier to reason about than "we will charge you for storage + streaming + tokens + quiz generations." Under the hood, our cost model cares about AWS, Gemini, OpenAI, etc., but that complexity is our problem, not the customer's.
Bakes in light vs heavy usage. Our internal cost model already assumes many learners will be light users and a smaller group will be heavy users; the mix is what we design margin around. We do not need to meter every action at the commercial level to be safe on costs.
We are not claiming "every single employee will be in the platform every day." We are saying: for each employee who has a seat, Spark + Athiya can build a durable, personalized learning experience - and that is what we are pricing. If we later see clear patterns where it helps to separate creator/admin seats from viewer/learner seats, we can explore that. For the initial offer, we recommend a single, predictable per-seat model plus optional setup, which is familiar to enterprise L&D buyers.
Many leading learning platforms use per-user / per-seat pricing:
These show that "per learner / per seat / per user" is the dominant pattern for enterprise learning tools today. The Athiya + Spark model is deliberately consistent with that.