Vernon Keenan

The governed context underneath—who can see what, how agents are constrained, how permissions hold—is the real competitive ground.

• The interface shift matters only if the Trusted Enterprise AI Harness and control layer actually ship.
• Without that, the UI move is a costume.

Keenan traces Salesforce from Parker Harris’s March 31 question—“Why should you ever log into Salesforce again?”—to the Dreamforce 2026 AIforce launch. They call the announcement “a control story wearing a UI costume” and note the harness rollout opens in early fiscal 2028, February 2027 at the earliest.

Read original

They call the capability class a Delivery Digital Twin—a dependency-resolved model of a Salesforce org’s objects, fields, automations, permissions, code, and dependencies that AI agents can query before changing anything. The strategic move is “control without data gravity”: govern agent work across enterprise applications while business records stay where they are.

Keenan analyzes ServiceNow’s acquisition of Sweep, reported at roughly $400 million.

• Sweep grew in the Salesforce ecosystem as a no-code configuration tool and evolved into a metadata graph.
• They call the move “a beautiful, predatory idea” and say the reported price is a valuation signal for the Salesforce DevOps category.

Read original

When Salesforce says Claude works better through AIforce than alone, the proof needed is a with-and-without comparison on correctness and permission boundaries, not usage counts. This is a guest analysis by Chris Pearson, presented through Keenan’s account; credit the argument to Pearson.

Pearson found launch materials offered 37 prebuilt sales skills, 100,000 Coworker activations in 35 days, and one bank with roughly 3,000 users—none measuring whether an answer was correct or a permission boundary held. Pearson says Salesforce owns the benchmark, the researchers, and the reference orgs to run the test.

Publishing this guest audit alongside Keenan’s own scorecards shows a consistent editorial line: test vendor claims rather than repeat vendor narratives.

Read original

They quote executives acknowledging gaps instead of smoothing them over and compare competitors already shipping similar control planes. A console that meters spend covers only part of the FinOps job, not the whole governance answer.

Keenan reports Salesforce platform chief Rohan Kumar saying the enterprise harness “needs to be a unified product.”

• They score the six trusted capabilities and AI Control Plane as three delivered, two partial, and three still open.
• Kumar says trusted security and FinOps still need building.
• Keenan argues the AI Control Plane is the war Salesforce needs to win against ServiceNow, Microsoft, and Workday, and that a console metering spend covers about 10 percent of the FinOps job.

Read original

Newcomers should start here: it turns scattered product events into one timeline with named quotes and a clear argument.

Vernon Keenan traces Salesforce’s move from Parker Harris’s March 31 question, “Why should you ever log into Salesforce again?” to the Dreamforce 2026 launch of AIforce.

• The post says Salesforce described AIforce as “a live interface layer that brings the full power of Salesforce to wherever people and agents work,” reaching people in Claude, Slack, Lightning, or wherever they work.
• They frame the sequence as five acts across 168 days and argue the “interface revolution Salesforce announced today is a control story wearing a UI costume.”
• The post also notes the Trusted Enterprise AI Harness rollout begins in early fiscal 2028, which it says means February 2027 at the earliest, and that pricing remains subject to change.

For brands planning a campaign

This is a strong model for a co-authored enterprise AI governance series: take a live product story, arrange it as a dated timeline, and use a scorecard to argue that the real competition is over governed context and control, not screens.

Newcomers should start here for a concrete example of how an ecosystem tool can become a strategic category.

Vernon Keenan analyzes ServiceNow’s acquisition of Sweep, which the post says was confirmed at an undisclosed price that Israeli outlets report at roughly $400 million.

• They explain that Sweep grew in the Salesforce ecosystem as a no-code configuration tool and evolved into a metadata graph that can show AI agents the objects, fields, automations, permissions, code, and dependencies inside a Salesforce org.
• They call that class of artifact a Delivery Digital Twin and argue ServiceNow acquired the ability to see inside Salesforce estates and govern agents without requiring customers to move CRM data onto ServiceNow.
• The post calls this “control without data gravity” and “a beautiful, predatory idea,” and says the reported price is a strategic valuation signal for the Salesforce DevOps category.

For brands planning a campaign

A co-authored series can use a named framework like Delivery Digital Twin to explain acquisitions and category shifts, then build a webinar around how brands should evaluate agent governance without moving their core data.

Newcomers should start here for a clear example of separating a comparison claim from the numbers needed to support it.

Vernon Keenan highlights a guest post by Chris Pearson examining AIforce’s core claim: that Claude working through Salesforce’s new layer will do better CRM work than Claude left alone in an org.

• The post says the comparison is the whole sale, but the launch materials offer an adoption count instead.
• Pearson found 37 prebuilt sales skills, 100,000 Coworker activations in 35 days, and one bank with roughly 3,000 users.
• The argument: every number counts inventory or adoption, but none measures whether an answer was correct or whether a permission boundary held.

For brands planning a campaign

A thought-leadership series can include evidence-audit episodes that ask what would prove a vendor claim, and a webinar can use this post to show governance and quality questions that adoption metrics do not answer.

