Prove Risotto in 30 days, with our team beside you
Every Risotto deployment starts with a 30-day pilot on your real requests. We set it up with you, build your first workflow live, meet every week, and measure the results against criteria you choose.
What every pilot includes
- A shared Slack channel. Your team and ours in one Slack Connect channel, from scoping to readout.
- Your success criteria. Agreed at scoping, in your words, with how each one is measured.
- Hands-on onboarding. We connect your stack with you and build the first workflow on the call.
- A simulation first. See Risotto’s answers to your past requests before employees do.
- Weekly checkpoints. A short session each week to tune what Risotto does and add more.
- A readout on day 30. Results against your criteria, so the decision is easy to make.
Your 30 days, week by week
Before day 1: scope the pilot
A 30-minute call picks the requests Risotto takes first and the criteria it’s judged on. Then you connect Slack or Teams, your identity provider and your ITSM, so the first session goes to building.
Pilot success criteria
- Access requests resolved in SlackResolved with no IT touch
- Faster MFA resetsTime to resolution, before and after
- Answers from our docsAnswered with a source link
Week 1: onboard and go live
In a 60-minute session, we connect the rest of your stack with you, and the Assistant builds your first workflow while you watch. You leave the call with Risotto answering in your help channel.
Weeks 2 and 3: roll out and tune
Your pilot group asks Risotto for help the way they already ask IT. Each week we look at what Risotto solved and what it handed to a person, then fix the gaps together.
Week 4: expand and measure
Add the next requests and pressure-test the edge cases. On day 30, the readout shows what Risotto resolved, how fast, and where it stands against each criterion.
See Risotto’s answers before your employees do
Risotto runs your past requests through a simulation before it goes live. You see the answer it would give each one, where it would route it and what it would do, without anything actually running. Review the results with your team and fix what you’d change first.
Simulation · #it-help✓ Complete
| Past message | Risotto's answer | Dept | Tool |
|---|---|---|---|
| How do I add the Support shared mailbox in Outlook? | In Outlook, right-click Folders and choose Add shared folder or mailbox… | IT | None |
| Can I get access to Figma? | I can request Figma for you. It needs your manager's approval. | IT | Okta: add to group |
| My laptop won't connect to the VPN | Try signing out of GlobalProtect and back in. If it still fails… | IT | None |
| Where do I update my home address? | You can update it in Rippling under Personal info. | HR | Rippling: update address |
Bring your workflows. The Assistant rebuilds them.
Describe a workflow from your current tool, paste it in or attach a screenshot, and Risotto’s Assistant builds the forms, approvals and runbooks to match. Each change waits for your approval. If a step calls an API, hand the Assistant the vendor’s API spec and it builds that tool too.
Risotto learns from the docs you already have
Connect Confluence, Notion, Google Drive, SharePoint or your help center, and Risotto answers from them on day one, with a link to each source. When IT answers something no doc covers, one reaction turns that reply into an article. Insights shows which questions still have no answer, so you know what to write next.
One knowledge indexScoped by departmentConfluence
Notion
Google Drive
SharePoint
OneNote
Guru
Coda
Slack
Zendesk Guide
Freshservice
Jira
GitHub
Or set up Risotto from your own AI assistant
Risotto has an MCP server. Connect Claude or another MCP client with your own Risotto sign-in, and ask it to create departments, set up access rules and draft runbooks. Drafts stay drafts until someone approves them in Risotto.
Your AI assistant
Set up Risotto for our pilot. Create an IT department, access rules for the apps in our Okta, and a draft runbook for laptop requests.
- Risotto
create_departmentIT - Risotto
create_access_rulesFigma, Notion, GitHub - Risotto
upsert_runbook_draftLaptop request
Done. The IT department and three access rules are set up. The laptop runbook is a draft: approve it in Risotto to make it live.
What teams see in the first month
Doubled resolution rate on day one at Gusto. Read the story
80% of tier 1 requests resolved during the first month at Vidyard. Read the story
6 departments onboarded in less than two months at Thinkific. Read the story
“Risotto is one of the easiest tools I’ve implemented.”
Frequently asked questions
How long does it take to deploy Risotto?
Risotto’s pilot runs 30 days. Most teams go live in their help channel during the first onboarding session in week 1, then spend the rest of the month rolling out and measuring.
What do we need before onboarding?
A Risotto account, the Risotto app in Slack or Microsoft Teams, and your identity provider and ITSM connected. Our pre-work guide walks through each step, and we can do any of it with you on the call.
How much of our team’s time does the pilot take?
One champion on your side, a 60-minute onboarding session and a short checkpoint each week. Your pilot group uses Risotto the way they already ask IT for help.
Do we have to replace our ITSM to run a pilot?
No. Risotto syncs both ways with Jira Service Management, ServiceNow and Freshservice, so tickets keep landing where your team works today. AI for your ITSM
Can we run a Risotto pilot next to the tool we use today?
Yes. Point Risotto at one Slack or Teams channel or one department, and compare results on the same requests.
Is the pilot free?
Yes. The 30-day pilot is free, and you decide on day 30. Pricing

