Event merchandising · Yerevan tech calendar · lead capture · consent · season budget

Running merchandise around the Yerevan tech event calendar

Event merchandise has a reputation problem that is mostly earned: thousands of identical totes, lanyards and stress balls leave tech conferences every year and go straight into a cupboard. The events are not the problem. The problem is that most programmes buy an item, print a logo on it, and hope. A programme that works treats every event as a small piece of a season, gives away items designed to be scanned rather than carried, captures consent properly, and has a follow-up plan written before the stand is packed down. This page is a working playbook for that, written for marketing and demand generation teams in Yerevan.

Plan an event programme All B2B notes

The reason most event merchandise ends up in a cupboard

Ask a visitor what they took from a stand at a conference six months ago and they will usually describe a tote bag, a pen and a lanyard. They will not describe any of it as useful, because none of it was designed to be. A promotional tote is chosen because it photographs well on a table, not because anyone needs another tote. A promotional pen is chosen because it is the cheapest item with a printable surface, not because anyone writes with the one they were given. This is not a failure of taste; it is a failure of specification, because most programmes specify an item and a logo rather than a job the item has to do.

An item given away at a technology event is competing against a very specific set of alternatives in the visitor hand. A good notebook from a vendor two stands down, a USB drive handed over with a white-paper session, a conference tote that every other exhibitor is also handing out, and a phone. Against that competition, a generic logo tote has no reason to survive the conference centre. The items that do survive are the ones with a built-in reason to be kept: something that gets used during the day, something that carries a detail the visitor has to look up later, or something that signals access rather than advertising.

The second reason programmes underperform is that they are built event by event. A team that plans each event independently re-pays setup on every design, buys in quantities that give no advantage, ships to a different venue address every time, and has no consolidated view of what worked. The same team planning a season — four events, one artwork system, one production partner, one budget line — amortises the setup across the whole year, holds a single colour specification across venues, and can say which event actually produced pipeline.

Programme unit: The season, not the event: four to six events sharing one artwork system and one budget
Typical season budget: AMD 6 000–40 000 per event for a mid-size exhibitor, all-in including production
Giveaway quantities: Attendance plus 15–25% overage, never exactly attendance
Badge and lanyard volume: Driven by registration, not attendance; badge production needs a data cut-off 3–4 weeks out
Useful give-away unit cost: AMD 4 000–15 000 for an item designed to be used, versus AMD 1 500–4 000 for a logo tote
Follow-up window that still gets replies: 48–72 hours for a warm contact, 5–7 days for a captured lead
Consent rate to expect: 30–60% of stop conversations on a useful item with a real exchange
Storage between events: All off-season stock in one Yerevan location, counted monthly
Working-back timeline: 12 weeks for a standard booth item; 8 weeks minimum for stocked giveaways

Four blocks that turn a giveaway into a working tool

A seasonal merchandise programme has four moving parts, and each one fails in a characteristic way when it is handled casually. Giveaway design fails because nobody specified the job. Lead capture fails because consent was treated as a formality. Follow-up fails because it was scheduled after the event rather than before it. On-site logistics fail because badge and lanyard volumes were guessed. Each of these has a specific fix, and the fix is not expensive — it is mostly a decision made in advance.

Giveaways built to be scanned, not binned

The test for a conference giveaway is whether it still has a use three weeks later. If the item can be used during the day itself, it is far more likely to be taken home than something that only represents the company. In practice this means a notebook with a page-per-session layout rather than a plain cover, a quality pen that writes rather than a plastic one, a cable organiser or a travel pouch for a laptop-carrying audience, or a printed field guide to a technical topic the exhibitor is credible about. What these have in common is that they were designed by somebody who has been to a conference and knows what people carry. What separates a giveaway that gets scanned from one that gets binned is usually a single detail: something on the item that makes the visitor want to look at it twice. A short URL printed on it, a tiny version number in the corner, a specific and slightly opinionated line of copy, a small diagram. That detail gives the visitor a reason to keep it rather than a reason to scan the QR code and drop it in a bag. The design rule is simple and it is worth enforcing: one item per stop, one idea per item, and no item that exists only to carry a logo.

Lead capture that is actually consented

