Source-linked RevOps signals, held to an editorial relevance gate. Each item names the operator question worth checking and keeps the original source visible.
Amplitude can now stop an experiment or flag at a scheduled time and freeze the analysis window. Operators still need to reconcile late data, fallback behavior and downstream actions outside Amplitude.
Marketo Engage now disables and deschedules campaigns when their folder is archived. Adobe also says two lead-activity endpoints will reject static lists of 10,000 or more members from 30 September.
Core, Advanced and Max packages combine agent capacity with Slack, analytics, security and support. For RevOps, the practical work is to separate included entitlements from usable workflow coverage and future consumption.
HubSpot’s UNBOUND conference is approaching as Agent Hub, Agent Builder and Agent Tools remain in beta. Sighub is aligning Renewal Radar around bounded renewal evidence and deterministic action states—not open-ended churn prediction.
The new control layer evaluates proposed agent actions before business tools execute. A public reference endpoint is available, while production workspaces remain subject to approved early access.
Clay has made its sequencer generally available with audience, eligibility, inbox, reply, and analytics controls. The operator question is whether the combined workflow remains inspectable when source data changes between enrollment and send.
The release expands Agentforce into reusable skills, cross-platform orchestration, quoting and renewal preparation. Its 12 October general-availability date gives RevOps teams a short window to define evidence, permissions and post-action verification.
Webhook data sources, merge-safe workflow enrollment and app-object associations can remove custom integration work, but each feature also moves an operational boundary. RevOps should review secret handling, match keys, merge outcomes, pending automation and association authority before relying on the new behavior.
The 2026-08-26 Dahlia release adds customer-portal links, entitlement access in Customer Sessions, frozen invoice-item fields, another invoice payment method, and a higher subscription-item limit. Each is non-breaking at the API level, but each can still change an operating workflow.
A single Wait Until path can now combine chained delays, nested And/Or conditions, and relationship logic. The canvas may become shorter, but the lifecycle decision becomes more expressive. Preserve timing, identity, branch meaning, exits, and test evidence before consolidating production journeys.
HubSpot grouped invoice prioritization, billing defaults, price books, tax monitoring, project-contract associations, and a payments-readiness API into one August update. RevOps should not deploy them as one bundle: each release changes a different authority, evidence, or handoff boundary.
Salesforce is making CRM capabilities discoverable to more agents through MCP, Skills, Data 360 and headless experience layers. Reuse can reduce integration work, but discovery is not permission and a reusable capability still needs a named identity, bounded object access, approval policy, duplicate-write control and revocation path.
Salesforce presents prebuilt connectors and AgentExchange as a faster route to connected work. RevOps should translate that convenience into explicit identity, field authority, sync direction, agent access, retry, reconciliation, and exit controls before production use.
A SaaStr operating account shows how one short, usage-timed message turned a product test into detailed implementation evidence. RevOps and CS Ops should connect onboarding outreach to verified product behavior, preserve the response in the customer record, and separate support, research, and expansion decisions.
MarTech’s email-program audit moves from delivery foundations to lifecycle flows, ESP controls, and testing. RevOps should add identity, consent, ownership, suppression, revenue-event, and reconciliation checks before calling an automation gap a revenue opportunity.
AAMP 2.3 adds the governance, integrations, and privacy controls organizations need to move AI agents into production.
We just moved 10+ years of data off Marketo into Salesforce Marketing Cloud. It took us years to get there. The final straw was the rate-limiting in their API made it unusable for 10K, our AI agent for marketing and…
June's HubSpot updates are focused on turning information you already have into something HubSpot can act on directly.
Simplify Salesforce security with Security Center Essentials. Learn how to track Health Check scores, audit integrations, and monitor IP ranges in one place.
Beyond the backlash lies a bigger issue for marketers: when vendors need customer data for their products, who captures the value?
May's HubSpot updates focused on making AI an active participant in your work, not just a tool you prompt.
The main stage at SaaStr AI 2026 in San Mateo ran end to end on agents. Agents in production, carrying quota, writing to systems of record, and reshaping how companies are built.
HubSpot is moving filters, metrics, report views, AI insights, and property management into the object index. The rollout can reduce navigation, but it also changes the workspace where reps and admins inspect and alter CRM records. Treat it as a controlled user migration, not a cosmetic refresh.