Last week was compressed: Memorial Day took Monday, and you were out through Wednesday. I still had 30 completed client calls from Tuesday through Friday, and the useful conversation is less about the raw count and more about where that work should go next.
The lane I want to lean into is triad intervention: account team, GTME, and customer in the same working motion, with me owning the path from customer problem to usable Apollo workflow.
The account pattern is getting clearer. Domo already shows the motion: signal, list, research, approved message plan, workflow, and learning loop. Securiti is the current triad version. Telnyx is an early agentic outbound candidate. Martal Group looks like a high-value activation candidate, but I do not want to call it an active AI motion until I have the account context confirmed.
I also want your read on how much of my week should move toward team enablement for MCP and Apollo CLI requests, plus client-shareable skills for customers building AI-assisted outbound systems.
The clean takeaway is this: last week produced 30 completed client calls, two closed-won renewal records in the May context pull, and a clear customer pattern around AI-assisted outbound. Domo shows the most mature version. Securiti is the current triad intervention. Telnyx and Martal Group need tighter discovery before I treat them as active motions.
These are the customer patterns I want to discuss with you. I am separating active motions from candidates so we do not overstate what is verified.
| Account | Verified pattern | Decision for our one-on-one |
|---|---|---|
| Domo | Weekly EMEA enablement, Claude MCP connector, gated-content workflow, AI Research, scoring and messaging, and Projects work. This is the closest working example of the motion. | Use Domo as the proof pattern for signal to research to approved outbound to learning loop. |
| Securiti | Current triad intervention: Salesforce field discovery first, Apollo exposure second, Claude exposure third, then BDR skills and a narrow pilot. | Decide if Securiti becomes the first formal triad intervention lane this week. |
| Telnyx | May 26 first intervention around Apollo AI-powered prospecting inside an agent-focused system, with enrichment, scoring, and outbound in scope. | Confirm whether Telnyx needs an account-team scoped follow-up or a reusable discovery path. |
| Martal Group | $90.1K ARR account with high-risk flags, 27 paid seats, 53-person sales team, June and August renewal exposure, and activation gaps across CRM, sequences, AI sequence, workflows, and enrichment. | Treat Martal as a discovery candidate, not an active AI outbound motion, until I verify customer intent. |
| DemandScience | Live AI messaging build, MQL workflows, account prioritization, and dialer plus sequencing pilot. | Use as another proof point for turning trial work into governed outbound experiments. |
| VideoAmp | Live AI Context Center support, Buyer Lane Router, prompt library, and ten client-shareable GTM skills. | Use as the best example of packaging skills customers can actually reuse. |
| EZRA Coaching | ChatGPT MCP workflow support, contact-data workflow review, approval phrases, and fallback guidance. | Use as the cleanest example for team support on MCP and safe customer workflows. |
| Achievers | Claude as the home base, MCP mapping, Context Center, AI research layers, Salesforce-triggered enrollment, and inbound automation. | Decide whether this becomes a repeatable inbound-to-sequence pattern for the team. |
Monday had no completed client call I am counting here. The client call coverage starts Tuesday after the holiday.
| Date | Client | Call |
|---|---|---|
| Tue, May 26 | Perplexity | 9:30 AM, Pocus and Apollo discussion |
| Tue, May 26 | Yelp | 10:00 AM, proof-of-concept check-in |
| Tue, May 26 | Domo | 10:00 AM, EMEA team enablement |
| Tue, May 26 | Telnyx | 11:00 AM, Kevin Ward and Vince |
| Tue, May 26 | Myers Industries | 12:00 PM, Sabrina Robertson and Vince |
| Tue, May 26 | Rapidflare | 12:30 PM, bi-weekly check-in |
| Tue, May 26 | Securiti | 1:30 PM, weekly connect |
| Tue, May 26 | EZRA Coaching | 3:00 PM, pilot office hours |
| Tue, May 26 | Domo | 3:45 PM, weekly office hours |
| Wed, May 27 | Anchin | 9:30 AM, client working session |
| Wed, May 27 | Glean | 11:00 AM, client working session |
| Wed, May 27 | Veeam | 12:30 PM, client working session |
| Wed, May 27 | Perplexity | 2:30 PM, client working session |
| Wed, May 27 | Domo | 3:45 PM, daily check-in |
| Thu, May 28 | Arcesium | 9:30 AM, client working session |
| Thu, May 28 | eHealth Technologies | 10:30 AM, client working session |
| Thu, May 28 | Paramount | 12:00 PM, account team session |
| Thu, May 28 | Achievers | 12:30 PM, bi-monthly connect |
| Thu, May 28 | ColumnTech | 1:00 PM, client working session |
| Thu, May 28 | VideoAmp | 1:30 PM, sales troubleshooting and live support |
| Thu, May 28 | Cineplex | 2:00 PM, working session |
| Thu, May 28 | EZRA Coaching | 2:30 PM, client working session |
| Thu, May 28 | MissionSquare | 3:00 PM, client working session |
| Thu, May 28 | Domo | 3:45 PM, daily check-in |
| Thu, May 28 | Renesas | 4:30 PM, scoring and integration |
| Fri, May 29 | WP Engine | 8:30 AM, Apollo workflow discussion |
| Fri, May 29 | Appier | 9:00 AM, sales strategy sync |
| Fri, May 29 | Stephen Gould | 10:00 AM, monthly sync |
| Fri, May 29 | Domo | 10:30 AM, Projects Deep Dive |
| Fri, May 29 | EZRA Coaching | 12:30 PM, contact data workflow discussion |
The accounts I would use as the proving ground this week are Securiti, Domo, Telnyx, VideoAmp, EZRA, Achievers, DemandScience, and Martal Group once customer intent is verified.
These are the lanes I want to carry into the next one-on-one.
My first vote is Securiti because the current work already has the right shape: Salesforce field discovery, Apollo exposure, Claude exposure, BDR skills, owner-backed decisions, and a narrow pilot. Telnyx and Martal may belong in the same motion, but I want to confirm intent before I label either as active.
I want to build a cleaner support lane for customers asking how Apollo connects into Claude, ChatGPT, MCP, and command-line workflows. That means reusable discovery questions, approval language, credit-sensitive action maps, and examples the team can use without starting from zero.
The likely starting points are account research, sequence analysis, buyer lane routing, Salesforce field mapping, enrichment review, and safe Apollo workflow planning. VideoAmp is the best current pattern for packaging this cleanly.
If this becomes a team lane, I want to know where I should stay the technical owner and where another GTME or account partner should carry the repeatable version forward.
I can bring completed calls, one formal triad example, client-shareable skills created, MCP or Apollo CLI support handled, and account candidates moved from discovery to active motion. I want your read on what matters most.
| Account / Topic | Action | |
|---|---|---|
| 1 | Securiti | Use the June 3 working session as the first formal triad intervention: field contract, Apollo exposure, Claude exposure, skills, and approval gates. |
| 2 | Domo | Write down the repeatable signal-to-research-to-outbound pattern so it can guide other agentic outbound accounts. |
| 3 | Telnyx | Confirm whether the May 26 agent-focused prospecting conversation needs a scoped account-team follow-up. |
| 4 | Martal Group | Run discovery before making AI claims: confirm customer intent, current activation blockers, and whether an outbound skill would be useful. |
| 5 | MCP and Apollo CLI | Create a support path for team asks around Apollo-connected AI systems, including questions, safety gates, approval phrases, and examples. |
| 6 | Client-shareable skills | Package the first reusable skills customers can use for account research, sequence review, buyer routing, enrichment review, and workflow planning. |
| 7 | VideoAmp and EZRA | Use VideoAmp for skill packaging and EZRA for MCP support patterns so the team has examples from real customer work. |