Can customers reach a trusted answer fast?
We ask each tester to bring one real cloud-cost question. The session measures how quickly Cloud Horizon gets from raw provider data to an answer they would forward to finance or engineering.
Customer pilot
Test Cloud Horizon on the cloud question you already need answered.
Current customers and friendly pilot teams can bring a real AWS, Azure, GCP, StackIT, or MCP workflow. We watch where the product helps, where it slows you down, and what must change before a wider launch.
pilot session
45 minBring one workflow
Anomaly triage
Find the highest-confidence spend spike, explain why it happened, and decide who owns the next action.
Forecast review
Compare the current run rate with budget, commitments, and known upcoming changes.
Attribution pass
Map spend to teams, apps, environments, or cost centers without relying on perfect tags.
MCP workflow
Ask an agent for cost, inventory, or forecast context and check whether the answer is grounded enough to trust.
Surfaces
Covers AWS, Azure, GCP, and StackIT 
scorecard
5
decision questions after every session
What we need to learn
The pilot is not a sales demo. It is a product learning loop with explicit questions and a short follow-up after fixes ship.
Where does the workflow create doubt?
Every confusing label, missing drill-down, weak explanation, and unclear recommendation gets captured as a product note with a follow-up owner.
Which cloud surface matters first?
The form and session separate AWS, Azure, GCP, StackIT, and multi-cloud needs so the roadmap follows real customer pressure instead of internal guesses.
How a pilot runs
Four steps, designed to keep the session about your real workflow and the product changes that would make Cloud Horizon easier to adopt.
-
01
Pilot request
You tell us your cloud surface, spend bracket, role, and the workflow you want to test. We use that to avoid generic demo calls.
-
02
Session setup
We prepare demo data or read-only access steps. If real tenant access is involved, the scope stays narrow and reversible.
-
03
Customer test
One 45-minute session: perform the task, call out friction, score trust in the answer, and identify what would block adoption.
-
04
Product loop
We group notes by theme, ship the highest-impact fixes, and send a short follow-up with what changed because of the session.
The scorecard after every session
These questions turn customer sessions into product decisions. The answers decide what we fix before inviting the next cohort.
- Could the tester explain the answer to a teammate?
- Did the workflow remove a spreadsheet or manual export?
- Was the recommendation specific enough to act on?
- Did the tester trust the cloud source and calculation?
- What one fix would make them use it again next week?
Customer testing
Join the customer pilot
Tell us which real workflow you want to test. We will use this to schedule the right session and track what needs to improve.