by

77% of U.S. Businesses Now Use AI Regularly — Intuit’s New Report Says the Quiet Part Out Loud: It’s Adding Revenue, Not Cutting Jobs

If you’ve been waiting for a number big enough to settle the “is AI actually working for small businesses” argument, Intuit just handed you one. On May 12, 2026, the company released its 2026 AI Impact Report, and the headline figure is hard to wave away: 77% of U.S. businesses now use AI regularly, up from 48% in July 2024. In less than two years, regular AI use among American small and midsize businesses went from a coin flip to a clear majority.

What makes this report worth more than the usual survey is the size and the sourcing. Intuit didn’t just poll people. It combined survey responses from more than 34,000 small and midsize business owners with anonymized usage data from more than 5.3 million QuickBooks businesses across the U.S., Canada, the U.K., and Australia. When you cross-reference what owners say against what millions of real businesses actually do in their books, you get something closer to ground truth than a press-release stat.

And the ground truth is encouraging. Across all four countries, roughly 7 in 10 businesses now use AI regularly, and daily use has more than doubled in some markets. In the U.S. specifically, 78% of businesses say AI has improved their productivity — up from 46% in July 2024. The most-cited use cases are marketing, customer service, and data processing, with generative AI the most popular flavor. None of that is surprising on its own. What’s surprising is the next layer of data.

Here’s the part that should reframe how a cautious founder thinks about this: 43% of U.S. businesses say AI has increased their revenue, and only 2% say it’s gone the other way. That’s a better than 20-to-1 ratio of “helped” to “hurt.” For a tool category that’s still routinely described as hype, a 21x positive-to-negative revenue split is the kind of number that turns skeptics into pilots and pilots into line items.

Then there’s the question everyone actually worries about: jobs. The dominant media narrative for two years has been AI-as-job-killer. Intuit’s data points the other direction for small businesses — **four times as many U.S. businesses say AI has increased hiring as say it reduced it.** That tracks with how small firms actually behave. When a five-person company gets more productive, it usually doesn’t fire someone; it takes on the bigger client it couldn’t service before, and then it needs another hand. AI at small scale tends to be a capacity story, not a headcount story.

So what should you do with this if you run a small business and you’re somewhere in that 23% who aren’t using AI regularly — or you’re using it casually but haven’t seen revenue move? The report’s own pattern suggests the gap isn’t tools, it’s integration. The businesses reporting revenue lift aren’t the ones who opened ChatGPT once; they’re the ones who wired AI into a workflow that touches money — lead follow-up, quoting, invoicing, customer replies, marketing production. Pick the single workflow in your business that’s closest to revenue and slow because you are the bottleneck, and put AI on that one first. Measure it for 30 days. If it moves a number, expand. If it doesn’t, you’ve spent almost nothing learning that.

If you want a place to actually turn a report like this into a working system instead of another browser tab you’ll forget, take a look at LevelUpLabs.co. It’s a membership built for entrepreneurs who want to build real income systems with AI — stocked with prompt libraries you can run today, no-fluff video training, ready-to-use checklists for the money-adjacent workflows (lead intake, quoting, follow-up, monthly close), and partner discounts on the tools owners are already adopting. The difference between the 43% seeing revenue lift and everyone else is rarely the software — it’s having a playbook. That’s what’s inside.

The takeaway from Intuit’s report isn’t “AI is coming.” It already came, and the majority of your competitors are using it daily. The open question is no longer whether AI helps small businesses — 5.3 million sets of books say it does. The question is whether your business is in the 77% compounding the advantage or the shrinking share still treating it as optional. Pick one revenue-adjacent workflow this week and close the gap.

Sources:

by

The HowTo Edge: Why AI Search Quotes Your Step-By-Step Posts Before Anything Else You Publish

Procedural queries are the loudest, most underserved slice of AI search traffic right now. Anyone who has ever watched a ChatGPT session knows the rhythm: someone asks how to do a thing, the model returns a numbered list, and the user follows it. Brands keep publishing 2,000-word thought pieces and then wonder why none of it shows up when a buyer asks “how do I migrate from X to Y.” The shape of the answer is not the shape of your content.

The mechanic

There are three forces working together here, and once you see them you cannot unsee them.

First, AI chat shifts query mix. Classic Google biased toward navigational and short head terms; people gave it nouns. LLMs are conversational, so people give them verbs — “how to,” “what do I do if,” “walk me through.” That category is enormous, and procedural intent rewards a very specific content shape: enumerated, sequential, imperative.

Second, passage retrieval rewards structured steps. AI engines do not read your post; they slice it at heading boundaries, embed each chunk, and score chunks individually against the prompt. Step-numbered content slots in perfectly. Each step is already a self-contained answer-unit with a verb, an outcome, and a clear boundary. Compare that to a flowing essay where the model has to guess where one idea ends and the next begins. That is part of why 68.7% of AI-cited pages follow a strict H1→H2→H3 hierarchy, and why 44.2% of LLM citations land in the first 30% of a page — structure makes retrieval cheap.

