The AI Agent Category Just Got a Scoreboard and an Incumbent
OpenAI's productized voice agent lands the same week two deployments attach hard-dollar numbers to agent ROI — turning build-versus-buy into a question of which layer you can defend.
Where the opening actually is
OpenAI shipped Presence through a high-touch GA run by forward-deployed engineers and systems integrators. No public pricing. No disclosed geographic limits. No integration-cost estimate. Read that as the seam, not the strategy: while OpenAI hand-builds deployments one enterprise at a time, a competitor leading with transparent, self-serve pricing reaches the mid-market before the sales calls even start. Viktor is already doing the alternate motion. It runs natively inside Slack and Teams for 40,000-plus teams and hands out $100 in free credits. That is the self-serve wedge sliding under the white-glove one.
The more durable shift is what buyers now grade agents on. Presence pairs model reasoning with permissions, policies, evaluations, and escalation rules — nearly the same control surface Cursor just shipped for admins, with per-team toggles and model allow/block lists, and the one Anthropic is building into managed projects. Three vendors landed on the same governance controls in a single cycle. When that happens, the surface is the entry ticket, not the differentiator. An enterprise agent PRD without permissions, escalation, and audit logging is not losing on marketing. It is incomplete.
The ROI language that unlocks budget
Two deployments moved agent ROI from the deck to the ledger. Wordsmith, a startup rather than a lab, runs in production at $7.6B Belron, cutting contract drafting from an hour to five minutes and saving $400,000 in a single quarter. Belron operates in 40+ countries with in-house lawyers in only 15 and is now rethinking legal headcount. Viktor's Hampton rollout reached 18 active staff, 12 internal apps, 26 scheduled tasks, and 887 CEO-level threads in 44 days, against a $440K hiring budget that went entirely unspent. In both, the foundation model is table stakes and the workflow fit is the moat. Wordsmith wins because you email an Excel sheet and get a contract back, routing across OpenAI, Anthropic, and Google underneath. The user does not see the model. That is the point.
The demand gap says the same thing. 83% of 1,402 surveyed leaders say they need infrastructure upgrades to move agentic AI from pilot to production. Buyers want this and cannot get there on their own. That is the lane for a product that makes agents deployable and governable, not just capable.
The smart move
Don't imitate Presence. Out-position it. Lead where OpenAI is slow: pricing transparency, self-serve speed, and a specific vertical workflow the labs skip. Then measure the feature against the external benchmarks buyers now carry — a 44-day adoption curve and hard-dollar savings, not a quarter-long pilot with engagement charts. If the business case can't produce a CFO-legible number, the problem is the feature's design, not its marketing.
The agent's model is table stakes; the workflow it fits into is the only part a foundation model can't ship for you.
What to do
Re-run your build-vs-buy for any voice/support-agent feature against Presence's capability set (task routing, record lookup, ticketing) this sprint, and decide whether you differentiate on price transparency, self-serve speed, or proprietary workflow.
Add a governance tier — permissions, model allow/block lists, escalation rules, audit logging — to any enterprise agent PRD in flight this quarter.
Benchmark your agent feature's business case against a 44-day adoption curve (active users, apps built, tasks scheduled) rather than a quarter-long pilot before your next roadmap review.