The event stand produces two very different kinds of conversation. One is a person who stops because they want something and is willing to exchange contact details for it. The other is a person collecting every tote bag in the hall. A programme that treats both identically ends up with a large list that no one can contact and a compliance problem they did not plan for. The fix is to separate the exchange from the giveaway. The item is available to everyone; the useful content, the demo, the technical guide, the consultation is available in exchange for a contact detail, and the visitor is told that plainly at the point of the exchange rather than discovered afterwards in a privacy notice they did not read. Capture should be as fast as the tool allows — one field where two will do — and the visitor should be able to choose the channel they are contacted on. Where the event organiser provides a scanning system, using it is usually better than running a parallel one, because the attendee has already consented to be contacted through that channel. Record the source event on every record, always, even when it feels obvious, because six weeks into follow-up nobody remembers which stand a lead came from.

Follow-up timing, written before the stand is packed

Most event merchandise programmes lose their value between the last day of the event and the first follow-up email, because the follow-up is written by someone who is also dealing with the inbound from the same event. The dates are fixed by physics. A contact who gave their details at a stand at four in the afternoon on the final day has the highest receptivity in the next 48 hours and a materially lower one after a week. That contact has just been away from a computer for two days, has the notes from the event fresh, and has the item in their bag. By the time a conventional corporate follow-up sequence reaches them, they have returned to a full inbox. The workable pattern is: a same-evening or next-morning short message to anyone captured that day referencing the specific conversation, then a substantive follow-up with the thing that was promised at the stand, then a normal sequence. What kills the sequence is a mismatch between what was promised at the stand and what arrives by email. If the conversation at the booth was about a specific technical problem, the email should be about that problem and not about a product catalogue. Promising something concrete at the stand is also what lifts the consent rate: people exchange details far more readily for a specific answer than for a newsletter.

Badge and lanyard logistics

Badges and lanyards are the one category of event merchandise where volume is decided by the organiser rather than by the exhibitor, which makes them the one category most often ordered wrongly. Printed badge stock is typically tied to registration numbers, and registration data usually locks three to four weeks before the event. Ordering badges before the registration cut-off means carrying the risk of unused stock; ordering after it means no time for a misprint. Lanyards are the opposite problem: they are standardised by most organisers to a sponsor-supplied width and length, with a safety breakaway requirement and sometimes a printed organiser logo that must be respected. The exhibitor branded element is usually the loop, the badge sleeve, the insert card, or a small badge over-sleeve rather than the lanyard itself. Two operational rules keep this manageable. First, order lanyards far earlier than badges, since they are a stock item with a long production tail and no data dependency. Second, print the badge sleeve and the insert insert card locally and late, since they carry the exhibitor content that changes most between the moment the order is placed and the moment the event opens. Keeping the printed quantity slightly above final registration and treating the surplus as reusable across the season avoids the all-or-nothing problem entirely.

Choosing the right item for each job

A season programme should not use one item everywhere. Each event in the calendar has a different audience and a different job, and the merchandise should follow the job rather than the brand consistency requirement. The four jobs are recognition, conversation, utility and access, and they justify different objects.

Recognition is about being seen across a hall. It is the tote, the lanyard, the sleeve, the thing that is visible in a photograph and confirms who was there. Recognition items are cheap, high-volume and should never carry the message on its own; they exist so that a photograph of the stand shows a branded object in the frame. Conversation is about starting an exchange, and it is where the useful giveaways belong. A technical guide, a benchmark sheet, a printed checklist relevant to the audience, or a small tool that solves an annoyance. These are lower-volume and higher-cost, and they are the items that produce a captured contact detail rather than a polite nod. Utility is about being kept after the event, which is the same test described in the giveaway card above: an item that gets used in the following week survives, and one that does not, does not. Access is about signalling what the visitor gets by talking to the team — a technical conversation, a pilot, an architecture review. It is rarely an object at all. Sometimes it is a card that names the thing the visitor can have, sometimes it is a badge sticker that marks them as having had that conversation, and sometimes it is nothing physical beyond a page in the notebook that was handed out at the start.

The most effective seasonal programmes allocate roughly half the budget to recognition, which is bought in volume and ordered early, and the other half across conversation and utility items, which are produced in smaller runs and often differ per event. That split keeps the visible part cheap while making the memorable part worth talking about, and it means the budget that matters most — the one that produces pipeline — is not being spent on a bag.

