Sofia O'Malley

Familiarity inside the company starts to feel like fatigue.

• The reflex is to refresh the campaign or introduce a new theme, but they treat that as a misread signal.
• The post offers four questions to answer first: has the customer changed, has the category shifted, is the positioning no longer differentiated, and is the message no longer working?
• If the answer is no, the problem is internal, not a market signal.

Salesforce is the worked example: more than two decades of building on one underlying idea through Dreamforce, community, customer success, and later Trailblazers, with the expressions evolving while the story was not reinvented. O'Malley draws the rule directly: change when the market gives you a reason, not when the organization gets bored.

Read original

Across categories, one-time transactions are giving way to subscriptions, consumption-based pricing, and hybrids of the two.

• When value is realized over time, the sale stops being the finish line and becomes one point in an ongoing relationship.
• That changes which signals matter: what the customer is using, where they find value, where adoption is slowing, and what they might need next.
• O'Malley notes those signals are easier than ever to capture, but turning them into growth requires connecting them across the journey.
• That, in turn, changes how marketing, sales, product, and customer success work together: less as a series of handoffs and more around a continuously evolving view of the customer.

Software is the easiest place to see the shift — O'Malley points to anyone who has looked at their own subscription list lately — but the argument is explicitly broader than software. The post closes by observing that the most advanced teams already design go-to-market this way while most are still organized around the transaction.

Read original

Each can look internally like a function doing its job, but to the customer it is one company.

• They conclude that some of the hardest go-to-market problems are not functional problems but problems between functions — and often nobody fully owns them.
• The opportunity is not better marketing, better sales, or better customer success individually, but designing the system so the customer experiences the business as one.

The repeated-information scenario is the concrete one: a customer has to supply something the company already holds because it never crossed the handoff. O'Malley pairs it with an expansion conversation that opens without reference to the experience that came before, showing how a sales motion can be internally sound and still read as a single broken company to the buyer.

Read original

O'Malley argues against changing the market-facing story without a market reason, while also arguing that most companies need to redesign how go-to-market works for recurring revenue.

• The two changes are in different places: the positioning and message stay put while the operating model — ownership, signals, and cross-functional handoffs — changes.
• The recurring sign-off, 'Strategy First.
• Always.', states the ordering they apply throughout: strategic choices lead operational and creative ones, rather than the other way round.

The contrast between the Salesforce example and the journey-centric argument makes the distinction concrete: Salesforce kept compounding one idea in public for over two decades, while the internal work of community, customer success, and ecosystem building kept changing. The message was the stable part; the system around it was not.

Across the three posts, the emphasis moves from the message to the revenue model to the customer's experience of the organization. The constant: a strategic decision should come first, and the operating model should follow.

Read original · Original 2 · Original 3

See how O'Malley separates an internal feeling from an actual market signal.

O'Malley argues that company insiders see the same positioning, message, creative, and campaign every day, while customers encounter them only occasionally among hundreds of competing messages.

• Familiarity starts to feel like fatigue.
• The post challenges the reflex to refresh a campaign or swap in a new theme, and lays out four things to check first: has the customer changed, has the category shifted, is the positioning no longer differentiated, or is the message no longer working?
• Salesforce is the worked example: more than two decades building on one underlying idea through Dreamforce, community, customer success, and later Trailblazers, with the expressions evolving rather than the story being reinvented.
• O'Malley's rule: change when the market gives you a reason, not when the organization gets bored.

For brands planning a campaign

A useful opening frame for strategy consulting when a client arrives wanting a rebrand but cannot say what changed in the market. Four questions turn that instinct into a diagnostic, and the Salesforce example shows how to hold a position longer than internal stakeholders find comfortable.

O'Malley's core argument: the sale is one point in a relationship, not the finish line.

O'Malley argues that revenue models have become continuous while most go-to-market models have not.

