ParisR – Page 9 – Bring To Market

The Permanent Tariff Era Just Got a Name — Why Your 2026 B2B GTM Has to Bake In Trade Policy as Background Noise, Not a Surprise

For two years, B2B sales leaders have been treating tariffs as an event — a quarterly P&L surprise, a “we’ll revisit pricing once this settles down” conversation, a procurement problem someone else owns. In May 2026, three reports landed within four weeks of each other that quietly closed that argument. UNCTAD’s 10 Trends Shaping Global Trade in 2026, the World Economic Forum’s Navigating Trade in 2026, and KPMG’s March 2026 Biannual Supply Chain update all converge on the same uncomfortable framing: tariffs are no longer an event. They are a standing feature of US trade policy and a permanent input to enterprise pricing, sourcing, and sales motion. Your GTM has to bake them in as background noise.

The numbers in this round of reports are now the operational reality, not a forecast. US tariff levels are sitting at 20–32% on China, 18% on India, and 25% on countries doing business with Iran. KPMG’s tracking puts 97% of large companies running active tariff-mitigation programs as of Q1 2026. Deloitte’s projection that 40% of US firms would relocate at least part of their supply chains to North America by EOY 2026 is now showing up in actual capex: Q1 2026 industrial capex announcements in Mexico and the US Southeast hit record levels, with McKinsey’s Geopolitics and the Geometry of Global Trade 2026 update noting that “geopolitical dynamics are now a primary driver of capital expenditure decisions” — not cost, not labor, not tax. That’s a structural change in how customers buy.

The GTM implication is sharper than most sales orgs have absorbed. Buyers are now running tariff scenarios on every multi-quarter contract you put in front of them. Procurement is asking, in plain language, “what’s your tariff pass-through clause” before they get to discount terms. Contract durations are compressing — UNCTAD flags shorter average B2B contract length across 2025-26 as one of its top-10 trade signals. Decision committees have added a geo-risk seat at the table; it’s usually whoever handles supply continuity, and they have veto power most reps don’t yet recognize. Regional modularity — UNCTAD’s term for the shift away from globalized just-in-time to regionalized configurations — means your buyer is increasingly making vendor decisions through a regional sourcing lens, not a global one. If your pricing, your inventory location, and your contracting are all still designed for the pre-2024 world, you are losing winnable deals to competitors who have rewritten their materials.

Three things to fix in the next 60 days. One — make tariff posture a one-page artifact that every rep can hand to a procurement contact. Where is your product sourced? What percentage is exposed to which tariff lines? What’s your pass-through policy, and what happens if the tariff stack moves? This document does not exist in 80% of B2B sales orgs and it is now the single highest-leverage piece of sales enablement you can build. Two — add a tariff-adjusted pricing variant to your standard proposal template. Two prices: tariff-stable assumption, and a contractually-clean mechanism for adjustment if a named tariff line moves more than X%. Buyers are no longer surprised by this language; they expect it. Three — shorten your standard contract term. If you are still defaulting to 36-month enterprise terms in this environment, you are pricing in policy risk your buyer no longer wants to take. The faster you offer 12-month renewals with clean reset mechanics, the easier you make it for procurement to say yes.

If you want a steady feed of signals like this — curated trend reporting written for CEOs and founders, not data scientists — bookmark TrendInsightsJournal.com. It’s where these moves get tracked weekly so you can spot the meaningful shifts (AI, crypto, macro, metatrends) without drowning in feed noise. Read the brief, run your week.

There’s a deeper play here too. WEF’s Navigating Trade in 2026 explicitly frames “trade as a strategic positioning lever.” Companies whose pricing, sourcing, and contracting flexibility match the new environment are quietly winning share from competitors whose terms still assume 2019. McKinsey’s 2026 geopolitics update calls this “geo-fluent GTM” and ties it to a 4-7 point gross margin spread across surveyed industrials. That spread is your real opportunity. The competitor who hasn’t rewritten their B2B motion to account for a permanent tariff regime is, in 2026, the easiest mark in your category. Build the artifact, ship the pricing variant, shorten the term — and treat tariffs the way you treat FX: a background variable you’ve already priced in, not a quarterly surprise that costs you the deal.

