Pricing Appointment Packages for Fair and Event Directories in 2026

Fair and event directories that sell “intro meetings” or “buyer intros” to exhibitors rarely fail because of marketing copy. They fail because pricing and packaging are fuzzy: one SKU tries to mean outreach attempts, held meetings, and pipeline outcomes at once; city and fair tiers are not reflected in cost; SLAs promise the wrong unit; refunds become emotional negotiations; and quotes in CRM do not match the contract language legal will actually sign.

This guide is for directory operators, marketplace teams attached to fairs (when you are selling a commercial product, not impersonating the organizer), and lead-gen partners who productize local or remote B2B introduction pipelines. FUBYTE is a growth and RevOps operator. We are not a trade-fair organizer, not an official booking desk for any named exhibition unless a contract says so, and we do not endorse “guaranteed meetings with decision-makers” as a commercial claim.

The commercial job is narrow and honest: help exhibitors request and confirm calendar introductions with relevant B2B contacts under documented quality criteria, with transparent attempt SLAs, held-meeting definitions, and refund rules that do not invent deal outcomes. Pipeline strategy for directories is covered in event and fair directory lead pipelines and geo appointment operations in trade show appointment setting with geo leads. This article is about how you price and package that work so unit economics and procurement both survive.

What You Are Actually Selling (Name the Unit)

Before tiers or city multipliers, freeze the commercial unit. Ambiguity here is how directories overpromise.

| Unit | What the exhibitor receives | What you can SLA | What you must not imply | | --- | --- | --- | --- | | Outreach attempt | Documented contact attempts to ICP + geo filters | Number, channels, cadence window | That attempts equal interest | | Positive reply | Verified reply expressing willingness to discuss | Reply definition, response window | That a reply is a meeting | | Confirmed meeting | Calendar hold accepted by both sides | Confirmation criteria, reschedule policy | That the contact will show | | Held meeting | Meeting occurred (join/no-show rules defined) | QA checklist, evidence standard | That a held meeting becomes revenue | | Pipeline outcome | Exhibitor’s own opportunity after the intro | Nothing you control | Guaranteed RFPs, POCs, or deals |

Most healthy catalogs sell packages of confirmed or held meetings, with attempt minimums as operational SLAs—not as the headline SKU. Selling “100 emails” trains buyers to compare you to spam vendors. Selling “eight held intros with QA” trains buyers to compare you to field marketing ROI, which is the right peer set—see field marketing pipeline and events ROI.

Compliant offer language

Use language like:

• “Intro meeting packages help exhibitors request calendar holds with relevant B2B contacts in the fair region or remote ICP.”
• “We operate on behalf of the exhibitor brand under approved messaging; we are not the fair’s official appointment desk unless contracted as such.”
• “Pricing reflects outreach capacity, confirmation work, and held-meeting QA—not guaranteed commercial outcomes.”

Avoid:

• “Guaranteed meetings with buyers who will purchase”
• “Official [Famous Fair] appointment partners” without a license
• “We unlock exclusive attendee lists”
• Any implication that scraped consumer or visitor data powers the package

Data provenance and consent posture belong in the MSA exhibit, not only in a blog footer. If you cannot document lawful B2B sources and purpose limitation, do not sell the package.

Fair Tier and City Tier: Price the Constraint, Not the Logo

Exhibitors intuitively know that a flagship industrial fair in a dense metro is different from a regional niche show. Your price book should make that explicit with two orthogonal multipliers: fair tier and city (or metro) tier. Combining them into one vague “premium” SKU hides where margin actually goes.

Fair tier (illustrative)

| Fair tier | Typical characteristics | Pricing implication | | --- | --- | --- | | Tier A / flagship | High booth density, crowded buyer calendars, short booking windows | Higher price per held meeting; longer lead time; stricter blackout rules | | Tier B / national mid-market | Solid traffic, more flexible calendars | Mid price; standard package sizes | | Tier C / regional / niche | Smaller addressable ICP, longer cycles to find fits | Lower absolute package price or smaller pack sizes; may need wider geo |

Do not invent affiliation with the organizer to justify Tier A. Tier A is about market difficulty and opportunity cost of calendar space, not about pretending you run the show.

City / metro tier (illustrative)

