The Value Agent is an AI assistant that helps you build and edit your value framework—use cases, calculations, tags, and global inputs—through conversation. During the beta we’re inviting a small set of users to try it. This page explains how to access it, what it can and can’t do, and how to recover if something goes wrong.
Where to find it and where it works
The Value Agent is available only on the Value Framework area of Minoa.
- Go to Value Framework in the main navigation.
- On the Value Framework overview (Use Cases, Tags, Resources, etc.), look for the teal circular button in the bottom-right corner of the screen.
- Click it to open the agent panel. You can chat in the panel, then close it with the X; the button stays available so you can open it again anytime.
The agent does not appear inside business cases or elsewhere in the app—only on the Value Framework screens. Use it when you’re building or updating your use case library or tags.
What the Value Agent does and doesn’t do
Use the table below as a quick reference for what the agent can help with and what stays outside its scope.
| What it does | What it doesn’t do |
|---|
| Use cases — Create, rename, edit, and delete use cases. Describe a value story and the agent can propose names, descriptions, and full calculations. | Company context — It does not read or edit the Company Context section of your Value Framework. Use the Company Context page in the UI for that. |
| Calculations — Add or replace calculations, define inputs (with types and defaults), set up subtotals and totals, and write formulas. It can build cost reduction, revenue uplift, and non-monetary calculations. | Resources — It does not manage Resources (files, links) in your Value Framework. Use the Resources tab for that. |
| Tags — Create tag categories and tags, rename or delete them, and add or remove tags on use cases. It can help you organize use cases by industry, role, or theme. | Business cases — It only works on the Value Framework. It does not create or edit business cases, deals, or opportunity-specific data. |
| Global inputs — Create, update, and delete global inputs. Link or unlink calculation inputs to global inputs so shared values stay in sync across use cases. | Other Minoa areas — It does not change settings, integrations, slide templates, or anything outside the value framework. |
| Reading your framework — Ask what use cases, tags, or global inputs you have; the agent reads your current value framework and can summarize or suggest next steps. | |
| Batch work — Request multiple use cases or tags at once (e.g. “create three use cases for support, sales, and onboarding”); you’ll get a single approval step for the batch. | |
| Files and spreadsheets — You can attach a spreadsheet or document; the agent can analyze it and propose use cases or structure based on the content. | |
The agent will ask for your approval before creating or changing use cases and tags. You can approve or reject each suggestion. Once you approve, changes are saved to your Value Framework.
Suggested messages to get started
Try sending one of these to see what the Value Agent can do:
- “What use cases do we have?” — Get a summary of your current use case library.
- “Create a use case for reducing customer support costs” — The agent will propose a use case with a cost reduction calculation, inputs, and formulas.
- “Add a revenue uplift use case for sales productivity” — Get a new use case focused on revenue impact (e.g. win rate, cycle time).
- “Rename this use case to [new name]” — Use when you have a use case open or in context; the agent will rename it.
- “Create a tag category for industry and tag our use cases” — Set up a tag structure and apply it across use cases.
- “Add an input for number of agents and set the default to 50” — Refine a calculation in the use case you’re working on.
- “Create three use cases from this spreadsheet” — Attach a file first, then send this; the agent will analyze the file and propose use cases for your approval.
- “Create a global input for number of employees with a default of 500” — Create a shared input that can be linked across multiple use cases.
- “What global inputs do we have?” — List all global inputs and see which use cases reference them.
- “Link the headcount input to the Number of Employees global input” — Connect a calculation input to a global input so changes propagate automatically.
You can also ask in your own words—for example, “We need a use case for compliance risk” or “Add a subtotal for labor cost to this calculation.”
Who has access
During the beta, the Value Agent is turned on for a limited set of users only. If you don’t see the teal agent button on the Value Framework page, you’re not in the beta yet. We’ll expand access over time.
What to avoid during the beta
Concurrent use
Only one person should use the Value Agent to edit the Value Framework at a time. If two or more people (or the same person in multiple browser tabs) use the agent at once, changes can conflict or overwrite each other. For the moment, coordinate with your team so that only one person is using the agent when making edits.
Relying on it for critical-only edits
The Value Agent is in beta. We recommend using it for non-critical updates or experimentation when possible. For mission-critical changes to your value framework, you can still use the standard Value Framework UI (Use Cases, Tags, etc.) so you have full control.
Getting out of a problem state
If the agent gets stuck, gives an error, or the conversation feels broken, you have three options. Each does something different, so choose based on what you want.
New conversation
What it does: Clears the chat only. Your conversation history disappears and you start a fresh chat. The agent does not save or discard any value framework changes when you do this.
When to use it: The chat is stuck or you want to start over with a new request. You’re not trying to change what’s in your Use Cases or Tags—you just want a clean chat.
How: In the agent panel header, click the + (New conversation) icon.
Refresh value framework
What it does: Reloads the Value Framework from the server into your current view. You see the latest saved state of your use cases, tags, and related data. Any unsaved edits you had in the Value Framework (for example in an open drawer or form) can be lost when you refresh, because the app replaces your current view with what’s saved.
When to use it: You want to see the latest saved state (e.g. after the agent made changes that were already approved and saved, or after someone else edited the Value Framework). Use it when you’re okay with discarding any in-progress, unsaved edits.
How: In the agent panel header, click the refresh (Refresh value framework) icon.
Refresh value framework replaces your current view with what’s saved. If you have unsaved edits in the Value Framework, they can be lost. Save or discard them first if you care about them.
Reload the page
What it does: Fully reloads the app in your browser. Everything in memory is reset—including the agent conversation and your current view of the Value Framework. After reload, the app loads the latest saved data from the server again.
When to use it: The agent or the whole page seems stuck and the options above didn’t help. Reload is a last resort. Be aware: any unsaved value framework edits (in drawers or forms) will be lost; anything already saved remains.
How: Use your browser’s reload (e.g. refresh the page with F5 or the browser button).
If the agent has already saved changes (e.g. you approved new use cases), those are stored on the server. New conversation or refresh value framework will still show them after reloading from the server. Only unsaved work is at risk when you refresh or reload.
Summary
| Goal | Action |
|---|
| Start a new chat without touching the Value Framework | New conversation (+) |
| See the latest saved Value Framework and accept losing unsaved edits | Refresh value framework (refresh icon) |
| Reset the whole app when something is stuck | Reload the page (browser reload) |
The Value Agent is designed to make building and updating your value framework faster. During the beta, use it in a single-user (or single-tab) way and prefer these recovery steps when you need to get out of a bad state. For more on building use cases and calculations by hand, see Use Cases and Tags.