Sources: UNCTAD 10 Trends Shaping Global Trade in 2026, World Economic Forum Navigating Trade in 2026, KPMG Biannual Supply Chain (March 2026) and 2026 Trade Outlook, McKinsey Global Institute Geopolitics and the Geometry of Global Trade: 2026 Update, Marsh, Ivalua, Lambda SCS, Global Trade Magazine, Deloitte (2025) supply-chain relocation projection.

Stripe Just Made Selling Through AI Agents a Single Integration — Here’s the SMB Go-to-Market Playbook

On May 7, 2026 at Stripe Sessions, Stripe announced the Agentic Commerce Suite — a single integration that lets a business become discoverable, transactable, and refundable across multiple AI shopping agents at once. It is the most consequential SMB go-to-market shift since “open a Shopify store and run Meta ads” became the default playbook a decade ago, and it deserves more attention than it got.

The lede: AI agents — ChatGPT, Claude, Gemini, Perplexity, and the agents inside Slack, Microsoft 365 Copilot, and a dozen vertical assistants — are increasingly making purchase decisions on behalf of consumers. The bottleneck has been that those agents had no clean, standardized way to find your products, fill a cart, check out, and handle refunds. Stripe’s Agentic Commerce Suite is the plumbing that closes that loop in a single integration, layered on top of Stripe’s existing payments rails.

The early launch list is the most telling part of the announcement. On the merchant side: Coach, Kate Spade, URBN (which owns Anthropologie, Free People, and Urban Outfitters), Revolve, Ashley Furniture, Halara, ABT Electronics, and Nectar. On the platform side — and this is where SMBs come in — Wix, WooCommerce, BigCommerce, Squarespace, Etsy, and commercetools. If you run a store on any of those, agentic commerce just stopped being a 2027 problem and became a Q3 2026 decision.

The macro picture frames why this matters now. AI search traffic to retail sites grew 269% year-over-year heading into 2026, and the agent layer on top of that is where the next phase of discovery is happening. The Universal Commerce Protocol Tech Council — Amazon, Meta, Microsoft, Salesforce, and Stripe joined in April 2026 — is standardizing how agents read your catalog, evaluate alternatives, and submit orders. On the same day Stripe announced its suite, Amazon and AWS announced Bedrock AgentCore Payments with Coinbase and Stripe, which adds stablecoin-denominated rails for agent-to-agent purchases. The infrastructure layer is converging fast.

For a small or mid-size GTM team, here is the 30-day playbook to be on the right side of this shift before the holiday season.

Week 1 — audit. Pull a list of your top 25 products by revenue and your top 25 by margin. Score each on three axes: structured data quality (does it have proper title, description, attributes, price, inventory, image URLs?), policy clarity (return window, shipping, warranty), and identifier completeness (GTIN/SKU/MPN). AI agents need the same data search engines have needed for two decades — most SMBs still don’t have it clean. Fix the worst ten this week.

Week 2 — pick your rail. If you’re on Wix, WooCommerce, BigCommerce, Squarespace, or Etsy, your platform is rolling out the Stripe Agentic Commerce Suite — check the docs and turn it on in a sandbox. If you’re on a custom stack, you’re integrating directly. Either way, point it at a low-risk subset of your catalog first (say, your evergreen bestsellers) before exposing the long tail.

Week 3 — agent-readable storefront. Build (or ask Stripe’s docs for) the product feed format, structured policy pages, and FAQ payload that agents will consume. Make sure your return policy is machine-readable. Make sure your size charts and compatibility data are structured, not buried inside product description prose. This is the agentic-commerce equivalent of “writing meta descriptions in 2008” — boring, mechanical, and the people who do it first win.

Week 4 — instrument and learn. Set up reporting that tags agentic orders separately so you can measure: average order value (typically lower than direct), refund rate (typically higher in early agent experiments), repeat rate, and which agents drove which conversions. Establish a baseline now. You will not get the analytics later.

