Marketing & GTM Portfolio

Launching a technical product end to end

• Situation: A technical infrastructure product where the buyer is technical and the value is not visible in the interface.
• The call: Build the launch around what the buyer had to believe before they could adopt, rather than around feature coverage.
• Rejected: Treating it like a B2C or SMB launch. Technical B2B buyers evaluate differently and the proof requirements are not interchangeable.

• → Technical Product Launch
• Case Study - Product Marketing: Launching a Technical Product for a $1B company
• Experience: Why Launching a Technical B2B Product is Different than B2C or SMB

Repositioning a product portfolio as platform infrastructure

• Situation: A company selling individual products into a market that wanted a single API-first integration surface.
• The call: Reposition the portfolio as one endpoint customers could layer onto, and build the launch narrative around delivery model rather than individual products.
• Rejected: Continuing to sell products individually, which put the integration burden on the customer and slowed implementation and business outcomes.

• Experience: Product Launch of Single API Infrastructure as a Commercialization Strategy

Taking a product to market, then expanding the story after traction

• Situation: A new infrastructure product in a category buyers did not yet have a mental model for.
• The call: Lead the launch with the customer outcome rather than the mechanism. The positioning line was the promise that "you don't have to be there to bank there" - with the narrative extended into working capital, liquidity, and FX once the product had traction.
• Rejected: Launching on technical capability, which would have limited the buyer set to people already looking for the mechanism.

• Experience: Product Launch of "You Don't Have to Be There to Bank There" Virtual Accounts as Global Growth Infrastructure
• Experience: Product Launch Expansion of Virtual Accounts as a Cross-Border Payments Solution for Working Capital, Liquidity, and FX 

Anchoring a launch to a regulatory window

• Situation: Merchants had just gained the right to steer customers toward preferred payment methods and surcharge by card type, following Durbin 2.0 and the Visa/Mastercard settlement. But tokenization had removed the card data they needed to act on it. Most card-not-present (CNP) merchants hold a PSP token, not the full PAN, and a six-digit BIN lookup no longer resolves the attributes the new rights depend on.
• The call: Launch Card Attributes as the missing piece of a right merchants had just won, timed to the regulatory moment, and carrying the technical explanation of why their existing BIN logic wouldn't get them there.
• Rejected: Leading with the dataset and its compliance advantages. That framing competes on coverage against every other data provider and did not give the buyer a reason to act now.

• Experience: Product Launch of Card Attributes - When Richer Data is a Growth Lever for Better Business Decisions

Holding positioning and messaging hierarchy under compressed time

• Situation: A live showcase slot with one day of lead time, a broad audience at very different stages of need, and assets about to go to print.
• The call: Resolve five decisions before anything was produced: how a conversion is defined, which single buyer state to optimize for, which message the existing paid signal supported, where the spend goes, and how success gets measured. Killed a six-foot banner already heading to print and moved the money to interaction and incentive.
• Rejected: Marketing to the general audience, which weakens both messaging and offer.
• What it demonstrates: The decision logic was pressure-tested afterward against a different buyer, category, and offer. It held. Since client work was confidential, published sample assets were rebuilt for a fictional company.

• Experience: The Event Was Last Minute. The AI-Native Layer Made it Feasible.

Rebuilding growth for an established B2C brand

• Situation: Established brand, flat paid spend, conversion underperforming.
• The call: Rebuild the GTM system around an AI-Native operating model rather than optimizing the existing funnel.
• Result: 7x conversion and 43% lower CPL on flat spend.

• → Case Study: B2C Growth Rebuild

When the revenue target exceeds viable pipeline

• Situation: An $18M new ARR target against $52M of CRM pipeline. At a 25% qualified-opportunity win rate, the target requires roughly $72M in qualified pipeline, and only $20M is actively progressing toward an in-period decision.
• The call: Name it as a $52M qualified-pipeline gap rather than a $20M coverage gap, then diagnose where growth is actually constrained before allocating anything.
• Rejected: Spending more on marketing before running the pipeline analysis. Additional spend against a conversion or quality constraint produces more of the pipeline that was already not converting.

Marketing works in two directions. Forward from the market - market, ICP, use case, positioning, motion, buyer response - usually led by product marketing, brand, and partner marketing. Backward from the business - revenue target, required pipeline, active opportunities, their sources, investment decision - usually led by growth, demand generation, and revenue operations.

The diagnosis routes the next dollar. A creation problem points to ABM, partner and channel expansion, events, and paid. A quality problem points to tighter ICP and targeting. A conversion problem points to proof, messaging, offers, and sales education. A velocity problem points to multi-threading, executive engagement, and open objections.

• Perspective: Marketing from Insight to Revenue

Whether an established product with a working sales motion should introduce PLG

