Marketing frameworks
that earn their keep.

Revenue marketing connects marketing decisions and investment to customer acquisition, commercial outcomes, retention, and expansion. The ambition is more repeatable and scalable growth, with a clearer understanding of how marketing contributes. Predictability is an objective, not a guarantee that comes with the terminology.

Clicks and impressions are not automatically vanity metrics. They become vanity metrics when they are presented as success without a useful connection to the objective. Relevant reach may tell you whether the intended audience is encountering your work. A click can reveal interest or confusion. Neither, by itself, explains whether the business is becoming healthier.

I would also resist the claim that anything we cannot trace neatly to pipeline has no value. A referral, a remembered story, a conversation at an event, or months of useful reading may influence a purchase without leaving a complete digital record. Revenue accountability should make us more honest about evidence, including its gaps.

Several approaches that appear on lists of revenue marketing frameworks actually belong to different categories. PLG is a growth approach. The T-shaped marketer is a skills model. Attribution is a measurement method. RM6 addresses organizational maturity. Comparing them as interchangeable systems would be like asking whether a telescope is better than a laboratory notebook. First tell me what you are trying to do.

A marketing framework is a structure for organizing questions and decisions. A methodology adds a way of working through them. A marketing strategy contains the choices your business makes. A plan assigns the activities, resources, timing, and responsibilities required to act on those choices.

Those distinctions matter because completing a framework does not automatically produce a strategy.

You can fill every box in a positioning worksheet without finding a meaningful reason for customers to choose you. You can document a customer journey without improving a single frustrating interaction. You can purchase a platform that supports sophisticated nurturing before deciding what a useful conversation with a prospect should sound like.

The value appears when the structure changes a decision. Perhaps you stop pursuing an audience that generates inquiries but rarely buys. Perhaps you discover that the website attracts appropriate buyers, but the proposal process loses them. Perhaps you protect a valuable brand investment because the business has finally agreed on how and when to evaluate it.

A useful framework makes those choices easier to explain and harder to avoid.

You usually need more structure when the business has become too complicated to run on shared assumptions.

That can happen in a small company with an owner, a salesperson, and two outside vendors. It can also happen in an enterprise with specialized teams that each maintain their own definition of success. Size changes the number of handoffs. It does not eliminate the need for agreement.

The warning signs tend to be familiar:

• Every new campaign begins with another debate about the audience and message.
• The business attracts attention but cannot connect it reliably to appropriate inquiries, opportunities, purchases, or retention.
• Sales and marketing disagree about what makes someone qualified.
• Nobody can explain which part of the customer journey needs attention first.
• Technology purchases keep increasing while manual work and reporting disputes remain.
• Growth depends on one person remembering what happens next.
• Expansion into a new market exposes assumptions that worked only in the original one.

A framework is also useful before a major change: a repositioning, a new service, a CRM migration, an acquisition, or a shift from transactional sales to longer relationships.

There are occasions when a full framework exercise is unnecessary. If a qualified customer submits a form and nobody receives the notification, fix the notification. You do not need a strategic retreat to establish that answering people is generally good for business.

The amount of structure should fit the decision. A small business may need a one-page operating agreement. A multinational organization may need formal governance, shared data definitions, and a staged implementation program. Both need clarity.

STP: deciding whom you will serve and why they should choose you

Segmentation, targeting, and positioning, commonly shortened to STP, addresses three foundational decisions. How does the market divide into meaningfully different groups? Which groups will you prioritize? What position will you occupy in their minds relative to the alternatives?

Its great strength is forcing selectivity. “Business owners” is an audience description, but it is rarely specific enough to guide a strong offer. An independent hotel owner trying to reduce reliance on third-party bookings has different concerns from an investment group evaluating the repositioning of several properties.

Both may operate in hospitality. That does not mean they should receive the same message, evidence, or proposal.

STP works especially well when a business is entering a market, sharpening an indistinct offer, or attracting too many poorly matched inquiries. It helps connect market opportunity with an audience the business can serve credibly and profitably.

Its limitation is that segmentation can become an exercise in labeling people. Age, revenue, job title, and location may help identify an audience without explaining why that audience buys. Positioning can also remain an internal statement that never survives a real customer conversation.