If you want a structured place to put a playbook like this into practice — alongside the prompt libraries, video training, and ready-to-use checklists that pair with it — LevelUpLabs.co is built for exactly that audience: entrepreneurs and small GTM teams who want to install new revenue motions without burning a quarter on reading think-pieces. The partner discounts alone usually cover the membership.

The closing takeaway: agentic commerce is not a future channel. As of May 2026 it has a payments standard (Stripe), a discovery protocol (UCP), a stablecoin rail (AWS Bedrock AgentCore Payments), and a half-dozen platforms shipping the integration to SMBs in-product. The teams that pick one platform, turn it on this quarter, and own a 25-product agent-ready catalog by August will be measuring agent-driven revenue in Q4 while their competitors are still asking whether this is real. It is. Decide which side you want to be on, then ship the audit on Friday.

Sources:

The $28M SiriusXM Lesson: Your Internal Do-Not-Call List Is a GTM Asset, Not a Compliance Checkbox

SiriusXM’s $28 million TCPA class action settlement reached its final approval hearing on May 11, 2026, capping a case that should be required reading for any GTM organization running an outbound calling motion. The headline is the dollar figure. The actionable insight is what the case reveals about how internal Do-Not-Call lists fail — and why those failures are increasingly a GTM ops problem, not just a legal one.

The case in one sentence

In Campbell v. SiriusXM Radio, Inc., a class of consumers alleged that SiriusXM continued to make telemarketing calls to people who were either on the National Do Not Call Registry or who had specifically asked SiriusXM to stop calling — over a window stretching from April 27, 2019 to October 31, 2025. The size of the class and the duration of the alleged violations point to a systemic operational failure, not isolated incidents.

Why this is a GTM problem

Most large companies don’t actively decide to call people who asked them to stop. The violations accumulate at the seams — the places where customer requests pass between teams, systems, and vendors. Those seams are exactly the places GTM ops typically owns. Specifically:

The opt-out → suppression handoff. A customer texts “STOP” or asks a CSM to remove them. Where does that signal go? In most stacks, it goes to a marketing automation tool or a CRM. Does it propagate to the outbound dialer, the SMS platform, the partner contact pipeline, the data warehouse used for upload to new acquisition campaigns? In most companies, the answer is “yes, partially, with lags.” That’s where Campbell-style cases originate.

The lifecycle marketing seam. A consumer opts out of marketing but stays a customer. Your retention motion fires up a re-engagement push. Whose responsibility is it to confirm the consumer didn’t opt out of all calling? This question is increasingly being litigated, and answer-by-default is starting to fail.

Acquired-data and partner-source contact. A consumer opted out three years ago. Your company acquires a new business unit, ingests its contact lists, and runs a campaign. The opted-out number isn’t on the new list’s suppression — but your master list still has the opt-out. Whose responsibility is it to enforce?

The GTM control plane

The companies that get this right treat their suppression infrastructure as a first-class GTM asset:

A single source-of-truth opt-out table, owned by GTM ops, that ingests opt-outs from every channel (web forms, SMS keywords, inbound calls, email link-clicks, partner-reported opt-outs, postal mail) within hours, not weeks. Outbound sending systems — dialer, SMS, email, partner-facing CDP — read from that table as a blocking check before any send. Migration and acquisition playbooks include a “merge suppression lists” step with reconciliation. Quarterly audits sample random opt-outs and verify zero outbound contact since the opt-out date.

Companies that don’t get this right typically discover the gap only when a plaintiff’s counsel runs the dataset analysis that produced Campbell.

The reputational layer

The brand cost of being a defendant in a case like this is real but often underestimated. The settlement website (sxmtcpasettlement.com) and accompanying claim form become high-traffic destinations for ex-customers, current customers, and prospects researching the brand. The narrative that “this company kept calling people who asked them to stop” surfaces in news coverage, social media, and search results — affecting acquisition and retention metrics in ways that show up in the dashboard but don’t get attributed to the underlying compliance failure.

