From Amsterdam to Armenia: SMM Hub and Juniper Networks discussed the next phase of developing technology and local expert capacity.
During a meeting in Amsterdam between representatives of SMMHub and Juniper Networks, discussions covered the implementation of current and future projects in Armenia, Juniper Networks' technological solutions, and the requirements of Armenian clients. They also addressed a topic extending beyond the scope of individual projects: the development of local technical expertise regarding Juniper solutions in Armenia.
Some business meetings are dedicated to a single, specific project.
There are meetings where pricing, delivery timelines, technical specifications, or upcoming projects are discussed.
However, there are also discussions that cover a much broader scope.
What can we create next?
What does the market actually need?
And what must be done today to build stronger technological capabilities for the future? On September 18, representatives from SMMHub LLC met with the Juniper Networks team at the company's Amsterdam office.
Representing SMMHub at the meeting were Lida Nalbandyan, Founder and CEO of SMMHub LLC, and Ara Sargsyan, Director of B2B Operations at SMMHub LLC.
Juniper Networks was represented by Ivan Iashagashvili, Senior Director for Central and Eastern Europe and the CIS; Irina Voblaya, Territory Account Manager; and Dmitry Zavelsky, Technical Engineer.
However, the most important aspect of this meeting was not its location.
Far more important was the subject of the discussion.
Not just today’s projects, but tomorrow’s opportunities.
A significant portion of the meeting was dedicated to current initiatives in Armenia and potential future projects.
Armenia’s technology market is growing. Organizational operations are increasingly dependent on the reliability, security, and scalability of their digital infrastructures.
Today, the network is no longer merely an infrastructure connecting devices.
It connects employees.
Applications.
Data centers.
Cloud environments.
Security systems.
Customers.
And, increasingly, AI systems and new digital services.
This means that infrastructure decisions made today can impact an organization's technological capabilities for years to come.
Therefore, for an IT integrator, the question cannot be limited to just the following:
"What equipment does the client need?"
It is far more important to understand:
"What does the client want to build, and what infrastructure is required to ensure it operates reliably—not just today, but in the future?"
It was from this perspective that the meeting addressed both current capabilities and the prospects for implementing future projects with clients in Armenia.
Technology is important. However, it is even more important to understand where it creates real value.
A specific part of the meeting was dedicated to Juniper Networks' solution portfolio and its technological capabilities.
Discussions covered the architectural features, capabilities, and distinguishing characteristics of Juniper’s technologies, as well as their market positioning—particularly in a landscape where enterprise clients can choose from solutions offered by various global manufacturers.
And that choice matters.
The client needs to compare options.
They need to ask tough questions. Evaluate the architecture.
Performance.
Scalability.
Security.
Management capabilities.
Technical support.
The solution's entire lifecycle.
Total cost of ownership.
At the same time, the integrator's role is not merely to explain what a given manufacturer offers.
It is also necessary to answer far more important questions:
Why this specific architecture?
What are its technological features?
For which environments and tasks is it best suited?
How does it change things for the client from an operational perspective?
And it is equally important to understand:
in which situations a different approach might be more appropriate.
Because mature IT integration does not mean proposing the same technology for every project.
It means understanding where a specific technology creates real value for the client.
But one part of the discussion was more important than the individual products themselves.
Hardware can be supplied.
Software can be licensed.
Technology can be purchased.
However, expert knowledge cannot simply be delivered in a box along with the hardware.
And this became one of the key topics of our meeting.
As more complex and modern technological infrastructures are created in Armenia, there is a need for specialists capable of designing, implementing, operating, and further developing them.
Even the most state-of-the-art technological platform cannot fully realize its potential without specialists who deeply understand how it works.
For this reason, special attention was paid to the training of technical specialists in Armenia and the further development of expertise regarding Juniper Networks solutions.
How can we help engineers gain a deeper understanding of Juniper’s solutions? How can knowledge regarding the underlying architecture be developed?
How can the professional skills necessary not only for installing the equipment but also for fully understanding the technology be cultivated?
And how can the development of local technical expertise contribute to the more active and professional promotion and implementation of Juniper Networks solutions in the Armenian market?
These questions are truly important.
Because a technology market does not mature simply when more technologies become available within it.
It matures when knowledge about those technologies becomes local.
A vendor may be global, but expert capabilities must exist locally as well.
Let’s imagine two markets.
In both, the same technologies are available to customers.
The same equipment.
The same licenses. The same software.
Technical support from the same manufacturer.
On paper, the technological capabilities of the two markets might appear identical.
However, the first market has engineers who possess a deep mastery of the technology.
They understand the architecture.
They are capable of designing it.
They have undergone appropriate training.
They have participated in real-world implementations.
They know what issues can arise.
They know how to diagnose and resolve them.
And they understand how the infrastructure should evolve alongside the client's business growth.
In the second market, the technology is available, but such expert capacity is limited.
These are, in effect, two different technological environments.Because the value of a technology is ultimately determined by more than just its capabilities.
It also depends on the organization's ability to properly implement and effectively utilize that technology.
This is particularly important in the context of corporate infrastructures.
You cannot simply buy a network, install it, and then forget about it.
It becomes part of the organization's operational foundation.
And that is precisely why local engineering capabilities are crucial.
The role of the IT integrator is also changing in this regard.
At one time, the IT reseller's business model could be quite straightforward.
The customer requests a product.
The partner obtains the price.
The order is placed.
The equipment is delivered.
The project concludes.
Enterprise IT has long since moved beyond the confines of that model.
Today, clients increasingly require a different level of collaboration. They need a partner capable of acting as a connecting link—
between the client and the technology,
between the local market and the global vendor,
between the business challenge and the technical architecture.
This is precisely the role SMMHub aims to develop.
For us, collaboration with a technology vendor should not be limited merely to accessing a product portfolio or securing commercial terms.
A strong partnership should, over time, create something far more valuable—
capabilities and professional expertise.
The ability to understand.
The ability to provide consultancy.
The ability to design.
The ability to implement.
The ability to provide support.
And, over time, the ability to build a stronger professional ecosystem around that technology. Why is technical expertise important for the customer?
From the customer's perspective, discussions about vendor ecosystems and the technical capabilities of partners can sometimes seem far removed from day-to-day business operations.
In reality, they are directly linked.
Consider an organization making a significant investment in its infrastructure.
That infrastructure might be used for five, seven, or even more years.
During that time, the company evolves.
The business grows.
New applications emerge.
Security requirements change.
Data traffic increases.
New offices and branches are connected.
Cloud environments become part of the overall architecture.
New services are introduced.
Therefore, the question is not merely whether the equipment will function on the day of installation.
The real question is different: "Who will understand this infrastructure three years down the line, when the business needs to modify or develop it further?"
That is precisely why the technical expertise built around a solution is sometimes just as important as the technology itself.
For Armenia, this is an issue of broader significance.
Armenia possesses strong technical potential.
However, talent alone is not enough to build a mature enterprise technology market.
What is needed is continuous access to modern architectures.
Vendor-led training.
Certification.
Real-world projects.
Practical experience.
Knowledge sharing.
Direct communication with technology manufacturers.
And opportunities for engineers to transition gradually from knowing specific products to gaining a deep understanding of comprehensive architectures. Every specialist who gains deeper expert knowledge expands the potential of the entire local market.
Every successfully executed project builds experience for the next one.
Every complex technical challenge solved by local specialists strengthens Armenia’s technology ecosystem.
That ecosystem is not built overnight.
Engineer by engineer. Project by project. Capability by capability.
The most valuable outcome of a technology partnership might not be the next order.
Orders are important.
Projects are important.
Commercial results are important.
Without them, there is no business.
Yet, the quality of a technology partnership can also be measured by another question:
What remains after the project concludes?
Has the client gained a more robust infrastructure?
Have the engineers acquired new knowledge?
Has the integrator become technically stronger?
Does the vendor have a better understanding of the local market's specifics?
Will it be possible to execute the next project at a higher level?
If the answer is yes, then the partnership has created far more than just the revenue from a single transaction.
It has created opportunities for the next project.
Amsterdam was the meeting point. The work continues in Armenia.
The meeting in Amsterdam with Juniper Networks’ Ivan Iashagashvili, Irina Voblaya, and Dmitry Zavelsky provided an opportunity to discuss ongoing projects.
However, the opportunity to look further ahead was even more important.
Towards future projects. Focusing on the requirements of Armenian clients.
Focusing on the opportunities for applying Juniper Networks technologies in the Armenian market.
Focusing on the knowledge and skills specialists need to work with these technologies.
And focusing on how developing local technical expertise can foster further progress in this area within Armenia.
For SMMHub, this is precisely how a genuine technology partnership should evolve.
Not merely:
Vendor → Partner → Client.
But rather:
Global technology → Local expertise → Enhanced client capabilities.
Because bringing technology into the country is one thing.
Cultivating the knowledge and skills required to apply that technology correctly is something else entirely.
And in the long run, the latter may be even more important than the former.
Amsterdam was the meeting place. And the next chapter continues in Armenia.
