As Featured in Forbes Kazakhstan: How PanDev Metrics Helps CTOs See What Actually Happens in Development
Forbes Kazakhstan dedicated pages 104–107 of their April 2026 issue to engineering intelligence — and to PanDev Metrics specifically. The article, titled "Доверься «большому брату»" ("Trust the Big Brother"), explored how data-driven development management is gaining traction across Central Asia and beyond.
Rather than republishing the piece, we want to highlight the parts that matter most: what our clients actually said, what the numbers show, and where the industry is heading.
What CTOs Are Saying
The Forbes article featured interviews with two CTOs currently using PanDev Metrics. Their feedback captures what we hear most often — the platform works because it measures processes, not people.
"As a CTO and for our tech leads, it's important to see not individual employees but the state of the development process: where it's efficient and where it breaks down. For this you need transparent metrics and convenient tools. The product allows natively collecting metrics right from the IDE, without feeling controlled or surveilled. Implementation was very simple — the main challenge was correctly communicating the tool's value to the team."
— Maksim Popov, CTO, ABR Tech
"The main thing that stands out about the team is their responsiveness and client orientation. If questions or bugs arise, the team reacts quickly and promptly makes fixes. Our improvement requests are always heard and considered. The service continues to improve, there are growth areas in onboarding and metric collection."
— Rauan Bozabaev, CTO, Chocofood
Two different companies, two different scales — but a consistent theme: transparency without surveillance, and a team that listens.
Results by the Numbers
Forbes cited several data points from PanDev clients. Here's a summary:
| Metric | Impact |
|---|---|
| Developer productivity | +30% increase |
| Release quality | +25% improvement |
| Labor cost reduction (hourly pay model) | 25–30% savings |
| Overall development budget savings | 10–30% |
These aren't projections. They come from real pilots across ~40 companies, including Biometric, Neo Code, Parqour, Zeely, ABR Tech, and Chocofood.
The "Whoop for Developers" Analogy
One comparison from the article stuck with us. Forbes drew a parallel between PanDev and fitness trackers like Whoop and Garmin — devices that don't tell athletes what to do, but give them the data to make better decisions.
The same principle applies here: a developer can evaluate how productively they work, identify patterns, and improve on their own terms. Management gets process-level visibility. Nobody gets a surveillance camera pointed at their screen.
AI Transparency: A Real Problem, A Real Solution
The article highlighted a telling data point: within the same team, one developer writes 30% of their code with AI, while another writes 70%. Without visibility into this, a CTO has no way to assess actual skill levels, code ownership risks, or where AI-generated code might need extra review.
PanDev also includes anti-fraud protection — the system detects when developers attempt to game their metrics. This isn't about catching people; it's about ensuring the data teams rely on for decisions is trustworthy.
Company Snapshot
For those unfamiliar with PanDev, here's where things stand as of April 2026:
- Founders: Artur Pan (CTO, former early engineer at Kaspi Marketplace) and Madiyar Bakbergenov (CEO)
- Investment: $400K at a $5M valuation from MA7 Ventures, MOST Accelerator Fund, and Axiom Capital
- Next round: Planning $15–20M
- Clients in pilot: ~40 companies
- Revenue (YTD from start of 2026): $8,000
Pricing
| Team Size | Monthly Price |
|---|---|
| Up to 20 engineers | $300/mo |
| 20–50 engineers | $700/mo |
| 50–100 engineers | $1,500/mo |
What This Means
Being featured in Forbes Kazakhstan is a milestone, but it's not the point. The point is that engineering leaders across the region are actively looking for better ways to understand their development processes — and the old methods (gut feeling, lines of code, story points) aren't cutting it anymore.
If you're a CTO or VP of Engineering dealing with the same questions Maksim and Rauan described — where does time go, where do processes break, how do you measure without micromanaging — we'd like to show you what we've built.