The test is whether the choices change your offer, your proof, your priorities, and the work you decline. If every segment still receives the same campaign, the segmentation has accomplished very little.

The 4Ps and 7Ps: examining the whole offer

The classic marketing mix considers product, price, place, and promotion. The expanded 7Ps adds people, process, and physical evidence. The Chartered Institute of Marketing’s explanation of the 7Ps is a useful reference.

I appreciate this approach because it keeps marketing connected to what customers actually receive. Advertising cannot carry the entire burden of an offer whose pricing, availability, delivery, or credibility creates resistance.

Consider a premium hospitality experience. The photography may be exceptional, but the booking process may be confusing. The room rate may communicate luxury while the confirmation email reads like a utility notice. The promotional promise and the delivered experience are now arguing with each other.

The 7Ps is particularly useful for service businesses, where employees, procedures, and tangible signs of quality influence confidence before a purchase. It helps reveal when the apparent communications problem originates elsewhere in the business.

Its limitation is that it is a diagnostic checklist, not a complete operating sequence. Listing weaknesses across seven categories does not tell you which change deserves the next dollar. You still need customer evidence, economic judgment, and a clear priority.

Jobs to Be Done: understanding the progress behind a purchase

Jobs to Be Done examines the progress someone is trying to make in particular circumstances. It helps move a discussion beyond demographic descriptions and product features.

A buyer looking for a marketing consultant may be trying to understand a disappointing quarter, regain confidence before a board meeting, enter an unfamiliar market, or find someone who can turn conflicting vendor recommendations into a coherent decision. The requested service is only part of the story.

The strength of this approach is the quality of questions it encourages. What changed? Why is the current solution no longer adequate? What makes the buyer hesitate? What would a successful decision allow that person to accomplish?

It is particularly valuable for customer interviews, offer development, positioning, and content that addresses the circumstances surrounding a purchase. A useful article answers the question the buyer is wrestling with, including the concern they may not yet know how to articulate.

Its limitation is that a compelling interview can be mistaken for a market. One person’s explanation is a clue, not proof of widespread demand. Interviews need to be considered alongside observed behavior, commercial viability, and evidence from other customers. Understanding motivation also does not supply a campaign calendar, a sales process, or a reporting system.

SOSTAC: turning analysis into an accountable plan

PR Smith’s SOSTAC organizes planning around Situation, Objectives, Strategy, Tactics, Action, and Control. It asks where you are, where you want to go, how you intend to get there, what you will do, who will do it, and how you will evaluate progress.

Its strength is the connection between thinking and implementation. A channel recommendation has to sit within a strategy. A strategy has to serve an objective. Activities need ownership, and results feed the next round of planning.

This is useful for annual planning, launches, agency briefs, and businesses whose marketing consists of a growing list of disconnected initiatives. It gives a plan a structure that other people can interrogate.

The limitation is not a missing box. It is the temptation to fill every box politely. A team can produce an extensive situation analysis, choose an unconvincing objective, and proceed as though the document has solved the underlying problem.

SOSTAC works best when the strategy section contains actual tradeoffs and the action section names people with enough authority and capacity to deliver. A task assigned to “the team” is often a task assigned to hope.

RACE: connecting discovery, action, conversion, and the ongoing relationship

Developed by Dave Chaffey at Smart Insights, RACE covers Reach, Act, Convert, and Engage, supported by an initial planning stage.

Its strength is helping a business see beyond acquisition. Getting discovered, encouraging a useful interaction, earning a conversion, and building an ongoing relationship each require attention. A company can be excellent at one and weak at another.

RACE is useful when a digital program needs clearer priorities and measurement across the customer lifecycle. For example, a website may earn relevant organic traffic but offer little help to someone comparing options. More traffic would enlarge the audience encountering the same weakness.

The limitation comes when the categories become a literal prediction of buyer behavior. People revisit decisions, involve other stakeholders, disappear for months, and return through a different channel. The framework organizes the business’s work; it should not force every person into a neat procession.

It also requires judgment about what counts as meaningful action. A download is easy to measure. Its importance depends on who downloaded it, why, and what happened afterward.

Account-based marketing: coordinating around the accounts that matter

Account-based marketing, or ABM, concentrates coordinated marketing and sales effort on selected accounts. Salesforce’s explanation of ABM describes the focus on specific valuable accounts and personalized engagement.