Third, HowTo signaling still pays even when it is not “officially” rendered. Google retired the rich result for most queries, which led a lot of operators to rip the markup out of their templates. Bad call. The structured data is still parsed by AI answer-fetchers — OAI-SearchBot, ChatGPT-User, PerplexityBot — and it tells the machine “this page is a procedure, with N ordered steps, each with a name and a body.” That is metadata your prose alone cannot give them.

What to do this week

Pick the top ten procedural queries in your category — the literal “how to [verb]” and “what’s the process for [X]” prompts your buyers are already asking ChatGPT and Perplexity. Type each one into all four major engines and write down who is being cited. If the answer is competitor blog posts, third-party how-to roundups, or — in 2026, still — Reddit threads, that is your map of which surfaces to either replace or join.

Rewrite or build the matching posts in this shape. Headline names the outcome (“How to migrate from HubSpot to Customer.io without losing automations”). Lede is a 40-word “here is the short version” answer-unit, sitting in the first 30% of the page so it gets cited verbatim. Then a numbered series of H2s, one per step, where the H2 is the step name in imperative form (“Export your existing workflows”). Each step body is 50 to 150 words, restates the subject (do not write “now do this” — write “now export the workflows”), and ends with an explicit outcome sentence. Avoid cross-references like “as mentioned above” — each step has to make sense in isolation because it will be retrieved in isolation.

Add HowTo JSON-LD. `@type: HowTo`, a `name` matching the headline, an `estimatedCost` and `totalTime` where they apply, and a `step` array where each `HowToStep` has its own `name` and `text` that mirror the on-page H2 and body. Do not duplicate the prose into the schema — paraphrase tightly so the schema text is its own quotable unit. Some engines retrieve from the JSON-LD before the body.

Layer one more thing on top: a “common mistakes” or “if this fails” subsection after the steps. Those exception blocks get pulled into AI answers as caveats and add the kind of honest-trade-off texture LLMs treat as a trust signal. Bonus: long procedural posts with steps, screenshots, and gotchas naturally clear the depth bar that earns 4.3× the citations short posts do.

If you’re a brand that wants to be the answer LLMs reach for (not just rank on Google), Paris Roussos has been engineering search visibility for 30 years and now runs done-for-you AI SEO. Flat-rate, no-fuss. Email parisroussos@gmail.com.

AI search has already decided what a “how to” answer should look like — match the shape, or stay invisible while the model quotes someone who did.

by

The $725 Billion AI Capex Sprint Is Now Supply-Constrained — Why Q3 2026 Is When CEOs Have to Stop Treating AI Compute as a SaaS Line

The $725 Billion AI Capex Sprint Is Now Supply-Constrained — Why Q3 2026 Is When CEOs Have to Stop Treating AI Compute as a SaaS Line

The number that should reorder every CEO’s Q3 2026 AI plan is $725 billion. That’s the combined 2026 hyperscaler capex figure Q1 earnings just confirmed across Amazon ($200B), Alphabet ($175–185B), Meta ($125–145B — raised mid-year from $115–135B), Microsoft (~$120B+), and Oracle ($50B). It’s a ~64% year-over-year increase on top of an already record 2025. And the most important sentence in those earnings calls wasn’t the number itself — it was that every one of them said the same thing about demand: it’s supply-constrained, not demand-constrained.

That phrase is the inflection. Last year the question was whether enterprises would actually spend on AI in production. This year the question is whether the people who built the compute can pour enough of it fast enough. Microsoft’s AI business surpassed $37 billion in annualized revenue (+123% YoY). Google Cloud grew 63% YoY, well above analyst expectations, driven by enterprise AI infrastructure and platform usage. Meta raised guidance citing higher component pricing and additional data center build costs. The supply side is bidding against itself for GPUs, transformers, substation lead times, and skilled construction labor — and the demand side keeps showing up with bigger checks.

Three signals lock the picture in. First, individual deal sizes are now telling: hyperscaler-scale 2026 capex is roughly the size of the entire 2025 U.S. nonresidential construction sector by some estimates. Goldman Sachs’ “Tracking Trillions” work pegs the multi-year buildout in the multi-trillion range and explicitly flags the assumptions — power, chips, water, labor — that have to hold for the curve to extend. Second, the bottleneck has moved from chip allocation to grid interconnect (4–10 year queue in tight regions vs. 2–3 year datacenter build) and SMR offtake (45 GW pipeline by May ’26). Third, mid-year guidance raises — Meta’s +$10B in particular — say the people closest to the demand curve don’t think it’s slowing in 2026.

For CEOs buying AI through Q3 2026, that’s not a bullish-or-bearish call on the market — it’s a procurement and architecture problem with real operating consequences. Supply-constrained compute means three things. (1) Vendor leverage tightens. The capacity-allocation conversation is now part of every frontier-model contract; reserved-capacity, multi-region failover, and committed-spend tiers replace the old “spin it up on-demand” assumption. (2) Inference economics matter even more. Frontier inference is ~1,000× cheaper per token than three years ago, but agentic loops still burn 10–30× more tokens, inference is ~85% of enterprise AI spend, and one frontier lab is now ~40% of enterprise LLM spend — your AI bill goes up even as the unit price falls. (3) Build-vs-buy has to factor compute access, not just model quality. Fine-tuned 70B-class open-source (DeepSeek/Qwen/Mistral) running in your VPC is not just a cost play — it’s a continuity play when capacity at your primary frontier vendor gets rationed.

