Your GTM stack knows who to reach. It doesn't know your boards.

Most growing OOH operators eventually sign up for a sales intelligence tool. ZoomInfo. Apollo. Lusha. LinkedIn Sales Navigator. Sometimes more than one. The annual contracts run between $15,000 and $80,000 depending on the seat count and feature tier. Most operators are paying for them right now.

These tools are good. They do something real. They tell your reps which advertiser contacts to reach, where those contacts work, what their titles are, how to email them, what the company's headcount and revenue look like, and which technologies the company uses. The contact database is genuinely better than anything an independent operator could build in-house, and the cost-per-contact is a fraction of what the same data cost a decade ago.

Six months after signing the contract, most operators are quietly disappointed. Outbound volume is up. Pipeline is not. The reps now know whom to email but still don't know what to say. The expensive tool became a fancier mail-merge engine for the same generic outreach the operator was sending before they had the tool.

This piece is about the gap between contact data and context data, why these tools cannot close that gap by design even when fully configured, and what OOH operators specifically need that sits on top of their existing GTM stack rather than in place of it.

What sales intelligence tools actually solve

The category of products variously called sales intelligence, sales engagement, or B2B contact data is solving a real problem. The problem is finding the right person at the right company.

Before these tools existed, a rep who wanted to reach the regional marketing manager at a Midwest grocery chain had to start with a Google search, work through LinkedIn, guess at email formats, and frequently end up sending cold messages to gatekeepers. The hit rate was bad and the cycle time was slow. Modern GTM tools collapsed that workflow. The rep now searches a database, filters by title and geography, exports a list, and has direct email addresses for fifty regional marketing managers at grocery chains across their footprint in fifteen minutes.

That is a genuine workflow improvement, and it is what these tools are properly understood as: a rolodex. The most current, most complete, most filterable rolodex the industry has ever had access to.

A rolodex is necessary. A rolodex is not sufficient.

What the rolodex doesn't tell you

The rep with a freshly exported list of fifty regional marketing managers at grocery chains has fifty names, fifty titles, fifty emails, and fifty company URLs. Depending on how the GTM stack is configured, they may also have a rich layer of brand activity signals — which of the fifty chains is expanding into which metros, which ones just announced a leadership change, which ones are entering a hiring sprint, which ones are launching private label this quarter, which ones are pushing into new categories, which ones are showing intent signals through their digital behavior. The better the GTM stack and the higher the tier, the richer that signal feed is.

Even with all of that turned on, the rep still does not have any of the following.

They do not know which specific boards on the operator's network sit in the trade areas of which specific store locations for each of those fifty chains. They do not know which corridors carry which chain's customer flow versus a competitor's. They do not know which boards own the morning-commute daypart that aligns with grocery shopping decision moments, or which boards face the wrong direction for that audience. They do not know which boards' contextual surroundings — the anchor retail, the residential density, the income mix of the immediate trade area — match each chain's positioning rather than its competitor's.

They do not know how a regional infrastructure change has shifted which audiences pass which boards on which days of the week. They do not know how a stadium opening twelve miles away changes the consumer-behavior gravity in their boards' immediate trade area. They do not know how this summer's tourism corridor traffic patterns differ from last summer's because the regional festival circuit expanded.

They do not know what to say to any of these fifty people that would distinguish their email from the other forty-three sales emails those marketing managers received this week — because the what to say depends on the synthesis between the brand activity signals the GTM stack is surfacing and the inventory and context layer the GTM stack does not.

This is the actual gap. Not the brand activity signals — those are increasingly available, and the better GTM tools provide them well. The gap is the layer underneath: the operator's own inventory DNA, refreshed against the live context around each board, as the substrate against which all of the brand signals get matched to specific assets.

The two kinds of data sales teams actually need

It's useful to separate sales data into two categories, because operators frequently treat their GTM stack as if it covers both — and end up over-investing in the one they already have while neglecting the one they don't.

The first category is brand and contact data. Who the buyers are at each target company, how to reach them, what their titles are, what's changing at their companies, what they're launching, where they're expanding, who they're hiring, what intent signals their digital behavior is throwing off. This is the territory of the modern GTM stack, and the better tools — properly configured and properly paid for — cover it well. They answer the questions who do I reach and what are these companies doing.

The second category is inventory and context data, and this is the one the GTM stack does not cover by design. It is the operator's own assets — which boards, in which corridors, with which audience profiles, daypart splits, seasonal patterns, contextual relevance — combined with the live conditions around each board that determine which advertiser activities those assets are positioned to capture. The inventory and context layer answers the question given everything we now know about the buyer's company, which of my specific boards are the right answer for them this quarter, and why.

The first category is broadly available and increasingly commoditized. The second category, for OOH specifically, has barely existed as a category. The reason it does not exist in the GTM stack is structural — the GTM stack's customers are software companies, professional services firms, and SaaS sales teams. Those customers don't need to know which trade area sits behind which billboard. They need to know that the target company has a procurement department and how to reach the procurement director. The GTM vendor's roadmap reflects who pays them.

The OOH operator who has been hoping the GTM stack would eventually surface OOH-relevant inventory matching has been waiting for a feature that is not on anyone's roadmap because the buyer for that feature is too small a fraction of the vendor's customer base to justify building it. The wait was always going to be infinite.

