Describe the process, systems you use, and intended output. The assistant helps organize requirements, propose a workflow, and identify data, permissions, and questions that change the design.
Start with recurring work
Design a procurement review process.
Prepare follow-up for invoices in different states.
Define sources for an internal knowledge assistant.
Review a plan connecting a process to your systems.
A useful starting message names the trigger, the team involved, the systems holding the data and the output you need. For example: a purchasing team receives three offers and needs a comparison for approval. Use fictional details. The assistant can help shape the design discussion; it does not connect to your purchasing system or approve an order.
What it can provide here
Workflow design, gap checks in the definition, baseline workload calculations from your inputs, and selected technical references when available. A proposal remains a plan for process-owner approval.
Before sending
Use fictional examples. Submitted conversations are processed through the model provider; read the data notice. Do not include secrets or customer records.
This is a public design experience. Enterprise tools, memory, and execution approvals are defined and implemented in a separate customer workspace within the project.
Only recent context is sent; restate important decisions when needed.
Use fictional data only. Sending processes the conversation with Groq. Do not share secrets or customer data; no writes to your organization's systems are performed. Privacy