If your demand-gen motion leans on outbound calling or SMS, a litigator-suppression layer belongs in your stack right next to your DNC scrub and consent-capture audit. Tools like TCPALitigatorList.com index numbers tied to known TCPA plaintiffs and serial filers; running your dialing lists through that file before you hand them off to SDRs or a dialer vendor is one of the lowest-friction risk controls a GTM team can deploy.

The action list for GTM leaders

Within 30 days: map every system that captures an opt-out and every system that initiates outbound contact, and confirm the data flow between them. Within 60 days: stand up a quarterly suppression audit using a random sample of opt-outs. Within 90 days: revise any partner or vendor agreement that involves outbound contact to mandate shared use of your suppression list. The companies that operationalize these basics are the ones whose growth motions look defensible 18 months from now; the ones that don’t are the next round of Campbell defendants.

Sources

Campbell v. SiriusXM Radio, Inc., No. 2:22-cv-2261 (C.D. Ill.); class settlement website (sxmtcpasettlement.com); reporting by Inside Radio, TopClassActions, and Cord Cutters News.

When Your ‘Independent’ Reps Become a TCPA Liability: The eXp Realty Cautionary Tale for GTM Teams

Every GTM leader running a channel motion, partner program, or distributed sales model needs to spend an afternoon with the eXp Realty TCPA case. In the first week of May 2026, a federal court in Washington denied eXp’s motion to stay Usanovic v. eXp Realty — a certified class action covering calls eXp agents made using third-party dialer software. The case is moving forward, on a record that already includes a finding that eXp can be directly liable for calls placed by its agents. For any company whose growth engine depends on people who don’t technically work for them, this is the framework that’s about to test your structure.

The structural problem the case exposes

The classic GTM design — corporate brand, distributed selling — assumes a clean line between principal and agent. The eXp ruling shows that line is much blurrier than most companies realize once you start looking at the actual operational relationship: did corporate provide the training? The lead lists? The CRM? The dialer? The script? Every “yes” tightens the principal-agent relationship and increases vicarious liability exposure.

This isn’t just a real estate problem. It’s a structural problem for any GTM motion that includes:

Channel partner programs where corporate provides leads or marketing automation. Franchise systems where corporate maintains a CRM or call center. Affiliate programs where corporate provides scripts or call recordings. SDR-as-a-service vendors where the brand is the customer’s, the people are someone else’s. Distributed insurance or financial services models where corporate runs the platform and the agents run the dialers.

What GTM should be auditing now

Three audits worth scheduling this quarter:

The lead-provisioning audit. Map every channel through which the people calling on your brand’s behalf get phone numbers. Identify which leads originated inside your systems versus which were sourced by the agent. For corporate-sourced leads, verify the consent record and the vendor’s documentation practices. The eXp court paid particular attention to the testimony of lead vendors who admitted they didn’t have consent — that pattern is not unique to real estate.

The technology-stack audit. Inventory every piece of dialing or messaging tech that touches an outbound contact made under your brand. For each: who pays, who configures, who governs compliance settings (rate limits, quiet hours, DNC scrubbing)? If corporate pays and corporate configures, corporate inherits the operational control that supports vicarious liability.

The training and policy audit. Pull every piece of compliance training you provide to agents or partners. The eXp case has surfaced that training material is double-edged: insufficient training is evidence of indifference, but robust training plus violations can actually support a defense if you’ve done the documentation work. Make sure the training is real, recurring, and tracked at the individual-agent level.

The reputational dimension

The other thing the eXp case underscores for GTM leaders is reputational. eXp already paid $26.9 million in a prior TCPA settlement. Usanovic is incremental on top of that, and the court has been increasingly explicit in its language about agent calling behavior. For brands whose marketing message is built around trust, customer-first, or any kind of integrity narrative, ongoing TCPA exposure is a slow-bleed brand problem in addition to a financial one.

The strategic question

