For buyers watching AI reshape software.
The system of record stopped insisting on its own interface, but kept the permissions, semantics, and meter
Week 38 of 2026 · September 19, 2026
Big read
Salesforce's AIforce announcement is the week's application-layer fact home. The company now exposes CRM data, workflows, business logic, semantics, permissions, security, and governance through Claude, Slack, and its own Lightning interface. That is not the application disappearing; it is the application giving up control of the screen while retaining control of the data, actions, and commercial boundary.
The move is strategically coherent and commercially incomplete. Agentforce Coworker is described as immediately activatable, Claudeforce and Slackforce are less mature, and no standalone AIforce price was published. In the same week Salesforce introduced Koa, a CRM reasoning model it controls and runs inside its own trust boundary. The stack now spans interface, agent, domain model, data, permissions, and workflow under one incumbent, which simplifies deployment and deepens concentration risk at the same time.
Startup capital moved toward the same control points. Temporal raised $550 million for durable application and agent execution, Tandem Health raised $100 million to expand from clinical documentation toward a clinic operating system, and Nara Health disclosed $14 million for benefits administration. The buyer's decision is therefore not generic incumbent versus startup. It is which layer may own workflow state, permission enforcement, and the definition of a completed outcome, because those are the layers that survive when the user interface becomes interchangeable.
Vertical movements
2026-09-15 · Salesforce · Sales · Incumbent Saas · Unknown
AIforce and Agentforce Coworker
CIOs should treat the interface as replaceable and diligence the retained control plane: identity, permission inheritance, action logging, and metering. Coworker is described as immediately activatable, but pricing and packaging remain subject to change, so adoption should begin with usage caps and an exit path.
Sources Salesforce
2026-09-15 · Salesforce and NVIDIA · Sales · Incumbent Saas · Unknown
Koa CRM reasoning model
Regulated buyers gain a specialist model whose weights and inference remain inside Salesforce, but the vendor also owns the benchmark used to claim fewer errors. Use the select pilot to reproduce performance on actual CRM actions and retain a general-model fallback before general availability.
Sources Salesforce
2026-09-14 · Tandem Health · Healthcare · Startup · Unknown
AI-native clinic operating system
Healthcare buyers should evaluate Tandem as an emerging workflow system rather than a scribe feature. The $100 million round funds expansion beyond notes into patient flow, which raises the integration, clinical-safety, identity, and audit requirements well beyond ambient documentation.
Sources Tech.eu
2026-09-14 · Nara Health · Healthcare · Startup · Unknown
AI-native benefits administration
Benefits leaders should demand reconciliation controls before accepting a unified administrative layer, because the same system would interpret plans, process claims, and communicate outcomes to members. The company-reported processed-claims and member figures are operating signals, not independently audited results.
Sources Nara Health via Business Wire
Incumbent responses
2026-09-15 · Salesforce
AIforce
Salesforce is defending the control plane rather than the screen. Buyers can reduce user-interface lock-in only if they separately negotiate data access, action portability, audit export, and the commercial terms for headless use.
Sources Salesforce
2026-09-15 · Salesforce
Koa
Owning the model closes the gap between workflow semantics and inference, but it also lets one vendor define the dataset, benchmark, deployment boundary, and fallback policy. Require comparative evaluation against at least one general model.
Sources Salesforce
2026-09-14 · GitHub
Copilot automatic model selection
Engineering leaders no longer choose only a model; they choose an optimization policy while usage is billed on the model selected. Export the actual routing and cost record, because the tier label alone cannot explain spend or outcome variance.
Sources GitHub Changelog
Startup signals
2026-09-14 · Engineering · $550M
Temporal
Capital is moving into durable execution beneath agents, not only into models and applications. Engineering leaders should compare a workflow engine's recovery, replay, and audit semantics with the proprietary durability bundled into agent platforms before committing stateful automations.
Sources Reuters
2026-09-14 · Healthcare · $100M
Tandem Health
The round funds a move from documentation into workflow ownership across patient flow and additional clinical tasks. Buyers should reassess Tandem's risk tier before those capabilities arrive rather than carrying forward a scribe-level review.
Sources Tech.eu
2026-09-14 · Healthcare · $14M
Nara Health
Nara is attempting to combine plan design, claims, care orchestration, and member support rather than sell a point agent. Employers should separate the convenience of one interface from the control risk of one platform influencing both adjudication and member communication.
Sources Nara Health via Business Wire
Pricing shifts
2026-09-15 · Usage Based → Hybrid
Gemini 3.8 Live meters audio input at $0.005 per minute and output at $0.018 per minute while tools and deeper reasoning can run behind the conversation. The workflow bill therefore combines time-based voice charges with whatever usage-based tool and model charges the application invokes.
Sources Google
2026-09-14 · Usage Based → Usage Based
GitHub
Automatic selection now exposes efficiency, balance, and intelligence policies, but billing still follows the model chosen for each prompt. The user chooses an optimization objective rather than a fixed SKU, which makes route-level cost export necessary for chargeback.
Sources GitHub Changelog
Vertical scorecard
As of 2026-09-19
| Vertical | Leader | Challenger | Read |
|---|---|---|---|
| Healthcare | Tandem Health | Nara Health | Tandem is expanding from documentation toward clinic workflow; Nara is consolidating benefits administration and claims. |
| Sales | Salesforce AIforce | Independent outbound agent vendors | Salesforce now exports CRM actions into third-party interfaces while retaining the permission and workflow control plane. |
| Support | Salesforce | Zendesk and independent support agents | The incumbent's interface layer and domain model deepen integration, while public standalone AIforce pricing remains absent. |
| Operations | Temporal | Managed agent runtimes | Durable recovery and replay become procurement questions as long-running agent state moves into production. |
| Engineering | GitHub Copilot | Cursor | GitHub made routing policy explicit and expanded agent session operations; the control contest is shifting to observability and recovery. |
| Finance | Automation Anywhere | Workday | No verified W38 finance launch displaced the standing W37 ordering. |
| Security | Zscaler | Incumbent security-operations platforms | No verified W38 release changed the standing autonomous-containment ordering. |
| Legal | Harvey | Adobe Acrobat Analyzer | No verified in-window legal application event changed the W37 specialist-versus-bundled-feature read. |
Architecture watch
The interface becomes optional while the control plane persists
Salesforce is willing to let users work through Claude, Slack, or Lightning because the durable assets remain below the interface: data, semantics, permissions, workflows, and billing. Buyers should test whether those assets and the resulting action logs remain exportable if the chosen interface or model changes.
- Examples
- Claudeforce, Slackforce, Agentforce Coworker
Sources Salesforce
Domain models move inside incumbent trust boundaries
A system-of-record vendor can post-train an open base on domain-shaped synthetic data, control the resulting weights, and host inference beside enterprise permissions. That can simplify compliance and latency, but it gives the incumbent control over the benchmark, model lifecycle, and fallback policy.
- Examples
- Salesforce Koa, NVIDIA Nemotron 3 Super
Sources Salesforce
Durable execution becomes its own investable layer
Temporal's round values recovery, replay, and state persistence as infrastructure independent of any model or application. Enterprises should decide deliberately whether durable state belongs in a portable workflow engine or inside a proprietary agent platform, because that choice sets the practical exit cost.
- Examples
- Temporal durable workflows, Long-running enterprise agents
Sources Reuters
Watchlist
Sep 21-30
AIforce packaging and headless-use terms
Standalone prices, cross-product credits, and action-level audit export will determine whether interface choice reduces lock-in or only relocates it.
Oct 2026
Koa pilot evidence
Absolute error rates, task definitions, and comparison models are needed before the vendor benchmark informs a purchase.
Q4 2026
Tandem clinic-operating-system rollout
Patient-flow and agent features would move the product into a materially higher integration and clinical-risk tier.
Next financing update
Temporal use of $550 million round
Product investment versus go-to-market expansion will show whether durable execution remains developer infrastructure or becomes an enterprise control plane.
Changelog
- Evidence cutoff September 19, 2026; product claims use primary sources, with Reuters and clearly labeled secondary reporting used for financing.
- AIforce is the issue's fact home. The Weekly and Agent Techniques issues use only the system-level implication rather than repeating its full product detail.
- No legal, finance, or security event in the window justified changing the standing scorecard leaders in those verticals.