AI

Meet the new Eko: deeper context, sharper judgment, action on your approval

John Baker John Baker • Nov 4, 2026 • 14 min read • Updated November 4, 2026
Eko working across a terminal, the Torii app, and Slack
Summary

The new Eko helps IT and Procurement understand their SaaS and AI stack, spot what needs attention, and turn findings into governance that lasts.

Ask about this article

Opens Claude in a new tab to answer, using this article as the source.

SaaS already changed faster than any team could track by hand. AI compounds it. The latest Eko update helps IT and Procurement understand what is happening across their stack, see what deserves attention, and turn what they find into governance that lasts.

Ekoin Torii
What renews next?
Zoom renews first, on Dec 15, at $38,400 a year.
Slack#it-ops
DK
Dana Kim 9:41 AM
@Eko how many Figma seats are unused?
Eko APP 9:41 AM
18 of 120 Figma seats haven't been used in the last 30 days.
Claude Code
> What did we spend on AI tools last quarter?
⏺ eko - ask (MCP)
$184,200 across 11 AI tools.
Largest: OpenAI at $71,400.
>
Eko is available in the Torii app, in Slack, and via MCP.
Illustrative examples with sample data.

SaaS moved fast, AI accelerates it

For most IT and Procurement teams, SaaS was never a static inventory. New apps arrive through expense reports and free trials. Licenses drift away from what people actually use. Renewals come due on their own schedule, ready or not.

AI adds new layers on top of that. Teams build their own internal apps. Usage is billed in tokens instead of seats. API keys and secrets spread across tools. Integrations link systems that used to stand alone. And AI features now ship inside software you already approved, quietly changing what that software can reach.

None of these is a separate problem. A single new AI tool touches spend, access, security, and vendor risk at once. The work is not only bigger. The decisions are more connected, and each one depends on context from the others.

Management is more than visibility

Torii helps IT and Procurement manage SaaS and AI together, so spend stays optimized and governance stays strong as the stack evolves. Seeing everything in one place is the foundation. As environments get more complex, we believe a management platform should carry more of the load on top of it.

That means interpreting what is happening, pointing out what deserves attention, and helping your team respond. It is the standard behind this update to Eko.

What’s new in Eko

Eko now brings three things together: trusted answers from your own data, the ability to recognize patterns across your environment, and the means to act on what it finds once you approve. Here is what that looks like in practice.

Answers from your own contracts, not general knowledge

Claude CodeMCP · Eko
> What's the notice period in our Salesforce contract?
⏺eko - ask (MCP)(question: "Salesforce contract notice period")
⎿  Found Salesforce Order Form, Section 9.2
⏺
Your Salesforce agreement requires 60 days' written notice to cancel before it auto-renews.
Your current term ends March 31, 2027, so the last day to give notice is January 30, 2027.
Source: Salesforce Order Form, Section 9.2 (Term and Renewal)
Illustrative example with sample data.

Eko reads your contract and gives you the answer. A missed notice window can lock you into another term at the old price, so a fast, accurate answer here translates directly into money.

It reads how your environment actually works

#it-opsSlack
SR
Sam Rivera9:41 AM
@Eko explain what our offboarding workflow does.
EkoAPP9:41 AM
Your Employee offboarding workflow starts when someone's status changes to Terminated in BambooHR. Then it:
  1. Waits until their last day of work
  2. Removes their access to every app connected through Okta
  3. Opens a ticket for each app owner where access has to be removed by hand
  4. Transfers their Google Drive files to their manager
  5. Posts a summary in #it-ops on Slack
One condition: if the person is a contractor, it skips the file transfer.
Source: Workflows › Employee offboarding (5 actions, 1 condition)
Illustrative example with sample data.

Eko explains the workflow you built, with its real triggers, conditions, and steps, rather than a generic description from the help center. That helps when you inherit a workflow, review one, or need to walk an auditor through it.

It knows where you are

Ekoin ToriiTorii
On page: Zoom › Users · 14 selected
What happens if I click Remove users on this page?
Remove users takes the 14 people you selected out of Zoom.
They lose access right away, their licenses go back into your available pool, and each person's manager gets an email from Torii.
Heads up: 3 of the 14 used Zoom this week. You may want to filter by Last used first.
Illustrative example with sample data.

Eko sees the page you are on, so it can tell you what an action will do before you take it. You act with confidence instead of testing in production.

It builds things worth sharing

Ekoin ToriiTorii
Build a renewal tracker.
Here are your renewals through March 2027: 6 contracts worth $412,000 a year.
AppRenewsAnnual cost
ZoomDec 15, 2026$38,400
AtlassianJan 8, 2027$96,000
SlackFeb 1, 2027$74,500
SalesforceMar 31, 2027
Notice by Jan 30
$186,000
+ 2 more renewals
Open trackerShare
Illustrative example with sample data.

