Technology companies arrive at Strategic Meetings Management from a different direction to everyone else. There is usually no entrenched opposition to coordination, no partner autonomy to negotiate with, and often genuine appetite for doing this properly. What there is instead is rate of change.
A business that has doubled headcount in two years and reorganised its go-to-market twice has not refused to build a meetings process. It has never had a stable enough organisation chart for one to attach to. Every time a process is agreed, the team that agreed it is restructured.
That matters because it changes the design. A programme built for a static organisation assumes fixed owners, fixed cost centres and fixed approval chains. One built for a fast-growing business has to survive all three changing.
The event portfolio is larger than people think
Technology businesses typically run a wide and frequent event programme relative to their size, spread across functions that do not think of themselves as event owners.
Sales kick-offs and QBRs
The largest single internal commitment of the year, with accommodation and production attached, and a date set by the fiscal calendar rather than availability.
Customer and user events
Roadshows, user groups, executive dinners and a flagship conference. Marketing-owned, with a pipeline number attached.
Developer and community events
Hackathons, meet-ups and sponsorships. Frequently bought on a card at short notice, rarely captured centrally.
All-hands and onsites
For remote-first teams, bringing people together is a recurring cost, usually commissioned by managers with no buying experience.
Recruitment and employer brand
Campus events, technical meet-ups and hiring days, run by talent teams under their own budget.
Partner and channel activity
Joint events where cost-sharing arrangements make the true spend particularly hard to see.
Card-first purchasing is the visibility problem
Purchasing in fast-growing technology businesses is usually card-first and speed-optimised, for understandable reasons. Raising a purchase order for a venue deposit takes longer than putting it on a company card, and the person doing it is judged on the event happening, not on how it was bought.
The consequence is that meetings spend enters the finance system as expense lines coded to whatever category the submitter chose. It is not hidden. It is simply unaggregatable, which is precisely the problem meetings spend visibility exists to solve.
The fix is rarely to ban the card. It is to ensure anything above a sensible threshold goes through a route that captures the same fields every time — see meetings spend management and event spend reporting.
Distributed and remote-first teams change the maths
Where a business is remote-first, in-person gatherings are not an occasional extra. They are the mechanism by which teams meet at all, and the cost is structural rather than discretionary.
Two implications follow. Volume: many small offsites add up to a material number, each sourced from scratch by a manager with no venue experience. And duty of care — when an organisation brings distributed people together somewhere none of them live, knowing who is where stops being an administrative nicety.
That is the strongest argument for a single briefing route here. Not control, but the fact that fifty managers sourcing fifty offsites independently is fifty times the effort and none of the leverage.
What a proportionate programme looks like
Policy
- Conventional approach
- A document covering every scenario.
- Better fit for fast growth
- One page: thresholds, the route in, the fields to record.
Approvals
- Conventional approach
- A new approval chain specific to meetings.
- Better fit for fast growth
- Mapped onto the finance thresholds already in use.
Supplier arrangements
- Conventional approach
- Full preferred venue programme from the outset.
- Better fit for fast growth
- Agreed terms with the handful of venues and cities that actually repeat.
Ownership
- Conventional approach
- The team currently running the biggest event.
- Better fit for fast growth
- A function that survives reorganisation.
Reporting
- Conventional approach
- Comprehensive quarterly programme pack.
- Better fit for fast growth
- A few fields reported monthly, consistent enough to trend — see meetings KPIs.
Technology
- Conventional approach
- Platform implementation ahead of process.
- Better fit for fast growth
- Process and data standard first; tooling follows.
| Element | Conventional approach | Better fit for fast growth |
|---|---|---|
| Policy | A document covering every scenario. | One page: thresholds, the route in, the fields to record. |
| Approvals | A new approval chain specific to meetings. | Mapped onto the finance thresholds already in use. |
| Supplier arrangements | Full preferred venue programme from the outset. | Agreed terms with the handful of venues and cities that actually repeat. |
| Ownership | The team currently running the biggest event. | A function that survives reorganisation. |
| Reporting | Comprehensive quarterly programme pack. | A few fields reported monthly, consistent enough to trend — see meetings KPIs. |
| Technology | Platform implementation ahead of process. | Process and data standard first; tooling follows. |
That last row is worth dwelling on. A technology business is unusually comfortable solving problems with software, and unusually likely to buy a system before agreeing what it should record. A data standard everyone follows in a spreadsheet beats a platform nobody populates consistently. Implementing Strategic Meetings Management puts the sequence in order.
Frequently asked questions
01We move too fast for this. Will a programme slow us down?
Only if it is designed badly. A route returning venue options in a day is faster than a manager searching themselves, and a pre-agreed contract position is faster than legal reviewing a venue contract from scratch each time. The speed argument usually favours the programme once the comparison is made honestly.
02Our biggest event is the annual sales kick-off. Is that the place to start?
It is the most visible place to start and often the most valuable, because the commitments are large enough to matter and the requirement repeats annually. The caution is that a single large event can absorb all the attention while the long tail of small offsites — frequently the larger aggregate number — stays untouched.
03Who owns meetings in a tech company?
There is rarely an obvious answer, which is part of the problem. Marketing owns the customer events, revenue operations the kick-off, talent the hiring events, and workplace the offsites. Somebody has to own the category across all of them, and finance or procurement is usually the most durable home — see meetings governance.
04We have offices in several countries but everything is coordinated from one place. Does that count as multi-office?
Partly. Coordination from a single point avoids most of the fragmentation problem, but currency, local supplier terms and cross-border contracting still apply. Multi-office meetings management covers those.
Related reading
- 01Proportionate by designMid-market SMMA proportionate programme for organisations that do not need enterprise infrastructure.
- 02The money itselfMeetings spend managementGetting control of spend that arrives as card transactions and expense lines.
- 03GuideReducing fragmented event spendA practical guide to consolidating activity bought in many small pieces.
- 04Our frameworkThe SMM maturity modelFive levels, and an honest read on where a fast-growing business usually sits.