The CEO move for Q3 isn’t to slow AI spend — it’s to upgrade the procurement and architecture posture to match a supply-constrained world. Four specific actions. Renegotiate your top frontier-model contract with capacity allocation, region, and reasoning-tier as separate, priced line items — not bundled assumptions. Instrument cost-per-completed-task on your top three AI workflows so you can see when token burn outruns business outcome (and so the CFO has a number that isn’t “AI budget”). Run a fine-tuned-OSS bake-off against frontier on at least one default-routed workload — even if you don’t switch, you’ve created the multi-model fallback that supply-constrained buyers need. And put a capacity-and-energy line into M&A and site-selection diligence: if your acquisition or new facility assumes “we’ll just buy more AI capacity,” you need a real answer on grid interconnect and committed-capacity contracts before that assumption shows up in the model.

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.

The $725B number is going to keep getting bigger before it stops. Mid-year guidance raises this quarter aren’t an outlier — they’re the new pattern. The CEOs who treat AI compute like they treat power, water, and skilled labor — strategic inputs procured under long-term contracts with named substitutes — will end 2026 with operating leverage. The ones still treating it like a SaaS line item will spend the second half of the year explaining surprise overruns and capacity denials.

Sources: InvestorPlace (“Big Tech Is Spending $700 Billion”), Futurum Group (“AI Capex 2026: The $690B Infrastructure Sprint”), Artificial Intelligence News (Big Tech Q1 2026 results), The Motley Fool (“Is AI Infrastructure Spending Heading for an Even Bigger Boom?”), Goldman Sachs (“Tracking Trillions”), Fortune (“Big Tech’s $700B AI spending spree”), IndexBox (“AI Infrastructure Spending: Hyperscalers to Invest $720B in 2026”).

by

Microsoft Just Turned Outlook Into Your First Real AI Employee — and Solo Founders Are Already on the Cheap Side of the Bill

If you opened Outlook in the last two weeks and noticed Copilot offering to manage your calendar for you, you weren’t imagining it. Microsoft began rolling out the new Calendar Agent capability inside Microsoft 365 Copilot through April and May 2026, and the feature quietly answers a question every solo founder has been asking for two years: when does the AI start actually doing the job, not just summarizing it?

The answer, at least for the calendar, is now. Calendar Agent lets a user write a plain-English rule — Microsoft’s own example is “Decline any meeting longer than 60 minutes that doesn’t have an agenda” — and Copilot enforces it going forward. No app to open. No menu to configure. The agent reads incoming invites, applies your rules, and accepts, follows, declines, or cleans up canceled events on your behalf. It works across Outlook and Teams, respects compliance settings, and required no new admin controls to ship. It’s the first time Copilot has been allowed to take an action on a calendar without a human in the loop on every single meeting.

That sounds small. It isn’t. For a solo founder who spends two to four hours a week on calendar triage — sales calls, vendor pings, partner intros, the “got a sec?” Slack-to-meeting conversions — Calendar Agent is a 100-plus-hour-a-year refund. And it ships inside Microsoft 365 Copilot Business, which is currently priced at $21 per user per month, with a Copilot Business promotional bundle that runs through June 30, 2026. If you already pay for Microsoft 365 Business Standard, the marginal cost of installing a 24/7 executive assistant is roughly the price of a cheap streaming service.

Calendar Agent is only one of several agentic capabilities Microsoft pushed into general users’ hands in the same window. SharePoint added an AI Charts web part — page authors describe the data they want visualized in natural language and SharePoint builds the chart. Copilot Notebooks added AI summaries. File Explorer added “Ask Copilot.” Microsoft 365 E7 and Agent 365 went GA on May 1, 2026 (the enterprise side of the same story). The message is consistent across every surface: the Office suite that small business owners have used since the late 1990s is being rebuilt as an agentic platform, and the rollout is happening at the SMB price point, not the F500 price point.

Step back and the pattern across May 2026 is hard to miss. Anthropic launched Claude for Small Business on May 13 with 15 pre-built workflows. Notion shipped a free Workers runtime. Google announced Gemini Spark for Workspace Business at I/O 2026 on May 19. GoDaddy Airo for WordPress shipped on May 11. Square Managerbot is in open beta inside every U.S. Square Dashboard. And now Microsoft has turned the most common business workspace on Earth — the Outlook calendar — into a place where an AI can take action without supervision. Every major SaaS the average founder already pays for is becoming an agentic layer on top of itself.

If you want a place to actually translate all of this into an income system — instead of accumulating subscriptions and hoping productivity shows up — take a look at LevelUpLabs.co. It’s a membership built for entrepreneurs who want to put AI to work: prompt libraries you can paste in and run today, video training that gets to the point, ready-to-use checklists for the workflows that eat your week (calendar, inbox, lead intake, monthly close), and exclusive partner discounts on the same tool stack Microsoft just rebuilt. Instead of refreshing tech news and watching others compound, you get the strategies and the templates to ship.