• Situation: A functioning sales-led motion, and a segment with real need that cannot justify the contract size, implementation effort, or sales process.
• The call: PLG as expansion, with a sales-assisted path built into it.
• Rejected: PLG as replacement within a defined segment. It would have put the existing revenue base at risk and stranded the customers who still needed human involvement to buy.

• Experience: PLG After SLG - Choosing PLG's Job, Designing the Journey, and Proving the Economics.

What belongs in the quarter that protects revenue, and what belongs in the quarter that builds the system

• Situation: Q4 with the revenue base most exposed, and a backlog of new initiatives competing for the same period.
• The call: Q4 protects and converts revenue already in motion. Q1 builds the repeatable system. New work in Q4 clears a higher bar - clear customer need, validated product experience, low operational risk, direct path to revenue.
• Rejected: A blanket Q4 freeze on anything new, which forfeits demand that is already there and pushes a quarter of learning into Q1.

Buyer metrics map to business outcomes: checkout conversion to revenue from existing traffic; authorization rate and platform stability to less wasted demand; chargeback control to lower servicing friction and more predictable fees; subscription renewal to recurring revenue durability; retention to near-term cash and long-term enterprise value.

• Framework: Is Your Q4 Marketing and GTM Strategy Safe or Expensive?
• Experience: Q4 vs Q1 Operating Plan

How to shape a marketing team when the work no longer divides cleanly by function

• Situation: Customers experience one story across the ad, the landing page, the sales conversation, the website, the email, the demo, the product, and the follow-up. Marketing is organized to produce that story in pieces. Messaging, demand programs, and competitive context now move faster than most planning cycles, so set-and-forget planning leaves openings for competitors.
• The call: Design for positionless coverage - fewer silos across product marketing, brand, demand generation, paid, AEO/GEO, and GTM planning - but only with a standards layer built underneath it first. Two mechanisms solve different problems: a skill makes a specific repeatable task consistent; a digital twin applies standards across an entire body of work. The team then works in tandem rather than separated by function.
• Rejected: Staffing *only* as a specialist per function. It preserves depth but fragments the customer experience across surfaces, and it cannot keep pace with cycles that now move faster than the planning cadence.
• Also rejected: Going positionless without the standards layer. Cross-functional speed with nowhere for standards to live is how the wrong message ships.
• The distinction that makes it work: a product marketing skill drafts the launch brief; the twin pushes for benefits-led messaging, clear buyer value, proof behind claims, and a real CTA. A paid media skill generates ad variants; the twin holds ICP fit, offer strength, conversion quality, and spend discipline over cheap volume that doesn't convert. A GTM skill produces the monthly plan; the twin challenges the priorities before the plan gets built.

A skill helps complete the work. A twin knows whether the work is being approached with the right assumptions, standards, and priority. In practice: while evaluating GTM priorities, competitive signal was missing - so a recurring weekly competitive review was built and fed back into planning. The skill supported execution; the twin improved the operating system.

• Perspective: Implementing "Positionless" Marketing

Turning customer outcomes into commercial evidence

• Situation: Customers achieving real outcomes, and sales unable to produce credible proof at the moments buyers needed it.
• The call: Treat advocacy as commercial infrastructure rather than a content program, and build a governed layer that produces proof on demand.
• Rejected: A case study calendar, which produces assets on a publishing schedule rather than at the point of buyer decision.

• → Tool: Customer Proof AI Layer
• Case Study - Customer Marketing: Leveraging Customer Proof as Commercial Evidence
• Experience: Operating Customer Marketing Day to Day

Responding to customers at volume without losing judgment

• Situation: Customer response quality degrading as volume grew, with the choice framed as headcount or templates.
• The call: Build a playbook-driven response system where AI drafts and explains and humans decide when to escalate.
• Rejected: Full automation, which scales tone and speed but not judgment.

• → Tool: Customer Response Engine

Positioning a B2B brand when AI is assumed

• Situation: Every competitor claims AI. The claim no longer differentiates and the category has flattened.
• The call: Build the brand on what the company stands for beneath the AI claim.
• Rejected: Competing on AI capability messaging, which would have made the brand indistinguishable from the field.

• → Case Study: AI-Native Brand Playbook

Search and AI visibility

• Situation: Buyers increasingly reach a first answer inside an AI assistant rather than a results page, and the brand had no measurement of how it was represented there.
• The call: Treat AI visibility as a measurable GTM surface - recommendation, mention, share of voice, citation, accuracy, average position - and build the tooling to track it.
• Rejected: Extending the existing SEO program, which optimizes for ranking in a list rather than selection inside a synthesized answer.

→ Checklist & Skills: AEO & GEO·→ Tool: AI Visibility Scorecard