• The shift is from one-time transactions toward subscriptions, consumption-based pricing, and hybrids of the two — easiest to see in software, where anyone can look at their own subscription list, but not limited to software.
• When value is realized over time, the sale stops being the endpoint, and the signals that matter change: what the customer is using, where they find value, where adoption is slowing, and what they might need next.
• Companies can capture those signals more easily than before, O'Malley notes, but turning them into growth requires connecting them across the journey.
• That changes how marketing, sales, product, and customer success work together: less as a series of handoffs, more around a continuously updated view of the customer.
• The most advanced teams already design go-to-market this way, while most are still organized around the transaction.

For brands planning a campaign

Directly relevant to integrated go-to-market advice: O'Malley ties organizational design to the revenue model rather than treating them as separate questions. A campaign or consulting brief can use the signal list — usage, value, slowing adoption, next need — to guide cross-functional measurement.

Start here to understand why cross-functional go-to-market work keeps stalling.

O'Malley lists how customers feel a company's internal structure: marketing tells one story and sales another, context gets lost in the handoff, customers repeat information the company already knows, and expansion conversations happen without understanding what came before.

• Internally, different functions may see themselves as doing their jobs; to the customer, it is one company.
• The post argues that some of the hardest go-to-market problems live between functions, where nobody fully owns them.
• The opportunity is not better marketing, sales, or customer success in isolation, but a system that lets the customer experience the business as one.

For brands planning a campaign

Gives an agency concrete language for diagnosing gaps between teams and a reason to frame engagements around ownership of cross-functional problems rather than a single department's performance. Useful when scoping work across marketing, sales, and customer success.

Before changing a campaign, they recommend asking whether the customer, category, or competitive differentiation has actually changed, or whether the message has stopped working. The post uses Salesforce as an example of a brand that kept compounding an ecosystem idea over two decades—Dreamforce, community, customer success, later Trailblazers—while the expressions evolved.

Diagnostic questions: Has the customer changed?

• Has the category shifted?
• Is the positioning no longer differentiated?
• Is the message no longer working?

O'Malley recommends changing the story when the market gives a reason. The argument is against undirected refreshes, not all change.

For brands planning a campaign

For an integrated go-to-market consulting engagement, O'Malley can pressure-test whether a brand needs a new story or more consistent repetition. An agency should show evidence of market change—not just internal fatigue—before proposing a repositioning.

Examples: Source 1

When value is realized over time, the sale becomes one point in an ongoing relationship.

• The signals that matter shift to product usage, where customers find value, where adoption slows, and what they may need next.
• Turning those signals into growth requires connecting them across the journey and aligning Marketing, Sales, Product, and Customer Success around a continuously evolving view of the customer.

Journey-centric GTM model: treat the sale as one point in an ongoing relationship, capture usage and value signals, and connect them across functions.

For brands planning a campaign

This topic suits an agency pitching integrated GTM strategy to subscription, consumption, or hybrid-revenue businesses. The engagement can focus on designing cross-functional journey ownership, defining leading adoption and value signals, and moving teams from handoffs to a shared customer view.

Examples: Source 1

They feel it when Marketing and Sales tell different stories, when context is lost in a handoff, when they must repeat information the company already knows, or when an expansion conversation happens without understanding their prior experience.

• Internally, these can look like separate functions doing their jobs, but to the customer it is one company.
• The hardest GTM problems are often the ones between functions—and those are often the ones nobody fully owns.

Design the system so the customer experiences the business as one, starting with the handoffs and ownership gaps between functions.

For brands planning a campaign

An agency can use this lens for customer-experience audits, cross-functional GTM workshops, and ownership mapping. The work should identify gaps between functions and assign ownership of a shared customer journey rather than optimize Marketing, Sales, or Customer Success in isolation.

Examples: Source 1

Each post opens with a sharp reframe, develops one argument through familiar business examples, and closes with the recurring sign-off 'Strategy First. Always.' The posts rely on diagnostic questions and cross-functional framing rather than data dumps or step-by-step templates.

For brands planning a campaign

For a consulting engagement, this approach suggests O'Malley can translate strategic arguments into accessible executive content and workshop prompts. An agency can assess whether this style fits an advisory engagement that needs clear framing.

Examples: Source 1 · Source 2 · Source 3