Every GTM leader running an agent-based motion should answer one question before this quarter ends: if a TCPA plaintiff sued us on a vicarious-liability theory tomorrow, which specific operational facts in our agent program would the court find most damning? Then either fix those facts or build the documentation that explains why they’re not what they appear to be. The companies that do this work proactively will be the ones whose growth motions survive the next wave of TCPA enforcement. The ones that don’t will be the next eXp.

Sources

TCPAWorld coverage of stay denial in Usanovic v. eXp Realty (May 1, 2026); National Law Review on direct-liability holding; prior $26.9M eXp TCPA settlement records.

Why Your Facebook Lead Forms Just Became Your Strongest TCPA Defense (If You Documented Them Right)

If your demand-gen team buys leads — and if you’re running a B2C motion, you almost certainly do — a federal court ruling out of Tennessee this week deserves a slot on next Monday’s GTM standup. In Brockington v. Hume Health, LLC, the U.S. District Court for the Eastern District of Tennessee refused to let a TCPA plaintiff stall summary judgment with a Rule 56(d) discovery request, paving the way for the defendant’s Facebook-lead consent defense to be decided on the existing record. For marketing ops leaders, this is the rare case where the right documentation upstream determines whether you’re a defendant for two weeks or two years.

The lead-gen consent stack just got more important

Hume Health’s defense isn’t novel: it argues the plaintiff clicked through a Facebook lead form, accepted the TCPA-style consent language above the submit button, and authorized the very calls she now claims were illegal. What’s new is that the court is willing to hear that defense early, before discovery has expanded into the seven-figure cost range that pressures most defendants to settle.

For GTM teams, the implication is direct: the asset that determines whether a TCPA suit becomes an expensive class action or a fast summary judgment dismissal is your lead-capture record. Not your CRM. Not your dialer logs. The raw form-submission artifact — with the disclosure text as rendered, the IP, the timestamp, and the link back to the source ad creative. Most marketing ops teams cannot produce that artifact on a per-number basis. Most are about to find out they need to.

What this means for the demand-gen funnel

Three places this ruling should hit your GTM playbook this quarter:

Lead vendor contracts. If your vendor’s data-retention policy lets them purge raw submission records after 90 or 180 days, you’re buying leads with a shelf life on your defense. TCPA suits routinely cover a four-year lookback. Negotiate for indefinite retention of consent artifacts on any lead you ingest, and a contractual right to retrieve them per-lead within 48 hours.

Disclosure copy. Lead forms still routinely bury TCPA consent language in fine print or below the submit button. After the Fifth Circuit’s earlier consent ruling and now Brockington‘s procedural posture, the consent disclosure language and its visual prominence at the moment of click are the single most-litigated facts in any TCPA case. Get legal review on every active landing-page variant — including the ones SEM and paid social are still running.

Funnel attribution. Your lead source tracking has to survive a deposition. If a plaintiff’s number routes through three vendors before hitting your CRM, you need each handoff documented. “We bought it from Vendor X” without the underlying Vendor X submission record is functionally useless as a defense.

The procedural signal matters more than the merits

The reason this ruling matters even though summary judgment hasn’t actually been decided yet is the message it sends to plaintiffs’ counsel about how Tennessee federal courts (and others watching) will handle Rule 56(d) requests. The professional-plaintiff playbook depends on extending discovery to make defense uneconomical. A court that requires plaintiffs to articulate specific facts they expect to find — rather than fishing expeditions — shifts the cost curve back toward defendants who actually have their paperwork in order.

For marketing leaders, the strategic takeaway is that pre-litigation hygiene now has a much higher ROI. The companies that win fast are the ones whose lead artifacts are clean, complete, and produceable. The companies that drag through discovery are the ones whose ops teams treated lead-capture data as a marketing analytics problem rather than a litigation evidence problem.

The GTM action list

This week: pull a sample of 10 leads from each active source and try to produce the raw submission artifact. Next sprint: revise lead-vendor MSAs to include retention and retrieval SLAs for consent records. This quarter: get legal sign-off on every active lead-form disclosure variant. The teams that do this work now will look prescient in 18 months; the teams that don’t will be the case studies.

Sources

