EUREKA EXPRESS
Express is not a simulation. It is the configurable generator the Eureka simulations are built with: nine view templates, one adapter contract, nine interface languages and a governed quality lifecycle. The ready-to-run portfolio it produces is called Eureka Basics.
A simulation generator, not a simulation
An author picks one of nine view templates and configures it with a scenario, decision variables, scoring rules, a number of rounds and a competition switch. The result is one simulation that runs in a browser. Every short exercise a professor takes into class comes out of that same pipeline.
Nine view templates
Each template pairs an interface with its own logic layer and its own stylesheet. The library grows by following that same three-part pattern, so adding a new visual format never disturbs the simulations already published.
One adapter per simulation
The framework owns state, rounds, interface bindings and charts. The adapter owns the subject: the scenario, the model and the verdict. That division of labour is the whole product.
Two run modes
Hosted on the Eureka platform with teams, instructor dashboards, leaderboard and class analytics, or exported as a single self-contained HTML file that runs inside your own learning platform.
One definition per simulation
Scenario, interface, model, scoring and translations travel together in a single versioned definition, so a simulation can be reviewed, copied, localised or rebuilt without archaeology.
Express is how we build; Basics is what you license
Two different things share a family name, so it is worth being precise. Express is the engine and the method. Eureka Basics is the customer-facing portfolio of ready-to-run simulations that the engine produces.
The production engine and its method: the USF framework, the nine templates, the standalone export and the build cycle that turns a brief into a working simulation in weeks rather than months.
The ready-to-run portfolio produced with that engine, which is what an institution licenses and what a professor takes into a classroom next Tuesday.
Every catalogue figure and every coverage claim refers to Basics. The framework, the templates and the build cycle refer to Express.
The long tail a heavyweight platform cannot reach
Large simulation platforms are built around multi-week capstones: expensive, slow to set up and dependent on faculty facilitation. Whole programmes are left out, not because a simulation would not help them but because that kind of simulation does not fit. The engine exists to make the other kind economically possible.
A different unit of time
Built for short exercises that fit inside a single class session. The professor who needs something for next Tuesday is a different buyer from the one planning a six-week capstone.
Speed is the point
A new or reskinned simulation takes weeks, not months. That is what makes it viable to build one for a single syllabus, a single cohort or a single workshop instead of only for the mass market.
Subjects nobody serves
Sports management, hospitality, healthcare administration, public policy, non-profit management, real estate, tourism and sustainability: disciplines full of real decisions and almost empty of simulation coverage.
Regions nobody prices for
Price-sensitive programmes across Latin America, Southern Europe and Southeast Asia. The nine interface languages exist for exactly this reason.
A framework, an adapter, a view
The framework came out of refactoring one monolithic simulation into a generic layer and a domain layer. The generic layer never changes from one simulation to the next; the adapter is the only thing an author writes.
The framework
Generic, and identical in every simulation. It is the reason a new one never starts from zero.
- State and persistence
- Round progression
- Declarative interface bindings
- Charts and run history
The adapter
Written once per simulation. A single class implementing seven methods: the starting state, input validation, the round model, the run summary, the closing message, every player-facing string and the interface wiring.
The view and the session
Shared. The player shell that renders the simulation, and everything an instructor needs around it.
- Template and stylesheet
- Unified player dashboard
- Leaderboard and class analytics
- Standalone HTML export
Why that split matters to you
Because it is what makes a bespoke simulation affordable. Commissioning one does not mean commissioning a piece of software: the platform, the dashboards, the analytics and the languages already exist. What gets written is the part that is genuinely yours, which is the scenario, the numbers and the debrief.
Specification before code, every time
The build process is specification-driven, and its rule is stated plainly: never skip a step. What comes out the other end is a working simulation with its scenario, its model, its interface and its debrief already in place.
Specification
What the exercise teaches and why, its acceptance criteria (functional, educational and experiential), its constraints and assumptions, plus one worked example scenario.
Plan and tasks
Architecture, state, interface and data model, broken into a tracked task list covering calculations, bindings, charts, validation, round progression, scoring and documentation.
Implementation
The adapter and the view template, written against the framework contract, with the styling kept in a stylesheet of its own so nothing leaks into shared code.
Testing
Unit and integration tests, a complete play-through, save and resume, responsiveness and accessibility, extreme values and user errors.
Release
Registered, deployed and verified on a development environment before production, with a rollback plan in hand and a launch checklist signed off.
Two ways to run a session
Every simulation supports individual play and real-time team competition. Switching between them is a session setting, not a different product.
Individual mode
Each participant plays at their own pace. Progress is saved automatically, so a session can be closed and picked up again on any device.
- Round-by-round progress at each participant's own speed
- Immediate feedback after every decision
- Instructor dashboard with live progress for each participant
Team competition
Teams decide together and the instructor controls the pace, advancing the round when the room is ready.
- Teams discuss and submit one decision per round
- Live leaderboard with rankings, scores and round-by-round evolution
- The instructor advances rounds and owns the rhythm of the class
Three ways teams can compete
Each model produces a radically different session, because each one changes what a team has to pay attention to.
-
1
Scoring race
Whoever manages best winsTeams play independently and are ranked on their own performance. No team can damage another; all the pressure comes from the scoreboard.
Financial management, operations, supply chain -
2
Market competition
Competing for the same customersTeams compete for market share through price and commercial effort. Demand is distributed according to each team's offer relative to the others, so every decision is read against the competition.
Marketing strategy, pricing, competitive dynamics -
3
Shared resource
Tragedy of the commonsTeams draw from one common pool. Moderate extraction lets it recover; collective over-extraction depletes it and every team's revenue falls with it.
Sustainability, business ethics, environmental management
A grade you can defend in front of the class
How a simulation scores is not left to each author's taste. It is a contract every simulation on the platform has to satisfy.
A score every round, out of 100
The composite score is computed and stored at the close of every round, on a scale of 0 to 100. The value recorded in the final round is the authoritative grade.
Deterministic and bounded
The same decisions produce the same score. The value is clamped inside the simulation itself, so a run can never report a number outside the scale.
The number has to agree with the verdict
Where a simulation tracks disqualifying outcomes, the score is capped on them. A run described as value-destroying cannot reach the gradebook carrying a high mark.
A debrief, localised
A score out of 100, a verdict in the participant's own language, a short strip of key indicators and the list of takeaways, with the stable identifier kept separate from the displayed label so analytics compares like with like across languages.
Nine languages in the interface, two in the contract
The broadest language coverage of any module in the Eureka portfolio, and a precise commitment about what that number does and does not cover.
Nine interface languages
Catalan, German, English, Spanish, Basque, French, Italian, Portuguese and Chinese. Navigation, buttons, waiting screens, leaderboard and analytics labels.
English and Spanish content, always
Briefings, scenarios, verdicts, chart legends and takeaways, which is the substantive text, are authored in English and Spanish with full parity and never hardcoded into the interface.
Switching language in the middle of a session re-renders the content, not just the interface around it.
Nothing reaches a classroom without passing the loop
A simulation moves through a governed lifecycle one stage at a time and cannot be marked customer-facing until every stage is signed off. Once it is, content edits are rejected rather than quietly accepted.
The random player
Plays a full run making arbitrary choices, to prove the simulation survives anything a participant can do to it.
The subject expert
Reads the model the way a professor would: are the trade-offs real, is the top tier reachable, does a careless run score like a careless run?
The student
Takes the learner's point of view: is the briefing clear, is the feedback useful, does the debrief explain what just happened?
Any change applied at scale has to be proven behaviour-preserving before it ships: the original and the edited simulation are driven through dozens of seeded decision profiles and compared round by round.
Built for educators and training teams
The same engine serves a first-year lecture hall and an executive workshop, because the format is scoped to the session rather than to the market.
Universities and business schools
Simulations aligned with a specific syllabus, running inside the learning platform the institution already uses.
Corporate learning teams
Onboarding, leadership development and process training built around the decisions your own organisation actually faces.
Consulting firms
Proprietary simulations that bring a methodology to life in a client workshop instead of describing it on a slide.
Training providers
Programmes differentiated by simulations competitors do not have, with white-label options available.
Eureka Express at a glance
The essentials, in one place, for proposals, briefings and quick reference.
Simple, Transparent Pricing
One simulation or a full institutional catalog — we have an option for you.
Custom Build
One simulation, built for your curriculum
- Custom simulation development
- 1-week delivery timeline
- Individual and Team Competition modes
- Instructor dashboard and analytics
- Hosted on Eureka Cloud
- 3 months support
+ Usage-based licensing per active student
Institutional
Full catalog access and custom builds included
Requires €25,000 license commitment
- Everything in Custom Build
- FREE development (save €5,000)
- Access to the full simulation catalog
- Priority delivery and dedicated account manager
- Advanced analytics dashboard
- 12 months premium support
Best value for 1000+ users
Frequent questions
Express is the engine. What you run with your students is a simulation produced by it: the Eureka Basics portfolio, or one built for your own course. The distinction matters when you read a proposal, because coverage figures refer to the catalogue while the templates and the build cycle refer to the engine.
Anything from a ten to thirty minute exercise that opens a class, to a full ninety-minute session of five rounds with four to eight decisions in each. The format is chosen when the simulation is scoped, and it is one of the first things a bespoke build settles.
Yes. Every simulation can be exported as a single self-contained HTML file that runs on your own infrastructure, alongside the hosted mode with teams, instructor dashboards, leaderboard and class analytics.
Scoring race ranks teams on their own performance with no interaction between them. Market competition distributes demand between teams according to price and commercial effort. Shared resource puts every team on one pool, where collective over-extraction depletes it for everyone.
That is what the engine is for. A brief becomes a working simulation in weeks rather than months, because the platform, the dashboards, the analytics and the languages already exist. What gets written is your scenario, your model and your debrief. Tell us about the course and we will scope it with you.
Let us talk about your programme
Tell us about the course, the cohort and the session you have in mind, and we will tell you what fits, whether from the catalogue or built for you.
General enquiries
info@eurekasimulations.comPhone
(+34) 688 953 242Technical support
tech@eurekasimulations.comReady to get started?
Put a simulation in your next session
Request a demo and we will show you the engine, the portfolio, and what a build for your own course would look like.