Trade fair organisers · CRM
Keep every participant, buyer and meeting in one record that outlives the fair.
A CRM for a trade fair organiser holds the manufacturers who took stalls, the buyers who attended and the meetings between them, edition after edition. GullySales works on setting it up so the team stops rebuilding contact lists from spreadsheets each year.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What CRM means
A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.
Also for trade fair organisers
- Lead generation for trade fair organisers
- Follow-up systems for trade fair organisers
- SEO for trade fair organisers
- Social media for trade fair organisers
- Content marketing for trade fair organisers
- Buyer personas for trade fair organisers
- WhatsApp marketing for trade fair organisers
- Digital marketing for trade fair organisers
Sales and marketing for trade fair organisers, the overview.
Last updated 18 Oct 2026.
For trade fair organisers
Where it usually goes wrong, and what we would do.
“Every edition starts from a blank sheet”
The previous fair's contacts live in a spreadsheet kept by someone who has left, and a new team member begins with a folder of forms. A record that holds each participant's history across editions lets a caller say what the maker did last time.
“Two kinds of contact need two views”
A participant is a sales lead that becomes a paid stall, while a buyer is an invitee who becomes an attendee. Mixing them in one list hides who has paid, who has confirmed and who has been asked for a reply by both teams.
“Meetings are the product”
A buyer-seller meeting is what the participant pays for, yet it sits in a schedule sheet and a paper note. Logged against both records, with the product, samples and next step, it becomes the evidence that decides next year's renewals.
“Partner bodies need a place of their own”
An association or council is neither participant nor buyer. Its contact person, the circulars sent and the members registered through it belong to a third record of their own, or the credit for those registrations goes to nobody on the team.
What we do
What we deliver for trade fair organisers.
Every deliverable, what it covers for you, and the result it is there to produce. Nothing here is an extra.
A record structure for participants, buyers and bodies
Separate views for each with the fields that matter, such as product group, city, consent and edition history.
Result: Each contact sits in the view that matches its role.
Stages that fit a fair
Participant stages from enquiry to stall signed to payment received, and buyer stages from invited to confirmed to attended.
Result: The team can say how many are at each stage.
A meeting log linked to both sides
Each meeting entered with buyer, participant, product, samples and the agreed next step.
Result: Open any maker and see the buyers met and what was agreed.
Import of past editions
Old spreadsheets cleaned for duplicates and loaded with the edition each contact belonged to.
Result: Past participants appear with their history.
Source and consent fields
Where each contact came from and whether permission to message was recorded.
Result: Before any broadcast you can filter to those with permission.
How the result is measured
- Enquiries logged in the CRM
- Data completeness
- Reports generated from CRM data
Recorded as a baseline before work starts, so every later report has an honest comparison.
Fields worth keeping
Fields a fair organiser should keep against every participant and buyer.
- Contact type
- Filled at entry: participant, buyer or partner body. Two kinds of contact need two views, so the sheet should filter by this first.
- Products made or sourced
- Filled by whoever speaks to them. It lets you match a buyer to makers before the next edition.
- Meetings booked and held
- Filled by the floor team during the fair. Meetings are the product, and this field is how you show them.
- Follow-up outcome
- Filled by the participant's or buyer's reply. It separates a sample requested from an order discussed, without inventing a value.
- Editions attended
- Filled from past lists. A maker who attended twice is a different lead from a first enquiry.
- Partner body and contact
- Filled for each association or council. It shows which body shared the fair and which went quiet.
Who it is for
This is written for these trade fair organisers.
- Fairs run by sector associations, such as textiles, leather, engineering or handicrafts
- Fairs organised with export promotion councils for overseas buyers
- State and district industrial fairs that bring in MSME units
- Agri and food processing fairs that draw wholesalers and processors
- Hosted buyer programmes where buyers are flown in and meetings are scheduled
- Regional buyer-seller meets run by a chamber of commerce
- Private organisers who run a fair across several cities
- Virtual and hybrid trade fairs that list suppliers online
Not for
It is not the right fit if.
- The floor team will not log meetings, and the record would be empty where it matters.
- You change organisers or staff every edition, and nobody owns the data to carry forward.
- You want a tool for a one-off fair that will not run again.
How it works
How the CRM work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Map the sales process
We sit with the people who sell and write down how a deal moves from enquiry to payment, including where it stalls.
- 2
Agree stages, fields and owners
Each stage gets a name your team already uses and a proof that the deal has left it. We agree which fields are required at which stage, and who may change what.
- 3
Build on a copy
Pipeline, fields and views are built on a trial copy where the CRM offers one, or in a separate pipeline where the plan allows. Live work stays untouched.
- 4
Connect channels, then switch on automations
Channels are connected first. Each automation is then switched on separately, so a misfiring rule is easy to find.
- 5
Test with real deals
The people who will use the CRM run open deals through it. Gaps are fixed before the whole team switches over.
- 6
Switch over and trim
Once real use shows which fields stay empty and which stages nobody uses, those are cut and the handover record is updated.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales management. A target, a review routine and someone who owns the number.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3 · you are here
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
Do we need paid software, or is a spreadsheet enough?
Who owns the data after the fair?
How do we get the floor team to log meetings?
Who owns the data after the fair?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
What do you need from us?
What if we are not happy with the work?
More for trade fair organisers
Everything else we would do for you.
Closest to this: leads and follow-up
Also for trade fair organisers
Or start from the overview: sales and marketing for trade fair organisers.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.