ParisR – Page 7 – Bring To Market

Stop Optimizing Blind: The AI Share-of-Voice Stack Every Operator Should Be Running by Friday

For the last 18 months, almost every conversation about AI SEO has been about production — write longer pages, restructure the H2s, add stats, get on Reddit. All correct. All necessary. None of it is the bottleneck anymore.

The bottleneck is that almost nobody is measuring whether any of it is working.

AI Overviews now appear on roughly 48–50% of queries (BrightEdge, Feb 2026), AI-referred sessions grew 527% YoY through mid-2025, and AI traffic converts about 4.4× better than traditional organic. Yet most teams — agencies included — are still sending clients a Search Console screenshot and an Ahrefs traffic chart. Neither tool can tell you whether ChatGPT, Perplexity, Gemini, or Google AI Overviews currently cite you, mention you, or describe you accurately. That gap — measurement, not production — is the largest operational hole in the field right now, and whoever fills it first owns the conversation with the client.

The mechanic: what “AI visibility” actually decomposes into

Traditional SEO had one currency: position. AI search has four, and they don’t move together.

Citation share is the percentage of relevant prompts where your domain appears as a clicked source under an AI answer. ChatGPT cites Wikipedia 47.9% of the time. Perplexity leans Reddit 46.7%. Gemini stays on brand-owned sources about 52% of the time. Your citation share is engine-specific — averaging across them hides the truth.

Brand mention share is the percentage of relevant prompts where your brand is named in the answer text without necessarily being cited. This is the metric that maps to the +35% organic-clicks lift cited brands inside AIO see (Amsive). A brand can be mentioned without being clicked, and mentioned without being linked — both still move demand.

Representation accuracy is whether the AI describes you correctly when prompted. Wrong category, wrong founders, wrong pricing, outdated product description, ghosted-from-the-knowledge-graph — all of that is fixable, but only if you’re checking.

Share of voice is the head-to-head: across a fixed prompt set, what percent of citations or mentions go to you vs. each named competitor. This is the number that gets a CMO’s attention because it’s directly comparable to organic SOV reports they already read.

You need all four. A site can have rising citation share on Perplexity, falling mention share on ChatGPT, perfect representation accuracy in Gemini, and shrinking SOV against a single fast-moving competitor — all in the same week. The aggregated “AI visibility score” most vendors are selling collapses those four into one number and tells you nothing actionable.

What to do this week

1. Define your prompt set first, then pick tools. Pull 50–150 prompts directly from customer questions: sales-call transcripts, support tickets, your own Search Console long-tail queries, and the “People also ask” boxes around your top 20 keywords. This prompt set is the only ground truth in the entire stack. Refresh it quarterly.

2. Run the four engines manually for one week. Before you buy a tracker, hand-run your top 30 prompts against ChatGPT, Perplexity, Gemini, and Google AI Overviews. Log: cited? mentioned? described correctly? competitors named? Forty-five minutes a day for five days will teach you more than any dashboard.

3. Stand up automated tracking for the top 50. Profound, Otterly, AthenaHQ, Peec, and a handful of others now do this — pick one, pipe it into a sheet, and start a weekly snapshot. You don’t need real-time. You need a clean week-over-week trend on citation share, mention share, and SOV per engine.

4. Build the one chart that matters. A single stacked-bar showing your mention share vs. your three biggest competitors across the four engines. Update it weekly. That chart belongs in every client report from now on — and at the top of every internal review.

5. Set the dial for representation accuracy. Once a month, prompt each engine to “describe [your company]” and “list the top three companies that do [your category].” Fix anything wrong by editing the source of truth — usually Wikipedia/Wikidata, your About page, and your top three citation sources — not by trying to argue with the model.

You can’t optimize what you can’t see. The teams winning AI SEO right now aren’t the ones writing the most content — they’re the ones who can show a client, on a single page, whether last month’s work moved the share-of-voice line. The production playbook is already in the public domain. The measurement playbook is still wide open.

Variant B — direct, services-first

Need this done for you? Paris Roussos runs a flat-rate AI SEO service ($500–$1,500/mo per client, white-label for agencies) covering audits, schema and entity work, AI-visibility tracking, and content engineered to be cited by LLMs. Reach him at parisroussos@gmail.com.

If you don’t have the share-of-voice chart yet, you don’t have a program — you have a content calendar.

OpenAI Just Made Production-Grade AI Voice Agents an SMB Line Item — Here’s the GTM Playbook to Win on the Phone Before Q3

