From client requirements to commercial investment choices

Mandate

Connect the commercial proposition with what customers can buy, implement and use.

Outcomes

• Replaced an incomplete first-year cost example
• Stopped a campaign whose timing did not fit the buying decision
• Clarified software and physical-service responsibilities in partner presentations

Decisions in context

The CMO appointment brought responsibility for the overall commercial explanation and the investment used to bring it to buyers. I lead three managers and twenty-one colleagues, working with sales, product and implementation owners. I do not decide every product capability or accept a venue's operational arrangements. My role includes asking whether the marketing account creates an expectation those colleagues can fulfil. The three cases here required corrections to work I had approved, not simply stronger enforcement on other teams. I report campaign expenditure, including abandoned activity, and distinguish an unfinished pilot from a proved return. Presenting those choices to directors has helped me see how a commercial assumption becomes an investment decision. It has not made me a director. I want the team to explain why a narrower invitation or a more complete cost example can be a stronger commercial proposition.

Reason for the move

Current appointment; building a more precise buying journey for specialist venue software.

Mandate

Bring product, partner and implementation perspectives into the commercial story.

Outcomes

• Included implementation colleagues in selected proposition reviews
• Established clearer distinctions between partner and company services
• Reported unsuccessful campaign expenditure alongside continuing activity

Decisions in context

Leading the marketing function changed the scale of the choices I had to explain. I could no longer concentrate only on whether a presentation was clear within our own team. Partners, sales colleagues and implementation staff used that explanation in different settings, and each could add assumptions the original material had left open. I began bringing those perspectives into selected reviews before approving broader use. The work also required a more candid discussion of expenditure. A campaign that generated conversations could still fail to create a useful purchasing opportunity. I wanted managers to explain that outcome without hiding the cost or blaming the receiving team. The promotion to CMO followed a wider responsibility for commercial positioning and investment, including the relationship between our product account and the services customers needed around it. It was a functional leadership title, not a statutory board appointment.

Reason for the move

Promoted to CMO as the remit broadened across commercial positioning and investment.

Mandate

Understand how different venue operators make and time a software purchase.

Outcomes

• Distinguished recurring venue operations from single-event needs
• Connected customer segments with their planning calendars
• Prepared product explanations around the buyer's next decision

Decisions in context

Segment planning taught me that a buyer category needed more substance than a different brochure cover. A permanent exhibition centre and an operator arranging a small number of professional events could ask similar product questions while facing different planning calendars. I led six colleagues who worked with sales observations and customer visits to understand those circumstances. We used that work to decide which questions an introductory conversation should answer and when the invitation was likely to be useful. I did not assume that a venue's interest meant it was ready to implement. The role developed my ability to connect an audience definition with the practical work behind a purchase. Moving into marketing leadership broadened the same discipline to partner propositions, budget choices and the way our own teams interpreted the promises they were taking to customers.

Reason for the move

Advanced to function leadership with broader partner and expenditure responsibilities.

Mandate

Explain planning-software capabilities through the actual work of venue teams.

Outcomes

• Translated customer questions into clearer demonstrations
• Separated product functions from physical event outcomes
• Supported sales materials and implementation-aware customer visits

Decisions in context

Joining a software company required me to learn the product rather than assume that my event-services experience explained it. I supported demonstrations, customer visits and sales materials within a small marketing team. The familiar setting helped me recognise the work around the screen, but I had to distinguish that context from the capability we were selling. A product could organise a diary or illustrate a space plan without providing equipment, staffing or approval for the event itself. I asked product and implementation colleagues to review the explanations I prepared and learned from the questions customers asked afterwards. I held no independent budget authority. The promotion reflected a growing ability to connect a specific capability with a buyer's decision and to recognise why different operators needed different conversations. It gave me responsibility for developing that understanding with a team.

Reason for the move

Promoted to lead customer-segment planning and a six-person team.

Mandate

Keep the client's requirements connected with the operating and supplier teams.

Outcomes

• Recorded who owned material event requirements
• Surfaced differing assumptions before operating handovers
• Developed practical understanding of venue preparation

Decisions in context

I began after completing my full-time MBA and worked under a senior account manager. My tasks included recording requirements, following supplier questions and helping the operating team understand what had been discussed with the client. I was not the event owner or the person approving expenditure. The value of the experience was seeing how an apparently simple description could mean different things to the people expected to deliver it. A client might assume staffing was included while an equipment supplier understood a much narrower request. I learned to ask who would do the work and whether that understanding had reached the next team. Moving into software marketing gave me a way to apply that practical curiosity to a product used by venue operators. It also required me to learn new limits rather than presenting an event background as technical expertise.

Reason for the move

Moved into software marketing to apply operating knowledge to a product proposition.