Practical prompting
How to ask for useful output, refine it, and keep the work moving without overengineering the prompt.
What it covers
Training stays practical.
The goal is to help the team use the tools in real work, with clear habits around prompting, review, and output quality.
Tool-specific workflows
How Claude, ChatGPT, Claude Code, Codex, Manus, and similar tools fit different kinds of work.
Review and quality control
How to check output, catch mistakes, and keep AI assistance aligned with the business standard.
Team standards
Shared rules for what the tools are used for, what they are not used for, and how the team stays consistent.
Formats
Training can be one session or a small rollout.
The format depends on the team size, the tools already in use, and how much handholding is needed after the first session.
Team workshop
A live session for the whole team to learn the tools, see examples, and leave with a usable starting playbook.
Manager or champion session
A smaller session for the people who will set standards, answer questions, and keep adoption on track.
Working clinic
A hands-on session using the team's actual work, prompts, and examples so the training maps to reality.
How it relates to automation
Training helps the people. Automation fixes the process.
Training is useful when the team needs to adopt the tools better, write better prompts, or use AI in a more consistent way. It does not replace workflow automation. When the workflow is the real problem, Jorvek will say that directly and keep the two offers separate.
Better for training
The team already has a workable process and needs help using the tools well.
Better for automation
Work is stalling because routing, handoff, or repeated admin is not handled well.
When AI training makes sense
Your team already uses AI tools, or wants to start using them with less confusion.
People need shared standards for how to ask, review, and apply AI output.
You want training that is tied to real work, not generic hype.
When it is not the right offer
You want a generic keynote with no practical follow-through.
You only need a workflow automation project and no team enablement.
You want the tools to replace process clarity instead of supporting it.