Wissam Tabbara

Can You Use Text Messages for Cold B2B Outreach?​

The short answer: automated cold texting is generally not a sound B2B outreach strategy.

The complete answer is more nuanced. Whether a message crosses a legal line depends on the recipient, jurisdiction, technology, content, and how it was sent. But legality is only the first gate. Mobile carriers, messaging providers, Apple, and WhatsApp impose their own rules, often requiring consent even where someone argues that the narrow legal floor is less clear.

That means a business cannot answer this question by asking only, "Can we technically send the message?"

It has to ask four questions:

1. Does the law permit this exact message and sending method?
2. Does the carrier permit the traffic?
3. Does the messaging provider's contract permit it?
4. Will recipients welcome it rather than block or report it?

A mobile number tells you where a person can be reached. It does not tell you that they agreed to automated outreach.

The Signal-Based Opener Is the Last Step, Not the Play​

A timely signal can produce a good opening line.

A new executive joins. A company starts hiring for a new motion. A product launches. An account publishes evidence of a problem you understand. You give that context to an AI model, ask for a relevant opener, and get something much better than “I noticed your company is doing great things.”

That feels like progress, but the opener is still only the visible artifact. The valuable part is the operating contract behind it: which signal was trusted, whether the account fits, which buyer matters, what evidence the message may use, and who reviews the result before it becomes outreach.

The opener should cite why now. The workflow should preserve why it was trusted.

Signal-to-Sequence Outbound Needs an Execution Control Plane​

Signal-to-sequence outbound is becoming an operator goal.

The demo is easy to understand: find a buying signal, collect contact data, generate the right sequence copy, and push the lead into outreach.

That is why the approved topic matters. Adam Robinson's workshop post about Claude skills for signal-to-sequence outbound is not interesting because it proves one toolchain will win. It is interesting because it shows where the market is moving. Operators want deployable workflows, not more AI commentary.

The bottleneck is not finding one more signal. The bottleneck is deciding whether that signal should become reviewed, relevant outreach.

Outbound Reporting Needs a Defensible Outcome Ledger​

Outbound reporting has a habit of becoming too busy to manage.

A weekly dashboard shows sends, opens, clicks, bounces, replies, meetings booked, meetings held, sequences running, domains warming, reps active, accounts touched, contacts added, tasks completed, and maybe a few pipeline numbers if the CRM is clean enough.

Some of that data is useful. Most of it is debugging data. It helps an operator understand whether the machine is physically moving.

It does not always explain whether the GTM motion is getting better.

The useful outbound report is not the busiest dashboard. It is the ledger that lets the team defend the next decision.

Signal-Weighted Routing Needs Explainable Assignment​

Round-robin lead routing solved a real operations problem: it made distribution feel fair. When every lead looked roughly the same, next rep up was a simple rule that everyone could understand.

But fair distribution is not the same as good assignment.

A lead can now carry account fit, product behavior, source quality, relationship history, hiring signal, technographic context, territory, urgency, and rep capacity. If the routing system only sees queue order, it throws away the context GTM teams worked hard to collect.

The routing question is no longer who is next. It is who has the best context to move this account now.

The next GTM AI failure mode will not look dramatic.

It will look like work that technically happened, but cannot be trusted.

An agent researched an account, but nobody can see which source changed the qualification decision. A lead moved forward, but the buyer context is missing. A draft was generated, but the premise is not tied to evidence. A campaign step is marked complete, but the exception that should have stopped it never surfaced.

The failure is not that AI did nothing. The failure is that the workflow cannot explain what happened.

HubSpot vs Salesforce may be becoming the most interesting battle in GTM.

For a long time, the framing was simple. Salesforce was the enterprise CRM. HubSpot was the SMB and mid-market CRM.

That framing is starting to feel outdated.

The new battle is not just CRM vs CRM. It is the battle to become the operating layer for GTM teams.

That means the system that connects customer data, account signals, buyer context, AI agents, and human review into one repeatable motion.

The most valuable person in the AI era may not be the deepest specialist.

It may be the person who can manage the most context across disciplines.

For years, building something required a full cross-functional team.

A product manager to define the problem.

A designer to shape the experience.

An engineer to build it.

A QA person to test it.

A marketer to position it.

A growth person to distribute it.

A leader to keep everyone aligned.

For years, I made a deliberate bet: the browser was my operating system.

Mail, Slack, docs, spreadsheets, passwords, bookmarks, writing tools, all of it lived in the browser.

It made my laptop feel almost disposable.

My real work environment was not the machine. It was the browser state.

That model was incredibly powerful in the SaaS era.

The most valuable data in AI may no longer be on the public internet.

A few years ago, public internet data was the prize. It was human, messy, massive, and still largely untapped.

Now a growing share of the web is AI-generated. The public layer is getting flatter, and in many places, less original.

At the same time, our behavior is changing. We are feeding these systems everything: docs, chats, images, spreadsheets, notes, memory, and context.

More context in, better output out.

That shift is already visible in the data. Microsoft's 2024 Work Trend Index, based on 31,000 people across 31 countries, found that 75% of global knowledge workers use AI at work and 78% of AI users bring their own AI tools to work. McKinsey's 2025 State of AI survey found that 88% of organizations report regular AI use in at least one business function, but only about one-third say they have begun scaling AI programs.