Low-code and no-code platforms were sold to enterprises on a promise of democratised application development at lower cost than traditional software delivery. The promise has largely materialised on the development side — business users genuinely can build functional applications with minimal developer involvement. The cost promise, however, has not. Microsoft Power Platform, OutSystems, Mendix, Appian, and ServiceNow App Engine have all evolved into significant annual licence commitments for the enterprises that adopted them at scale, and the pricing models are designed with expansion mechanics that ensure initial commitments grow substantially year over year.
Understanding how each platform prices, where costs escape initial estimates, and what negotiation leverage enterprise buyers hold is essential for IT leaders managing low-code investments that now routinely exceed $1–3M annually for mid-to-large organisations.
Microsoft Power Platform: The Hidden M365 Expansion
Microsoft Power Platform — comprising Power Apps, Power Automate, Power BI, and Power Pages — is the market leader by enterprise adoption, largely because its entry-level capabilities are bundled with Microsoft 365 licences at no additional charge. This creates a deceptively attractive starting point: users can build basic Power Apps and automated flows within their existing M365 entitlement.
The licensing complexity emerges when applications require premium connectors (connections to databases, APIs, or third-party services outside the standard M365 data sources), Dataverse storage (Power Platform's proprietary data layer), or advanced Power Automate flows with non-standard connectors. Each of these triggers premium per-user or per-flow licensing that sits entirely outside the M365 bundle.
The Power Platform cost escalation pattern: Organisations that start with M365-included Power Apps and automate a critical business process on premium connectors often discover mid-year that the "free" platform is generating $400K–$800K in annual premium licensing across 200–400 power users — without any centralised governance having approved the commitment.
Power BI Premium deserves specific attention. Power BI Desktop and Pro are well-understood; Power BI Premium Capacity (now Premium Per User and Premium Capacity modes) unlocks paginated reports, AI-powered analytics, deployment pipelines, and large dataset support. Enterprises that deploy Power BI at scale and enable Premium features for business users frequently accumulate Premium Per User licences without a corresponding business case review, creating annual commitments of $500–$900 per user above the Pro base cost.
Negotiation strategy for Power Platform centres on its relationship to the Microsoft EA. Power Platform commitments negotiated as part of, or alongside, Microsoft EA renewals benefit from the bundling leverage that exists in EA negotiations generally. Microsoft Azure Consumption Commitment (MACC) agreements sometimes include Power Platform credits as part of the Azure commercial commitment. Securing Power Platform capacity within a Microsoft platform negotiation — rather than through a separate Power Platform purchasing motion — consistently delivers better economics.
OutSystems: The Enterprise High-Productivity Tier
OutSystems positioned itself as the high-productivity, enterprise-grade low-code platform — capable of delivering complex, large-scale applications with more architectural sophistication than workflow-focused competitors. This positioning commands premium pricing: OutSystems Enterprise licences are among the most expensive in the low-code market, with annual commitments typically in the $300K–$2M range for mid-to-large enterprises.
OutSystems pricing is based on Application Objects (AOs) — a proprietary unit that reflects the complexity of applications built on the platform. Each screen, entity, logic element, and integration contributes to an AO count, and licences define the maximum AO count permitted. Organisations that build aggressively on the platform, or that use OutSystems for complex enterprise systems integration, can exhaust their AO allowance and require licence expansion mid-term.
The AO model is opaque to buyers who haven't used OutSystems previously. Development teams that haven't been trained in AO-efficient design patterns build applications that consume four to five times the AO budget of equivalent applications built by experienced OutSystems developers. The first AO expansion conversation with OutSystems — typically coming 9–12 months into a deployment — arrives with limited negotiating leverage, as the organisation is already committed to the platform and facing a genuine operational constraint.
Preventive measures include negotiating a generous initial AO buffer at the point of platform adoption (typically 30–40% headroom above the initial estimate), securing the right to expand AOs at the original committed per-AO rate throughout the contract term, and investing in OutSystems-specific development training that reduces AO consumption through better design patterns.
Mendix: Siemens Platform Economics
Mendix, acquired by Siemens in 2018, is the preferred low-code platform for industrial and manufacturing enterprises, particularly those already in the Siemens ecosystem. Mendix pricing has evolved to a cloud-based subscription model offering tiers from Free through Single App, Pro, and Enterprise, with significant capability and governance differences between tiers.
| Platform | Pricing Model | Key Cost Driver | Typical Enterprise Spend |
|---|---|---|---|
| Power Platform | Per user + capacity | Premium connector sprawl | $200K–$1.5M/yr |
| OutSystems | Application Objects | AO expansion mid-term | $300K–$2M/yr |
| Mendix | Per app per environment | Environment proliferation | $200K–$1M/yr |
| Appian | Per user (full/infrequent) | User tier misclassification | $250K–$1.5M/yr |
| ServiceNow App Engine | Bundled with platform | Creator user licences | Varies by platform tier |
The key Mendix cost driver is environment proliferation. Mendix charges per application per environment — development, test, acceptance, and production are separate environments, each attracting licence fees. Organisations that maintain multiple versions of each application in multiple environments, or that use Mendix for rapid prototyping with many short-lived applications, can accumulate environment counts that substantially exceed initial estimates.
Siemens' ownership creates an interesting negotiation dynamic for industrial customers. Siemens is motivated to grow Mendix adoption within its existing industrial software customer base (MindSphere, Opcenter, Teamcenter customers). Bundling Mendix into a broader Siemens software renewal or digital transformation agreement can unlock pricing flexibility unavailable in a standalone Mendix negotiation.
Appian: Process-Centric Licensing and User Tiers
Appian's low-code platform is oriented toward process automation, case management, and regulatory compliance — making it a common choice in financial services, government, and healthcare. Appian's pricing model uses two user tiers: Full Users (named users who design, manage, and participate actively in processes) and Infrequent Users (external parties or occasional participants in workflows).
The user tier model creates a recurring audit and governance challenge. External parties — customers, regulators, external partners — who participate occasionally in Appian-managed workflows are priced as Infrequent Users at lower rates. As process adoption grows and more stakeholders are incorporated into workflows, the boundary between Infrequent and Full User cases can be ambiguous, creating compliance risk and renewal-time reclassification conversations that consistently result in higher costs than anticipated.
Appian's competitive positioning against ServiceNow and Salesforce for process automation creates genuine negotiating leverage. Organisations evaluating Appian renewals that can credibly demonstrate evaluation of alternatives — particularly ServiceNow App Engine or Salesforce Flow — will find Appian's enterprise team significantly more accommodating on pricing than organisations that signal incumbent commitment.
ServiceNow App Engine: Expansion Trap within the Platform
ServiceNow App Engine is the low-code development layer within the ServiceNow platform, available to organisations already on ServiceNow IT Service Management or other ServiceNow products. App Engine Studio enables IT and business users to build custom applications on the ServiceNow data model, extending platform capability without traditional development investment.
The App Engine licensing model requires "Creator" licences for users who build applications — distinct from standard ServiceNow ITSM user licences. As organisations expand their use of App Engine to address business process automation beyond IT service management, the Creator user count grows and the incremental licensing cost accumulates. For large ServiceNow customers, App Engine expansion can add $500K–$1M annually to the ServiceNow invoice without clear budget approval.
App Engine licensing should always be negotiated as part of, not separate from, ServiceNow platform renewals. Our detailed analysis of ServiceNow licensing strategy is available in the ServiceNow negotiation guide and the companion article on ServiceNow Now Assist and AI licensing.
Governance: The Root Cause of Low-Code Overspend
The common thread across all low-code platforms is governance failure. Low-code was designed to put application development in the hands of business users — and it has succeeded. The consequence is that the governance structures that apply to traditional enterprise software procurement (IT approval, licensing review, budget authorisation) have not kept pace with the speed at which business users create and expand low-code deployments.
Governance imperative: Every enterprise with more than 200 low-code users across any platform should have a formal low-code centre of excellence that tracks active applications, monitors environment counts, audits user tiers, and manages the renewal calendar. Organisations without this governance structure consistently overspend by 35–50% of what peer organisations with mature governance pay for comparable capabilities.
A low-code governance programme has three components. First, a complete inventory of all applications, environments, and users on each platform — typically surfacing dozens of applications whose business justification no longer exists. Second, a user tier audit that identifies misclassified or inactive users who can be removed or downgraded before renewal. Third, a renewal calendar that initiates negotiation conversations 180 days in advance, avoiding the cost-plus-urgency pricing that arrives when low-code teams discover their platform is auto-renewing in 30 days.
Recommended Advisory Approach
Low-code platform negotiations benefit from advisors who understand both the technical complexity of platform pricing models and the commercial dynamics of the vendors involved. Firms such as Redress Compliance benchmark low-code platform spend across hundreds of enterprise engagements and can identify quickly whether an organisation's Power Platform, OutSystems, or Mendix costs are competitive relative to peers of comparable size and complexity.
The return on advisory investment is particularly high for low-code renewals because the governance deficit in most enterprises means there is almost always discovered savings — inactive users, unused environments, misclassified tiers, or negotiable pricing — that a structured engagement will surface. A 12-week advisory engagement for a $1M low-code renewal typically generates $200–$400K in identified savings, net of advisory cost.
For the broader emerging technology contract framework, see our Emerging Tech Contracts Guide. Related articles include our guides on RPA platform licensing and DevOps toolchain licensing. Our SaaS licence optimisation service covers low-code platform rationalisation. For Microsoft Power Platform specifically, see the comprehensive Power Platform licensing guide and our coverage of Microsoft enterprise licensing.