InsightsOutward
I/O Loyalty Platform Fabric

The Loyalty Platform That Doesn't Penalize You for Growing

Many enterprise loyalty platforms become more expensive as member, transaction, and event activity grows. InsightsOutward was built on a different premise: program growth should improve your economics, not reprice the platform.

THE COMMERCIAL MODEL

Annual platform fee Deployed capability scope

The meter does not move with

  • Members
  • Transactions
  • Events
  • Standard configuration
Separate ownership path Negotiated source-code purchase Rights, transition, and support defined in the agreement.

HOW PRICING BEHAVES

Scale the Program Without Moving the Meter.

The annual fee follows the platform capabilities and operating structure you deploy. Ordinary growth in members, transactions, and event activity stays inside the model.

Pricing behavior as the program scales

Usage-linked pricing

Platform cost rises with members, transactions, and activity.

InsightsOutward fixed fee

Platform cost stays tied to deployed capability scope.

What sets the annual fee

Deployed capability scope I/O modules · tenant structure · operating complexity

The distinction: activity and platform price move independently until deployed capability scope changes.

Illustrative platform cost behavior as program scale increases Usage-linked platform cost rises as program scale increases while the InsightsOutward fixed annual fee remains level.
Illustrative cost behavior. Actual commercial terms follow deployed capability scope.

Not pricing levers

  • Member growth
  • Transaction volume
  • Event activity
  • Standard configuration

THE COMMERCIAL BOUNDARY

Know What Stays Inside the Model.

The commercial boundary is established before implementation begins. Routine operation stays inside it; genuinely new scope is identified outside it.

Annual license boundary Agreed at signature · governed through renewal

Inside the agreed commercial model

Predictable by design
01 Launch

Defined deployment and configuration under a fixed implementation scope.

02 Operate

Member, transaction, event, and standard configuration growth.

03 Evolve

Standard Elucidate connections, releases, and security updates.

04 Renew

Contracted terms with agreed CPI-based escalation caps.

A dedicated Client Success Manager remains accountable to operating outcomes—not just platform uptime.

Separately scoped outside the boundary

  • Bespoke development outside the I/O framework
  • Connections outside the standard 250+ API library
  • White-glove campaign services through Tricycle Studios

AN OWNERSHIP PATH BEYOND SUBSCRIPTION

Choose Renewable Access or Transfer Control.

The platform begins in the client’s Azure environment. From there, the commercial relationship can continue as a supported license or move through a negotiated source-code purchase.

Common starting point

Client-controlled deployment

Your cloud, data, configuration, and operating history remain under client governance.

Continue the license

Renewable platform access

  • Predictable annual terms
  • Tricycle-supported operation
  • Contracted renewal structure

Exercise the purchase option

Client-owned operating asset

  • Negotiated source-code and use rights
  • Independent operation and extension
  • No forced migration at vendor exit

Best suited to: organizations with infrastructure-independence requirements, regulated or sovereign constraints, white-label ambitions, or a long-term capital-allocation case for ownership.

Source-code purchase is separately negotiated around platform scope, rights, transition structure, and support terms.

FINANCE DILIGENCE VIEW

What Finance Should See Before Signature.

This is a diligence framework, not an implementation timeline. Deployment speed and long-term commercial exposure are separate questions; both should be clear before approval.

Entry scope

What is known at signature?

Separate deployment, integrations, and the annual license so the approved entry cost is inspectable.

Inputs: deployment · integrations · license

Operating economics

What happens when the program grows?

Test member, transaction, and event growth without assuming that success automatically reprices the platform.

Inputs: growth forecast · margin · new capability

Renewal mechanics

Which changes can move the fee?

Separate contracted escalation from genuinely new modules, tenants, or operating complexity.

Inputs: CPI cap · term · planned scope

Ownership and exit

Which strategic choices remain open?

Evaluate portability, transition support, and negotiated source-code rights before they become urgent.

Inputs: rights · support · accounting policy

The decision standard: every future event that can change price, scope, or control should be visible before signature.

Build the commercial model

Accounting treatment depends on transaction structure and organizational policy; validate capitalization and EBITDA effects with your finance advisors.

QUESTIONS FINANCE TEAMS ASK

Answers to the Questions CFOs Always Ask

What triggers a fee increase?

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.

What is not included?

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.

How does source code pricing work?

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.

What happens at renewal?

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.

What is the exit process?

Data portability is contractually guaranteed. Your member data, transaction history, and program configuration remain yours, and migration support is available. When source code is purchased, continued operation follows the use rights, transition structure, and support terms defined in the negotiated agreement.

Build a Defensible Commercial Case

Model cost across your evaluation horizon using your current platform, expected growth, capability roadmap, and ownership requirements. Leave with assumptions finance can inspect—not a generic license comparison.

  • Build a Commercial Cost Model

    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.

    Build Your Cost Model

  • Discuss the Commercial Structure

    If you're in an active evaluation or operational independence is a priority, review the fixed-fee proposal, source-code purchase option, support terms, and transition structure with Tricycle's commercial team.

    Start a Commercial Evaluation