Brockington v. Hume Health, LLC, 3:25-cv-00161 (E.D. Tenn. May 11, 2026); National Law Review; PacerMonitor docket.

The 20,000-Character Floor: Why AI Search Cites Long Pages 4.3× More Than Short Ones

For a decade, the standard small-business content advice was “write tight.” 700 words, one keyword, hit publish. That formula still works fine for Google’s classic ten blue links. It is quietly catastrophic for AI search.

The hard data: pages above 20,000 characters of body text get 4.3× more AI citations than shorter pages. ChatGPT, Perplexity, Google’s AI Overviews, and Gemini are not reading your headline and guessing — they are retrieving chunks from inside long, structured documents and stitching answers together. Thin pages do not have enough surface area to be retrieved.

This is the inverse of what most founders and operators were taught about content, so it gets ignored. It shouldn’t.

The mechanic — why length is a retrieval signal

LLM-powered search does not work like ranking. A ranking system looks at the whole page and decides “this URL is #4.” A retrieval system slices your page into passages (usually 200–800 tokens each), embeds them into a vector space, and pulls the closest passages to the user’s prompt. A 700-word post gives the retriever maybe 2–3 candidate passages. A 4,000-word guide gives it 15–25.

More candidate passages means more chances of being the closest match to some sub-question the user asks. The model is not picking your “best” article. It is picking the best sentence-cluster for that exact prompt. Length increases your surface area.

There’s a second effect: long pages signal topical authority to embeddings models. When a single URL exhaustively covers a topic — definitions, sub-cases, exceptions, examples, comparisons — its semantic centroid sits closer to the topic’s centroid than a thin page does. The retriever’s similarity score climbs. This is why pillar-page strategies and topical clusters are now load-bearing, not optional.

The third effect is mundane but real: long pages get more internal links, more entity mentions, more anchored citations from your own site. That cluster of supporting signals reinforces the long page’s authority and pulls more retrieval traffic toward it.

“But long content is dead” — no, it’s the opposite

The “short, snackable content” advice came from a world where the goal was getting a single click off a SERP. In the AI search world, you are not competing for a click. You are competing to be the source the model quotes back. The mechanics flipped without most marketing teams noticing.

This is also why the +22% lift from adding statistics and the +37% lift from adding direct quotations show up so consistently — both reward longer, denser pages. You cannot squeeze that density into 500 words. You need room.

What to do this week

1. Audit your top 20 pages by traffic and pick the 5 with the strongest topical fit to your business. Run a character count. Anything under 8,000 characters is a candidate for expansion. Anything under 4,000 is barely a stub by AI search standards.

2. Expand by adding sub-topics, not filler. The goal is more retrievable passages, not more words. For each page, ask: “What are the five adjacent questions a buyer would ask after reading this?” Each one becomes an H2 with a tight 80–150 word answer beneath it. That’s how you cross the 20,000-character line without padding.

3. Add at least one original data point and one named expert quote per major section. Statistics and quotations are the two highest-lift content elements for AI visibility. They are also what the retriever extracts. If your page has neither, you are invisible to the citation layer regardless of length.

4. Keep the heading hierarchy strict. The retriever uses H2/H3 boundaries as passage breakpoints. Sloppy nesting collapses your passages into one giant chunk that nobody quotes. Treat your outline like API documentation.

5. Don’t merge short posts blindly. Two well-written 1,500-word articles on different sub-topics will out-cite one bloated 3,000-word amalgam. Length matters; coherence matters more. Expand each page on its own topic, don’t Frankenstein.

Paris Roussos has been doing SEO since 1996 (co-founded a Forbes Best of the Web–winning site back in the day) and now runs a white-label AI SEO practice for agencies and brands — flat-rate, $500–$1,500/mo per client. If your top-of-funnel traffic is leaking into ChatGPT and Perplexity and you want it back, email parisroussos@gmail.com.

The cheap-and-thin content era is over for AI search. The pages that get cited — and convert at the 4.4× rate AI-referred traffic delivers — are the long, well-structured, stat-rich ones. Build five of those before you publish another short post.