02Experience / Web3Mi S.r.l.
A ticket-price panel, a traceable evidence base, and the cost-budget template adopted for the 2027 cycle.
The mandate
Finance and data work for the company behind Milano Blockchain Week, formerly ETHMilan. Scattered sources in, a defensible evidence base out. Method first, numbers second.
Placeholder values. Real figures pending selection.
What a booking curve says
Demand does not arrive evenly. It arrives in phases, and the phases repeat across editions. Indexed to peak: the shape is the finding.
- 2023
- 2024
- 2025
- 2026
Fig. 1. Cumulative demand by edition, indexed (peak = 100). Demonstration data.
Source: synthetic placeholder · Method: index to edition peak · Limit: not real data
How the work is done
- 01
Derive, never trust
Every ingredient is reconstructed from source. An inherited number with no derivation is not evidence, it is a rumour with a decimal point.
- 02
Verify with a different tool
What is computed in one language is recomputed in another. If the two disagree, both are wrong until proven otherwise.
- 03
Separate observed from estimated
Commercial value is not revenue. A platform timestamp is not a payment date. Null is not zero.
- 04
Publish the limits
Every deliverable ships with what it cannot support. Stating the boundary is what makes the claim inside it usable.
Case studies
Each follows five beats: problem, contribution, method, result and limits.
Booking curves, four editions
Daily ticket demand reconstructed across four editions, decomposed into phases and cross-read against marketing pressure.
OpenFrom scattered sources to an evidence base
Deliverables built on traceable lineage, explicit date semantics and a controls layer. Architecture, not answers.
OpenBudget structure and the BvA bridge
A category taxonomy, a template people actually fill in, and a bridge from plan to actual to variance.
Open