Its strength is recognizing that a substantial B2B purchase usually involves more than one person. The operational champion, financial approver, technical evaluator, and executive sponsor may each need different evidence.

ABM is well suited to a defined market with valuable opportunities, complex buying groups, and enough potential return to justify deeper research and coordination. A specialist firm pursuing a limited number of appropriate enterprise customers has a different challenge from a retailer seeking thousands of modest transactions.

The limitation is cost and concentration. Personalization takes work. Bad account selection can direct significant resources toward organizations that were never likely to buy. A target-account list also becomes stale if it is treated as a permanent declaration instead of a working hypothesis.

Putting a prospect’s logo on a landing page is not the hard part. Understanding that organization’s priorities and coordinating a relevant response is.

The Pedowitz Group is a consulting and services firm focused on revenue marketing. Its published service offering spans strategy, marketing operations, revenue operations, demand generation, account-based marketing, marketing technology, creative work, content, and AI-related services.

That breadth is relevant to understanding RM6. The framework sits within an effort to connect organizational capability with implementation, rather than functioning only as a campaign-planning worksheet. The group’s work includes assessing the current situation, identifying priorities, and helping businesses implement and operate the capabilities needed to improve performance.

Its public maturity model describes four stages: Traditional Marketing, Lead Generation, Demand Generation, and Revenue Marketing. I read that progression as a useful prompt to examine the distance between producing activity, generating interest, and understanding business contribution.

My admiration here is for the system and the thinking behind it. This is an independent perspective, not a claim of partnership, certification, or involvement in The Pedowitz Group’s work. For its formal RM6 assessment and methodology, go directly to the group.

I would give RM6 serious consideration when a business has several interdependent marketing problems and needs to decide what to fix first. It is especially relevant to organizations with meaningful sales cycles, multiple teams, and technology that has become more capable than the operating practices around it.

The limitation of a broad maturity framework is that it can become another large program if nobody translates the diagnosis into a manageable sequence. Six pillars should not automatically become six simultaneous transformation projects.

A small firm may benefit from examining all six areas and then making three modest changes: defining an appropriate inquiry, assigning follow-up ownership, and recording outcomes consistently. That is a legitimate improvement even without a large implementation budget.

There is also a risk in interpreting revenue accountability too narrowly. A business still needs reputation, distinctive positioning, useful education, and relationships with people who are not ready to buy today. Long-term value does not disappear because it is harder to assign to a single campaign.

I would apply the model with two guardrails. First, use maturity findings to prioritize observable changes, not to pursue a score for its own sake. Second, match measurement to the purpose and time horizon of the work. A quarterly pipeline report cannot fully evaluate every investment a brand should make.

The Revenue Waterfall has evolved beyond counting individual leads

Earlier SiriusDecisions Demand Waterfall models helped teams standardize lead stages such as inquiry, marketing-qualified lead, and sales-accepted lead. That historical contribution matters, especially in organizations where departments still count different things under the same label.

However, the Forrester B2B Revenue Waterfall extends the approach to buying groups and both new and existing customer opportunities. Describing the current model as an anonymous-visitor-to-MQL pipeline would miss that development.

The strength of waterfall thinking is operational precision. You can examine conversion, elapsed time, and stalled opportunities using agreed stages. In a buying-group approach, several people researching the same purchase can be understood as part of one commercial opportunity rather than celebrated as unrelated leads.

The risk is treating a status field as reality. Sales accepting a lead does not necessarily establish an opportunity. An opportunity being created does not prove that a serious evaluation exists. Stage criteria need evidence, and progress should reflect the customer’s situation as well as your internal activity.

This approach is especially useful for complex B2B organizations with contested pipeline numbers, multiple stakeholders, and meaningful handoffs. It takes disciplined data practices to maintain; a smaller business should keep only the stages it can define and use consistently.

Lead-to-Revenue connects the rules to the actual work

Lead-to-Revenue, often abbreviated L2R, is a broad lifecycle and operating concept rather than one universally standardized proprietary framework. It connects initial interest, qualification, sales handling, opportunity progression, and revenue outcomes.

Its strength is making the transitions explicit. A service-level agreement, or SLA, should say what triggers action, who owns it, what response is expected, and what happens if the owner cannot act. It should also explain recycling, rejection, and later follow-up.

