> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Risk-Free Pilot

> Validate GermainUX on your own workflow, against the tools you already use, with the pilot fee tied to the criteria your team validates.

> [card] [How the Pilot Works](#how-the-pilot-works)
>
> One workflow, one question

> [card] [Pilot Challenges](#pilot-challenges)
>
> What to test and how to compare

> [card] [Request a Pilot](#request-a-pilot)
>
> Get started

## How the Pilot Works

> [!NOTE]
>
> Bring us **one workflow you want to improve** and **one question your team struggles to answer today**.

**1. Agree upfront on what GermainUX needs to prove**

Together, we define the success criteria before the pilot starts.

**2. Run the same challenge against the tools you already use**

Each vendor gets the same challenge, so results can be compared side by side.

**3. Tie the pilot fee to the criteria your team validates**

You pay based on the outcomes your team confirms.

## Pilot Challenges

Use the following challenges to test GermainUX and every other vendor under the same conditions.

| What to test | Challenge to give each vendor | How to compare |
| - | - | - |
| **1. Help us avoid business impact** | "Pick a recurring issue that causes lost orders, delays, or rework. Show how early you can warn us and what our team can do in time to limit the impact." | Warning lead time, whether the right team can act within that window, and any impact the client verifies was avoided |
| **2. Detect our top 10 UX, workflow, or technical issues in near real time** | "Show us the top 10 issues affecting this workflow as they emerge. Explain how you rank them and show the evidence behind each and get recommendations on how to fix them." | Time from occurrence to visibility, how many findings the client validates, and whether the ranking reflects affected users, transactions, or business outcomes |
| **3. Shorten the time from detection to resolution** | "Take one real issue from detection through diagnosis, assignment, fix, and verification." | Elapsed time at each step. If the fix falls outside the pilot window, agree upfront to score time to a verified diagnosis and an actionable handoff |
| **4. How quick can you build on top** | "Once the first use case is live, have our team add a custom automated insight, build an automation, change a scheduled report, and create a dashboard for another team or workflow." | Time and effort per change, what the team can do on its own, and what requires vendor services, custom code, or new instrumentation |

> [!TIP]
>
> Our advice: **The devil is in the details!** Never subscribe to a tool without first running a pilot to validate that it actually delivers what you need.

## Request a Pilot

[Request a risk-free pilot](https://calendly.com/germainux/riskfreetrial?back=1) or [contact the Germain Team](https://docs.germainux.com/getting-started/support.md) to define your workflow, question, and success criteria.

## Get Help

> [card] [Contact GermainUX Support](https://docs.germainux.com/getting-started/support.md)
>
> The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

> [card] Can't Find What You Need?
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.