Power Automate flows, Canvas Apps, Model-driven Apps and Power BI dashboards put into production for clients.
The impact of our projects, in data.
Aggregated metrics from every project the Yottaflow team has worked on, including before the company was founded. Each indicator shows its source and calculation method.
Basis: all of the team’s projects | basis declared in October 2026The numbers that matter
Aggregated data from the team’s whole track record. Every KPI is tied to a business decision, and what we measure matters more than the absolute value.
The total monthly hours that client operations stopped spending on manual work after our deliveries, in the projects with before-and-after measurement.
Companies served by the team across all projects, whether implementation, enhancement or support.
Satisfaction survey at the end of the delivery, in the projects where the survey was run. Basis: sponsors who responded.
Why count all of the team’s projects? The numbers add up the projects the team has worked on, including before Yottaflow, because that experience goes into every delivery. The count is reviewed every quarter. Basis declared in: October 2026.
How we calculate each indicator
A number without a method says nothing. Here is the technical sheet for each KPI.
Solutions in production
We count every flow, app or dashboard that passed client acceptance and went into production. Discontinued pilots and proofs of concept do not count.
Time saved
Measured at project kickoff (baseline) and after 30 days in production (observation). We use real sampling from the client’s team, not theoretical estimates. We sum the gains in the projects where there was a before-and-after measurement.
Clients served
Companies served across all of the team’s projects, under any type of contract. We count distinct companies; economic groups are not inflated.
Average recommendation score
Standard question (“from 0 to 10, would you recommend our work?”) sent to the project sponsor after delivery, in the projects where the survey was run. Simple average of the responses received. The response rate is reported alongside the number, when requested.
Want to see how these projects are structured?
The portfolio shows examples for each delivery area, with context, challenge and solution.
View portfolio