OpenAI Select Partner
Completion certificates your team can put on LinkedIn.
Workforce AI enablement. OpenAI Select Partner. Built for Tech and NonTech functions. Hands-on with ChatGPT, Claude and Gemini.
Build an AI-ready workforce, beyond having a few AI experts.
A no-theory, hands-on workshop for every employee to learn by building for real problems in your org.
The format
Two days. One room.
Something real at the end.
Day one levels everyone up. Day two turns that into a build. We can also design a custom workshop, based on your needs.
- The tool landscapeChatGPT, Claude, Gemini: what each is good at.
- Prompting that worksFrameworks your team still uses on Monday.
- Limits and safe useWhere AI is wrong, and what never goes in.
- AI in your workflowsMap use cases, shortlist Day 2 problems.
Day 01Foundations
for everyone
for everyone
Day 02A working build
relevant for
your business
relevant for
your business
- Pick the problemA real one, from your team's week.
- Build in mixed squadsA Codewave practitioner beside every squad.
- Demo to leadershipOne build gets a named owner.
- Hand-offBuild it, hand it over, or park it.
Why Day 2 exists. One of our facilitators built a hackathon feature that became his company's biggest selling point. We designed the second day around that.
We don't teach AI from slides.
We teach it from what we ship.
Partners &
credentials
OpenAISelect Partner
Claude[Partner programme name]
CodewaveBuilding since 2013
IIM UdaipurGuest faculty
IIT MadrasSession on entrepreneurship
100+Professionals trained
3Continents we build for
The same people who teach AI and design thinking at IIM Udaipur and ISBR, and experts, have spent 13 years rebuilding how businesses work. That's who walks into your room.
[Claude partner programme name]
[One line on what the Anthropic partnership means. Confirm wording before launch.]
Builders, not trainers
The AI enablement arm of Codewave. Your facilitators ship AI products weekly.
The real gap
You bought the best models for your team. But it's still not giving the best results.
Before Foundery
- Licences paid for. Most seats barely touched.
- Shadow AI, with client data in personal accounts.
- AI ideas everywhere. No one picking which to build.
- An AI mandate from the top. No owner below it.
After Foundery
- Everyone using AI to its max potential producing real work.
- Everyone aware of data risks and usage rules.
- Your team decides what is worth building for max ROI.
- Your team builds it and owns testing it in your org.
The business case
AI used right,
pays back.
AI used right doubles the ROI and used wrong wastes the spends. Two days teaches your teams the difference.
1 [Source for the 25% and 40% figures: published study or pilot data. Add before launch.]
0%+Faster when AI is used
on the right tasks1
on the right tasks1
0%Higher-quality work
on the same tasks1
on the same tasks1
0Days to learn
the difference
the difference
0+Working AI tool,
with a named owner
with a named owner
Two days of their time.Hours back, every week after.
Walk away with
Build the skill,
beyond the certificate.
/ 01
A working build solving a real problem
At least one tool or workflow built on a real problem on Day 2, demoed to leadership, with a named owner.
/ 02
Your prompt playbook
The prompts that worked in the room, written up by function.
/ 03
Safe by default
A risk baseline from a pre-workshop survey and usage rules people read.
/ 04
Upgraded skills and a certificate that counts
Tokens, context, hallucination. Your team can talk about AI, so they keep improving together. Certificates from an OpenAI Select Partner.
How it runs
From knowing the right thingto doing the thing right.
Every workshop follows the same path, shaped around your team. Nothing off the shelf.
See if we're a fit01
Discovery call
30 minutes to understand where your team is, and whether we're the right fit.
02
Team survey
A short pre-workshop survey builds your risk baseline: tools, habits, gaps.
03
Setup checklist
Accounts ready, training switched off, Day 2 problems shortlisted with your leads.
04
Day 1 · Foundations
The whole room fluent in the fundamentals by 5pm.
05
Day 2 · Hackathon
Mixed squads build on real problems and demo to leadership.
06
Hand-off pack
Playbook, guidelines, certificates and a clear next step for every build.
Who runs the room
People who ship AI work weekly.
Not trainers who read about it.
Abhijith HK
Founder and CEO, CodewaveBuilds agentic systems for clients across three continents. Guest faculty on AI and design thinking at IIT Madras.
Vidhya Abhijith
Co-founder, Head of DesignA decade shaping products across India and Southeast Asia. Teaches teams to frame the problem before they prompt.
Nilesh Deshmukh
AI Product BuilderHas trained 100+ engineers and professionals. Runs the hackathon and keeps teams honest about what's useful.
Is this right for our team?
It's built for teams at zero, one or two on AI: founders and CXOs who don't know where to start, HR and L&D heads who want training people show up for, and mixed teams across sales, design, ops, finance and product. It's not for teams already building agents, RAG or using Claude Code and Cursor daily. For that, talk to Codewave.
Do participants need their own AI accounts?
Yes. They work in their own ChatGPT, Claude or Gemini accounts so the learning goes straight back to their desk. We send a setup checklist before Day 1, including how to switch off training on your data.
Is this only for technical teams?
No. It's built for mixed rooms: sales, design, ops, finance, HR, product. Nobody needs to code.
How many people can attend?
A standard room is [X to Y] people so every squad gets a practitioner beside them on Day 2. Larger groups run as parallel tracks over up to four days.
What happens to our company data on Day 2?
Teams work in their own accounts with training switched off, on anonymised or sample data unless you approve otherwise. Nothing is stored by us, and we sign an NDA before the workshop if you need one.
Where do you run it?
In person, at your office or a venue you choose. We're based in Bengaluru and travel to [cities covered]. Travel outside [base city] is quoted separately.
How far ahead should we book?
[N] weeks is comfortable. It gives us time for a short discovery call, the setup checklist and shortlisting Day 2 problems with your leads.
Stop spending more on AI.
Maximize ROI from what you've spent first.
Train your team to make the most of the sophisticated models you've got them, before you spend more.