> For the complete documentation index, see [llms.txt](https://knowledge.magicworksitsolutions.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.magicworksitsolutions.com/knowledge/ai-consultation-and-readiness/90-day-pilot.md).

# The 90-day AI pilot

A practical 90-day structure for validating an AI opportunity before scaling.

A good AI pilot tests a business hypothesis, not just a technology demo.

## Days 0–30: define and baseline

Document the current workflow, establish baseline metrics, identify risks and define the human-review model.

## Days 31–60: implement and evaluate

Run the solution with a controlled user group. Measure quality, speed, error modes, adoption and operating cost.

## Days 61–90: validate the operating model

Decide whether the result is reliable enough to scale. Document exceptions, ownership, governance, training needs and integration requirements.

At the end of the pilot, the decision may be **scale, refine or stop**. Stopping a weak use case is a successful outcome when it prevents a larger bad investment.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.magicworksitsolutions.com/knowledge/ai-consultation-and-readiness/90-day-pilot.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.