Newcomers should start here for a delivery scorecard that distinguishes promises, partial capabilities, and open work.

Vernon Keenan reports that the enterprise harness now has six trusted capabilities, an AI Control Plane, and a rollout window opening in February 2027.

• They score what was delivered against what was promised: three delivered, two partial, three still open.
• The post quotes Salesforce platform chief Rohan Kumar saying, “I wouldn’t say we have all the capabilities, just to be fair,” and naming trusted security and FinOps as areas that still need building.
• They also argue the coding harness is the inner ring, the AI Control Plane is a war Salesforce needs to win against ServiceNow, Microsoft, and Workday, and a console that meters spend covers only about 10 percent of the FinOps job.

For brands planning a campaign

A co-authored analysis series can adopt this scorecard method for each enterprise AI governance announcement, and a webinar can frame the AI control plane race around delivered capabilities, missing security, and incomplete FinOps.

The post traces a 168-day arc: Parker Harris asks why anyone should log into Salesforce again; Slack becomes the front door; and AIforce becomes a live interface layer across Claude, Slack, Lightning, or wherever people work.

• Keenan argues that the screens were never the product; the governed context beneath them was.
• The Trusted Enterprise AI Harness rollout is described as early fiscal 2028, February 2027 at the earliest.

Reads vendor announcements and executive remarks as a timeline, separating the visible interface from the control layer beneath it.

For brands planning a campaign

A B2B SaaS platform company could use this thought-leadership hook: interface changes raise new questions about control and governance. A co-authored piece could map which layers of an AI control plane buyers should ask about, opening with the shift away from a single CRM interface.

Examples: Source 1

Sweep grew in the Salesforce ecosystem as a no-code configuration tool, then became a metadata graph showing AI agents the objects, fields, automations, permissions, code, and dependencies inside a Salesforce org.

• Keenan calls that artifact a Delivery Digital Twin.
• The argument: ServiceNow is pursuing control without data gravity, governing agent work across enterprise applications while business records stay where they are.
• They also treat the reported price as a strategic valuation signal for the Salesforce DevOps category.

Names a category, then uses an acquisition to argue that metadata and dependency context are becoming governance assets.

For brands planning a campaign

This offers a concrete category story for enterprise AI governance: agents need a dependency-resolved model of the system before they change it. A co-authored analysis could compare agent observability with a delivery digital twin and ask what brands' agents can query today.

Examples: Source 1

Drawing on experience with models that guess confidently and burn tokens, Pearson is inclined to believe the claim but finds adoption counts in the launch materials instead: 37 prebuilt sales skills, 100,000 Coworker activations in 35 days, and one bank with roughly 3,000 users.

• None measures whether an answer was correct or a permission boundary held.
• The post argues Salesforce has the benchmark, researchers, and reference orgs to run the with-and-without test.

The analysis is by guest author Chris Pearson and appears on Keenan's account. Credit it as a guest contribution, not Keenan's sole-authored work.

For brands planning a campaign

This is a ready-made evidence angle for enterprise AI governance content.

• A brand could publish a buyer's checklist for AI claims, covering with-and-without tests, correctness measures, and permission checks.
• The topic suits a co-authored point-counterpoint or a webinar on what proof enterprise AI vendors should publish.

Examples: Source 1

They score delivery against promises: three delivered, two partial, three still open.

• The post quotes Kumar acknowledging gaps, especially in trusted security and FinOps.
• It frames the coding harness as the inner ring, the AI Control Plane as the war Salesforce most needs to win, and ServiceNow, Microsoft, and Workday as competitors already shipping theirs.
• Keenan argues that a console that meters spend covers only part of the FinOps job.

Uses a delivery scorecard, executive quotes, and competitive comparisons to assess a platform launch.

For brands planning a campaign

This format could anchor a co-authored series: a vendor promise-versus-delivery scorecard with named gaps. A campaign could apply the same scorecard across Salesforce, ServiceNow, Microsoft, and Workday, then build a webinar around practitioner responses to the security and FinOps gaps.

Examples: Source 1

The posts mix numbered takeaways, pull-away arguments, and questions for readers, such as whether they are building their own Delivery Digital Twin or what it understands today. They promote longer analyses on SalesforceDevops.net, with LinkedIn as the distribution and discussion layer.

For brands planning a campaign

A brand could commission a series pairing a sharp category frame with a transparent evaluation method.

• The format suits executive thought leadership built around analysis and a scorecard, not product marketing.
• Open questions also offer natural hooks for audience engagement and webinar prompts.

Examples: Source 1 · Source 2 · Source 3 · Source 4

The posts describe the site's coverage of Salesforce news. Ask Keenan whether they own, work for or are paid by the publication.

View example

They write about the AIforce interface launch and the Dreamforce 2026 announcements, and quote co-founder Parker Harris and Marc Benioff. Ask Keenan whether they have a sponsorship, client or employment tie to Salesforce.

View example

