Case study — Iterpro
After the MVP: how Iterpro went from 2 people to 200+ customers and an exit
As co-founder and CTO, I built Iterpro — a B2B SaaS for professional sports clubs — from the first commit to the company’s acquisition in 2025. This is the story of what happened after the MVP: product, team, delivery and infrastructure, growing alongside the customer base.
The challenge
In 2017, Iterpro was an idea: no infrastructure, no team, no customers. Building the MVP was the easy part. The hard part came next: turning it into a reliable product for an industry — professional sports — where downtime during the season isn’t negotiable, while customers, team and requests were all growing at once.
Product
With the first customers, the backlog turned into a Slack thread and a spreadsheet nobody trusted: every request arrived as “urgent”. I introduced a lightweight validation filter — usage data, affected segments, revenue impact, cost of not doing it — that every request had to pass before touching the roadmap. Within two months, half of the “urgent” requests disappeared on their own, and the rest got prioritised faster than ever, because everyone finally agreed on why.
Engineering & team
The engineering team grew from 2 to 10 people over the years. Every stage of growth meant redefining process and ownership — not once, but continuously: what worked with 2 people didn’t work with 6, and what worked with 6 didn’t work with 10. The real challenge was never hiring — it was evolving organisation and skills at the same pace as the product.
QA & delivery
Early on we worked in 4-week sprints with scheduled releases — a fitting pace for a young product. As product and team matured, we moved to 2-week sprints with independent, per-feature releases instead of batching everything at sprint end. The most concrete result: an 85% drop in regression bugs.
Cloud, security & operations
In professional sports, an outage mid-season is not an option. The infrastructure grew on Azure and AWS side by side, with serverless workloads on AWS Lambda and always-on services on Azure; Datadog and Sentry give continuous visibility into errors and performance, Mixpanel into user behaviour. Working with top-tier clubs and federations also demanded a matching security posture: Iterpro is currently being audited for ISO 27001, with certification expected by the end of 2026.
The stack
Cloud & infrastructure
- Azure and AWS side by side
- AWS Lambda with CDK for serverless workloads
- Azure Functions and App Service for always-on services
Backend
- Node.js, with services built over time across Express, LoopBack v3, NestJS and Fastify
- MongoDB as the primary database
- Redis for caching and queues
Frontend & mobile
- Angular for the web product
- Flutter for the mobile app
Integrations
- Supabase Auth for authentication
- TalkJS for in-app messaging
- OneSignal for push notifications
- JSReport for report and document generation
Observability
- Datadog and Sentry for monitoring and error tracking
- Mixpanel for product behaviour analytics
The outcome
200+
enterprise customers
5,000+
active users
−85%
regression bugs after the delivery process change
In 2025 I managed Iterpro’s acquisition, also leading the integration of the acquiring company’s video editing and analysis system — keeping the engineering team, the product, and the organisation stable through the entire transition.
Clubs & federations
- AC Milan
- Bologna FC 1909
- SSC Napoli
- Al Qadsiah
- Torino FC
- Malta FA
- Benetton Rugby
- Gas Sales Bluenergy Volley Piacenza
This is the work I bring to post-seed startups as a Fractional CTO: structure for product, team, delivery and cloud, keeping pace with growth.
Book a free 30-minute call