Jason + Stephanie | Week of June 1
The signal is getting consistent: customers are not just asking for better copy or cleaner resources. They are trying to turn Apollo data, Salesforce context, Model Context Protocol access, Apollo CLI workflows, and approval gates into outbound systems that can actually run.
I want to use this week to burn down the in-motion work and package the next motion: a Context Center upgrade engagement where the first leadership call is agentic discovery. We map the Apollo use cases, score readiness, identify context gaps, and leave with an automation path.
The Renesas upsell is the opportunity shape I want to focus on for custom builds: a customer-specific business case tied to Apollo-to-Salesforce mapping, scoring, mailbox strategy, and a 300-seat expansion path. We presented work their team could use to evaluate the operating value, not just the feature set, and that is the pattern I want to repeat when the account has real expansion motion and clear execution constraints.
The triad lane should go to accounts where the ask needs more than advice. These are the week-of candidates where GTME can help the account team connect customer context, Apollo data, Salesforce controls, agent workflow design, and approval gates.
Use the account team, GTME, and customer-owner model for Salesforce fields, Apollo exposure, Claude exposure, business development representative skills, and a narrow pilot plan.
Turn the June 2 account session into a readiness review: target motion, source data, approval requirements, and where an outbound agent could safely assist.
Continue the Signal, List, Sequence, Workflow model and use it as the cleanest example of turning inbound motion into a controlled automation path.
Map Context Center, account prioritization, marketing-qualified lead routing, dialer flow, sequencing, and approval gates before adding more execution assets.
Use the transcript workflow and support handoff as the pattern for moving client requests into reusable skills that can support larger agentic systems.
Domo remains the reference pattern for agentic outbound: research, scoring, workflow design, approval, and team-ready prompts in one operating path.
The first call should not start with a deck or a feature tour. It should start with the customer motion: who they want to reach, what Apollo already knows, what Salesforce must control, where approvals are needed, and which automations can safely run.
Use cases, buying motion, and data sources.
Readiness for context, routing, and approval gates.
Context Center, skill, workflow, or Apollo CLI path.
Test with the account team and customer owner.
Turn the path into a reusable package.
The strongest motion is repeatable: discover the use case, score the readiness, build the path, validate with owners, and make it reusable.
Renesas is the strongest current proof point. The work moved from Salesforce mapping into mailbox discussion, a protected Project Vanguard business case, and a June 5 Customer Success Qualified Lead for 300 seats.
The triad model is the operating pattern to reuse when the customer needs technical build work, not just advice: account team, GTME, and customer owners aligned around Salesforce fields, Apollo exposure, Claude exposure, business development representative skills, and a narrow pilot.
The verified state is 512,966 Apollo records, 451,782 locally ingested, 88.07 percent coverage, 13,277 duplicate email groups, and 18,339 redundant Apollo IDs to merge away. Merge execution remains locked until the remaining source and execution blockers clear.
VideoAmp is the best example of support becoming a reusable client skill path: transcript API analysis, Joe's runbook, Claude Code prompt library, and two transcript skill ZIPs with high-grade QA.
DemandScience should move into a readiness map that connects Context Center, account prioritization, MQL routing, dialer, sequencing, and approval gates before more one-off resources get built.
Both stay on the burn-down list, but I would not report new week-specific metrics as current. eHealth has a resource-center and approval path to maintain; Cint needs a readiness refresh before agentic outbound recommendations are safe.
| Asset | Status | Why it matters | Link |
|---|---|---|---|
| Context Center skills package | Packaged | Three skills make the upgrade motion easier to run across customers and teammates. | Open package |
| VideoAmp transcript skills | Client proof | Transcript export and call-analysis skills turn live support into a reusable agent workflow. | Open resource |
| Apollo CLI client setup skill | Packaged | Foundation for helping clients connect API, CLI, and workflow paths without custom rebuilds each time. | Open ZIP |
| Apollo workflow atlas | Mapped | Thirteen workflow variations and nine primitives for turning customer context into automation design. | Open atlas |
| Training module factory | Built | Spec-first gate, usage lens, and 20 GTME skill cards support repeatable enablement. | Open console |
Calendar meetings, week-of account coverage, Slack Customer Success Qualified Lead notifications, AI usage observatory, QA Wolf current state, and Cloudflare-backed resource links.
The Salesforce engagement query was refreshed and stays in the source trail for disposition cleanup. The operating story for the call is triad readiness, not row volume.
Live Apollo Admin, live Apollo usage, and refreshed Cint/eHealth week-specific metrics were not pulled. Those should stay out of performance claims until refreshed.
Turn the engagement into a repeatable sequence: discovery, readiness score, context build, validation, and automation path.
Use Renesas, Securiti, VideoAmp, DemandScience, eHealth, Cint, and QA Wolf to pressure-test the first-call model.
Decide which accounts move into the triad lane and which stay in normal account-team support.
Separate verified progress from account lanes that still need current usage, admin, or Salesforce refreshes.