Back to signature work

Perspective · Integrated demand

How I Build an Integrated Demand Engine.

I start with the growth problem the business needs to solve, then connect market focus, customer journeys, Sales partnership, measurement, investment, and organization design around it.

Demand is a business choice before it is a channel plan.

I do not begin with the question, “Which campaigns should we run?” I begin with what the company is trying to change. It may need to enter a market, recover growth, integrate an acquisition, improve conversion, create demand for a new product, or make a broad portfolio easier to buy.

That distinction matters because a channel can perform well while the business does not. Activity, response, and pipeline are useful signals, but they only become meaningful when they help the company reach the customers it can serve, give Sales something useful, and produce commercial movement.

Once the growth problem is clear, I can work backward into the choices that Marketing, Sales, Product, Finance, regions, and partners need to make together.

Focus starts with a shared account choice.

The next question is where the company will focus. At IBM AI Applications, multiple businesses, geographies, routes to market, and sales teams brought legitimate but competing account lists. I led the work to consolidate those inputs into a governed foundation of 6,005 accounts.

The number was not the accomplishment by itself. The important decision was that an account did not become a priority until Sales validated it. Marketing could bring data, intent, portfolio context, and program recommendations, but the people closest to the customer had to confirm the relationship, objective, and commercial relevance.

That shared choice made 1:1, 1:few, and 1:many motions useful rather than decorative. It created a common starting point for deciding where to invest, how much adaptation an account needed, and which teams had to participate. The deeper story is in Turning Account Lists into Growth.

Positioning has to survive contact with the growth system.

After choosing where to focus, the company still has to give the market a clear reason to care. I have often worked at the point where a portfolio or company decision had to become something customers, sellers, partners, and channels could actually use.

For IBM Sterling, IBM leadership made the decision to put a proven name back at the center of the market identity. My role was to lead the integrated go-to-market activation across web, seller readiness, campaigns, events, field marketing, partners, and pipeline governance. The Sterling relaunch shows how a positioning decision became a coordinated market motion.

At OpenText, Project KIS made the same principle visible at company scale. A rebrand and more than 150 rebuilt product pages affected search, paid media, nurture, forms, routing, attribution, field programs, partner materials, and sales plays. The website mattered, but the larger job was to carry a clearer portfolio through every system customers and sellers used.

Channels should work together around what the customer needs next.

I treat channels as different ways to help a customer or account progress, not as independent production lines. Search may reveal a need. Content can help a buyer understand it. A webinar can make expertise available at scale. A workshop or demonstration can let someone experience the product. A field program can bring the story closer to a market. An executive conversation can help an important relationship move.

The sequence changes with the customer, the product, and the commercial situation. The discipline does not. Each element needs a job, an audience, a handoff, a Sales role, a follow-up path, and a measure that tells us whether the experience helped.

That is why I manage events as part of the demand engine rather than as a separate calendar. In Giving Every Event a Job in the Growth System, I explain how I decide whether an experience should create access, teach, solve, build community, progress accounts, or strengthen market position.

Pipeline creation matters. What happens after creation matters more.

Sales partnership is not a handoff at the end of a campaign. It begins with the account and growth choices, continues through activation, and becomes most visible after an opportunity appears.

I want Marketing and Sales looking at acceptance, qualification, progression, sales cycle, wins, and revenue, not arguing from different definitions. Marketing should understand whether sellers see value in the opportunities being created, where those opportunities slow down, and what the customer behavior is telling us to change.

At IBM, this approach connected demand programs to downstream commercial outcomes. Watson Supply Chain recorded $18.9 million in marketing-sourced wins, B2B Collaboration recorded $12.8 million, and Planning Analytics recorded $4.4 million in win revenue. Those were IBM outcomes produced by broader commercial teams. Marketing did not close the business alone. My responsibility was to help build the demand, operating cadence, and performance visibility that supported those results.

The dashboard should change what the organization does next.

Measurement is valuable when it helps people make a different decision. That requires trusted definitions, a common view, and enough detail to see when a healthy total is hiding a weak product, geography, source, stage, or quarter.

Beacon grew from a path out of macro-heavy Excel workbooks into a connected reporting environment spanning pipeline, revenue, campaigns, funnel performance, and marketing return. The technology mattered, but adoption came from making the information understandable and useful in the operating rhythm.

At OpenText scale, Marketing created $908 million in quarterly pipeline, reached 112% of plan, grew 32% year over year, and contributed 42% of company pipeline. Those figures show the size of the operating environment. They are not the end of the story. In When Marketing and the Business Disagree, I explain why an aggregate pipeline result is only the starting point. The leadership work is understanding acceptance, progression, timing, conversion, and sales-win revenue, then changing course while there is still time.

Every dollar and hour should have a reason to be there.

An integrated engine makes tradeoffs visible. It helps leaders compare audiences, programs, markets, channels, and experiences without pretending they all perform the same job or should be measured the same way.

I look at what an investment was meant to change, what happened downstream, what Sales learned, and whether the result justifies repeating it. Sometimes the right choice is to increase the investment. Sometimes it needs a different audience, offer, experience, or follow-up path. Sometimes the responsible decision is to reduce it or stop.

This is not about forcing every decision into one efficiency ratio. It is about knowing whether an investment is building market position, creating access, helping an account progress, producing revenue, or teaching us something valuable enough to improve the next decision. Making Investment Decisions Before Every Answer Was Clear shows how I applied that discipline when the evidence was useful but incomplete.

The organization is the final layer of the strategy.

The engine only works when the organization can carry it. Structure, roles, technology, data, agency support, decision rights, and operating cadence have to reinforce the same priorities.

As my remit expanded, I connected demand generation, field and partner marketing, digital, web, lifecycle, analytics, marketing operations, technology, and account-based marketing across nine business units. The goal was not to centralize every decision. It was to give specialist teams clear guardrails, shared measures, and enough context to use their judgment while the business still moved as one system. An Org Chart Does Not Make a Team explains how I learned to combine that structural clarity with voice, trust, and belonging.

That is where growth and transformation meet for me. Good demand creates attention and pipeline. Great demand also helps the company focus, gives Sales something useful, learns from customer behavior, and improves where the next dollar and hour go.

What does the business need to change, and how can Marketing help it happen?

I build demand engines to answer that question with shared choices, useful experiences, commercial visibility, and an organization that can keep learning.