For example, a proposal request from an appropriate account should not sit in the same queue as a student downloading an industry guide. Nor should that student be treated rudely because the inquiry has no immediate sales value. A sound process routes each situation appropriately.

L2R is useful when a CRM and an automation platform exchange data but the people using them remain disconnected. Its limitation is the possibility of bureaucratic precision: twelve statuses, eight required fields, and nobody available to answer the customer. Keep the process proportional to the decision it supports.

ABM, account-based revenue, and account-based experience are related ideas with different emphasis. ABM organizes marketing around selected accounts. Account-based revenue generally broadens the responsibility across revenue-facing teams. ABX, as described by Demandbase, emphasizes the experience of the account across interactions and stages.

An ideal customer profile, or ICP, helps identify organizations likely to be a good fit. It is not the same thing as a buyer persona, which describes a person or role. A target-account list translates those criteria into specific organizations worth pursuing.

Tiering helps determine how much attention each account justifies. A small number may merit deeply researched, individual programs. A larger group may be served through relevant industry or challenge-based work. The economics should support the effort.

Consider a consultancy pursuing a hotel ownership group. The operations leader, finance team, property managers, and ownership may share a business problem but evaluate the proposed solution differently. Coordinated communication should help them make a decision together. It should not mean four departments sending four campaigns to the same organization.

These approaches work best when account value and buying complexity justify coordination. Their limitations include costly research, weak identity matching, and the temptation to mistake intent signals for an invitation. Someone researching a subject is not automatically asking to be pursued. Track account progression, relevant stakeholder involvement, opportunity quality, and retention rather than congratulating yourself for reaching a long list of names.

Product-led growth, or PLG, uses the product experience as a major driver of acquisition, adoption, retention, and expansion. Trials and freemium offers are common mechanisms, but giving something away does not, by itself, create a product-led business.

Its great advantage is letting people experience value instead of asking them to imagine it from a presentation. A useful first experience can answer questions that no amount of promotional copy will settle as convincingly.

A product-qualified lead, or PQL, uses product behavior and appropriate fit to identify a promising next step. ProductLed’s explanation of PQLs is useful here. A PQL can complement MQLs in a hybrid business; it does not have to replace every other qualification method.

For a collaborative reporting product, a meaningful signal might involve connecting a real data source, building a usable report, and sharing it with a colleague. Logging in repeatedly is less informative if the person cannot accomplish anything. The actual qualification rule should be validated against conversion and sustained customer value.

Time-to-value, or TTV, asks how long it takes someone to reach a meaningful benefit. Define both the starting point and the value event before comparing results. Shortening onboarding by removing necessary setup may improve one metric while leaving users less prepared to succeed.

PLG works best when customers can reach value through a manageable self-service experience. It becomes harder when implementation, security review, procurement, or organizational change must happen first. Sales assistance may remain essential.

Lower acquisition costs are possible, not automatic. Free users consume infrastructure and support. Product development and lifecycle work cost money. Evaluate paid conversion, retention, expansion, cost to serve, and acquisition economics together. A large free-user population can be evidence of demand or an expensive audience with no reason to pay.

Four useful RevOps lenses: people, process, data, and technology

Revenue operations, or RevOps, coordinates the operating foundations that marketing, sales, and customer-facing teams share. A common four-part treatment examines people, process, data, and technology. Different practitioners organize the categories differently, so I would not treat one list as an industry standard.

Revenue marketing and RevOps overlap, but one does not inevitably turn into the other. Revenue marketing concerns marketing’s contribution to commercial outcomes. RevOps helps establish the shared responsibilities, information, systems, and procedures that make cross-functional execution possible.

Its value becomes obvious when the same customer has three conflicting statuses in three platforms. Someone must own the definition, the authoritative record, the correction process, and the consequences for communication. That is operational work with a direct effect on customer experience.

RevOps is most useful when organizational complexity has outgrown informal coordination. Its danger is becoming a reporting department that serves internal requests while losing sight of customers. Review whether the work improves decisions, reduces avoidable effort, and helps customers move forward. Producing more dashboards is not a sufficient outcome.

The T-shaped marketer connects breadth with depth