What an OOH-specific context layer actually looks like

If the GTM stack answers who do I reach and what are these companies doing, the OOH-specific context layer answers three further questions in sequence.

Where is this advertiser, geographically and contextually, relative to my specific inventory? Which of my boards are in this advertiser's trade area. Which corridors carry their actual customer flow. Which boards are positioned at decision moments for their category. The mapping from advertiser activity to specific assets on my specific network — the layer no horizontal tool can provide because no horizontal tool knows what my network is.

Why is this advertiser a good fit for this specific board, in this specific moment? The intersection of board-level audience composition, vertical-level fit logic, brand-level current activity, and seasonal alignment. Not generic relevance — specific relevance, refreshed weekly, against an inventory model that understands the operator's assets at the individual face level.

What should the rep actually say in the first email? The synthesis. Given the brand activity signal coming from the GTM stack, the inventory match coming from the operator's network, and the live context shaping the trade areas around each board, what is the angle that turns this contact's inbox from “another generic OOH email” into “this operator actually understood my Q2 priorities and brought me a specific answer.”

The three questions stack on top of the brand and contact layer the GTM stack already provides. They are not a replacement — they are the OOH-specific synthesis that turns horizontal sales intelligence into specific outreach against specific inventory at specific moments. Without them, even a fully-loaded GTM stack produces generic outreach with current contacts attached. With them, the rep walks into every call with the synthesis already done.

Why operators have been quietly underutilizing their sales data stack

The honest reason most operators are disappointed with their sales intelligence investment six months in is that they bought brand and contact data thinking it would solve an inventory matching problem.

The pattern is consistent. Operator signs the contract. Operator instructs the sales team to use it. Sales team uses it to build outreach lists. The lists are bigger and cleaner than before. The outreach volume goes up. Conversion does not, because the outreach itself is unchanged — generic introduction emails sent to a larger universe of generic contacts.

Six to twelve months in, the operator concludes that the tool “doesn't work” or “isn't worth what we paid” or “is fine but not transformative.” They renew the contract because the sales team would complain if they didn't, but they move it to the budget cost-cutting list.

The diagnosis is wrong. The tool is working. It is solving the problem it was built to solve. The reason pipeline didn't move is that the problem the tool solves was not actually the binding constraint on the operator's outbound motion. The binding constraint was inventory and context matching, and the operator did not buy that.

The fix is not to cut the GTM tool. The fix is to add the layer the GTM tool was never built to be. Brand and contact data plus inventory and context data, working together, is what produces the conversion lift the operator was originally hoping for. Either one alone, no matter how good, will not.

The integration logic, briefly

A reasonable question, if the argument above lands, is what the practical integration looks like between an existing GTM stack and an OOH-specific context layer.

The shortest version: the GTM stack is the source of truth for who to reach and what those companies are doing. The context layer is the source of truth for which of my boards are positioned for it, and what to say. The two systems talk to each other at the moment outreach is being prepared.

The rep, working from the context layer, sees a brand activity signal flow in from the GTM stack — a regional QSR chain announcing a Q2 value-menu push. The context layer surfaces five boards on the operator's network positioned for that push, along with the brand-specific story angle for each. The rep then pulls from the GTM stack the right contacts at that QSR chain — the regional marketing manager, the agency of record's planner, the franchisee marketing lead — and the context layer drafts the outreach using brand activity, inventory match, and live trade-area context simultaneously.

The email that lands on the regional marketing manager's desk references their specific company, their specific upcoming push, the specific boards on the specific routes their stores sit on, and offers a specific schedule for the launch window. The brand and contact data put the email in the right inbox with the right context about the recipient's company. The inventory and context data made it the email that gets read.

That integration is the actual workflow. The GTM stack and the context layer are complementary, not competitive. The mistake operators make is buying the first and assuming it will do the job of both.

The frame worth holding

OOH operators have been spending real money on sales intelligence tools for the last five years and getting a fraction of the return they expected. The reason is not that the tools are bad. The reason is that the tools are solving a different problem than the one the operator's outbound motion actually has.

The tools are excellent rolodexes. OOH operators need a rolodex and a context engine. The rolodex tells the rep whom to email. The context engine tells the rep why now, why this board, and what to actually say. Without the second layer, the rolodex produces more outbound volume but not more pipeline.

The operators reading this who are renewing GTM contracts in 2026 should ask a different question than the one they've been asking. The question is not is the contract worth it. It is is the contract working as a contact and signal database while we add the contextual and inventory layer that turns those contacts and signals into conversations. The first question has a defensive answer (yes, technically, the data is fine). The second question has a strategic answer: the data is only worth what gets done with it, and what's been missing for ten years is the layer that turns it into conversations.

The operators who treat their sales intelligence spend as the floor of their sales data investment, not the ceiling, will spend the next decade out-converting the operators who treat it as a complete solution. The rolodex is necessary. It was never going to be sufficient.

doohthis is the OOH context engine that sits on top of your GTM stack. Your existing tools tell you whom to reach and what their companies are doing. doohthis tells you which of your boards are positioned for it, and what to say. If you're paying for the rolodex but not getting the pipeline, we should talk.