Exhibitions are worth attending. The largest cost of attending them is the one that never appears in the budget — and it is usually the least protected.
Who does your firm send to an exhibition? You send the people who can hold a technical conversation without flinching — a senior engineer, or a strong intermediate coming up behind. That is the right instinct. A buyer with a real problem can tell within two minutes whether the person across from them has actually done the work, and no amount of marketing polish substitutes for that.
It also means the people walking the floor are among your most billable. Three days on the floor, plus a travel day either end, times two people. Before you count a flight, a hotel, or booth space, you have committed something on the order of ten billable days. That cost rarely appears on the event budget, because billable time you did not bill does not arrive as an invoice. It arrives later, as a soft month.
Which makes the honest question an uncomfortable one: for ten days of your best technical capacity, what came back?
Exhibitions are worth attending. For a technical firm in energy, engineering, or infrastructure, few other things put several hundred or thousand people from your market in one building, in a mood to talk. Cold email does not do that. Advertising does not do that.
The problem is not the exhibition. It is that most firms buy attendance and hope it becomes business development. Attendance is not business development: it is the venue where business development can happen, if somebody has done the work around it.
There are really only two questions worth asking about your event calendar. Which of these do your engineers actually need to be at? And for those, how do we make sure the days they spend there are extremely effective? A surprising number of events do not require a senior engineer on the floor at all; they require someone credible in the room who knows your market, can identify the right people, and can bring the technical conversation back to you. The ones that do require your people are the ones worth protecting properly.
A hundred conversations sounds like a good week. It usually is not. Most of those hundred people cannot buy what you sell and will not influence anyone who can. A senior engineer spending three days discovering that, one handshake at a time, is the most expensive possible way to qualify a room.
Doing it properly starts weeks earlier, and it looks like desk work:
Prep is what turns your engineer from a qualifier into a closer. Their scarce and expensive skill is being credible in a technical conversation with someone who matters. Everything upstream of that — working out who matters and getting them into a chair — does not require them, and should not consume them.
The second failure is quieter and more costly. The conversations happen, the trip is judged a success, and then nothing is captured. Six months later nobody can say who said what. The cards are in a drawer and the context is gone.
Consider what a single relationship looks like when it is handled with rigour instead.
Month 0. You meet a prospect in a meeting you booked before you flew to the exhibition She mentions her current inspection contractor is competent but slow, and that her capital budget cycle closes in March. That gets written down — not “good chat,” but the substance and the constraint.
Month 6. You send her something useful with no ask attached, because the record told you what she cares about. A regulatory change, a comparable project, a short note. Trust moves a little. That gets written down too.
Month 11. Her company announces a project that touches exactly the problem she described. You reach out on that basis, and she tells you procurement is likely in the spring. Now you are holding a date and a reason, and she has heard from you three times without ever being pitched.
Month 14. Her trigger fires — the tender, the budget that finally cleared. She remembers a firm that stayed in touch without pestering her and already understands her constraint. You come back exactly when you said you would.
Month 14 is only available because month 0 was prepared for and months 0 and 11 were recorded. Take away the prep and you never met the right person. Take away the record and you meet her twice and arrive cold the third time. Either way, ten days of senior capacity converts into nothing.
Most business development gets measured as flow — meetings held, events attended, cards collected. Flow resets to zero every quarter. Rigour turns flow into stock, and stock only moves one way:
None of this is a long game you have to wait out. The first return lands during the event itself: six booked meetings with people who can buy, instead of three days of handshakes and a hopeful lap of the hall. The second lands within the month, when the tender or the enquiry you did not expect arrives and you can respond with a named contact, their stated problem, and a reason to call — rather than a scramble to remember whether anyone met them.
By the next event, six or twelve months in, you are not building the target list from scratch and a good share of the room already knows you, so your floor time goes to the people you have not met yet. That is where the compounding shows up: not as a payoff you finally collect in year three, but as each event costing the same and returning more than the one before it.
It compounds in a second way that is easy to miss. When a senior person is away, moves internally, or leaves, that stock stays with the firm rather than walking out the door in somebody's head.
Not for lack of discipline. Because of what your engineers walk back into.
They return from three days away to project work that is behind, a client who needs something by Thursday, and two hundred emails. That project work is the thing that actually pays the bills this month, so it wins — correctly. Following up on a conversation that might matter in six months loses that competition every single time, and it keeps losing it every week after that. Nobody decides to abandon the follow-up. It simply never becomes the most urgent thing on any given day.
Prep has the same problem at the other end. It needs to happen in the weeks before the event, which is exactly when the same people are trying to clear their desks in order to be away at all.
So the pattern repeats. The firm spends the money and the senior days, gets the one part only an engineer can do — a credible technical conversation — and quietly forfeits the two parts that would have made the trip pay for itself.
Those two parts do not require an engineer. They require someone whose actual job is the list, the outreach, the calendar, the record, and the return dates — and whose week is not interrupted by a project deadline. That is a different function, and most technical firms have never had one.
The exhibition is not the expensive part. Your people are.
So there are two decisions, not one. Which events genuinely need your engineers on the floor — and for those, do they walk in with twenty-five names and six booked meetings, and walk out into a follow-up process that still exists months later?
Same flights. Same booth. Same ten days of your best capacity. Wildly different asset at the end of it.
Pedal & Shift represents technical firms in energy, engineering, and infrastructure at events across Eastern Canada and Europe — and does the prep, the meetings, the record, and the return for the events where your own people need to be there. If you have something on the calendar, that work starts now, not the week before.