So the practical question for a solopreneur reading this on Wednesday: what’s the first Calendar Agent rule you should write? Start with three. First, decline any meeting longer than 30 minutes that doesn’t have an agenda — this is the single highest-leverage filter in any founder’s week. Second, auto-accept any meeting from your top five customers or co-founders, and put a 10-minute buffer on either side. Third, set a hard rule that no Tuesday or Thursday morning is bookable; protect two deep-work blocks per week from yourself. Then in 30 days, look at how many hours of calendar admin you actually got back. If the number is anywhere north of three hours per week, you have just hired a virtual executive assistant for $21/month — about 1/200th the cost of the real thing.

The closing takeaway is the part that matters. Two years ago, the AI conversation for solo founders was about which chatbot to subscribe to. Today it is about which corner of your existing toolset just turned into an autonomous coworker. Microsoft did not announce Calendar Agent as a small business story, but the operators it will benefit most are the ones running their whole company out of one Outlook inbox and one calendar. Write the rules this week. Let the agent run. The hours come back faster than you think.

Sources:

  • Microsoft Learn — Introducing Calendar Agentic capabilities in Microsoft 365 Copilot (MC1296874) — https://mc.merill.net/message/MC1296874
  • M365 Admin — Introducing Calendar Agent capabilities in Microsoft 365 Copilot — https://m365admin.handsontek.net/introducing-calendar-agent-capabilities-microsoft-365-copilot/
  • EMDTec — Explore Exciting Enhancements In Microsoft 365 Updates May 2026 — https://emdtec.com/blog/microsoft/microsoft-365-updates-may-2026/
  • Microsoft 365 Blog — Microsoft 365 Copilot Business: The future of work for small businesses — https://www.microsoft.com/en-us/microsoft-365/blog/2025/12/02/microsoft-365-copilot-business-the-future-of-work-for-small-businesses/
  • Microsoft Security Blog — Microsoft Agent 365, now generally available, expands capabilities and integrations — https://www.microsoft.com/en-us/security/blog/2026/05/01/microsoft-agent-365-now-generally-available-expands-capabilities-and-integrations/
  • Anthropic — Introducing Claude for Small Business — https://www.anthropic.com/news/claude-for-small-business
by

Test-Time Compute Is the New Dial on Your AI Stack — Why “Which Workloads Get to Think” Is Now a Q3 2026 CEO Decision

Test-Time Compute Is the New Dial on Your AI Stack — Why “Which Workloads Get to Think” Is Now a Q3 2026 CEO Decision

The 2026 model conversation has quietly shifted under most CEOs without an explicit purchase decision. For the last 18 months the question on the buying side was which frontier model. As of May 2026, the more important question is how much thinking you’re paying for, and on which workloads. Test-time compute — the “thinking meta” — is now the architectural default, and it has turned into a dial your AI stack operates whether you’ve configured it intentionally or not.

The shift is industry-wide. GPT-5.X Thinking, Claude’s extended thinking, and Gemini’s thinking models all bake test-time compute into the main product, with the model dynamically allocating more GPU cycles to harder problems instead of charging a separate “reasoning tier.” Pluralsight’s 2026 model roundup, IBM’s The trends that will shape AI and tech in 2026, and Google Cloud’s AI Agent Trends 2026 all describe the same architectural move: production agents route most calls to small/efficient models for extraction, routing and schema work, and invoke thinking-tier compute only at named decision nodes. Gartner still puts enterprise app embed at roughly 40% by EOY ’26, but the more useful number is the cost spread: an agentic workflow that “thinks” through every step burns 10–30× more tokens than the same workflow with reasoning gated to a handful of points. Inference is ~85% of enterprise AI spend, and the thinking dial is by far the most expensive lever in the stack.

That’s where the procurement problem hides. Most enterprises bought their AI access in 2024–2025 with a per-seat or per-token line item and a single default model. The thinking meta turns that line item into something closer to cloud compute — variable, workload-dependent, and very sensitive to default configuration. Vendors are not all the same here. Some bill thinking as part of the base. Some surface it as separate compute. Some quietly upgrade default workloads to thinking mode and the bill moves before procurement notices. Anthropic’s Q1 reporting +80× YoY ARR and one frontier lab now estimated at ~40% of enterprise LLM spend means a single configuration default at the top vendors can move the median customer’s AI budget by 20–40% in a quarter. Most CEOs are not running that math.

The other side of the dial is upside the same companies are not capturing. Production deployments report measurable economic impact, but the gating is governance, not model capability. Companies that have actually shipped value past pilot purgatory have done it by treating which workloads deserve test-time compute as a real classification — high-stakes diagnostic, ambiguous escalation, financial reconciliation, multi-step planning — and routing the rest to small fine-tuned models on schema-constrained tasks. Where this lands on the org chart matters: this is no longer a CIO call. It is a CFO, COO and CEO call together, because the dial moves capex-level dollars and ties to where you are willing to bet judgment cycles against speed.

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 see which AI repricings, GTM resets and macro shifts actually move your decisions next week, without drowning in feed noise.