Budgeting across a season rather than an event

Event budgets are usually built event by event because the commitment arrives event by event, and that is why seasonal programmes overspend. A programme planned across four to six events can do four things that an event-by-event programme cannot.

It can hold a single artwork system across the season, which means the setup cost — prepress, screens, digitising, moulds — is paid once for the year rather than four times. In a season where each event uses a slightly different version of the same logo, the saving on setup alone can be a meaningful share of the give-away budget. It can consolidate procurement so that four orders of 300 units become one order of 1 200 with a materially better unit price, while the delivery is still split to each venue. It can negotiate a season agreement with a single production partner, which brings faster reorders, a stored colour specification, and artwork files held ready for a new event added at short notice. And it can spread the spend so that no single event carries the full cost of a mistake.

The practical budget structure is straightforward: a recognition line bought once for the season and held in storage, a per-event line for conversation and utility items, and a contingency line of roughly ten per cent. The contingency is not optional in this category, because the two things most likely to go wrong — a registration number cut-off that moves, and a stand size that changes after the design is locked — both land in the same place. One further rule: keep the off-season stock in one location with a monthly count. Merchandise distributed to several people stores itself in several people's cars, and the season programme is the one context in which knowing what you already own is worth real money, because it prevents the same tote being ordered twice.

What a seasonal programme should be measured on

Counting giveaways handed out is the most common measurement in this category and almost the least useful. It measures booth activity, not outcome, and it is trivially gamed by ordering more. Four measures are worth putting in place before the season starts, and none of them requires anything beyond what the team is already doing.

Capture rate is contacts captured divided by stop conversations. This is the number that tells you whether the item and the pitch are working, because a low capture rate with high traffic means the exchange is not worth making. Consent quality is the proportion of records with a usable channel and a stated interest, since a list of blank records is a compliance liability with no commercial return. Time to first reply is the interval between the event day and the first substantive response, tracked per event. A programme whose reply window is slipping is losing pipeline it already paid to acquire, and the fix is staffing rather than merchandise. Event-attributed pipeline is the only number that answers the budget question, and it needs the source recorded on every record from the day the badge is scanned.

It is worth being honest about what merchandise can and cannot do. A well-designed giveaway improves the rate at which a visitor stops, raises the chance that the conversation happens, and gives a reason to exchange details. It does not create demand on its own, and a programme whose only success metric is units distributed will eventually buy a great deal of merchandise that changed nothing. Setting the measurement before the season starts is what prevents that, and it takes one page.

The twelve weeks, working backwards

Most missed event dates in this category are missed in the paperwork, not in the factory. A twelve-week backward plan for a standard season removes almost all of them, and the sequence is the same whether the item is made or taken from stock.

Week 12. Confirm the event, the stand size, the audience and the job the merchandise is doing. Nothing is ordered at this point and nothing is designed. Week 11. Choose the item, write the specification, and decide whether it is recognition, conversation or utility. If it is a stocked item, this is where the availability question is asked. Week 10. Artwork production and the first proof. Week 9. Proof approval and the Pantone or colour confirmation, with the decision recorded rather than assumed. Week 8. Order placement. Anything needing a long production tail — lanyards, moulded items, embroidered caps — is already late and should be moved forward by two weeks. Week 7 and 6. Production and finishing, with a mid-point check rather than a single delivery date. Week 5. Goods in, inspection, count, and the surplus reconciliation against the previous event. Week 4. Badge data cut-off with the organiser; badge sleeve artwork released to print. Week 3. Packing by venue, packing list by event, and the storage location confirmed. Week 2. Freight or collection booked, staff briefing, and the capture and follow-up process rehearsed once end to end with a colleague playing the visitor. Week 1. Final count, final call on quantities, and the capture sheet printed. Event week. Capture from the first hour, and the same-evening follow-up list exported before anyone leaves the hall.

The rehearsal in week two is the step most programmes skip and the one that matters most. A capture process that has never been walked through by the person who will run it will lose thirty per cent of the day to a form that will not submit on a phone connection, and nobody will notice until the follow-up list comes back short.

After the season: the surplus, the list and the next year

