Programme playbook · Annual calendar
Customer-events merch programme in Armenia: the calendar playbook
A portfolio view of running merch at customer-facing events across a year in Armenia — which events deserve merch at all, how to tier them by value, where the annual budget splits and what measurement justifies the spend to a finance stakeholder.
What "customer-events programme" actually means
A customer-events programme is the year-long calendar of client-facing touchpoints at which a company shows up with merch, hospitality, speaking slots or panels, plus the budget and measurement that wrap around it. The merch is the visible artefact. The programme is the structure that decides which events make the calendar, which tier they sit in, and how the spend reconciles against pipeline.
In Armenia the working pattern is roughly 18–30 named customer-facing events per year for a mid-sized B2B brand, with a long tail of repeated smaller get-togethers. The programme design question is not "how much merch" — it is "which events deserve what, and which ones we politely decline". Most overspend in this category comes from attending events that do not earn their slot.
The four moving parts of a one-year programme
The event calendar as a working document
A spreadsheet the marketing and the sales lead update together, holding every named customer event on a single page with date, venue, tier, owner, expected footfall and budget. The calendar is reviewed quarterly. Events on the calendar in a year with no review fall out of the programme as budgets shift. Events that survive a year of reviews are the ones the programme is built around. Anything not on the calendar is opportunistic and is funded out of a separate discretionary pot.
Tiering events by value, not by spend
We tier Armenian customer events into three bands against pipeline contribution, not against how visible the event is. Tier one events get the headline kit, the dedicated staff, the lead-capture rig and the post-event follow-up cadence. Tier two events get a smaller kit and a lighter handover. Tier three events do not get merch, they get hospitality and a thank-you note. Splitting events by visibility inflates tier three into doing merch work it cannot afford; splitting by pipeline keeps the budget honest.
Annual budget split across tiers
The working split for a mid-sized Armenian B2B programme is roughly 60% of the merch budget on tier one events (4–6 of them), 30% on tier two (10–15 of them), and 10% retained for opportunistic tier-three work and the surprise flagship the calendar did not anticipate. The split is not a rule — it is a starting position that the quarterly review rebalances against the actual pipeline contribution.
The single metric that justifies the spend
The metric that holds up to a finance stakeholder is cost per qualified pipeline opportunity opened against an event, plus a 90-day cost per opportunity that reached opportunity stage. Vanity metrics like "leads captured" or "brand impressions" do not survive a finance review. Pipeline-attributed events earn their budget. Events that produce impressions and no pipeline either move down a tier or out of the programme at the next quarterly review.
Working event calendar for an Armenian B2B brand
A mid-sized B2B brand in Yerevan usually runs against a calendar that looks roughly like this in a year, before any one-off amendments: four tier-one flagship events (own-hosted, 150–400 guests each), ten to fifteen tier-two events (industry conferences, partner co-hosts, roundtable dinners), and an opportunistic tier-three layer of meetups and association gatherings. The tier-one events set the brand position. The tier-two events sustain the relationships through the year. The tier-three layer is where new territories are tested cheaply.
The trap is to under-budget tier one and over-populate tier three. Tier one is where the merch earns its keep because the audience is captured, the kit is anchored to the brand for the entire evening and the data-capture is real. Tier three without merch is often the cheaper, better answer than tier three with merch that does not get used. Discipline at the quarterly review is the difference.
Where Armenian venues actually fit into the tier structure
Yerevan Expo Centre is the working default for tier-one flagship events with 200–400 guests, because the hall configurations handle a 60–80% footfall ratio against registration without compromising circulation. Marriott Armenia halls work for tier-one roundtables and partner co-hosts at 80–150 guests, where the room scale and the catering line both reward the smaller format. The Yerevan Sports and Concert Complex is appropriate for tier-one consumer-facing moments with higher footfall, but is rarely the right room for a B2B customer-event programme.
Tier-two events move through partner offices, smaller hotels (Best Western, Ani Plaza, DoubleTree by Hilton), coworking spaces and the Tsaghkadzor Marriott for off-site retreats where the change of place is itself part of the hospitality. Tier-three events usually happen in a partner's office or a small bar with no fixed venue. The programme design should name the venue tier into the brief at the same time as the merch tier, because the two choices are coupled.
Own-hosted events versus attended events
A customer-events programme mixes own-hosted moments with attended industry conferences. The two formats have different economics. Own-hosted events cost more per event and return more per attendee because the brand controls the room, the script and the data capture. Attended events cost less per event because the venue and the audience are paid for by someone else, but the brand has to compete with every other sponsor for guest attention.
The split a healthy programme lands on is roughly 40% of the merch budget on own-hosted events and 60% on attended industry conferences, because most of the customer-facing touchpoints in any given year are at the latter. The split inverts for brands that are still building their own audience, where own-hosted events become the majority of touchpoints until the brand has an external pull.
The annual budget in AMD that the programme is sized against
A working programme for a mid-sized Armenian B2B brand sits between 28 and 65 million AMD per year, including merch production, venue fees, hospitality, staff and data-capture tooling. Below 28 million the programme is essentially tier two only and cannot sustain a tier-one flagship. Above 65 million the programme has crossed into territory where a dedicated event lead is justified rather than a marketing generalist.
The line items that surprise finance are the venue fees (much higher percentage of budget in Armenia than in some neighbouring markets), the staff cost (handover-staff agencies are common in Yerevan), and the inbound kit that has to be replaced because guests took it home. Each line should be budgeted separately rather than absorbed into a single merch number, or the reconciliation will fail every year.
What goes wrong and how to recover
Three failure modes recur in Armenian customer-event programmes. The first is calendar drift: events that no longer earn their slot remain on the calendar because the lead who owns them is leaving the company. The remedy is a quarterly review with a single decision-maker who can move events in and out. The second is tier inflation: every event on the calendar wants to be tier one because tier one gets the nice kit. The remedy is to set a cap on the number of tier-one events per year, fixed in advance, and to refuse exceptions.
The third is measurement drift: the programme justifies itself on leads captured in the first half of the year and on pipeline in the second half. The two metrics are not interchangeable. Pick one at the start of the year and run the entire year against it; changing the metric mid-year is how a programme loses finance credibility and the next year's budget.
The quarterly review that keeps the programme honest
The quarterly review is the meeting at which the calendar gets rebalanced. It is also the meeting most programmes skip, because nothing is on fire at the time it is scheduled. The structure that works: sixty minutes, one decision-maker present who can move events in and out of the calendar, four agenda items — pipeline contribution since the last review, kit reuse versus new kit, venue cost versus footfall, and one open decision to make for the next quarter.
The output is not a status update. It is a set of calendar moves: one event promoted, one demoted, one added, one cut. If the meeting does not produce calendar moves, it has been a status meeting and the programme will drift. The decision-maker in the room is what makes the difference between a productive review and a polite one.
Reconciling pipeline back to the event
Pipeline attribution at the event level is the part most Armenian programmes get wrong. The data captured at the event is the input. The credit for the resulting pipeline can only be assigned cleanly if the CRM tags the source as the specific event, not as a generic "event" source. Without that tagging, the programme cannot run the cost-per-opportunity arithmetic that finance asks for and the next year's budget becomes a hope rather than a defence.
Set the CRM tagging convention before the first event of the year. Tag every contact that comes through the event-handover consent point with the event-specific source, the date and the consent text used. Then the quarter-end roll-up is one query and a pivot, not a three-day project. Skipping this step is the most common reason programmes lose their finance credibility by Q3.
Year-end close and what it tells next year's design
The year-end close has three outputs: total spend by tier, total pipeline attributed to the programme, and the list of events that did not earn their slot. The last list is the input to the next year's calendar. Events that fall below the cost-per-opportunity threshold once should be flagged. Events that fall below twice should be cut from the calendar unless there is a strategic reason to hold them, and "we did it last year" is not a strategic reason.
The close is also where brand-level decisions land. Which kit components survived the year? Which got retired after one event because they did not carry the brand? Which were worn past their useful life and need replacing in the next programme? The kit-side close feeds back into the production brief for the year ahead, so the next January starts with a kit refresh instead of a kit discovery.
The people side of the programme
A customer-events programme is run by a small group of people: one calendar owner (usually the marketing lead), one production owner (the vendor relationship), one finance counterpart who signs the budget, and one sales counterpart who reconciles pipeline. Four roles, ideally one person each. Programmes that try to run with two of those roles collapsed into the same person produce decisions that nobody challenged, and the calendar drift starts within six months.
The vendor relationship deserves more attention than it usually gets. A vendor that knows the previous year's kit, the agreed production windows, the consent text and the venue mix is worth more than a per-event procurement. Programmes that re-tender the vendor every year lose institutional knowledge and pay for it in production lead times and reconciliation errors. Lock a multi-year vendor relationship with annual review clauses; the programme design benefits more than the unit cost would suggest.
Consent, data-capture and the Armenian legal backdrop
The legal backdrop for customer-events data capture in Armenia is the Law on Personal Data Protection and the subordinate acts that govern consent. The programme design must treat consent as a programme-level decision, not a per-event detail. That means a programme-wide consent template, a programme-wide retention policy, and a programme-wide right-to-withdrawal procedure. Anything less makes every event a separate legal micro-system and the programme as a whole unaccountable.
The cleanest pattern is a programme-level data-processing agreement with the vendor and the venue, a master consent text reviewed annually, and a per-event overlay that captures the specific event, the date and the staff member at the handover point. The data subject's right to withdraw consent has to be honoured within the Armenian statutory window, which is short. Programmes that treat consent as a marketing formality rather than a legal obligation tend to find out about the gap from a regulator, not from internal review.
Sustainability and what happens to leftover inventory across a year
Across a year, customer-event programmes in Armenia generate between 5% and 15% leftover inventory by piece count, depending on the tier discipline. The disposal path is the question the programme has to answer before the year starts, not at year-end when the boxes are stacked in a corner of the marketing office. Three disposal patterns work: internal employee issue (the items become company merch at lower visibility), donation to a registered Armenian non-profit, or recycling through textile or paper streams where the material allows.
Donation is the cleanest answer for branded apparel and accessories that are still in good condition, and there are several registered organisations in Yerevan that accept corporate merch for distribution. Programmes that treat leftover inventory as a logistical after-thought tend to bin it, which is the worst outcome for the brand and the worst optics for the marketing lead. The disposal plan should be in the brief at the same level as the kit composition and the data capture.
Planning timeline
- Define the year's programme. Tier-one event count capped, tier-two list worked through, tier-three discretionary pot sized. One review with finance before January.
- Lock the calendar and the budget. Each tier-one event given an owner, a date, a venue shortlist and a kit decision. Tier-two and tier-three locked by the end of February.
- Run the year. Reconciliation after every event. Quarterly calendar review with one decision-maker present who can move events in and out.
- Close out and re-design. End-of-year review against the metric chosen at the start. Re-tier the next year's calendar against what earned its slot and what did not.
Frequently asked questions
How many tier-one customer events should an Armenian B2B brand run per year?
For a mid-sized B2B brand without a dedicated event lead, four tier-one events per year is the working maximum — quarterly, with one per quarter. Brands with a dedicated event lead can run six, which is the upper edge before the tier-one kit starts to repeat itself within a year and the event loses the headline effect.
What is the right tier for a partner co-hosted event?
Partner co-hosted events in Yerevan usually sit at tier two rather than tier one, because the audience is shared between the two brands and the data capture is split. Promote to tier one only when the partner brings a distinct audience the host brand does not already reach. Demote to tier three when the partner brings the same audience under a different banner.
What metric should the programme be measured against for finance?
Cost per qualified pipeline opportunity opened against the event, plus a 90-day cost per opportunity that has reached opportunity stage. Vanity metrics do not survive a finance review. Run the year on the chosen metric and do not switch mid-year, even if early results are unfavourable — switch the tier structure and the kit, not the metric.
Is Corp-Merch a partner or official supplier of any Armenian event 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 event, venue or association named on this site. Programme work is offered on standard commercial terms against the brief, with no implied relationship to the programme's hosted events.
How much of the annual programme budget should go on tier one?
A working range is 55–65% of the merch budget on tier one, 25–35% on tier two, and 5–15% retained for tier-three opportunity. The split should be reviewed quarterly against actual pipeline contribution, not against how visible the event was on social media.
This page is a programme-level playbook for running merch at customer events in Armenia across a year. Figures are illustrative for a mid-sized B2B brand and depend on tier mix, venue fees and the chosen finance metric. Use the structure to set the calendar, the tier cap and the measurement — not as a budget.