There are three Q3 2026 moves worth making while the dial is still adjustable. First, instrument cost-per-completed-task on your top three AI workflows and tag every call with whether it used thinking mode — most teams cannot answer this question today, which is itself the finding. Second, write an explicit workload classification policy: which categories of work are allowed to invoke thinking-tier compute by default, which require explicit elevation, and which are explicitly capped at small-model routing. This is not a technical document; it is a budget control with judgment baked in. Third, renegotiate your top AI vendor contract with the thinking-tier line item visible. The current generation of master agreements often bundles reasoning capacity into base pricing in ways that look generous and are not, especially if your usage profile is agentic. If your vendor will not separate the line, that itself tells you what your renewal leverage looks like.

The deeper point is that AI buying is finishing its transition from a software purchase to a compute purchase. Per-seat language is still on the invoice, but the unit of consumption is “thinking minutes against named decision nodes.” Companies that name those nodes win on both sides of the trade — they pay for reasoning where it earns its keep, and they refuse to pay for it everywhere else. Companies that do not name them get the thinking meta as a default and the bill as a surprise.

The CEOs who treat test-time compute as a dial to operate, not a feature that arrived, will spend the next two quarters quietly outperforming peers who are still buying AI like it is 2024 SaaS.

Sources: Pluralsight (The best AI models in 2026), IBM Think (The trends that will shape AI and tech in 2026), Google Cloud (AI Agent Trends 2026), Gartner enterprise embed forecast, MachineLearningMastery (7 Agentic AI Trends to Watch in 2026), Salesforce (8 Ways AI Agents Are Evolving in 2026).

by

SAP Just Spent Two Years Building the “Autonomous Enterprise” — Solo Founders Are Already Living in It

Last week in Madrid, SAP — the German software giant whose ERP runs the back office of roughly 80% of the Fortune 500 — used its annual Sapphire conference to declare itself an “Autonomous Enterprise” company. CEO Christian Klein took the stage on May 20, 2026 and announced the new SAP Business AI Platform, a transformation of SAP’s entire SaaS portfolio into the SAP Autonomous Suite, and a roster of 224 AI agents plus 51 assistants embedded across finance, procurement, and supply chain. Anthropic’s Claude was named the primary reasoning model. Headlines called it the most significant evolution of SAP’s applications business in the company’s history.

Here is the part of the story that didn’t get the press: the small business gap is widening. Analyst write-ups out of Sapphire openly acknowledged that the Autonomous Enterprise is built for companies large enough to already run SAP — which is to say, not you. A typical SAP S/4HANA rollout still takes 12 to 24 months and costs millions of dollars before a single agent runs. For a Fortune 500 CFO, “autonomous enterprise” is a five-year roadmap.

For a solo founder, it’s available right now.

That’s the part worth pausing on. Every component of SAP’s autonomous vision — agents that reconcile cash flow, draft customer responses, manage inventory, route invoices, generate marketing assets, prepare meeting briefings — has a working SMB equivalent that shipped in the last six weeks. Anthropic’s Claude for Small Business (launched May 13, 2026) packages 15 pre-built agentic workflows across finance, ops, sales, marketing, HR, and customer service, with native connectors to QuickBooks, PayPal, Gmail, Microsoft 365, Square, Stripe, Slack, Docusign, Canva, and Webflow. Shopify’s Sidekick Pulse proactively surfaces next steps for store owners. Block’s Square Managerbot is a 24/7 AI business manager running inside every U.S. Square Dashboard. Notion 3.5 added a free Workers runtime so a solopreneur can host a custom backend agent next to their notes. Microsoft Agent 365 went GA on May 1. GoDaddy Airo for WordPress lets one prompt build and maintain an entire site.

None of that requires an implementation partner. Most of it is included in the SaaS subscriptions you’re already paying. The Anthropic / PayPal / Canva “AI Fluency for Small Business” course is free.

So here is the asymmetry that solo founders should internalize this week: you are operationally lighter than SAP’s largest customers. You don’t have to migrate off twenty years of legacy ERP. You don’t have to convince a board, an auditor, or a 40,000-person change-management team. You don’t have to wait until 2030 for your finance department to be ready. You can wire an autonomous business this quarter — five tools, three weekends, one founder.

The data backs this. Microsoft’s AI Economy Institute’s Global AI Diffusion in Q1 2026 report (covered by Fortune in May) showed AI adoption diffusing fastest into Sun Belt suburbs and small businesses, not coastal enterprises. Intuit’s 2026 AI Impact Report — built with University of Chicago economists across 34,000+ owner survey responses and 5.3 million QuickBooks businesses — found that 68% of SMBs now use AI regularly, up from 48% in July 2024, with 74% reporting productivity gains. The Federal Reserve’s mid-2025 monitoring data flagged something it had never seen: small businesses adopting AI faster than large firms, with the 10-to-100-employee segment jumping from 47% to 68% in a single year.

If you want a place to actually do something with all of this — instead of refreshing tech news and watching the gap widen on the wrong side — check out LevelUpLabs.co. It’s a membership built for entrepreneurs who want to build income systems with AI: prompt libraries you can run today, video training that doesn’t waste an hour to make a point, ready-to-use checklists for the most common owner workflows, and exclusive partner discounts on the same tool stack SAP just declared the future of enterprise software. The strategies are the same as the ones being sold to Fortune 500 CFOs — minus the seven-figure implementation contract.