Eko pulls your upcoming renewals into a tracker you can review, refine, and send to finance or leadership.

It compares the apps you already pay for

#procurementSlack
DK
Dana Kim9:41 AM
@Eko we pay for ChatGPT and Claude. Which one should we renew?
EkoAPP9:41 AM
Recommendation: renew Claude (high confidence).
Claude has more active users, more assigned licenses, and higher tracked spend, so it's the cleaner renewal case. ChatGPT has fewer active users and messages, and its billing data doesn't line up. If you can keep only one, Claude is the easier renewal to defend.
ClaudeChatGPT
Active users (30 days)412268
Paid seats450400
Licenses assigned438391
Usage (30 days)48,900 messages17,300 messages
Active contractYes, renews Jun 2027Yes, renews May 2027
Tracked spend (12 months)$198,000$156,000
New chargesNone$4,800 not on the contract
I wouldn't cancel ChatGPT until its seats and billing are reconciled.
Illustrative example with sample data.

Ask which of two overlapping tools to keep, and Eko weighs them on your own data: active users, paid seats, usage, contracts, and spend. It also tells you when that data doesn’t add up.

It supports decisions before you buy

Claude CodeMCP · Eko
> Compare Dashlane and NordPass. Which should we buy?
⏺eko - ask (MCP)(question: "Dashlane vs NordPass")
⎿  Compared pricing, certifications, and identity features
⏺
Recommendation: Dashlane (medium confidence).
Dashlane has the stronger enterprise controls. NordPass costs much less, but Entra ID and Okta SSO and automated provisioning are Enterprise-tier features there, which narrows the gap.
DashlaneNordPass
Price$8/user/moFrom $3.59/user/mo (2-year term, 5 seats min.)
CertsSOC 2 Type II, ISO 27001SOC 2 Type 2, ISO 27001
SSO, SCIMOn business plansEnterprise tier only
Trade-offStronger controls, higher priceCheaper, key controls cost extra
Before you buy, run a short proof of concept on SCIM offboarding and audit-log export.
Sources: support.dashlane.com, nordpass.com (public list prices, not quotes)
Illustrative example with sample data.

Ask Eko to compare vendors on pricing and security certifications, and it returns a side-by-side view with sources you can check yourself.

It turns a request into a recurring job

EkoSlack
DK
Dana Kim9:41 AM
Check every license has a cost each week, ping the app owners, and send me a report.
EkoAPP9:41 AM
Here's the weekly job I'll set up. It won't run until you approve it.
Weekly license cost check
Every Monday at 9:00 AM
  1. Find licenses with no cost attached
  2. Message each app owner on Slack to add the cost
  3. Email you a report of what got fixed and what's still missing
This week it would flag 23 licenses across 7 apps.
ApproveEdit
Illustrative example with sample data.

One request covers all three parts: Eko finds the pattern (licenses with no cost attached), takes the action (notifying the owners), and reports back, every week, with your sign-off on what it does.

From a single answer to a standing process

A fast answer helps today. The larger payoff comes when a finding becomes something that keeps working after the conversation ends.

When Eko sees the same issue more than once, such as licenses with no cost, apps nobody opens, or renewals that keep arriving late, it points out the policy to tighten or the task worth automating. You review the suggestion and approve it. From then on, it runs as the stack grows, without anyone scheduling an audit.

Ekoin ToriiTorii
Policy gap: ownership is inconsistent.
1,240active apps have no owner
185active contracts have no owner
Recommendation: Run a weekly policy that flags missing owners, asks the likely owner to confirm, and prepares updates for approval.
Set up weekly policy
Illustrative example with sample data.

This is the link between everyday assistance and governance at scale. Each question your team asks can leave the environment in better shape than it was before.

What it means for each team

IT

The work you already do goes faster. Eko also points out policies worth tightening and tasks worth automating, then carries them out when you approve. Governance keeps improving between audits, and your team gets time back for the projects that need people.

Procurement

Answers about contracts and renewals arrive in seconds instead of after a search through folders. Patterns like underused apps or renewals that keep landing late surface early. That means better timing on every renewal and a stronger position at the negotiating table.

Leadership

Governance improves continuously, and a person approves every action. The stack stays optimized and within budget as AI adoption grows, without adding risk.

All three teams meet at the same point: governance that keeps up with how fast the stack changes, with people in control.

Your team stays in control

Eko proposes and people decide. Whenever Eko would change something, whether that’s a policy, an automation, or a message to app owners, it waits for your approval first.

That is what lets Eko take on more of the work without asking you to give up oversight. Your team sets the direction, and Eko helps carry it out across a stack that keeps growing.

SaaS and AI will keep compounding. With Eko, your governance can compound too.

Try it today: open Eko on any page in Torii and ask it something about your own stack.