| City tier | Examples of constraint | Pricing implication | | --- | --- | --- | | Metro 1 | Dense ICP, high meeting competition, multi-language outreach sometimes required | Uplift on labor minutes per confirmed hold | | Metro 2 | Adequate density, standard outreach | Baseline | | Metro 3 / remote-heavy | Thin local ICP; remote intros common | Discount on “local only,” or reframe package as hybrid local + remote |

Publish the tier matrix in your rate card. Buyers hate discovering mid-cycle that “Munich Tier A” was always going to cost more than “secondary city Tier C.” Packaging discipline here borrows from broader B2B packaging thinking in B2B SaaS pricing and packaging strategy and pricing and packaging growth levers—even though your product is a service package, not seats of software.

Packaging Tiers That Procurement Can Compare

A clean catalog usually has three exhibitor-facing tiers plus optional add-ons. Keep the value metric consistent across tiers (for example: held meetings with QA), and vary volume, support, and reporting—not vague “premium vibes.”

Suggested catalog

Starter — Discovery Intro Pack

• Fixed number of confirmed meeting attempts toward a smaller held-meeting target
• ICP filters: industry, title bands, geo radius, language
• Channels: email and professional network outreach under platform rules and exhibitor brand approval
• Weekly status report
• Explicit: no guaranteed held count if ICP is thinner than scoped; scope change triggers a change order

Growth — Held Meeting Pack

• Pricing primarily on held meetings with a written definition of held versus no-show
• Attempt floor (for example: minimum outreach volume per held target) as operational SLA
• QA sample review of call notes or meeting evidence fields
• Shared Slack or email war-room during the fair week window
• One reschedule cycle per confirmed hold included

Enterprise — Concierge + Directory Bundle

• Held Meeting Pack plus directory profile upgrades, creative approval workflows, and multi-stakeholder reporting
• Named CSM, custom ICP workshops, multi-language support if you truly offer it
• Optional post-fair follow-up assets owned by the exhibitor (you do not take over their CRM)
• Legal-ready exhibits: provenance summary, suppression rules, subprocessors

Add-ons that usually clear legal review when scoped tightly:

• Extra geo radius or second city
• Additional languages
• Executive-only title filters (priced for lower match rates)
• Remote intro track when local density is insufficient
• Recording or summary templates only if all parties consent and exhibitor policy allows

Do not sell “AI matching that guarantees buyer fit” as a price uplift without explaining that matching is assistive and human-reviewed. Overclaiming matching accuracy is how refunds start.

SLAs: Attempts Versus Meetings Held

SLAs should map to what your team controls. Confusing attempt SLAs with outcome SLAs is the fastest path to bitter renewals.

Attempt SLAs (operational)

Define for each package:

• Minimum unique accounts contacted
• Maximum touches per account in the window
• Allowed channels
• Quiet hours and local timezone rules
• Suppression: DNC, competitor list, consumer roles, prior opt-outs
• Documentation: timestamps and disposition codes in CRM

Attempt SLAs protect the exhibitor from under-work. They do not guarantee interest.

Confirmation and held-meeting SLAs (commercial)

Define:

• What “confirmed” means (calendar invite accepted, or written confirmation with time/place)
• What “held” means (both parties joined for a minimum duration, or exhibitor marks attended)
• No-show handling (one courtesy reschedule versus forfeit)
• Evidence required for invoice (invite IDs, disposition, short QA form)

A practical rule many directories use: invoice on held meetings, with attempt floors as a cure period—if attempts are below the floor, you extend outreach at no charge before discussing refunds. That structure is fairer than promising “ten held meetings or money back” with no ICP reality check.

For CRM hygiene around SLA clocks and disposition quality, align with HubSpot data quality SLAs and speed concepts from inbound SLA and speed to lead—adapted to outbound appointment ops, not website form response.

Refunds and Quality Policies Without Promising Deals

Refund policy is part of packaging. Write it before sales invents one on a call.

Quality criteria for a billable intro

Examples of criteria that are specific and auditable:

• Contact matches agreed title bands or a documented exception approved by the exhibitor
• Company matches industry and size filters
• Geo or remote flag matches package
• Meeting duration or attendance evidence meets the held definition
• No material misrepresentation of who would attend

Examples of criteria that should not be billability tests:

• Exhibitor closed a deal
• Contact had budget authority proven on the call
• Contact “liked” the product
• Contact agreed to a pilot

Those are exhibitor sales outcomes. Pricing packages on them turns you into a contingent seller of someone else’s pipeline—and invites claims you cannot control.

