1. License
Platform entitlement and roadmap access
What capability is included by default, and what triggers additional statements of work.
PRICING AND TCO
Core banking pricing needs a full-cost view
License line items are only one part of core banking economics. Durable decisions come from understanding operating cost, consulting dependency, and change friction over time.
WHY STICKER PRICE IS MISLEADING
License is rarely the biggest line
Core platforms are multi-year operating decisions. A lower first-year license can still produce a significantly higher total cost profile over time.
Legacy / ERP-based
Solid
What it means
The shape of the stack matters more than its total height. License levels differ between vendors, but the real multi-year number lives in operating and consulting.
Solid accepts a slightly higher license in exchange for a lower steady-state shape.
Illustrative shape only. No specific multiples or prices implied. Model your own numbers using the cost components below.
COST COMPONENTS
License vs operating vs consulting cost
Evaluate all three categories in the same model. This gives decision-makers a consistent baseline across vendor proposals.
2. Operating cost
Runtime and platform operations
Infrastructure footprint, monitoring, resilience setup, and daily support requirements.
3. Consulting cost
Change delivery dependency
How often external teams are needed for product updates, integrations, and compliance changes.
WHY SOLID'S OPS COST IS LOWER
Architecture choices reduce recurring runtime burden
Operational drivers
- Real-time processing removes batch windows and nightly peak overprovisioning
- No hidden third-party platform license beneath the banking layer
- Cloud-native service boundaries support targeted scaling
- Cleaner observability for faster issue isolation
Practical effect
- Lower baseline infrastructure footprint
- Fewer redundant operational components to maintain
- Less time spent on cross-platform compatibility management
- Improved predictability in annual run budgets
WHY CONSULTING COST IS MUCH LOWER
Configuration-first product operations
In normal operating cycles, banks should be able to manage product and policy changes without recurring external consulting projects.
Product updates
Rate, fee, and term updates are designed as controllable platform changes.
Policy changes
Operational rule updates can be made without rewriting core code.
Integration extension
Versioned APIs reduce heavy redevelopment across connected systems.
Regulatory adaptation
Compliance controls are integrated into operating workflows from the start.
EXAMPLE TCO FRAMING
A simple comparison format for procurement and architecture teams
The numbers below are example structure only, not published price commitments. Use your own assumptions with this layout.
Cost category
Typical interpretation
What to ask vendors
License
Annual platform fee
What is included vs add-on?
Separate base capability from optional modules and ask whether regulatory evolution and platform modernization are included.
Operating
Run and reliability cost
What runtime layers are required?
Quantify infrastructure, resilience setup, support effort, and any extra licenses from third-party platforms the solution depends on.
Consulting
Annual change delivery spend
How many updates require specialists?
Model recurring implementation and policy change work separately from one-time migration activity to avoid underestimating steady-state cost.
DESIGN PARTNER PROGRAM
Work the numbers on your own operating assumptions
Solid is shaping its pricing and operating model with Nordic banks. Bring your own inputs — we will walk through the shape of the stack with you.