A security company can tell you what happened on its network at 3.47 this morning, which credential was used, from which address, and whether the pattern matched anything seen before. Then its marketing arrives at the monthly meeting as a feeling. The brand is 'getting out there'. The posts are 'getting engagement'. The pipeline 'feels stronger than last quarter'. Nobody in the building would accept that answer from a SOC.
Marketing is a system, and systems can be instrumented. The same discipline that watches packets can watch pipeline: name the stages a buyer moves through, measure the conversion between them, and put this week's effort where the numbers stall.
Name the stages first
We run six, borrowed from growth practice. Reached: a named target has seen you. Engaged: they did something back, a reply, a download, a visit that lasted. Met: a real conversation happened. Opportunity: there is a problem, a budget and a date. Client. Advocate: they bring the next one. Every account on a target map sits at exactly one stage, which means progress is countable.
The diagnosis lives in the rates between stages. Say your map holds forty accounts: thirty-two reached, eleven engaged, two met. The leak is not awareness, whatever the instinct says. It is the step from engagement to a meeting, so that is where the week's experiment belongs, with the briefing offer or the roundtable invitation, and emphatically not with another awareness post.
Just as important is what you stop counting. Impressions, follower growth and page views can live on a dashboard somewhere, but they do not belong in front of a board, because none of them can miss. A number that only ever goes up is decoration. The numbers worth reporting are the ones that can embarrass you, and the habit of reporting them monthly is exactly what makes the wins believable when they come.
Measure money, not applause
Your buyer counts in dollars. The ASD put the average self-reported cost of an incident for a medium-sized Australian business at $97,200 in 2024–25, up 55 per cent in a year. A board hearing numbers like that about the threat expects numbers of similar weight about the response, and that includes the marketing it is paying for. Report meetings with named targets, opportunities with budgets and dates attached, and pipeline your work touched. Monthly, against the map.
The instrumentation is now cheap. Analytics events on the journeys that matter: started the assessment, reached the halfway mark, booked the meeting. Company-level identification of who visited. A CRM note recording which piece a buyer actually touched. Our own site works this way; it fires an event when a visitor starts our pen test, again at each quarter of it, again at the moment they unlock their report. The month's story assembles itself while we do other work.
Test weekly, like patching
The last habit is cadence. One experiment per stall per week: small, named, dated, and judged on whether the rate moved. Offer the one-page briefing instead of the demo. Send the printed letter to ten accounts and the email to ten others. Swap the webinar for a six-seat dinner. This is hygiene rather than heroics, the marketing equivalent of a patch cycle, and like patching it is boring right up until the moment it is the reason you are fine.
The SOC answers the same two questions every morning: what happened, and what do we do next. Marketing can be held to those questions too. Your firewalls would never get away with 'it feels stronger'. Neither should the budget that feeds them.
