# Plan an AI employee pilot around your first outcome

Bring your goal to an Elvina demo. Start with your main goal and a role. Keep related tasks together. Add detail if you have it, then use the brief to explore a relevant demo.

## Make the first result small enough to inspect.

Choose a main goal and role. Related tasks can stay together: an onboarding lesson, a shift checklist and answers to common questions may all support the same goal. Agree on a manageable first step in the demo; separate unrelated projects only when it helps.

## Name the people who own the decisions.

You do not need a finished training specification to request a demo. If you already know the source owner, reviewer or success measure, add them in the optional detail. Use role names rather than personal employee information.

## Agree on the prerequisites for going live separately.

Google Drive and Notion connect to Company Knowledge directly, while Dropbox and SharePoint are planned, not available today; review permissions, delivery rules, budget, and commercial terms are agreed for your environment. This brief does not provision an account, activate a pilot, or purchase a service.

## Decide when to share.

The form creates a versioned brief in this browser. You can download it and share it through an approved channel. There is no hidden CRM submission, email send, or payment step.

## Questions

**Q:** What should I prepare?

A permitted source, one target role, a useful deliverable, a reviewer, and a measurable acceptance criterion.

**Q:** Does saving start a paid pilot?

No. Saving is local only. Service availability, price, scope, and consent require a separate agreement.

**Q:** Should I upload confidential material here?

No. Describe source types only. Do not enter secrets or employee records into this public website.

No launch date is committed for planned features.
