IT industry · Yerevan · onboarding · team merchandise and AMD budgets
In Yerevan's IT sector, merchandise sits inside the ordinary procurement list rather than beside it. That sounds like a footnote and it is not. The merchandise is bought to a different timetable and to different standards from everything else a technology company produces, running from the week an engineer joins to the kit an engineer carries to a conference. This page covers why the standard corporate order fails on technical teams, how an onboarding kit has to be timed against a sprint calendar rather than a season, what a support team changes about the budget case, and how to specify the order so that it is still working twelve months later.
Most IT companies in Yerevan have a corporate history, but a small headcount. That scale is the whole reason standard bulk group orders are not sufficient. In a small team every new engineer is a visible fraction of the team, and the team is aware of exactly one person who has to produce a result. The same holds across every technical group, where responsibility is spread across many teams and the entire allocation waits to be gathered from one side.
The second difference is the timetable. A new bank employee arrives in December or January, while a technology company frequently expands in the first half of the year, when the new programming season begins and new teams are gathered around new sprints. The kit has to be timed to both of those points, which requires more careful planning than a seasonal kit does.
This is where the most common mistake in the IT sector happens. The kit is prepared on a seasonal rhythm but requested for January to March, by which point all the new teams are already in work. In that window production either does not arrive, or it arrives and sits in storage, because the request is executed by the leaders of teams who were already established three months earlier. The primary explanation is not a management failure. It is a miscalculation of time.
A first-three-days kit covering the information the new engineer actually needs at the desk: a laptop sleeve or equivalent technical accessory, a notebook, and the access-provisioning sequence on a printed card that can be followed without asking.
For international conferences: multi-language information booklets, multi-device charging and a small phone pouch, specified so that the bag is filled before the trip rather than after it.
The most visible part of the team outside the office is the team itself, so remote work gets its own quality line: a hooded layer rather than the standard seasonal tee, produced in one run for a single remote team.
When a team joins close to incidents, the kit functions as an identity marker: not as advertising, but as a tool from which the programming work begins.
A technical team's working day starts around ten in the morning and ends around seven in the evening, with four interruptions and an unexpected timetable along the way. At that point production is unlikely to land, because the collective budget is already committed to headcount growth, software licences and infrastructure spend, and a specific request is usually dropped. The cleanest solution is a new budget line for engineers, held at the start of the budget, revisable at mid-year and directed at the items a general budget does not name: onboarding, monitoring, holiday events and business training.
The second view is retention. In technical teams a new member is often isolated in the first months by demands that are not shared by everyone. That is exactly where the most useful principle in the sector applies: representing marks win, discovery marks do not. When a company's technical identity is discussed, people are usually close to the small details that were made with use rather than with display in mind.
The disposal question is worth stating plainly: will the item be used, kept or discarded, and when. An order placed in the second week of December is not sufficient, because a short interval rarely is. If the collective budget is left unspent in the last quarter of the year, then most of the largest onboarding kit spend will go not to field stock but onto a creative department's desk, and the result is that a certain specific portion never reaches its intended user.
The advice most often missed is that the merchandise should be a tool rather than a prize. When new engineers have useful and understood tools, those tools occupy a single layer of explanation: they are connected to the company, and the responsibility numbers rise for a functional reason rather than a ceremonial one. An onboarding sweatshirt and a good pair of headphones help people learn the official addresses, an entry keycard produces an implausible identity, and the international communication conditions prepare official delegates in a matter of hours.
There is one further point that the IT sector should never skip. A technical company places an order and expects no exciting activity as a result. The merchandise produced for the support team, the sales department and the onboarding team matters in the merchandise market, but the difference between their requirements is worth identifying before the order is placed, not after it has arrived.
Most IT companies in Yerevan run a hybrid model, and that creates a separate approach to clothing. An employee who works mainly from home may spend part of a day in a service centre, on the metro or at a client's offices. Formal official clothing designed for an office loses its functional meaning. The workable answer is a second layer with a small official signature, adapted for remote working, produced in one run for a single more remote team.
The second weakness that remote employees run into is that their clothing is left without a top-up for two seasons. The result is that a team receives a single line of reorders at the door, an old garment for the new employee that either does not carry the current identity or still carries the previous team's marks. When that becomes the norm, it is presented as the result.
Nothing about this is comparable to the other cities of the country, because it is in the capital alone that most remote teams are concentrated. It creates two requirements: the same mark repeated for many staggered teams, and a stock condition that lets the same-size kit be divided over a year of use rather than half a stock around the office.
The third view in this sector is the support team. If a company has merchandise, it is distributed in the sales department, and the field team is staffed by people who have to talk about the company to customers on the phone. This is a difficult environment for merchandise: roughly half of what is produced ends up misplaced, because it is actually wrong to call a team working near a centralised sales desk a field team. Where appearance matters, the merchandise has to arrive with more attention and more identity applied than it does for a team that leaves the office once a week during a discovery review.
The figures below are typical category bands for this kind of order in the Armenian market, in AMD and excluding VAT. They describe standard production practice rather than a quotation, and they assume one specification and one decoration method per line. A conference kit and a remote hooded layer are different orders even when the print is identical, because the component list is what sets the price.
| Order line | Indicative AMD | What moves the number |
|---|---|---|
| Onboarding kit, per new engineer | 8 000 – 15 000 | Whether the kit carries a decorated garment at all, or is built around accessories and printed information |
| Cotton base tee, undecorated | 6 000 – 11 000 | Fabric weight, colour count and size distribution |
| Decorated hoodie, per piece | 17 000 – 27 000 | Material weight, decoration method and colour count against the design |
| Headphones, mid range | 14 000 – 30 000 | Noise-cancelling specification and warranty terms |
| Conference tenure kit, per person | 31 000 – 58 000 | Multi-language booklet print, number of devices charged and the quality of the pouch |
| Print preflight and physical proofing | 8 000 – 18 000 | Number of distinct components and whether a sample is approved before the run |
The single most useful line in that table is the contingency. Holding 20-30 percent of the kit budget back for teams that form after the initial run is what turns an onboarding programme from a one-off delivery into a standing capability. A company that planned fifty engineers and hired sixty has a solvable problem. A company that planned fifty, hired fifty-eight and spent the entire budget in March has an unsolvable one, because the extra eight engineers are the ones who spend their first quarter without any marker of belonging.
Work is distributed on roughly the same scale across the day and the cycle. Nights carry the load of the day's work while teams review their own results at the end of the day. If a kit is distributed by branch, where the strong systems are, teams receive it as a single percentage share of the review, and at the end of the cycle it turns out that this percentage was real. In most technology companies the decision is not stable, and the reason is not a known rule but distrust and an argumentative process. A consistent decision without absorbing it into the budget has to be directed at the middle financial management and agreed with the financial lead, so that a team is not judged on a quantity it was handed.
Technical merchandise has to stay in use, if not for one reason. It most often operates away from home rather than from the office, so items translated into Armenian that do not depend on a single side of the coin matter, and for tool preservation there are separate pendants that do not rest against the edge of the device during a long charging period. The third is the technical sub-layer: size, load and a hooded model that allows work to continue through a cycle without seasonal words. Choosing between variants is not a matter of picking the option the night shift uses most, but of choosing so that the field share remains sufficient and does not at the same time look short.
It is planned as two specifications rather than one, which is what most technology companies in this market discover only after the first delivery. The office layer carries the full mark and the full set of references, because it is seen by people who do not know the company. The remote layer carries a reduced mark on a garment chosen for movement and camera visibility rather than for a meeting room. Both are specified against the same size curve so that stock does not fragment, and both are produced from a shared print file so that the colour match between the two layers is exact. Where one specification is used for both, the result is either an office garment that reads as casual on camera or a remote garment that reads as over-dressed in a client meeting.
No. Corp-Merch is an independent B2B merchandise supplier. Every technology company, conference, event format and institution referenced on this page is named as descriptive context for the planning argument only. None of them has appointed, endorsed, sponsored or authorised Corp-Merch to produce merchandise on its behalf, and no relationship, capacity or official status is claimed between this supplier and any of them. No trademark is claimed as owned by Corp-Merch.
This page sets out general planning principles for merchandise orders in the IT and technology sector in Yerevan. Corp-Merch is an independent B2B merchandise supplier and is not a partner, sponsor or authorised representative of any technology company, conference, association or institution referenced here. The AMD figures shown are typical category bands drawn from standard production practice rather than from a quotation; they exclude VAT, assume one specification and one decoration method, and will move with component selection, print complexity, quantity, artwork, packing, delivery windows and the number of distribution points. The seasonal timing described reflects a general planning pattern rather than a fixed market calendar. Every order is quoted individually against a written specification, and nothing on this page is a binding price.