Procurement forwards you the renewal ninety days out and asks whether to proceed. You know parts of the estate are wrong. Integrations built for a project that ended two years ago are still running, nobody has counted them, and there is no longer time to. The scope of the next term gets set months before the renewal date, usually by default, because the work that would change it takes longer than the notice period.
Integration is not the problem. If you run production volume on Workato it works, your team is good at it, and keeping it is the right call. What has changed is how much one signature now covers. You also answer for the agent mandate that landed this year, and for the applications your teams are building in Claude Code and Cursor. The contract in front of you covers the first of those cleanly.
Four dates matter before the renewal date.
Find out what you actually run
You have a full term of usage data. The scope you signed was a guess made before anyone had run a workload on the platform, and it is no longer the best information in the building.
The comparison you need is between the estate you scoped and the estate you run. It takes weeks, because the answers sit with the people who built the workloads rather than with the person signing the renewal.
Start here and a finding can still change the contract. Start at six months and it changes the conversation instead.
Put three questions to your account team
Your account team will answer all three. The answers are the scope of your next term.
Which edition covers agentic capability, and what is the billable unit?
Workato has a real agentic offering on its own platform. Their documentation puts agentic capabilities on Workato One, their most comprehensive offering, which “includes all Enterprise edition features and agentic capabilities.” Their metering documentation states that “1 input prompt = 1 Genie action,” measured on each prompt sent to the genie, including prompts sent by another genie.
Workato’s July announcement describes AIRO as “a multi-agent system built into the Workato platform.” Both sentences are accurate. Ask which one is in your contract, and what happens to that number when five agents are in a single conversation.
Gartner expects that by 2030, 60% of organizations will adopt platforms for AI agent orchestration from vendors outside of their existing systems of record providers. The agent decision is being made on this renewal whether or not it is on the agenda.
What is in the edition you are being renewed onto?
Ask for a written list of what your tier includes and what is priced separately, then check it against the inventory from the first window. Anything on the inventory that turns out to sit outside the tier is a cost you have already committed to without pricing it.
Gartner’s 2026 Magic Quadrant for Integration Platform as a Service named Workato a Leader for the eighth consecutive time. The same report advises buyers to evaluate what capabilities are provided in Workato One and how they meet their integration and agentic AI requirements.
Six months out you can act on that answer. At thirty days you are reading it.
Where do the applications your teams build actually run?
AIRO’s MCP integration builds Workato recipes, Genies, Skills, APIs, Recipe Functions, and MCP servers from Claude Code, Cursor, and Codex. That part is real, and it is good.
The application itself is a separate question. On a documentation review dated 19 August 2026, no Workato edition takes an arbitrary application a team built with an AI assistant and hosts it on a managed runtime with SSO in front, managed auth behind it, an audit trail, and a named owner. Workflow Apps is a no-code builder for forms, tables, and approvals on a hosted portal, with SAML configured at the portal level rather than per application, and no per-app cost attribution. If Workato has shipped something in this area since that date, ask them.
An application with nowhere to run lands on a laptop, or on infrastructure somebody in IT now owns without having agreed to.
“Everybody keeps coming to engineering asking us to run their stuff … we are not building infrastructure so you can run some random app that you built.”
Engineering leader, security technology company (August 2026)
Gartner expects enterprise application portfolios to include 40% custom applications built using AI-native development platforms by 2030, up from 2% in 2025. Whatever you sign now is the platform that arrives on.
Run the alternative properly or not at all
Security review, procurement, and a technical scoping conversation run in sequence more often than in parallel. Three months is close to the minimum for all three plus a decision. Start at thirty days and you have a formality.
The question you are asking is what a platform costs against the workloads you now know you run. That is a different question from the one you asked at first purchase, when nobody had the usage data. See where Tray.ai and Workato actually differ before you scope the conversation.
One Tray partner ran this exact exercise for an enterprise migrating off Workato: roughly 1,000 Workato recipes inventoried, then rebuilt as around 60 Tray workflows using Tray Headless — because a recipe-to-recipe migration isn’t the goal, a working platform is. Run this window and you arrive at the renewal with something to compare against, whether or not anything moves.
Notice and sequencing
Scope is set. Read your own agreement for the notice date, because it lives in your paper rather than on anybody’s website, and nobody will remind you.
Sequencing is what is left, and it is still worth something. Nothing has to move on day one. New work can start elsewhere while the existing estate keeps running and the team that knows it stays where it is.
The Workato Renewal-O-Meter
Tick what you actually run. Watch where the needle lands.
Ten functional categories, weighted the way Workato's own tiers are, plus your recipe volume. No price, no login — just a straight read on whether you're paying for the whole platform or the slice you use.
Check your reading →Sources +
GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally and is used herein with permission. All rights reserved.
- Gartner, Magic Quadrant for Integration Platform as a Service, G00836353, 16 March 2026 (Leader designation, Workato One evaluation guidance).
- Gartner, G00846572, 7 July 2026 (60% agent-orchestration-vendor forecast) — full title and author first names pending confirmation before this piece runs externally.
- Gartner, G00854706, 29 July 2026 (40% custom-applications forecast) — full title and author first names pending confirmation before this piece runs externally.
- Workato documentation on editions and metering, docs.workato.com/en/pricing and docs.workato.com/en/pricing/usage-metrics/agent-studio, retrieved 18 August 2026.
- Workato documentation on AIRO and Workflow Apps, docs.workato.com/en/airo/mcp, docs.workato.com/workflow-apps/saml.html, docs.workato.com/workflow-apps/faq.html, checked 19 August 2026.
- Workato, AIRO general availability announcement via BusinessWire, 30 July 2026.