Your champion will believe a business case made of real numbers a lot faster than one made of educated guesses. If your data team has connected Minoa to your warehouse, you can flip a toggle inside any business case and have verified values flow straight onto your inputs—pre-sales baselines, post-sales actuals, all of it. This recipe walks you through finding the Data panel, turning sync on for a scenario, and getting comfortable with what happens next.Documentation Index
Fetch the complete documentation index at: https://docs.minoa.io/llms.txt
Use this file to discover all available pages before exploring further.
When to reach for this
Pull in warehouse data anytime you want the numbers in your business case backed by what’s actually happening in the customer’s product:- Pre-sales — Your champion is pressure-testing the baseline. Real data turns “we think you save 30%” into “here’s what your last 6 months actually looked like.”
- Value realization — A deal just closed. Sync the realized-value scenario so monthly actuals land on their own, no spreadsheets required.
- QBRs and renewals — You’re prepping a customer review and want the latest numbers without pinging your data team.
Don’t see the Data icon in your business case? Your tenant doesn’t have a warehouse connection yet. Ask your admin
to set it up—see Set up data ingestion.
Open the Data panel
Open any business case. In the left rail (the Copilot toolbar), click the Data icon—a small download cloud. At the top of the panel, you’ll see the account this business case is linked to. Minoa always pulls warehouse rows for that account—you can’t override it from here.Check what’s mapped
Below the account, each scenario in your business case has its own row with two counts:- Mapped inputs — how many of the scenario’s inputs are connected to a warehouse metric.
- In the scenario window — how many of those mapped inputs already have data inside the scenario’s time range.
Turn on sync for a scenario
Flip the toggle next to any scenario you want warehouse data to flow into. Three things happen, in this order:Backfill
Minoa reads your warehouse for the scenario’s full window and writes any historic values it finds.
Switch inputs to timeseries
Any mapped inputs that aren’t already timeseries get switched over automatically.
Turning the toggle off later keeps every value already synced—only future writes stop. Your business case stays
intact.
Convert new mappings when they appear
If your admin adds new metric mappings after you’ve turned sync on, a banner shows up at the top of the panel. It detects inputs in your enabled scenarios that aren’t yet in timeseries mode (usually because the link was added recently). Click Convert in the banner. It converts the inputs and pulls in their values in one go.Open the full view
Click Open full view at the bottom of the panel for a deeper look. You’ll get two tables:- Mapped inputs — One row per (scenario, input, mapped metric). The clock icon on each row converts a single input to timeseries when you’d rather not bulk-convert.
- Runs for this account — The most recent syncs that touched this account, with how many metric values landed each time. Useful for confirming fresh data has arrived for your deal.
When to loop in your admin
A few patterns mean it’s time to talk to whoever owns the warehouse setup:- No Data icon at all — The feature isn’t enabled or no warehouse is connected.
- A scenario shows 0 mapped inputs — No metric links exist for inputs in this scenario yet.
- Mapped inputs exist but the in-window count is 0 — The mappings are there, but no rows have arrived for this account inside the scenario’s time range. Either the data hasn’t synced yet, or the account ID in your warehouse doesn’t match the Minoa account.
Your business case is wired up to live data. From here on, the numbers update on their own.