Refund / credit matrix (illustrative)

| Situation | Typical remedy | | --- | --- | | Held meeting fails QA (wrong persona, wrong geo) | Credit one replacement intro or refund that unit | | Confirmed meeting no-shows after one reschedule attempt | Credit per policy; do not auto-refund entire package | | Attempt floor missed by your team | Extend window or add attempts before cash refund | | Exhibitor changes ICP mid-flight | Change order; not a refund of sunk compliant work | | Exhibitor cancels booth / withdraws | Termination schedule in MSA; wind-down fee possible | | Buyer asks for “guaranteed deals” remedy | Decline; offer held-meeting credits only |

Publish the matrix in the order form. Ambiguity is not “flexibility”; it is margin leakage and dispute fuel. Negotiation patterns for commercial exceptions belong in a deal desk process—see deal desk negotiation playbook and HubSpot deal desk and CPQ governance.

Unit Economics: Build the Price From Minutes, Not From Vibes

Directories underprice when they copy a competitor’s “ten meetings for X” without modeling labor. Build a simple cost stack per held meeting:

1. Research minutes — account fit, title fit, geo fit, suppression checks
2. Outreach minutes — multi-touch sequences, personalization under brand rules
3. Coordination minutes — timezone negotiation, calendar logistics, exhibitor approvals
4. QA minutes — evidence review, reporting
5. Tooling and data — licensed B2B data, sequencing tools, CRM, consent logging
6. Management overhead — CSM time during fair week
7. Refund / credit reserve — percentage of revenue set aside for QA failures
8. Contribution margin target — after the above

Then invert: if a held meeting in Metro 1 / Fair Tier A truly costs you a certain fully loaded amount, your package price must clear that amount at expected held rates—not at fantasy close rates.

Capacity math exhibitors understand

Share a sanitized version of capacity math in enterprise deals:

• Expected attempts per held meeting by tier
• Expected confirm-to-held rate
• Calendar density constraints in the two weeks before the fair
• Why executive-only filters raise price (lower match rate, more attempts)

This is more persuasive than “premium positioning.” It also prevents sales from discounting below variable cost to win a logo.

Package size economics

Small packs have higher cost per held meeting (onboarding and research do not fully amortize). Large packs need volume discounts that still protect margin. A common pattern:

• 4–6 held intros: highest unit price, good for first-time exhibitors testing the motion
• 8–12 held intros: efficiency band for most booth programs
• 15+ held intros: volume pricing plus mandatory CSM and weekly steering

If an exhibitor wants “as many as possible,” sell capacity retainers with weekly caps—not unlimited meetings. Unlimited is how teams burn out and quality collapses.

HubSpot Quoting Basics for Appointment Packages

If quotes live in email PDFs while delivery lives in spreadsheets, you will misbill. Use HubSpot (or equivalent) so the quote line items match the delivery SKUs and the deal stages match reality.

Objects and fields

Minimum viable model:

• Company — exhibitor account
• Deal — one per fair + package (or one per season with line items)
• Line items — SKUs: Starter attempts pack, Held Meeting Pack units, city uplift, language uplift, concierge
• Custom properties — fair name, fair tier, city tier, geo radius, held definition version, attempt floor, package window start/end
• Quotes — buyer-facing totals with expiration and MSA exhibit links

HubSpot’s quote and line-item patterns are summarized in practice guides like HubSpot quote-to-cash basics. For platform mechanics, see HubSpot’s documentation on creating quotes. Keep delivery metrics on the deal or a custom object (for example: meetings_confirmed, meetings_held_qa_pass, credits_issued) so finance and CSMs share one truth.

Quote hygiene rules

• Quote currency and tax treatment match the MSA
• Expiration dates short enough that fair tier capacity still exists
• Discount approval thresholds in deal desk workflows
• No free “guaranteed held” clauses typed into quote comments
• Sync won quotes to delivery project checklists the same day

Reporting that supports renewals

Report what you sold:

• Held meetings QA-pass per package
• Credit rate
• Attempt-to-held ratios by fair tier and city tier
• Time-to-first-confirm
• Exhibitor NPS or CSAT on intro quality—not on their closed-won rate

Closed-won rate belongs to the exhibitor’s sales team. If you report it at all, label it as exhibitor-reported outcomes, not as your package KPI. Measurement culture tips for B2B teams appear in B2B growth metrics and KPIs.