The period after the final event is where a season programme either becomes an asset or becomes clutter, and the difference is entirely in what happens during the four weeks that follow. The first task is a physical count. Every event takes stock out and puts surplus back, and in a four-event season with two different storage locations the count at the end is routinely wrong by enough to matter. Count by SKU against the opening position, reconcile against the delivery notes, and record the result in the same place the budget is tracked. A programme that has done this once knows what it can carry into the next year and what it should not reorder, and that knowledge is worth more than any single event saving.

The second task is a decision on the surplus, made deliberately rather than by neglect. Unsold seasonal merchandise has three legitimate destinations: carry it into the next season if the item and the artwork are still current, repurposed it into an internal or partner use that does not conflict with the brand guidelines, or destroy it. What it must not do is drift into general distribution, because an item printed for an event and handed out later in a different context is a brand-governance problem rather than a marketing opportunity. The same applies to the list. A captured contact record has an expiry logic that belongs in the programme rather than in the marketing automation tool: if the visitor was told they would receive a technical follow-up and they did not receive one within an agreed window, that promise has been broken and the correct response is to honour it, not to move them into a newsletter.

Carrying the season forward is straightforward and worth doing deliberately. The colour specification, the artwork files, the supplier contact, the prepress work and the packaging design all persist, and a programme that carries them converts the next year's setup cost into a fraction of a first-year cost. In practice the second season should arrive with most of the production already at factory or local stock pricing and with the only genuinely new expense being the events themselves.

Questions buyers ask about event merchandise programmes

What kind of giveaway actually gets kept after a tech conference?

Items with a use during the day itself survive far better than items that only carry a logo. In practice that means a notebook built around a real task, a pen that writes properly, a small tool or organiser suited to a laptop-carrying audience, or a printed technical guide the visitor would keep on their desk. The common factor is a single specific detail on the item — a short URL, a small version number, a diagram, an opinionated line of copy — that gives the visitor a reason to pick it up twice. Items that exist only to display a mark are binned, and no amount of printing quality changes that.

How far ahead should event merchandise be ordered in Yerevan?

Twelve weeks for a made-to-order booth item is the working plan, and eight weeks is the practical minimum. Longer-tail items such as lanyards, moulded products and embroidered caps need to move two weeks earlier still, which is why they belong on a season agreement rather than an event order. Locally stocked giveaways can be handled in six to eight weeks because the items exist before the order is placed. The other date that constrains the plan is the registration cut-off, usually three to four weeks before the event, after which badge volumes can no longer be changed — so any badge-dependent item must be specified before that date even if it is produced afterwards.

How should a team split a season merchandise budget across several events?

Roughly half to recognition items — totes, lanyards, badge sleeves — bought once for the whole season and stored between events, and the balance to conversation and utility items produced in smaller runs per event. This keeps the visible, high-volume part cheap while concentrating the budget where pipeline actually comes from, and the recognition stock amortises its setup across every event in the year. Hold a contingency of roughly ten per cent, because the two most common failures in this category are a moved registration cut-off and a stand size that changes after the design is locked. Keep all off-season stock in one location with a monthly count so the same item is not ordered twice.

Is Corp-Merch a partner or official supplier of the events, conferences or organisers referenced on this page?

No. Corp-Merch is an independent B2B merchandise supplier. References to the technology event calendar, conference formats, organiser practices, registration processes and exhibitor requirements describe general practice in this category as we understand them, and imply no partnership, sponsorship, endorsement, exhibitor relationship or official-supplier status with any event, conference or organiser. Nothing on this page constitutes advice on any specific event's rules, and every requirement must be confirmed against the organiser own exhibitor documentation for the event in question.

This page is written for marketing, demand generation and field teams running corporate merchandise programmes around business and technology events in Yerevan. Corp-Merch is an independent B2B merchandise supplier. The budget ranges, capture rates, response windows, volumes and lead times described here are general planning guidance for this category as we understand them; they are not event rules, organiser requirements, consent or privacy advice, or a guarantee of any result. Registration cut-offs, stand dimensions, badge specifications, lanyard standards and exhibitor obligations are set independently by each event and can change between seasons, so all of them must be confirmed in the organiser current exhibitor documentation. Nothing here implies any relationship with any event or organiser. Every programme is quoted and scheduled individually against a written specification, and consent-based data collection must be reviewed against the organisation own privacy and legal requirements before any list is captured.