Prepare for AI consulting
AI project brief: define one workflow before a proposal
A useful AI project brief describes the current task, its owner and a result that can be checked. Choose a concrete transition, such as turning an unclear enquiry into a staff task. Do not start with a model name or a promise of full automation.
Understand the task
An unclear brief postpones disagreement until after development. “Better customer service” does not specify answers, channels or actions. Describe what staff will still do manually. This allows proposals to be evaluated without confusing an advisory deliverable with activated software.
Prepare these inputs
- The task’s trigger, final state and responsible staff member.
- A fictional normal example and two relevant exceptions.
- Approved sources, systems and known access limitations.
A practical workflow
- Write the current process as a few concrete actions. Mark waiting and repeated questions.
- Choose one improvement and an observable acceptance criterion. Keep possible system changes separate.
- Request a proposal stating output, exclusions, pricing basis and operating responsibility. Procora agrees these individually.
Worked example, not a customer case
An illustrative example
Illustrative brief: “Reception receives practical enquiries. We need a summary with topic, contact route and missing information. The model must not book. Testing uses fictional messages. Reception approves the summary and unresolved questions must stay visible.” This is more precise than “build an AI receptionist”.
Test failures and exceptions
| Test input | Expected outcome |
|---|---|
| The supplier proposes additional actions. | Assess them as separate scope before acceptance. |
| Nobody can explain when the task is complete. | Define final state and approver before starting. |
Evaluate whether it helps
Check whether two staff members describe the same result after reading the brief. Record unclear decisions before quotation rather than burying them in a general implementation price. A short brief can be strong when it bounds the right task.
Next step: Fill in trigger, final state, owner, sources and acceptance criterion before the first supplier conversation.
Sources and scope
Examples are editorial exercises using fictional information. They do not describe completed customer tests or activated integrations. The authority source below provides AI and data background rather than approval of the exercise.
Want to clarify your own workflow?
Bring one task and a non-sensitive example. Scope, price and timing are agreed individually before work. Reading a guide activates no customer messages or system actions.
Describe your task