Every other enterprise loyalty platform has one thing in common: the more successful your program becomes, the more you pay. More members. More transactions. More campaigns. More invoices. InsightsOutward was built on a different premise.
THE COMMERCIAL MODEL IN FOUR LINES
WHY STANDARD SAAS PRICING PUNISHES LOYALTY SUCCESS
Epsilon, Kobie, Capillary, Salesforce — every incumbent charges more as your program succeeds. Volume-based pricing is the industry default. It is also the reason so many loyalty programs stall at the moment they should be scaling.
What buyers are really comparing
This is not just a feature comparison. It is a comparison between a pricing model that taxes program momentum and one that lets growth improve the economics of the business case.
| Commercial trap | How standard SaaS monetizes it | Business effect | InsightsOutward model |
|---|---|---|---|
| The Transaction Tax Per-event billing | Every earn, redemption, trigger, and behavioral event becomes a billable unit. | The more engagement you create, the more the platform takes from incremental margin. | Activity volume does not change the annual fee. Better engagement improves program economics instead of eroding them. |
| The Member Fee Trap Per-member billing | Growth in enrolled members automatically expands the recurring platform fee. | Strong acquisition performance makes the business case worse as the program scales. | Member count is not a pricing lever. You can grow participation without triggering a fee penalty. |
| The Change Control Tax Configuration monetization | Routine configuration work becomes a scope document, quote, and invoice. | Operating teams slow down because every optimization carries approval friction and new cost. | Standard platform configuration is included in the model, so governance changes do not become a recurring revenue stream. |
| The Integration Ransom Dependency-based integration work | Each new feed or integration update becomes a separate commercial event. | The integration layer behaves like lock-in infrastructure instead of utility infrastructure. | The standard integration framework is part of the platform model, reducing the number of commercial surprises as the ecosystem evolves. |
| The Exit Cost Problem Switching friction | Vendor-owned architecture, opaque data handling, and no code ownership increase dependency over time. | Leaving becomes expensive enough that the incumbent can price against your inability to move. | Client-controlled deployment, guaranteed portability, and source code purchase options materially reduce vendor dependency risk. |
Commercial trap
Commercial trap
Commercial trap
Commercial trap
Commercial trap
"When we modeled the full cost of scaling our loyalty program to our five-year member target on our existing platform, the number was not defensible. The transaction fees alone would have consumed the program's incremental margin."
Composite from Tricycle commercial evaluation engagements
HOW INSIGHTSOUTWARD IS PRICED
InsightsOutward is priced on a fixed annual fee model scoped to the capabilities you deploy, not to the volume of transactions, members, or events you process. As your program grows, your costs do not.
Commercial architecture
Most enterprise loyalty platforms are priced to capture more value as the program gets more effective. More members means a higher platform fee. More transactions means more billable events. More configuration means more commercial friction. The model turns operating momentum into vendor upside.
InsightsOutward is structured differently. The annual fee reflects what you deploy: the I/O modules, tenant structure, and operating complexity required for your environment. Once live, transaction volume, member growth, and standard configuration work do not reprice the relationship.
That same architecture extends into integration economics. Standard Elucidate framework connections remain part of the operating model instead of becoming a recurring invoice stream every time the ecosystem changes.
Source code purchase is possible because the platform was designed to be client-operable infrastructure, not rented dependency.
TRICYCLE VS. STANDARD SAAS
This section is the procurement summary: one row per decision dimension, one view of how standard SaaS terms differ from the InsightsOutward model, and one column focused on the business consequence.
Decision lens
Use this as the commercial diligence view: not which platform has more claims, but which contract structure stays aligned once the program scales.
| Decision dimension | Standard SaaS | InsightsOutward | Commercial consequence |
|---|---|---|---|
| Pricing model | Per-transaction, per-member, or event-driven pricing that expands with usage. | Fixed annual fee aligned to capability scope, not activity volume. | The incumbent model becomes more expensive precisely when the program starts working. |
| Growth penalty | Every new member, transaction, or campaign can increase cost. | Program growth does not automatically reprice the relationship. | Forecasting stays stable instead of being re-opened every time growth outperforms plan. |
| Change control | Routine requirement changes generate scopes, approvals, and new invoices. | Standard configuration changes are included within the operating model. | Operating teams can optimize faster without treating every change as a procurement event. |
| Integration economics | Connections and updates are often priced as separate commercial workstreams. | The Elucidate framework is part of the platform model for standard connections. | The integration layer behaves more like infrastructure than recurring leverage against the client. |
| Code ownership | You license access while the vendor retains full platform ownership. | Source code purchase is available for organizations that want outright ownership. | The platform can move from recurring dependency to an owned operating asset. |
| Vendor lock-in | Migration cost, proprietary architecture, and contract terms compound over time. | Client-controlled deployment and purchase options create a structural exit path. | Negotiating leverage is stronger when exit is operationally possible, not theoretical. |
| Commercial alignment | Vendor upside increases as your program drives more transactions through its billing model. | The economic model stays tied to capability scope rather than usage extraction. | The program can scale without creating a structural conflict between client success and vendor revenue. |
THE OPTION NO OTHER PLATFORM OFFERS
Most platforms offer a license and call that flexibility. Source code ownership is different. It changes the balance of control, the accounting treatment, and the exit reality of the relationship.
Ownership proposition
InsightsOutward can be purchased because it was architected for a real transfer of control from the start. The codebase, deployment model, and operating assumptions support independent operation rather than symbolic ownership language.
A one-time purchase gives your organization negotiated rights to the platform, a defined transition structure, and the ability to deploy, modify, extend, and operate it on your own terms.
No renewal dependency. No forced exit event. No commercial penalty for wanting full control.
The platform can move from renewable license access to negotiated ownership rights over the codebase and its future use.
Your organization can run, modify, extend, and govern the platform independently instead of relying on vendor permission.
There is no vendor-controlled exit process when the client owns the platform and its operating path is structurally independent.
Commercial note
Source code purchase is negotiated based on scope, support transition, and governance requirements. It is not a list-price add-on because the operating and control implications are material.
Teams treating the loyalty platform as long-horizon operating infrastructure rather than recurring SaaS spend.
Organizations that need direct operational control of governed data and platform infrastructure.
Capital-disciplined buyers that prefer owned assets over recurring dependency exposure.
Organizations designing their next platform relationship around real independence from day one.
FOR THE FINANCIAL BUYER
Loyalty platform decisions involve a CFO because the commercial model has direct implications for P&L, balance sheet treatment, and long-term cost structure. The following addresses the questions that CFOs and finance teams raise during platform evaluation.
Finance diligence view
Finance teams do not need another platform promise. They need to understand what gets capitalized, what stays in OpEx, and what happens to the five-year model once member and transaction volume move above plan.
InsightsOutward is easier to diligence because the commercial structure is explicit: fixed annual license for deployed capability scope, no volume escalators, and an ownership pathway for organizations that want the platform treated as strategic infrastructure.
The finance question is whether your growth model creates operating leverage for you or billing leverage for the vendor.
Total cost of ownership
| Evaluation lens | What to model | Finance implication |
|---|---|---|
| Year 1 cost | Implementation fee scoped to deployment complexity plus Year 1 license. Standard Elucidate connections and standard configuration changes do not create separate surprise charges. | The entry-year budget is easier to defend because it is tied to deployment scope rather than a stack of contingent commercial events. |
| Years 2-5 cost | Annual license only unless you expand capability scope. Member growth, transaction growth, and standard operating changes do not automatically reprice the relationship. | The out-year model behaves more like planned infrastructure spend than volume-sensitive vendor tax. |
| Cost at scale | Run the five-year target case against transaction-based pricing and against the fixed-fee model. The economic delta expands as the program succeeds. | Strong program performance improves unit economics instead of eroding contribution margin through escalators. |
Accounting and capitalization
| Finance question | Commercial structure | Why it matters |
|---|---|---|
| Annual license | The standard subscription is recurring operating expense. ASC 350-40 considerations still apply to your internal-use assessment and related implementation allocations. | Finance can model the recurring run-rate clearly while separating it from capitalizable implementation components where applicable. |
| Source code purchase | A negotiated code purchase is structured as an owned software asset with defined rights, transition terms, and support boundaries. | For OpEx-sensitive organizations, ownership can change the balance-sheet and EBITDA conversation materially, subject to policy and accounting review. |
| Implementation costs | Professional services can be documented by workstream and project phase so your team can evaluate capitalization treatment under internal-use software guidance. | The approval package is stronger when accounting receives allocation detail instead of one undifferentiated services line item. |
Budget build support
Tricycle's commercial team supports capital approval workups with detailed TCO models, scenario analysis, allocation support, and commercial documentation shaped for finance, procurement, and board review.
WHAT COMES WITH THE LICENSE
The InsightsOutward commercial model extends to implementation and support with the same principle: predictable cost, no surprise invoices, and commercial terms aligned to your success.
Implementation is a defined-deliverable engagement with a fixed fee. No open-ended time and materials, no incentive for scope creep, and no re-pricing after contract execution.
Routine configuration changes and ordinary program refinements stay inside the annual license, so operating teams can improve performance without re-entering procurement.
Standard framework integrations, new modules, capability enhancements, and security releases are absorbed into the operating model instead of being turned into separate commercial events.
Included by default
Scoped separately
Accountability layer
Every enterprise deployment includes a dedicated Client Success Manager accountable to operating outcomes, not just uptime. The support model is designed to preserve momentum after launch rather than monetize routine dependency.
QUESTIONS FINANCE TEAMS ASK
Capability scope expansions — adding a new I/O module, adding a new tenant or business unit, adding a I/O Sovereign AI™ instance — or contract renewals. Transaction volume, member count, and event frequency do not trigger fee increases.
Custom development work outside the standard platform (bespoke features not in the I/O framework), integrations outside the Elucidate standard 250+ API library, and white-glove campaign services — which are scoped and priced separately through Tricycle Studios.
Source code purchase is a separate negotiated transaction based on platform scope and support terms. It is not a standard list price. Tricycle's commercial team works through a structured evaluation with your legal, finance, and technical teams.
Annual license renewals are governed by contract terms established at signature. Standard CPI-based escalation caps are included in enterprise agreements. No unilateral fee restructuring at renewal.
Data portability is contractually guaranteed. Your member data, your transaction history, your program configuration are yours. Migration support is available. With source code purchase, there is no exit process — you own the platform.
The commercial model conversation is different from the capability conversation. Most enterprise platform decisions stall because the business case wasn't built with the right model. Tricycle's commercial team has built the business case at every enterprise scale. You will leave with a defensible number for your CFO, not a vendor's marketing claim.
Model your total cost of ownership against your current platform using your actual transaction volumes and member projections. You leave with a defensible number, not a vendor estimate.
Request a Modeling SessionIf you're in an active evaluation, Tricycle can turn around a commercial proposal within five business days of a scoping conversation. Fixed fee, defined deliverables, no surprises.
Request a ProposalIf operational independence is a priority, Tricycle's commercial team will walk you through the source code purchase structure, the support and maintenance terms, and the accounting treatment options in a focused 60-minute session.
Start the Evaluation