The closing takeaway is simple. SAP’s announcement is real, important, and a leading indicator. The autonomous enterprise is happening. But the runway is twenty times longer for big companies than it is for you. Don’t read the headline and conclude that AI agents are an enterprise story you’ll get to when you scale. Read it as the most expensive trade conference in the world telling you, in 224 agents and 51 assistants, exactly what your business will look like in two years. Then go build that version of your business this weekend, while the people with $500M IT budgets are still in steering-committee meetings about it.

Sources:

  • SAP News Center — 2026 SAP Sapphire Keynote: Powering the Autonomous Enterprise — https://news.sap.com/2026/05/sap-sapphire-keynote-business-ai-platform-power-autonomous-enterprise/
  • SAP News Center — SAP Unveils the Autonomous Enterprise — https://news.sap.com/2026/05/sap-sapphire-sap-unveils-autonomous-enterprise/
  • Constellation Research — SAP Sapphire 2026: SAP makes its case… — https://www.constellationr.com/insights/news/sap-sapphire-2026-sap-makes-its-case-it-should-your-autonomous-enterprise-platform
  • Anthropic — Introducing Claude for Small Business — https://www.anthropic.com/news/claude-for-small-business
  • Fortune — America’s new AI map shows something surprising… — https://fortune.com/2026/05/21/normal-people-using-ai-microsoft-diffusion-report/
  • Federal Reserve — Monitoring AI Adoption in the U.S. Economy — https://www.federalreserve.gov/econres/notes/feds-notes/monitoring-ai-adoption-in-the-u-s-economy-20260403.html
by

Checks Are Going Out in the Zales TCPA Settlement — Here’s the Operator Lesson Behind the Headlines

This month, settlement checks started landing in mailboxes for the Zales TCPA class action — up to $100 each, across roughly 75,000 phone numbers, out of a $7.54 million fund. It is a useful moment to look past the headline number, because the three biggest TCPA settlements making news right now each fail in a different, very preventable way. For operators, they read less like legal news and more like a punch list.

Three settlements, three distinct mistakes

Zales — $7.54M. The jeweler was sued for sending marketing texts to numbers on the National Do Not Call Registry. The class definition is the lesson: numbers registered on the DNC list for at least 30 days that then received at least two texts within a 12-month period. That is a pure list-hygiene failure — texting people who had told the government, in writing, to leave them alone.

Truist Bank — $4.1M. The bank settled claims it placed prerecorded calls about accounts to the wrong people — roughly 6,000 numbers that were not the account holders and had not consented to anything. The plaintiff alleged he got two dozen robocalls meant for someone else. That is a wrong-number and data-quality failure: calling reassigned or mistyped numbers without a process to catch them.

Everything Breaks — about $995K. The warranty company settled claims of repeated telemarketing robocalls to consumers on the National Do Not Call Registry. Same root cause as Zales, smaller company, smaller fund — proof the exposure is not just a big-brand problem.

The volume behind the settlements

None of this is happening in a vacuum. More TCPA class actions were filed in the first quarter of 2026 than in any quarter in recorded history. The plaintiffs’ bar has industrialized the work: intake, list analysis, demand letters, and class definitions are now a repeatable pipeline. When filing volume is at an all-time high, the question for an outbound operation is not whether your practices will be tested but when.

The operator punch list

Scrub every outbound list against the National Do Not Call Registry on a fresh cycle — not a download from last quarter — and keep your internal do-not-call suppression synchronized across every system and brand. Build reassigned-number checking into your dialing so you stop calling numbers that changed hands; the FCC’s Reassigned Numbers Database exists for exactly this. Treat a wrong-number complaint as a stop signal, not a data-entry note. And keep consent and suppression records you can actually produce, because in every one of these cases the company’s inability to prove a clean practice is what turned a complaint into a fund.

For operators, the cheapest line of defense is also the most overlooked: scrub your call and text lists before you dial. TCPALitigatorList.com maintains the most widely used database of known TCPA plaintiffs and serial filers. Running an outbound list through it takes minutes and keeps professional litigants off your campaigns before they ever pick up the phone — which, given how fast statutory damages add up, is one of the highest-return compliance steps an operator can build into a launch checklist.

The takeaway

Zales, Truist, and Everything Breaks did not lose to exotic legal theories. They lost to stale lists, wrong numbers, and opt-outs that did not propagate. Those are operational problems with operational fixes — and in a record-setting filing environment, fixing them is cheaper than funding the next settlement.

Sources

Top Class Actions — “$7.54M Zales TCPA class action settlement”; Class Action.org — “$4.1M Truist Bank Settlement”; CompliancePoint — “Truist Bank Settles $4.1M TCPA Lawsuit”; Top Class Actions — “Everything Breaks $995,000 TCPA settlement”; CompliancePoint / Shipkevich PLLC — 2026 TCPA litigation trend reporting.

by

There’s a New TCPA Lawsuit Going Around — and It’s About What Shows Up on the Screen

Operators have spent two years bracing for the obvious TCPA traps: consent, quiet hours, do-not-call scrubbing. Here is the one most teams have not even put on the board. Plaintiffs’ lawyers have found a new claim, and it has nothing to do with whether the recipient consented. It is about what your call or text actually displayed on the recipient’s phone — the caller ID — and a string of 2026 rulings just confirmed consumers can sue over it.

