About
Founder-led software judgment, backed by product management discipline.
Zubkov Systems helps founders and teams turn software ideas, delivery problems, manual workflows, automation needs, and integration decisions into clearer plans and maintainable implementation.
Ilya Zubkov
Founder, Zubkov Systems
Founder profile
One person connecting business intent, software scope, and delivery reality.
Ilya's background spans software development, technical project management, product ownership, and product management. That progression creates a practical view of what software should be built, how it should be scoped, and where delivery risk usually appears.
Ilya holds a master's degree in Software Engineering and a master's degree in Project Management. The combination supports Zubkov Systems' focus on connecting business outcomes, software scope, product discipline, delivery structure, and technical implementation.
Before founding Zubkov Systems, Ilya worked across hands-on development, technical delivery, and product leadership. He also co-founded Naratta, an AI-enabled meeting productivity startup focused on preparation, agendas, notes, and follow-up workflows around tools such as Google Meet and Google Calendar.
His startup ecosystem activity includes participation in Web Summit Lisbon. Zubkov Systems keeps the public positioning focused on verified founder background, practical service scope, and direct software outcomes.
Software
Hands-on development background for understanding implementation constraints.
Delivery
Technical project management experience for making ownership, risks, and progress visible.
Product
Product ownership and management experience for turning business goals into buildable scope.
Education
Master's degrees in Software Engineering and Project Management.
Working principles
How engagements are kept practical
The work is designed to reduce ambiguity before implementation and keep business value visible while software is being planned or delivered.
01
Start with the business result before discussing features.
02
Define the smallest useful software outcome before expanding scope.
03
Keep requirements, tradeoffs, and acceptance criteria visible.
04
Prefer maintainable delivery over impressive but fragile complexity.
Bring the business goal. Leave with a sharper software path.
Share the workflow, customer journey, MVP, automation, integration, or system you want to improve. You will get a direct founder-led conversation about business outcome, software scope, risks, options, and the next responsible move.