Generative AI in practice
Ask the same question a different way and the answer can be far more useful. This course teaches how to ask, and how to turn a set of prompts into a reusable assistant (a Gem).
01
Who it’s for
- Staff use AI, but the answers are often generic and need heavy editing
- Everyone is figuring it out alone, and the company has no shared way of using it
- You want AI to help with analysis and decisions, not just write copy
- You have a lot of internal documents and want AI to answer based on them
Engagement cycle 3 months, 6 months or a year
Pricing Estimated per engagement
A question
Something your work really needs solved
Structured prompt
Role, task, format
AI-assisted reasoning
Compare options, spot blind spots
Custom assistant
Saved as a reusable Gem
02
What we do
Structured prompts
Writing clear instructions with four elements, role, task, context and format, so the output is predictable.
Reasoning and decisions
Guiding AI to reason step by step (chain of thought) to compare options and spot blind spots, not just generate content.
Knowledge base
Using NotebookLM to turn company documents into a knowledge base you can talk to, with sources cited.
Custom assistants (Gems)
Turning a department’s common prompts into a reusable Gemini assistant, so the whole team works the same way.
Usage policy
Which data can be given to AI, and how to check its output.
03
How it works
1. Needs interview
Learn what the department does and how staff use AI today.
2. Course planning
Design exercises around your actual work.
3. Teaching and practice
Every module includes hands-on work, and staff leave class with something they can use.
4. Follow-up
Collect common questions and arrange an advanced course if needed.
04
Deliverables
- Course plan
- Handouts and prompt templates
- In-class results (such as a department assistant)
- Post-course survey and feedback summary
05
Engagement cycle
Each cycle runs three months, six months or a year, depending on scope. At the end of each cycle we sit down with you and compare the results against the goals set at the start, then decide what the next cycle should cover, or whether to stop there.
06
Pricing
Each engagement is estimated on its own: how many systems and how much data are involved, the people and time needed, and how long the cycle runs. It comes in two steps. First we measure the baseline — before any quote, and priced separately — recording where things stand now. Then we estimate the rollout from the scope we measured, rather than quoting a price and fitting the scope to it. Write to us about where you are and we’ll explain what measuring the baseline involves.
07
Common questions
Can staff who have never used AI take the course?
Which AI tools does the course use?
What do we take away from the course?
08
Further reading
Tell us where you are
- Email us about where you are
- We reply with what could work
- Baseline first, then scope and estimate
Or write to hello@taux.io