Why a flower
didaflowers turns that daisy around. Ours doesn't take a petal from you — it gives you one. Each petal is evidence, drawn from your own enrolments, exams, and graduate careers: one clear answer, traceable to where it grew from.
Pluck a daisy, pull the petals one by one — loves me, loves me not — and let the last one decide. A coin toss dressed as a flower. Universities settle real decisions much the same way: which course to grow, which cohort to rescue, which intervention to fund — left to instinct and the petal that falls last.
didaflowers turns that daisy around. Ours doesn't take a petal from you — it gives you one. Each petal is evidence, drawn from your own enrolments, exams, and graduate careers: one clear answer, traceable to where it grew from.
We started in 2025 in Bologna, inside the University of Bologna research ecosystem — founded by academics tired of watching good institutions decide by feel. The rigour they demand of research, finally turned on the institution.
Didaflow watches each cohort through three Outcome lenses — each tied to ANVUR indicators you already report on. Drill into one, and the others stay in context.
Are applicants showing up — and from where? Track demand across regions, school types, and entry channels.
Are students moving through the program on plan? Spot bottleneck exams before they show up in dropout numbers.
Where do graduates land — and how fast? Connect outcomes back to program design, not just graduation rate.
Three steps. No data-science team required — though if you have one, they'll appreciate the audit trail.
ESSE3, U-GOV, surveys, AlmaLaurea exports — drop CSVs or wire APIs. Didaflow handles the join.
Has the program lost its appeal? Studio answers with charts, sources, and a confidence band — in any EU language.
Test what-if scenarios. Compare baseline outcomes with simulated policy changes — then export the report.
30-minute walkthrough with a Didaflow researcher. Bring a real question — we'll use your data shape to show how Studio would answer it.