Zumair argues that buying decisions often move before pipeline attribution can see them; O'Malley argues that a sale is one point in a longer relationship.

Zumair builds each post around published research and named figures — Forrester, Gartner, 6sense, McKinsey — then asks readers what to track, framing each post as a measurement argument in progress. O'Malley makes no statistical claims, states positions as conclusions, and closes with a fixed sign-off rather than a question.

Read original · Original 2

Fetterman's reflections on category creation and which marketing functions need to exist overlap with O'Malley's interest in ownership, cross-functional structure, and strategy preceding structure.

Fetterman draws on operator experience — leading marketing at Plex Systems and watching buyers change the language from "SaaS ERP" to "Cloud ERP" — and works through open questions in numbered sequences, openly unsure where AI ownership lands. O'Malley argues from general business observation, without personal history, and presents each position as settled.

Read original · Original 2

That principle underpins O'Malley's warning against refreshing a story out of internal fatigue.

Adams writes for professional services and business development audiences, covering event and tradeshow execution — lead time, messaging cadence, follow-up — with checklist formatting and a question to readers. O'Malley focuses on strategy and operating design inside software and subscription businesses.

Read original · Original 2

The two posts argue that consistency beats cleverness: repeating one message, showing up when results are not immediate, and following up when it would be easier to move on build trust.

• They also argue that event timing is strategy, built from lead time, a messaging cadence, and post-event follow-up.
• That maps well to a campaign repeatedly restarted before the market remembers it, or a conference and tradeshow program planned late and dropped after the event.
• In those cases, the client needs a repeatable calendar and follow-up discipline, which Adams addresses directly.

The tradeoff is scope.

• The posts focus on message repetition and event momentum; they do not address redesigning how marketing, sales, product, and customer success share one view of the customer, the core of the agency's stated need for Sofia O'Malley.
• A client whose main problem lies in cross-functional handoffs would get a narrower answer.
• The two posts also offer limited evidence of the practice beyond consistency and event timing; ask for examples of work in those areas.

Examples: Source 1 · Source 2

The two posts argue that B2B marketing faces a measurement problem: buyers form and rank shortlists before sales engages, much of that influence happens in AI and conversational search where analytics records no click or form fill, and marketing should be judged on whether it shaped the decision rather than on interactions created.

• Zumair names the metrics to consider — AI visibility, category association, share of consideration, brand recall, win-rate movement — and cites Forrester, 6sense, Gartner, and McKinsey research to support the shift.
• That is a better fit when the engagement is about reworking reporting and getting leadership to fund preference-building alongside demand capture.

The tradeoff is that this material diagnoses what to measure but stops short of changing how the work is organized.

• A client that has accepted the new metrics but still runs marketing, sales, product, and customer success as separate handoffs gets a measurement frame, not a journey or ownership design.
• The argument also leans on third-party statistics rather than firsthand client work in these two posts; ask for examples of applying the measurement model.

Examples: Source 1 · Source 2

One post describes leading marketing at Plex Systems when buyers shifted their searches from 'SaaS ERP' to 'Cloud ERP': the team changed keywords and ad copy to meet buyers where they were while holding the strategic position of cloud versus on-premises.

• The point is that marketers often mistake the language used to execute a strategy for the strategy itself.
• A second post works through rebuilding a B2B marketing organization around seven functions and asks where AI fits, concluding that the ownership question is still unresolved.
• This fits two needs: repositioning when the market's language has moved underneath you, and designing the marketing function and AI's place in it, both grounded in having run the function.

The tradeoff is transferability and maturity.

• The category example comes from one enterprise software company at a particular moment, and the organization series is explicitly unfinished: Fetterman writes that the AI ownership question is not fully worked out, so the org advice is a live line of thinking rather than a settled method.
• Neither post addresses the post-sale side of go-to-market: usage and value signals, expansion conversations, or the cross-functional handoffs that keep a recurring-revenue relationship working.
• For a client focused on the ongoing relationship after the sale, ask how O'Malley's approach addresses those needs.

Examples: Source 1 · Source 2