The T-shaped marketer is a skills model. The horizontal bar represents working knowledge across disciplines. The vertical stem represents deeper expertise in a particular area. It offers a useful way to plan development and hiring without assuming everyone should master everything.

A strong technical SEO specialist benefits from understanding positioning, conversion, analytics, and writing. A CRM specialist should understand the sales conversation their workflows support. A strategist needs enough technical literacy to distinguish a real implementation constraint from a habit nobody has questioned.

The advantage is collaboration. People can recognize how their work affects the next person and know when specialist judgment is needed. It fits naturally into the People dimension of an RM6-style discussion.

Its limitation appears in job descriptions seeking an expert in strategy, paid media, design, analytics, development, copywriting, CRM, and video, preferably at an entry-level salary. Breadth is awareness and competence sufficient to collaborate. It is not eight full-time specialties hiding inside one employee.

Use the model to map coverage and development needs. Judge depth through work, reasoning, and outcomes. A colorful skills chart should help a team become more capable, not create another way to overstate proficiency.

Demand generation builds awareness, understanding, interest, and preference. Lead generation identifies people or organizations that may become customers and creates a way to continue the conversation. A business can need both.

Gating is a separate decision. A useful consultation request is a form and a strong signal of interest. An ungated article may create demand but produce no immediate identifiable contact. Neither format tells you the quality of the strategy by itself.

My preference is to make substantial expertise easy to access when the reader needs it. If someone is trying to decide whether I understand their problem, forcing them to surrender contact details before I answer a basic question adds little value. A form becomes more reasonable when there is a useful exchange: a tailored assessment, a scheduled discussion, or something that genuinely requires context.

The limitation of aggressive lead generation is confusing contact collection with readiness. The limitation of loosely managed demand generation is claiming every unmeasured activity builds the brand. Both deserve evidence appropriate to the work.

For a complex service, I would examine the quality of conversations, the questions prospects arrive with, progression through evaluation, win rate, and commercial value. Compare similar segments and time periods. I would not promise that ungated content makes deals close a fixed percentage faster. Buying circumstances, deal complexity, and the offer all matter.

You do not need to choose one framework and swear allegiance to it. You do need to avoid building a separate planning bureaucracy around each one.

One sensible combination would use STP to select an audience, Jobs to Be Done to understand its buying circumstances, and the 7Ps to inspect the offer. SOSTAC could organize the plan, while RACE helps structure lifecycle activity. RM6 could provide a broader view of whether the people, processes, systems, and measurement can support the intended result.

ABM belongs in that arrangement only if the market and deal economics justify account-specific attention. It is not an obligatory badge of sophistication.

The test for combining frameworks is straightforward: does each addition resolve a different decision? If two approaches produce essentially the same conversation and documentation, simplify.

A framework becomes operational when its decisions appear in the systems people use every day.

CRM software helps manage relationships, records, ownership, and commercial activity. Marketing automation supports repeatable actions such as segmentation, communication, scoring, routing, and follow-up. Product suites overlap, and the exact capabilities depend on the products and editions a business has purchased.

The framework supplies the reasoning behind the configuration. It helps determine who belongs in an audience, what qualifies someone for a next step, which communication would help, when a human should intervene, and how the outcome will be recorded.

There is no universal “install RM6” button that creates this agreement. The decisions must be translated into configuration, tested, and maintained.

HubSpot

HubSpot’s lifecycle stages and workflow capabilities can support defined transitions, record updates, and follow-up actions. The business still needs to decide what those transitions mean.

For example, a content download could establish interest without making someone sales-ready. A direct request for a discussion may warrant immediate attention even when that person has little prior recorded engagement. The framework should help distinguish those situations before a workflow treats them as equivalent.

Adobe Marketo Engage

Adobe Marketo Engage supports marketing automation and buyer engagement. A framework can guide the audiences, program logic, nurture content, qualification criteria, and sales coordination that the platform executes.

The practical challenge is consistency across programs. If each campaign defines qualification differently, more sophisticated automation can make the inconsistency harder to trace. Shared definitions should precede an expanding library of automated programs.

Salesforce

Salesforce is a family of products, so a discussion should distinguish CRM responsibilities from the marketing automation products connected to them. Salesforce’s Sales Cloud material describes the use of account information in ABM, while Account Engagement supports B2B marketing automation.

