Economy & ownership
Connect currencies, inventory and catalogs with the items a player owns.
Progression
Connect what players earn, own and unlock.
A proposed Progression Solution for the systems that turn rewards and inventory into lasting player progress.
An idea under exploration. Scope and timing are undecided.
Is it a fit?
A starting point for your project.
For games that need economy, inventory, rewards and unlocks to work together as one progression loop.
Concept — not available
Before you plan around it
Concept. A complete player workflow and the boundary shared with Commerce and Retention still need verification.
Planned product scope
What it aims to bring together.
Candidate capabilities, subject to release verification.
Rewards & unlocks
Coordinate rewards, loot and unlock conditions with progression.
Persistent progress
Bring persistence and analytics into the planned progression workflow.
Know the boundaries
Scope & compatibility.
Review the intended installation and the evidence still needed before release.
Shared scope with other Solutions
Progression may be adopted independently or supply shared capabilities beneath Commerce and Retention. Final inclusion must define a complete use case and avoid charging separately for required hidden dependencies.
Providers & persistence
Account, analytics and backend choices depend on the intended configuration. Supported versions and end-to-end persistence behavior are not verified by this preview.
Game-specific rules
Your reward structure, unlock conditions and economy remain design inputs. Adapting those rules and existing player data requires a separately scoped implementation.
Product evidence
Demonstrations to come.
A representative progression and inventory sample still needs to be identified and verified. No product demonstration is published here yet.
Availability & working together
The product. Help when you need it.
Concept — not available. Scope and timing are undecided. Software licensing and project services are separate offers.
Software · Concept
Progression software license
A proposed Solution license would include its required shared dependencies. Final product inclusion, support terms and a purchase destination are not published yet. Project implementation is a separate engagement.
Ask about the productSeparately scoped services
Progression Integration
Discuss how your economy, inventory and reward rules should connect, then establish the configuration, data work and acceptance tests needed for integration.
Discuss progression integrationCompare service options & how we work together
Software licensing and project implementation are separate offers. Product-based setup and integration depend on a verified release and supported configuration; a concept page does not establish availability.
How working together works.
Start with a conversation
Describe the outcome you need. A short free fit call establishes whether the work is a fit; detailed investigation belongs in discovery.
Define the work
Where the requirements are uncertain, paid discovery produces findings, risks and a recommended path. Before delivery, we agree on inputs, deliverables, exclusions and acceptance checks.
Build, test and hand over
I deliver against the agreed scope and hand over documentation, test results and known limitations. Ongoing support is a separate agreement.
A direct line to the developer
Tell me what you're building.
Interested in the Progression concept? Describe the problem you'd want it to solve. This is an expression of interest, not a preorder or a release commitment.
