At one conference, we turned our booth into a live product demo so the sales reps could show the platform instead of describing it. I spent much of that show watching what drew buyers in and what made them drift away. Those observations went back into our messaging and into sales training. Watching buyers handle the product told me more about how they thought than anything we had written about them in advance. The booth and the product work below come from my years at Funnelback, a full-time role years before Cedar Collaborative existed, not a Cedar Collaborative engagement.
That kind of learning is hard to get when marketing is organized as a department that produces things. In many companies the function is defined by its outputs, the campaigns and collateral that other teams request. Each request arrives from somewhere else in the business, and marketing’s job is to fulfill it well. The arrangement is tidy and easy to staff. It also leaves marketing working from secondhand information, at a distance from the places where customers meet the product.
Product
The more useful position is closer to the work. At Funnelback, the North America team noticed that the enterprise product could reach a new segment if it shipped with templates built on industry best practices. The idea came out of working alongside the product team while they were experimenting, close enough to speak the product team’s language when it mattered. The templates made rollouts faster and less costly for clients, and they opened a segment the product hadn’t reached before. A request queue would never have surfaced that opportunity.
Sales
Sales hears what stalls deals and what competitors are promising, and marketing that stays away from sales calls is guessing at both. I sit in on sales conversations and take some of them myself, which is the fastest way I know to learn which claims land and what words buyers use for their own problems. The booth demo was a version of the same thing. A conference is one of the few settings where marketing can watch a buyer react in real time, and treating it as a place to hand out collateral wastes the chance.
Finance
Finance tracks where every dollar goes, and conversations with marketing can easily turn into a defense of spend. I’ve found it more useful to treat the relationship as shared learning. With finance teams I’ve built dashboards that tie marketing activity to renewals and revenue, which gives both sides the same picture to argue over. The relationship also runs the other way. Marketing tends to pick up shifts in buying behavior or pricing pressure before they show up in the financials, and when those signals reach finance early, budgets and timing can move ahead of the results instead of chasing them.
Leadership
The complication shows up at the leadership table. A CEO’s growth goals, a revenue leader’s targets, the product roadmap and the CFO’s budget limits can each be sound on their own and still pull against one another. In one case the CEO wanted to enter a new market, the product lead wanted more development investment and finance wanted a hiring freeze. Each position was defensible. What helped was putting the data and each group’s goals side by side, so the tradeoffs were visible in one place, and the strategy that came out of that conversation balanced speed against sustainability.
That translation work depends on marketing being trusted to represent each perspective honestly. Sometimes it means saying “not yet” to a move leadership is excited about, and sometimes it means pushing for a bigger one than anyone proposed. Contractors and junior staff can run campaigns well, but this role requires someone with enough standing to move between a board meeting and a sales call and carry what they heard from one into the other. The same pattern holds outside the private sector; I’ve written separately about how siloed teams play out in nonprofits.
What connects the pieces
I often start an engagement by drafting a corporate manifesto, even when it ends up living in a leadership drawer. Its main use is as a reference point the functions can share, a reminder that they are working toward the same purpose. The insight that changes a strategy usually arrives in small moments, like a raised eyebrow in a sales meeting or a prospect lingering at a booth longer than expected.
What I haven’t resolved is where that connective work belongs in an organization. It doesn’t map cleanly to an org chart, and its value shows up in other teams’ results, which makes it easy to cut and hard to defend in a budget review. A company can see marketing’s outputs at a glance. Whether it can see the connections marketing maintains, and who would notice when they stopped, is a harder question.