They also frame ServiceNow as one of the vendors shipping an AI control plane. Ask Keenan whether they have a commercial relationship with ServiceNow.

View example

Both writers argue that adoption, clean data, and permissions determine whether an enterprise AI surface works, and both publish short posts pointing to a longer argument.

Markman argues from revenue operations and return on investment: solo teams outrunning larger ones, the gap between AI hype and measured productivity, and the cost of a failed production bet. Keenan works a layer lower, on architecture and the control plane—metadata graphs, harness capabilities, and FinOps scope—and names emerging categories rather than framing the case around ROI.

Read original · Original 2

Both put messy data, change management, and user trust ahead of the launch narrative, and both break a conference into a small numbered set of recurring themes.

Coutts writes from inside industrial and commercial operations, focusing on quote-to-cash, forecast trust, and the cost of delaying a commercial stack fix. Keenan focuses on vendor releases and the governance layer beneath them, measured against what was promised.

Read original · Original 2

Both end posts with a direct question to practitioners, using the comments as a second source.

Goel synthesizes conversations with CIOs into organizational lessons: who owns AI risk, an oversight board, agent managers, and documentation incentives. Keenan focuses on vendor announcements and architecture, quoting executives in launch material rather than interviewing buyers.

Read original · Original 2

The posts argue that “AI replaces the UI” is a keynote line and that, a year on, well under 20% of users will be independent of logging in; that demos always look finished while adoption remains the real barrier; and that the hardest business problems yield to clean data, solid governance, and systems that earn user trust.

• For the same governance-themed series, Markman is the better pick for a skeptical, ROI-first counterweight aimed at a revenue-operations audience.
• They argue that putting an unproven surface on production CRM costs a year of cleanup and a hit to trust, not a refund.
• That makes them a natural fit for a launch piece or webinar that asks buyers to slow down and measure, while positioning the vendor’s product as the unglamorous foundation that must come first.

Markman's posts are short opinion and mission statements, not the dated timeline and promise-versus-delivery scorecard the co-authored series is built on.

• They state a personal objective—producing measurable ROI for revenue operations—and offer a general read on productivity and adoption, but do not examine a specific vendor launch, compare what shipped with what was promised, or name capabilities still missing.
• A series built around the control-plane race would need to supply the launch tracking and competitive detail itself.
• Ask for examples of how Markman would substantiate open items.
• There are two posts here.

Examples: Source 1 · Source 2

The posts describe what a tenth Dreamforce looked like inside companies running commercial operations: data still messy, now with a layer that can be confidently wrong about it; reps still buried in administration; change management the line item most often cut; and the pace of change as a problem in its own right.

• Coutts’s central argument—that the Manual Tax is where the revenue is, and that placing an agent on top of a broken process automates the tax rather than removing it—gives a governance campaign a concrete reason to fund process and data work before agents.
• The cost-of-delay post makes the same case commercially, describing a manufacturer running quote-to-cash across an ERP, a CRM the sales team works around, and about 40 spreadsheets.
• The bill, Coutts argues, tends to arrive in diligence or a value-creation review, when there is no runway left.
• That suits a practitioner webinar for an audience that must justify the spend internally and needs a small, measurable first use case.

Coutts’s posts focus on the commercial operations of manufacturers and industrial companies.

• They offer operational diagnosis and cost framing rather than analysis of platform and vendor competition.
• A series on the AI control-plane race—who shipped what, which capability remains open, and how ServiceNow, Microsoft, and Workday compare—would need competitive detail from another source; Coutts’s posts do not analyze launches or name vendors in that way.
• One post is a conference roundup, the other a general observation about how companies model cost.
• Neither provides the dated trail a scored installment would need.
• Ask for a sample showing how Coutts would handle technical comparisons in a co-authored series.

Examples: Source 1 · Source 2

The posts synthesize issues raised by IT executives at large banks, telecom, and technology companies: who governs the apps teams now build themselves, who owns AI risk, whether oversight belongs in IT or an independent body, employees recast as managers of agent teams, documentation gaps that make agent output unusable, and CRM–ERP integration as the underlying blocker.

• For the same campaign, Goel is the strongest of the three alternatives if the goal is to test the vendor’s governance message against what a CIO audience actually asks—or to add an outside signal that AI adoption is uneven, drawn from people who see many enterprises rather than the vendor’s own references.
• The post noting that Salesforce is presenting itself as an AI company and asking whether the balance of power shifts when the screen changes comes closest to the series’ framing of any alternative item, from a buyer-side rather than seller-side position.

Goel’s posts report conversations and conference takeaways rather than closely analyzing launch documents or presenting original analysis with a dated record.

• A co-authored series built around them would lose the promise-versus-delivery scoring that makes the vendor’s involvement credible, and risk republishing other executives’ concerns without supporting evidence.
• The organizational-design questions—oversight boards, agent managers, documentation incentives—are strong material for a webinar agenda, but not the same deliverable as a monthly installment scoring one platform’s claims.
• There are two posts here.
• Ask for examples of long-form work and audience performance before committing to a series.

Examples: Source 1 · Source 2