Consent, GDPR, and Data Provenance Inside the Price

Privacy is not a free add-on; it is part of cost of goods. Packages that rely on unlawful scraped consumer data are not “cheaper to deliver”—they are uninsurable risk.

Operational requirements that should be non-negotiable in every tier:

• Documented B2B sources and licenses
• Purpose limitation: outreach for exhibitor intro requests, not resale of contact files as a separate product unless contracted
• Easy opt-out and suppression sync
• No purchase of “fair visitor” consumer lists of uncertain origin
• Retention limits on outreach notes
• Processor agreements where you handle personal data for the exhibitor

For EU and UK outreach, work from primary sources such as the UK ICO guide to the UK GDPR and the European Commission page on GDPR. Your counsel adapts lawful basis analysis to your markets; this article is not legal advice.

If a prospect asks you to “just scrape the attendee badge list,” the correct commercial response is to decline and keep your price book attached to lawful sources. That refusal is a feature for enterprise procurement.

Sales Motion: From Rate Card to Signed Package

Discovery questions that protect margin

• Which fair, dates, and booth goals (awareness vs meetings vs partner recruitment)?
• Local-only, remote, or hybrid intros?
• Title bands and industries that are truly in-bounds?
• Languages required?
• Who approves outreach copy and calendar ownership?
• What does the exhibitor count as success internally (held intros, opportunities created)—and which of those are your KPIs?

Proposal structure

1. Scope and exclusions
2. Tier selection (fair + city)
3. Package SKU and unit definition
4. SLA table (attempts vs held)
5. Quality and credit policy
6. Timeline and blackout dates
7. Provenance and privacy exhibit
8. HubSpot quote / commercial summary
9. Optional add-ons

Discount discipline

Discount volume, not definitions. If a buyer wants a lower price, reduce held count or narrow geo—do not silently redefine “held” to include two-minute voicemails. Definition erosion destroys renewals faster than a higher sticker price.

Common Packaging Failures (And Fixes)

Failure: One SKU named “Lead Gen Package.”
Fix: Rename to attempt pack or held-meeting pack; put leads language in the museum.

Failure: Price tied to exhibitor revenue share on closed deals.
Fix: Avoid unless you have true contingent capacity and legal appetite; most directories should stay fee-for-intros.

Failure: Tier A fair priced like Tier C because sales wanted the logo.
Fix: Publish the matrix; require deal desk approval to break it.

Failure: Refunds decided in Slack.
Fix: Credit matrix in the order form; CSM applies it; finance audits monthly.

Failure: Quotes without line-item SKUs.
Fix: HubSpot products library; every uplift is a line item.

Failure: Promising organizer affiliation.
Fix: Train sales on approved claims; terminate the clause in templates.

90-Day Implementation Plan for Directory Teams

Days 1–30 — Define

• Freeze units: attempt, confirmed, held
• Draft fair tier and city tier matrix
• Write quality and credit policy
• List SKUs and add-ons
• Legal review of claims and privacy exhibits

Days 31–60 — Operationalize

• Build HubSpot products, quotes, and deal properties
• Create delivery playbooks and disposition codes
• Train CSMs on evidence standards
• Pilot with two exhibitors on different fair tiers

Days 61–90 — Price and publish

• Compare actual minutes to model; adjust uplifts
• Publish external rate card for standard packs
• Add renewal pricing rules (same tier vs upgrade)
• Review credit rate; if high, fix ICP scoping—not only price

How FUBYTE Helps

FUBYTE helps directory and event-marketplace teams turn vague “appointment packages” into rate cards, HubSpot quote catalogs, SLA language, and delivery metrics that procurement can trust. We focus on truthful packaging, lawful data practices, and unit economics—not on fabricating organizer status or guaranteeing exhibitor deals.

If your current offer is a PDF that says “meetings included” without defining held, start with unit definitions and the credit matrix. Pricing clarity is a growth strategy, not a finance afterthought.

Closing Checklist

Before you send the next exhibitor quote, confirm:

• Unit of sale is explicit
• Fair tier and city tier are applied
• Attempt SLAs and held SLAs are separated
• Refunds credit quality failures, not missing deals
• HubSpot line items match the MSA
• Privacy and provenance exhibits are attached
• Sales claims match what you can operationally prove

Directories that price intros this way win fewer fantasy RFPs and more renewable programs—because buyers know what they bought, and your team knows what they must deliver.