A useful implementation connects marketing activity with the account, the relevant people, and the commercial opportunity. It also gives sales a practical way to report what happened. A technically successful integration has limited value if users cannot explain why an inquiry was accepted, rejected, postponed, or won.

Oracle Eloqua

Oracle Eloqua’s lead-scoring documentation explicitly calls for marketing and sales to define criteria together. Its separation of profile and engagement is a useful example of why fit and activity deserve different consideration.

A highly active person may be a poor commercial fit. An appropriate decision-maker may have a limited digital trail. Framework-led scoring asks which evidence matters to this business and checks that judgment against subsequent outcomes, rather than assuming a busy contact is a good opportunity.

The wider Adobe environment

Marketo is already an Adobe product. If someone says “Adobe” as a separate platform option, the next question is which product and responsibility they mean. Adobe’s broader offering includes Journey Optimizer B2B Edition and related B2B capabilities, including support for buying-group journeys.

The implementation question remains practical: which system owns each piece of data, which system initiates each action, and how do teams prevent conflicting communications? A larger product ecosystem increases the importance of clear responsibilities.

Connecting platforms requires more than getting records to move between them. A useful design specifies field ownership, unique identifiers, account relationships, permitted stage transitions, synchronization timing, and what happens when a transfer fails.

Consent and communication preferences also need to remain consistent across the systems that act on them. Someone opting out should not be reintroduced to the same marketing stream through another list. An existing customer should not receive an introductory sales sequence because one platform has not received an updated status.

Scoring needs review, too. The weights assigned to behavior are hypotheses. If the contacts scoring highest rarely become appropriate opportunities, the model needs investigation. Raising the threshold may hide the symptom without correcting the logic.

Reporting requires equally clear agreements. Define sourced pipeline and influenced pipeline separately. Decide how opportunities connect to campaigns and how duplicate associations are handled. Do not add the full value of the same opportunity across several campaigns and present the total as new revenue.

Attribution helps describe recorded relationships. Establishing incremental impact requires additional reasoning and, where feasible, experiments or credible comparisons. A dashboard can be internally consistent and still encourage an incorrect conclusion.

This is why marketing automation and workflow design needs a business perspective as well as technical competence. The system should support a sensible customer experience and a workable operating process.

Consider a hypothetical specialist consulting firm in the professional services market. It publishes strong educational content and receives regular inquiries, but too few become worthwhile engagements. Leadership’s first thought is to buy more traffic.

An initial review discovers three different problems. Some inquiries concern services the firm does not offer. Appropriate prospects receive generic follow-up. Sales records outcomes inconsistently, making it difficult to distinguish poor fit from poor handling.

STP would help clarify whom the firm wants to serve. Jobs to Be Done could improve understanding of what prompts those buyers to seek help. The 7Ps might reveal that the proposal process introduces unnecessary uncertainty. RM6 provides a way to examine the capabilities surrounding the whole situation.

The resulting changes could be modest but connected. The website explains scope more clearly. The inquiry form gathers enough context to route the request without demanding a fully formed brief. A suitable inquiry receives an accountable owner and relevant background. A request outside the firm’s scope receives an honest response. Open opportunities stop receiving generic introductory messages.

The CRM records consistent outcome reasons. Marketing and sales review a sample of accepted and rejected inquiries together. An automation failure creates an exception someone can see and resolve.

Success would be judged through the quality and handling of opportunities, conversion, commercial value, and the experience of the people making contact. Inquiry volume might rise or fall. Either result requires interpretation.

This is an illustration of how the approaches can work together, not a client case study or a forecast. Its purpose is to show why the first useful change may occur well before the next campaign launches.

Choose one business outcome and one visible constraint. Establish what is happening now using real inquiries, actual sales records, customer conversations, and the work people perform. A framework will be more useful with imperfect evidence than with polished assumptions.

Then agree on the smallest meaningful change. Assign an owner who can implement it. Define how the team will recognize improvement and when there will be enough evidence to review it. Test ordinary cases and exceptions before expanding automation.

For a long sales cycle, an early review might evaluate response time, qualification consistency, or progression into substantive discussions. Revenue evidence may require longer. Choose the review period to fit the behavior being measured.

Keep the documentation useful to the people doing the work. If maintaining the framework begins to consume more attention than improving the customer experience, reduce it.