{"id":16281,"date":"2026-01-12T15:05:44","date_gmt":"2026-01-12T15:05:44","guid":{"rendered":"https:\/\/bluelotus360.com\/uk\/?p=16281"},"modified":"2026-01-12T15:07:21","modified_gmt":"2026-01-12T15:07:21","slug":"future-of-seat-based-erp-licensing","status":"publish","type":"post","link":"https:\/\/bluelotus360.com\/uk\/future-of-seat-based-erp-licensing\/","title":{"rendered":"The Future of Seat-Based ERP Licensing: Is It Dying, Evolving or Up for Disruption?"},"content":{"rendered":"

In an era when business models, technology and workforce structures are changing fast, the question of how we licence enterprise software is becoming just as important as what software we buy. For decades, many companies have bought ERP systems under a seat-based (user-based) licensing model: pay for each named user who logs in. But with AI Agents , remote\/hybrid workforces, bots and process automation rising, one must ask: Is the seat-based ERP licensing model still relevant in 2026 \u2014 or is it on its way out?<\/p>\n

This blog unpacks how traditional ERP licensing is being challenged, explores what\u2019s replacing it, and why flexible, consumption-or outcome-based models (including what we offer at Blue Lotus 360) are emerging as the logical next step.<\/p>\n

The Problem with Traditional Seat-Based ERP Licensing<\/strong><\/h2>\n

Seat-based licensing made sense when ERPs were confined to offices, desktops and a defined set of users. Every user logged in from a workstation. You counted them, you paid for them. But today\u2019s business reality is quite different.<\/p>\n

Here are some of the pitfalls:<\/p>\n

    \n
  1. \n

    Inefficiency and escalating cost<\/strong><\/h3>\n<\/li>\n<\/ol>\n

    Companies often pay for many more \u201clicensed users\u201d than actually log in every day. Imagine a manufacturing firm: 10 core ERP users, but 50 occasional users (supervisors, temporary staff, remote auditors). The seat model forces you to licence all 60 or find complex workarounds.<\/p>\n

    Some vendors try to make this easier by offering concurrent licenses instead of strict named seats. On paper, it sounds reasonable: you buy 20 concurrent users and let a pool of 50 people share them, as long as only 20 are logged in at once. In real life, it\u2019s messier – there\u2019s always a \u201c21st user\u201d who gets locked out, IT ends up policing who can log in and when, and most companies eventually over\u2011buy licences just to stop the system from blocking people during busy periods.<\/p>\n

    Traditional seat-based ERP doesn\u2019t just waste money, it quietly punishes collaboration. Every time you add someone who could help – a junior accountant, a branch manager, an external auditor, you also add cost. So finance teams start doing the \u201clicence math\u201d in their heads. Junior staff are kept out of the system and pushed back to spreadsheets. Auditors get exported PDFs instead of real\u2011time access. Department heads wait for someone else to run reports for them.
    \nYou\u2019re not really protecting data. You\u2019re slowing down decisions. That\u2019s the hidden problem with per\u2011user pricing: it creates bottlenecks that look like control.<\/p>\n

      \n
    1. \n

      Mismatch with process-centric workflows<\/strong><\/h3>\n<\/li>\n<\/ol>\n

      Modern work isn\u2019t purely human-user driven. Think of integration points: IoT sensors feeding data into ERP, APIs, AI Agents and bots that perform data entry, field workers logging via mobile outside traditional desks. Seat-based models don\u2019t account well for non-human or sporadic use, so they start to feel rigid.<\/p>\n

      AI agents today can read documents, create transactions, kick off workflows, and even chat with your team to sort out issues, without ever logging in like a traditional \u201cuser.\u201d If every one of those agents is treated as a full paid seat, it suddenly becomes expensive to experiment or scale automation. A modern licensing model should recognise that AI agents live in the process layer, not the org chart, and price them in a way that encourages you to automate more, not less.<\/p>\n

        \n
      1. \n

        A barrier to digital transformation<\/strong><\/h3>\n<\/li>\n<\/ol>\n

        If licensing costs scale with headcount, companies hesitate to onboard partners, vendors or remote teams for fear of extra cost. That slows down transformation. According to a 2024 article in Forbes<\/em>:<\/p>\n

        \u201cForward-thinking decision-makers should consider shifting toward performance-based software licensing.\u201d (Forbes<\/a>)
        \nIn other words, paying for seats rather than performance may be sabotaging software potential.<\/p>\n

          \n
        1. \n

          The licensing sea-change is already underway<\/strong><\/h3>\n<\/li>\n<\/ol>\n

          In a recent blog post about software licensing changes in 2026, one firm points out how major players are revisiting their licensing models:<\/p>\n

          \u201cWhen Tesco \u2013 one of the UK\u2019s largest retailers \u2013 sues a software vendor for \u00a3100 million over licensing changes, mid-market IT leaders should pay attention.\u201d (block64.com<\/a>)
          \nIt\u2019s a sign that re-thinking how we pay for enterprise software is not just talk \u2014 it\u2019s happening.<\/p>\n

          The Evolution: From User-Based to Value-Based ERP Licensing<\/strong><\/h2>\n

          Because of these pressures, we\u2019re already seeing licensing models pivot away from per-seat pricing towards usage, value or outcome-based models. Here\u2019s how the shift is unfolding.<\/p>\n