On Thursday, May 8, 2026, OpenAI moved its Realtime API out of beta to general availability and launched three new voice models on top of it: GPT-Realtime-2 (built on GPT-5’s reasoning architecture with a 128K-token context window, up from 32K), GPT-Realtime-Translate (live voice-to-voice translation across 70+ input languages and 13 output languages at $0.034 per minute), and GPT-Realtime-Whisper (low-latency streaming transcription at $0.017 per minute). GPT-Realtime-2 itself is priced at $32 per million audio input tokens ($0.40 cached) and $64 per million audio output tokens.

That’s the price-and-capability point at which “AI on the phone” stops being a science project and becomes an SMB go-to-market budget line. Real-time reasoning, real-time translation, real-time transcription — all sold as production API endpoints with SLAs, all callable from the same vendor every CRM and ad platform is already integrating with. For SMBs in high-call-volume verticals — home services, real estate, clinics, dental, HVAC, auto, legal intake, logistics, restaurants, brokered services — the math has now shifted decisively: 60–80% of first-touch interactions can plausibly be handled by a voice agent, in the customer’s native language, at sub-cent-per-minute compute cost.

Why the GTM angle is the real story. Most coverage of the launch treated it as a developer-API event. It isn’t. The relevant thing about a $0.034/min translation engine and a $0.017/min transcription engine isn’t the API surface — it’s what they unlock for SMB pipelines: every missed inbound call, every after-hours lead, every Spanish- or Mandarin- or Vietnamese-speaking customer your front desk currently bounces, every qualification you’d love to standardize but can’t afford to staff. Those are pipeline leaks. Voice models that reason now plug them — and the vendors building consumer-facing wrappers (Bland, Vapi, Retell, Twilio’s voice-AI tier, plus the inbound features now baked into HubSpot, Salesforce Service Cloud, RingCentral, JustCall, and CallRail) will have GPT-Realtime-2 lit up within weeks.

The reference data is already striking. In high-call-volume sectors — restaurants, clinics, real estate, HVAC services, logistics — early deployments are showing 60–80% of first-level interactions automated with conversation quality good enough that customers don’t ask for a human. Multilingual deployments in markets like Houston’s Hispanic small-business corridor and Latin America are showing the second-order GTM unlock: serving customers in their native language without hiring additional bilingual staff. That is a moat for any SMB that figures it out before its three closest competitors do.

A 30-day SMB GTM playbook to actually ship this:

Week 1 — Audit the funnel. Pull last 90 days of inbound call data: total inbound calls, % answered live, % missed, % outside business hours, average handle time, conversion-to-appointment rate, language mix. Identify the single highest-volume reason inbound callers call (most SMBs: appointment booking, hours/availability, price/estimate, “where is my order”). That is the agent’s job description.
Week 2 — Pick one rail and pilot one workflow. Pick a vendor (your existing phone/CRM provider if it already offers a voice-AI feature; otherwise Bland, Vapi, or Retell, all of which surface GPT-Realtime-2 as a model option). Pilot the agent on after-hours-only inbound for two weeks. Two metrics that matter: bookings created and conversation completion rate. Two metrics that protect you: escalation-to-human rate and time-to-correct-route.
Week 3 — Add translation as a competitive wedge. If your service area has any meaningful non-English-speaking population, flip on GPT-Realtime-Translate on the same number. The cost increment is roughly $2/hour of conversation. The conversion uplift in markets where your competitors don’t bother is real and immediate.
Week 4 — Instrument the GTM impact separately. Track agent-originated bookings as their own attribution channel in your CRM, with their own conversion-rate, no-show-rate, and average-ticket-value columns. If those numbers look like your human-originated bookings within 10%, scale to daytime overflow next month.

The SMBs that win this window are not the ones with the best AI prompt — they’re the ones who treat the voice agent as a real sales channel with metrics, ownership, and a weekly review, the same way they treat paid search or local SEO.

If you want a faster on-ramp to setting one of these up — the prompt scaffolds, the qualifying-question scripts, the escalation-rule libraries, the playbook for which workflow to ship first, and the partner discounts on the call-AI stack — that’s exactly the kind of playbook LevelUpLabs.co assembles for entrepreneurs. It’s a membership built to compress the gap between “interesting AI launch” and “this is now a working line in our P&L,” with video walkthroughs, ready-to-deploy checklists, prompt libraries you can lift directly into your voice-agent vendor, and discounts on the supporting tools.

Bottom line: by Q3 2026, “we have a voice agent on the inbound line” will be a default capability of any SMB doing more than $1M in revenue with meaningful phone traffic. The SMBs that ship it in May and June will spend the second half of the year compounding bookings while their competitors are still pricing it.

Sources:

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.