Programme playbook · Internal rollout
Launching an internal merch programme at an Armenian company
A working rollout for an internal merch programme — the communications sequence that earns employees' attention, the request path that doesn't bottleneck on a single approver, the brand-versus-personal-preference tension and the 60/90/180-day adoption plan that makes the programme measurable from week one.
Why an internal launch is harder than it looks
An internal merch programme is sold to the people who are also paying for it. The programme has one audience — employees — and that audience already has opinions about the brand, the HR process and the request path before the launch email goes out. A programme that does not anticipate that collective opinion will underperform in the first quarter and the eventual failure will be attributed to "merch apathy" rather than to a launch that asked for sign-up before it earned trust.
The launch that works in Armenian workplaces treats the rollout as a change-management exercise, not a procurement exercise. Communications matter more than the kit in the first month. The kit matters more than the communications from month three onwards. Skip the first month and the kit never gets worn. Skip the kit and the communications lose their anchor. Plan for both.
The four moving parts of a working internal launch
Communications sequence before day one
A three-touch sequence sent in the two weeks before sign-up opens: one short note from the CEO or country lead naming the programme and why it exists, one note from HR or internal comms naming the request path and the timeline, and one kit preview image with no prose. The kit preview is the load-bearing message — by the time the request form opens, the employee already knows what the items look like. Forms sent without an image produce vague requests and high churn.
Request path that does not bottleneck on one approver
The classic failure is every request routed to a single brand or HR approver, who becomes a queue and a delay and the visible face of friction. The working model for a 50–500 person Armenian company is one approver per department, a two-touch form (item + size + delivery address) and a 5-working-day decision SLA communicated in advance. Programmes that promise a faster SLA but routinely miss it produce more friction than programmes with a slower SLA they consistently hit.
Brand choice vs personal preference, named honestly
The tension that every internal programme wrestles with is what is fixed by the brand versus what the employee can choose. The honest answer in a working Armenian programme is to fix the colour, the artwork and the placement, and to let the employee choose the item type and the size. Trying to let employees customise artwork produces a programme that has no brand. Refusing to let employees choose size produces a programme that no one wears.
First-quarter adoption measurement
Adoption is a percentage, not a count. The metric is the share of eligible employees who have requested at least one item by the end of Q1, against the eligible headcount at the start of the quarter. Working adoption for a programme that has earned its launch lands between 55% and 75% by day 90. Below 45% and the programme is failing; above 80% and the brand will start to read as over-distributed. Both ends of the range deserve a Q2 conversation.
The 60/90/180-day plan, with what each phase measures
The plan runs in three phases, each with one decision point at the end. The decision points are not optional — they are how the programme gets corrected mid-flight instead of waiting for the year-end review.
Days 1–60 are the launch phase. The work is the three-touch communications, the request path going live, the first round of items shipping and the first wave of adoption signal. The metric at day 60 is request-fill rate against capacity, plus a count of which items got requested. The decision is whether the kit needs an early refresh — usually because one item unexpectedly over-performs and another under-performs.
Days 61–90 are the adoption phase. The work is the round-two communications, the resolution of request-path friction and the first re-stock if any item ran short. The metric at day 90 is the share of eligible employees who have made at least one request, plus the share who have worn their first piece visibly. Visibility is the harder signal to track but the better signal to follow. The decision at day 90 is whether the brand-versus-personal-preference split is working, or whether the rules need an amendment.
Days 91–180 are the consolidation phase. The work is the second kit drop, the second wave of request fulfilment and the cross-department redistribution if any team is sitting on surplus. The metric at day 180 is repeat-request rate per employee, plus the share of the original kit still in daily wear. The decision is whether to extend the programme into a permanent catalogue rather than a one-off launch, which is what a healthy internal programme graduates into.
What "personal preference" actually looks like in a working form
The request form is where personal preference lives or dies. A working form has between four and seven fields: full name, department, item selection, size, delivery address, and an optional comment box. Anything longer produces drop-off. Anything shorter misses the data needed to fulfil the order correctly. The comment box is the pressure release — most of the brand-versus-preference conversations happen there, and the comment box is the place where the brand-side decision gets explained back to the employee by the approver.
The form should not let the employee choose artwork. Any programme that lets the employee upload a logo or a custom graphic has stopped being a brand programme and become a print-on-demand service. The form should not let the employee pick a colour outside the brand palette. The form should let the employee pick the item type, the size and, where physically meaningful, a small material choice (cotton vs cotton-blend, glass vs ceramic). Beyond that, the brand decides.
Buying the kit against a budget that holds up
The internal merch budget for an Armenian mid-sized company is typically set as AMD per employee per year, between 28,000 and 75,000 AMD depending on the brand tier. Below 28,000 the kit reads as thin and the adoption drops. Above 75,000 the kit reads as wasteful and finance reopens the conversation the next year. Within that range the programme is honestly funded and can be defended at a year-end review.
The kit should not be ordered all at once at the start of the year. Order in two waves — one to fulfil the launch demand, one to fulfil the consolidation phase — and reconcile the surplus after wave one. Programmes that commit the full annual budget on day one absorb the inventory risk into the budget; programmes that commit in waves keep the inventory risk inside the production lead time, which is a much cheaper place to carry it.
Adoption measurement that survives an HR review
The single number an HR or finance counterpart will ask for is the adoption share. The number that actually matters and that the same counterpart will use at the year-end review is the wear-share — the share of employees who visibly wear their items in the office, in customer meetings, on events. Tracking wear is harder than tracking orders, but the gap between the two numbers is the story of the programme.
Track order-fill by week for the first 90 days, then by month thereafter. Track wear by casual observation, by the photo of the company's internal Slack or Teams channel, by the count of branded mugs in the kitchen, by the brand presence in customer meetings. The numbers are not perfect and they do not need to be perfect — they need to be honest. A 60% order share paired with a 35% wear share is a programme with a wear problem; the kit or the brand choice needs to change.
The brand-versus-personal tension, managed in advance
The single largest source of friction in any internal programme is the employee who wants something different from what the brand kit offers. There are three honest answers, and the programme should pick one and stick to it. The first answer: the brand chooses everything and the employee cannot customise. This works for small programmes where uniformity is the point. The second answer: the brand chooses the artwork and the colour, the employee chooses the item type and the size. This is the working default and is what the playbook above assumes.
The third answer: the brand offers two or three sub-kits (formal, casual, technical) and lets the employee pick the sub-kit rather than the item. This works for a larger company with genuinely different working environments — office, warehouse, field staff. Programmes that try to mix all three answers within the same audience produce internal confusion and a kit that nobody really wanted. Pick one, write it down in the programme brief, and refer back to the brief when the first negotiation arrives — because it always arrives.
Common launch failures seen in Armenian companies
Three failures recur often enough to be named. The first is sending the communications from HR without a senior voice in the sequence — the email is well-written, but the senior voice is missing and the programme reads as an HR initiative rather than a company one. The remedy is one of the three emails in the sequence must come from the CEO or country lead. The second failure is the request form that asks ten questions — the drop-off is silent and the programme looks under-adopted when the actual problem is the form.
The third failure is shipping the kit to people who have moved desks or departments without checking. Internal mobility in Armenian workplaces is high enough that the delivery list from the headcount at programme start is stale by month four. The remedy is a reconciliation against the headcount before each dispatch wave, not an annual headcount audit.
The distribution model: warehouse, hand-carry or office drop
How the kit reaches the employee is part of the launch design and the most common detail left to the warehouse team on the day of dispatch. Three models work in Armenian mid-sized companies. The first is central warehouse dispatch, where every employee receives their kit at a single office or their home address via courier. The second is hand-carry at a launch event, where the items are given out at a small in-office ceremony. The third is office drop, where each regional office receives a pallet and the office manager does the second-mile distribution.
Central warehouse dispatch is the cleanest audit trail and the highest per-item delivery cost. Hand-carry at a launch event is the most efficient model and the best brand moment, but only works for single-office Armenian companies. Office drop is the right answer for multi-site companies, but it requires a clear office-manager protocol and a reconciliation against what was supposed to reach each site. Pick the model in the brief, not at the warehouse on dispatch day.
Replacing kit as people join, move and leave
An Armenian mid-sized company in any given year sees 8–20% employee turnover, plus internal moves between departments and offices. The internal programme must replace items for new joiners, refresh items for movers whose old items carry the wrong department mark, and dispose of items for leavers in a way that respects the brand. Programmes that ignore this loop end the year with mismatched kit in circulation and a finance reconciliation that does not balance.
The practical model is a monthly reconciliation against the headcount, with a small standing reorder that does not need full programme governance to be triggered. New joiners get a default kit from the standing stock. Movers get a replacement for items that are visibly department-marked. Leavers surrender branded items at exit, the items are inspected and either recycled internally, donated, or destroyed if the brand warrants it. The reconciliation is one tab on the master programme sheet and runs on the first of each month.
What changes when the programme goes permanent
A successful 180-day launch graduates into a permanent catalogue rather than a one-off. The shift from launch-mode to catalogue-mode changes the production model. Launches are large-batch and time-bound. Catalogues are small-batch and continuous, with a standing order quantity and a standing replenishment frequency. The transition is usually one quarter, and the production lead times get shorter because the catalogue is predictable.
The catalogue also introduces a retire-and-refresh cadence. Items are rotated out of the catalogue when they reach saturation or when the brand updates. The retire decision is more important than the launch decision because retire is what protects the brand from over-distribution. Plan the cadence before the programme becomes permanent, not after.
Planning timeline
- Pre-launch. Communications sequence drafted, kit preview images ordered, request form tested internally. Two weeks before sign-up opens.
- Days 1–60, launch phase. Communications go out, request form opens, first wave ships. Day-60 metric: request-fill rate. Decision: early refresh of the kit if any item over- or under-performs.
- Days 61–90, adoption phase. Round-two communications, friction resolved, first re-stock. Day-90 metric: share of eligible employees with a request. Decision: brand-versus-preference rules amended if friction is concentrated there.
- Days 91–180, consolidation phase. Second kit drop, second wave of fulfilment, cross-department redistribution. Day-180 metric: repeat-request rate and wear share. Decision: permanent catalogue or close the programme.
Frequently asked questions
What is a realistic adoption share for an internal merch programme in Armenia?
A working programme lands between 55% and 75% adoption by day 90, measured as the share of eligible employees with at least one request. Below 45% the launch has failed and the brief should be reviewed rather than the kit. Above 80% the brand starts to read as over-distributed; the Q2 conversation is to slow the cadence, not to keep pushing.
How should the request form be designed?
Four to seven fields: full name, department, item selection, size, delivery address, optional comment. Drop-off on forms past seven fields is high enough that the form becomes the bottleneck on adoption. The form should not let employees customise artwork or pick colours outside the brand palette.
What is a defensible per-employee annual budget in AMD?
A mid-sized Armenian company sits in a working range of 28,000–75,000 AMD per employee per year, depending on the brand tier and the chosen kit. Below 28,000 the kit reads thin. Above 75,000 the kit reads wasteful and the next-year conversation reopens. The kit should be ordered in two waves against the year, not on day one.
Is Corp-Merch a partner or official supplier of any Armenian company or association?
No. Corp-Merch is an independent production vendor operating in Yerevan and Vanadzor. We are not an official supplier or partner of any company named on this site, including any bank, telecom, hotel or industry association. Internal launch work is offered on standard commercial terms against the brief.
How is the brand-versus-personal-preference split decided?
The brand chooses the artwork, the colour palette and the placement. The employee chooses the item type and the size, and optionally a small material choice. Programmes that try to give employees control over artwork stop being brand programmes and become print-on-demand. Lock the split in the brief and refer back to it at the first negotiation.
This page is a working playbook for launching an internal merch programme inside an Armenian company. Budget ranges, adoption metrics and form-design rules are illustrative and depend on headcount, brand tier and the kind of working environment in question. Use the structure to design the launch and the 60/90/180-day plan, not as a procurement specification.