The short answer
You do not need a selected tool or complete specification. Use sanitized (with identifying personal or client details removed) descriptions instead of sharing passwords or entire datasets.
Try it in three steps
- Write one everyday work example.
- State frequency, roles and common errors, leaving unknowns blank.
- Ask where initial discussion ends and implementation begins.
A practice prompt
Before you start
Practice an opening message with a fictional scenario, without private data or sending.
Practice material (fictional)
We run a fictional stationery wholesaler, record receipts in sheets and struggle to match item aliases. We want to consider a small improvement.Replace placeholders in the prompt with this material, or append the material if there are no placeholders. Reading time excludes doing the exercise.
We do [business] and use [process] for [task]. The hardest step is [step]. We want a small improvement assessment without sharing accounts or client details.What to look for (not a recorded test result)
The message covers business, process and blockage. Confirm volume and frequency later without preparing a full specification or sharing passwords.
If it goes wrong
If asked for full credentials or a major system immediately, clarify necessity and scope first.
Check your result
The first conversation clarifies the problem, unknowns and next step rather than merely listing tools.
References and scope
The links below support the concepts or product navigation. The steps and exercises are our teaching suggestions, not official certification or measured customer outcomes. Product interfaces and availability may change. References checked on 2026-10-17.