The rule nobody was watching

Buried in the FCC’s telemarketing regulations, 47 C.F.R. 64.1601(e) requires telemarketers to transmit caller identification information — a name and a number a consumer can call back to make a do-not-call request. For years this was treated as a technical rule enforced, if at all, by regulators. In 2026 that changed. Multiple federal courts have now held that consumers have a private right of action to sue over caller ID failures, and that the requirement applies not just to voice calls but to marketing text messages.

What the recent cases show

The picture is genuinely mixed, which is exactly why it is dangerous. In Zelma v. Ram, decided in the District of New Jersey on May 19, 2026, the court gave defendants something to like: displaying the recognizable brand name “RE/MAX” next to the number was enough to satisfy the caller ID requirement. But in Novia v. Mobiz, a Massachusetts federal court let a caller ID claim over marketing texts survive the pleading stage, and a second court has now recognized a private right of action for SMS caller ID failures. Translation: a defective sender ID on a text blast is now a viable class claim, and the safe-harbor line — what counts as adequate identification — is still being drawn case by case.

Why this hits operators hard

Most outbound text programs were never built with this rule in mind. Short codes, rotating 10DLC numbers, alphanumeric sender IDs, and “no-reply” configurations are everywhere — and several of those setups arguably fail to give the consumer a name plus a callable number for do-not-call requests. Because TCPA damages run $500 to $1,500 per message, a single campaign sent from a non-compliant sender ID to a large list is a ready-made class action, even if every recipient opted in. Consent does not cure a caller ID defect.

What to do this week

Pull up your last five outbound campaigns on an actual phone and look at what displays. Does the recipient see an identifiable business name? Is there a number they can call back — one that is monitored — to ask not to be contacted? For voice, confirm your transmitted CNAM and ANI resolve to your business, not a blank or a spoofed-looking string. For texts, make sure the sender identity and the opt-out path are unambiguous. And watch the states: Florida’s 2026 legislature is weighing strict caller identification mandates that would go further than the federal rule.

For operators, the cheapest line of defense is also the most overlooked: scrub your call and text lists before you dial. TCPALitigatorList.com maintains the most widely used database of known TCPA plaintiffs and serial filers. Running an outbound list through it takes minutes and keeps professional litigants off your campaigns before they ever pick up the phone — which, given how fast statutory damages add up, is one of the highest-return compliance steps an operator can build into a launch checklist.

The takeaway

The caller ID claim is attractive to plaintiffs precisely because it sidesteps the hardest part of a TCPA case — proving lack of consent — and turns instead on a technical display detail the defendant either got right or did not. Get it right before a plaintiff checks it for you.

Sources

Zelma v. Ram, 2026 WL 1398784 (D.N.J. May 19, 2026); National Law Review — “MAX TCPA Clarity”; Buchanan Ingersoll & Rooney — “Calling for Clarity: Navigating New Caller ID TCPA Claims”; Bubeck Law — “A New TCPA Risk: Caller ID Requirements for Marketing Texts?”; 47 C.F.R. 64.1601(e).

by

A Federal Court Just Drew a Cleaner Line Between You and Your Lead Vendors

If you run outbound calling or texting and you buy leads, hire a dialing vendor, or work through affiliates, here is a ruling worth pinning to the wall. On May 15, 2026, a federal judge in the Western District of Washington threw out TCPA claims against two insurance companies in Sundstrom v. Ocean Reef Media LLC, finding the plaintiff never plausibly explained why those insurers should answer for calls a different company allegedly placed. For operators, that is a rare piece of good news — and a clear roadmap for how to keep yourself out of the same complaint.

What happened

The plaintiff received marketing calls and sued not just the entity that dialed, but the insurers whose products were ultimately being pitched. The theory was vicarious liability: hold the brand at the end of the funnel responsible for the conduct of the lead generator at the front of it. The court was not persuaded. It dismissed the claims against the insurers because the complaint offered conclusions — “they were agents,” “they authorized this” — without the concrete facts a court needs to make that link plausible. Speculative inferences, the judge held, are not enough.

Why operators should care

TCPA liability has never stopped at the company that physically pressed “send.” Under the FCC’s long-standing agency framework, a brand can be on the hook for a vendor’s or affiliate’s calls if it controlled the manner and means of those calls, ratified them, or cloaked the caller in apparent authority. That is exactly how a plaintiff’s lawyer tries to reach the deeper pockets. Sundstrom does not erase that exposure. What it does is confirm that a plaintiff has to actually plead the relationship — who directed whom, what the contract said, who set the script, who controlled the lists — and cannot simply name every company in the chain and hope discovery fills the gap.

That cuts both ways. It is a defense win if your paperwork and your day-to-day practice genuinely keep you at arm’s length from a vendor. It is a loaded gun pointed at you if they do not, because the same facts that defeat a vague complaint will sink a well-pleaded one.

The operator checklist

Treat Sundstrom as a prompt to audit how much control you exert over the people dialing on your behalf. Read your vendor contracts: do they assign TCPA compliance, consent capture, and list scrubbing to the vendor in writing, with indemnification? Look at practice, not just paper — if your team writes the scripts, approves the call windows, hands over the lists, and monitors the dialer, a court will see an agency relationship no matter what the contract title says. Keep consent records that travel with the lead, so you can show where a phone number came from and what the consumer actually agreed to. And require proof, not promises, that your partners are scrubbing against do-not-call data and known litigants before any campaign goes out.

For operators, the cheapest line of defense is also the most overlooked: scrub your call and text lists before you dial. TCPALitigatorList.com maintains the most widely used database of known TCPA plaintiffs and serial filers. Running an outbound list through it takes minutes and keeps professional litigants off your campaigns before they ever pick up the phone — which, given how fast statutory damages add up, is one of the highest-return compliance steps an operator can build into a launch checklist.

The takeaway

The win in Sundstrom went to defendants who could not be plausibly tied to the calls. The lesson for everyone else is that the tie is built — or avoided — long before a complaint is filed. Tighten your vendor governance now, and a future plaintiff will have nothing concrete to plead. Leave it loose, and the next court may have plenty.

Sources

Faegre Drinker — “Washington Federal Court Dismisses TCPA Claims, Finding Insufficient Allegations of Vicarious Liability”; Sundstrom v. Ocean Reef Media LLC, No. 26-5036, 2026 WL 1361646 (W.D. Wash. May 15, 2026).

by

The Average Small Business Owner Now Works Five Jobs — A New Survey Shows AI Is Quietly Absorbing the Worst of Them

If you run a small business and have ever felt like you’re not one person but five, a new survey says you’re not imagining it. A May 2026 study of 1,000 American small business owners — commissioned by Adobe Express and conducted by Talker Research — found that the average owner performs five distinct operational roles every single day, and that the math of doing so adds up to more than 200 extra hours of work per year.

That’s the part worth sitting with. Two hundred hours is five full work weeks. It’s an unpaid second job hiding inside the first one.

The five hats, quantified

The survey put numbers on roles most founders already wear without naming them. On any given day, the small business owner is also acting as customer service representative (54%), marketer (44%), bookkeeper (43%), social media manager (41%) and creative director (35%). None of those jobs is optional. All of them compete for the same finite founder attention — and most of them are the kind of work that expands to fill whatever time you give it.

This is the quiet tax of being small. A larger company hires a person for each of those functions. A solo founder or a five-person shop simply absorbs them, usually in the margins of the day, usually after the “real” work is done. The result is the 200-hour overhang the survey measured: not dramatic, not a crisis, just a steady leak of time that never shows up as a line item.

Where AI is actually landing

What makes the 2026 data interesting is where AI has started to plug into that leak. Half of the owners surveyed — 50% — said they now use AI tools regularly or occasionally. And among those users, the two most common jobs they hand to AI map almost exactly onto the most draining of the five hats: 56% said they most often use AI for research tasks, and 46% use it for design and visual content creation.

Read that against the role list and the logic is obvious. Research is the invisible front end of being a marketer, a bookkeeper and a creative director all at once — figuring out what to write, what a competitor charges, how a form works, what a regulation means. Design and visual content is the social media manager and creative director hats fused together. AI isn’t replacing the founder in those roles; it’s compressing the hours each role demands.

The most telling number, though, is about confidence rather than time. Nearly three-quarters of AI users said the tools increased their confidence in handling tasks outside their expertise. That’s a different kind of value. It’s not just “AI did the logo faster.” It’s “I attempted the logo at all, instead of stalling or overpaying a freelancer for a job I could have briefed myself.”

AI is now part of the decision to start

The survey reached back even further — into the decision to become an entrepreneur in the first place. Among respondents at least somewhat familiar with AI, 38% said its availability played a role in their decision to start a business, and 40% pointed specifically to AI’s ability to help in areas where they lacked confidence.

That reframes AI from a productivity tool into something closer to an on-ramp. For a long time, the five-hats problem was a barrier to entry: if you couldn’t do bookkeeping, design and marketing, you either paid for all three or didn’t start. A meaningful slice of 2026’s new founders are saying they crossed that line because AI made the missing skills survivable.

Putting it into practice

Knowing AI can absorb a few of your five hats is not the same as actually getting it to. The gap is almost always knowing which tasks to delegate and how to brief them well. That’s the problem LevelUpLabs.co is built to solve — it’s a membership for entrepreneurs who want to turn AI from a novelty into real income systems, with prompt libraries, video training, ready-to-use checklists, and partner discounts on the tools you were going to buy anyway. Instead of reading one more survey about your missing hours, you walk out with the workflows that hand the worst of those hours to a machine.

Bottom line

The five-hats reality of small business isn’t going away — but the 2026 data suggests it no longer has to cost a founder five extra work weeks a year. Pick the two roles that drain you most, point AI at the research and creative grunt work inside them, and treat the confidence boost as the real prize. The owners already doing it didn’t get a sixth employee. They got their evenings back.

Sources:

  • Talker News — Survey finds entrepreneurs juggling 5 jobs to keep things running (May 21, 2026)
  • Business2Community — Small Business Owners Are Using AI to Manage Multiple Companies, Survey Finds
  • Adobe Express / Talker Research — 2026 survey of 1,000 U.S. small business owners