AI Capability Programme
The Art of the Possible with AI
Leadership Workshop & Practitioner Course for I.EVO
MELLONE
Understanding your organisation
Who you are
Where you're starting from
What you actually need
Raw material we'll build with
Founders

Rakesh Venugopal
Co-Founder, Product & Strategy
Indian School of Business"Seed to Series F – strategy, growth & org transformation."

Swadhin Sahu
Co-Founder, Operations & Revenue
IIT Madras IIM Lucknow"Ed-tech to AI products & services – revenue, growth, analytics & operations."

Balwinder Singh
Co-Founder, Technology
Motilal Nehru NIT"Nike & Lowe's to AI for impact – engineering leadership, systems & scale."
What we do
AI training for corporates
Upskilling teams and leadership through hands-on, role-relevant AI training
AI implementation & FDE services
Embedding AI solutions directly into client operations, from strategy to execution
AI training in colleges
Building AI fluency in the next generation through campus partnerships
AI products (stealth)
Proprietary AI products currently in development
Programme architecture
Training first, then consulting, then buildTrack A1 turns leadership into hands-on AI practitioners through live, in-person training; Track A2 then screens and ranks your opportunities into a build-ready shortlist. What gets approved moves into implementation, with practitioner rollout running alongside it.
Programme timeline
How the tracks sequence against each otherTrack A runs as a fixed 9-week sequence – the workshop, then consulting. Track C and Track B follow, scoped only once Track A is complete, so they're shown after without a week commitment.
Track A1 · Day 1 & Day 2
Think big on Day 1, go deep on Day 2Every session is hands-on – mentors work live against your own material, not generic demos, so leaders see exactly how AI applies to the work in front of them, not a hypothetical.
Illustrative Use-Case Menu
A sample of what the room will see liveIllustrative only – the mentor selects and demos the final 4–5 live, in the room, from I.EVO's own real material on the day.
Every single session carries a live AI moment built to land as a genuine "wow" — so participants leave each block more curious to go deeper, not less.
Roles & Responsibilities
I.EVO provides
Mellone delivers
Commercial Summary — Track A1 Training
Momentum · Why Mellone
AI Nexus for Leaders, Mauritius
A high-touch AI training programme curated specifically for industry and government leaders – strategic AI adoption, governance frameworks, and decision-making under uncertainty, delivered to senior officials and executives across sectors.
AI training deployment – 5 colleges, India
In progressCampus-wide AI fluency programme – proven ability to run structured curriculum across multiple cohorts in parallel.
Forward-deployed engineering partnership
In progressFDE talent embedded within a leading AI lab in Mauritius – hands-on implementation depth, not just training delivery.
A mentor bench built for this brief
Mentors with prior sector exposure spanning government, manufacturing, supply chain, BFSI, and enterprise AI architecture – not generalist trainers.
Programme feedback – 5-point scale
4.6/5
Service & delivery
4.8/5
Mentors & instruction
4.6/5
Content & curriculum
4.8/5
Likelihood to recommend
4.6/5
Overall programme
Annexure
Track A2 · Consulting
An 8-week path from 111 problems to 10 build-ready use casesFour steps, fully sequential – each one narrows the field further before the next begins, so effort only scales up once leadership has bought in.
Track A2 · Step 1 of 4 · 2 weeks
Opportunity Screening & AI-Fit Scoring
Track A2 · Step 2 of 4 · 3 weeks
BVR Development for Identified Use Cases
Track A2 · Step 3 of 4 · 1 week
Ranking & Steering Committee Approval
Track A2 · Step 4 of 4 · 2 weeks
PRD & Implementation Roadmap for the Approved 10
Commercial Summary — Track A2 Consulting
Available as a follow-on to Track A1 Training — see the 8-week workflow above for the full breakdown.
Opportunity Screening
From Problem Register to Implementation OpportunitiesThis step does not identify new problems — it takes the problems already logged in the audited Problem Register (plus anything fresh an HOD wants to add) and screens, scores, and ranks each one into a short-list of implementation project opportunities for Track A and Track B.
Screen
Pick an item already logged in the Problem Register, or add one not yet on the list. HOD is named as sponsoring owner.
→Score
Rate 4 Complexity factors and 4 Benefit factors, 1–5 each, against a written scale — not a blank number.
→Place
The two averages plot the opportunity on a Complexity × Benefit quadrant.
→Rank & Route
Quadrant sets a Priority Index and routes the item into the Track A or Track B implementation pipeline — the short-list sorts on that automatically.
Complexity — how hard to build
Averaged 1–5 across 4 factors
Build Time — hours of prompting → needs the iEvo Net rebuild
Build Cost (ROM) — ~₹0 → ₹5L+ spend
Data & Systems Readiness — already clean → doesn't exist yet
Dependency Risk — standalone → blocked on Infor LN / the rebuild
Benefit — how much it matters
Averaged 1–5 across 4 factors
Time Saved — negligible → frees up a meaningful share of an FTE
Cost Avoided / Value — negligible → ₹10L+ a year
Quality / Risk Reduction — negligible → removes a compliance-level risk
Strategic Reach — one task → cross-functional / whole lifecycle phase
Placement rule — Benefit ≥ 3.5 is "high", Complexity ≤ 2.5 is "low"
Quick Win
High benefit, low complexity → Track B implementation candidate
Major Bet
High benefit, high complexity → Track A leadership-sponsored initiative
Fill-In
Low benefit, low complexity → optional practice material only
Park
Low benefit, high complexity → not pursued this cycle
Ranking formula
Priority Index = Benefit − Complexity
The short-list sorts highest-to-lowest on this single number — Quick Wins naturally rise to the top, Parked items sink to the bottom, no manual re-sorting needed as more opportunities get screened.
Business Value Realization (BVR)
One-page implementation value caseFilled once per use case — Track A HODs, twice (intra + cross-functional); Track B participants, once — so the "Business Value & Quantified Impact" score in each rubric is backed by a real number, not a judgment call.
Suggested framework — not yet approved. The structure, formulas, and scoring bands below are Mellone's proposal for I.EVO to review. The rate card (₹/hour by role) is a required input from I.EVO Finance/HR and is not filled in until supplied. Nothing on this page should be treated as final until I.EVO leadership signs off.
1Cost to Build
| Line | Formula | Amount (₹) |
|---|---|---|
| Build effort | hrs invested × loaded rate/hr | |
| Tooling / licensing | incremental cost beyond approved stack | |
| One-time implementation | data prep + integration + testing | |
| Ongoing maintenance | annualized upkeep + champion time | |
| Total Cost to Build | ||
2Value Generated (annualized)
| Line | Formula | Amount (₹ / yr) |
|---|---|---|
| Time Saved | hrs saved/wk × 52 × loaded rate/hr | |
| Cost Avoided | direct spend avoided (rework, penalty, expediting) | |
| Quality / Accuracy Gain | error rate × cost/error × frequency (COPQ) | |
| Total Annual Value | ||
ROI
(Value − Cost) ÷ Cost × 100 = ___ %
Payback Period
Cost ÷ (Value ÷ 12) = ___ months
Confidence in this estimate
Pre-deployment, this is a projection — see the tracking sheet on the next page for how it gets checked against reality.
3Quantification Discipline — must all be checked before this counts toward the rubric score
Every value line shows its formula, not just a final number
Every assumption (rate, frequency, error cost) is stated in writing
The loaded rate used comes from I.EVO's approved rate card, not guessed
No line is left "intangible" — everything is converted to a number
BVR — Post-Deployment Tracking
Projected vs. actual, 30 / 60 / 90 daysThe BVR page's numbers are a projection made before the implementation goes live. This sheet is the same opportunity, checked three times after go-live, to see if the projection actually held up.
Suggested framework — not yet approved. Pending I.EVO sign-off, and pending confirmation of who owns the 30/60/90 check-in (Champion, HOD, or Mellone) and how it connects to the separately-proposed governance/kill-switch layer.
| Projected Value (from BVR page) | Actual Value Observed | Variance | Notes / Corrective Action | |
|---|---|---|---|---|
30DAYS |
₹ / month, pro-rated from annual value |
Early signal only — usage habit forming, not full run-rate yet |
||
60DAYS |
₹ / month, pro-rated from annual value |
|||
90DAYS |
₹ / month, pro-rated from annual value |
Decision point — see below |
On or above projection
Confirmed for production / scale-up. Feeds the leadership prioritization grid as a proven case.
Below projection, recoverable
Owner revises the approach with Champion support; re-checked at next 30-day mark.
Materially below, day 90
Candidate for discontinuation — this is the trigger point for the separately-proposed governance "kill switch," not yet approved either.
Track B · Practitioner Curriculum
Six modules per department, split between what's true for everyone and what has to be rebuilt for each function so the practice work is genuinely theirs.
AI Foundations for Our Work
What today's AI tools are good at, where they quietly get it wrong, and the habit of checking before trusting.
STATICResponsible Use & Data Rules
The Track A usage charter turned into everyday practice – what can go into a tool, and when to stop and ask.
STATICPrompting as a Craft
Role, context, constraints, format – practised on that department's own real tasks, not generic examples.
×6 DEPTSAI in Your Workflow
Mapping one recurring task to an AI-assisted version – the task is department-specific by definition.
×6 DEPTSWorking with Our Systems
Which Infor LN / 9AI touchpoints matter, and how to escalate when the agent gets it wrong – differs by function.
×6 DEPTSCapstone Assignment (brief)
Generic instructions to pick a real task, execute it AI-assisted, and document before/after for review.
STATIC3 hrs
Static content
(covering M1, M2, M6)
18 hrs
Dynamic content
covering M3, M4, M5 across 6 depts
M3–M5 · What "Dynamic" Actually Means
Not a Udemy course with a company logo on itEvery department is taught the same five-part prompting skeleton — but the content inside it is pulled from that department's own audited pain points, so the practice work is a real task, not a stand-in example.
What stays constant — the skeleton, taught once to everyone
What changes — the real task each department practises on
Costing & Tendering
"Cost this BOQ."
Prices must come from Hitesh's costing sheet; catalogue items pull the Library's locked price; flag anything missing instead of guessing.
PMC / Central Ops
"Summarise this thread."
Restate the open decision as a single yes/no question with a deadline and named owner — inside the 24–48h SLA, before it gets ducked again.
Design / Hanmac / PCD
"Fix this drawing note."
State what changed AND what didn't, so it survives all 4 hops of the Pytha→PCD→Designer→PCD→Pytha loop without a phone call.
Track B · Department AI Labs
In-personWhere the recorded modules meet real work, live – and where each department's AI Champion starts stepping into the mentor role they'll carry after we leave.
AI Lab – 1 dedicated day per department, in person
A live, hands-on session run on 1–2 real scenarios sourced directly from that department group's section of I.EVO's problem register – depth over coverage, not a tour of possibilities. Delivered as 4 hours per department group, split into two 2-hour sessions across the day.
Office Hours – 2 hrs/week, 3 sessions
Common to all departments, run together, and matched to what's just been taught – Week 1 covers M1–M3, Week 2 covers M4–M6, Week 4 supports the capstone push. This is the lightweight async-support mechanism I.EVO asked for.
Rollout – 5 weeks, all departments simultaneously
tentative, subject to I.EVO schedulingWeek 3 – one department per day
MON
Costing & Tendering
TUE
BD (Domestic & Intl)
WED
PMC / Central Ops / Installation
THU
Design / Hanmac / PCD
FRI
Production / QC / Dispatch / SMC / PPEC
SAT
Finance / HR / IT / MIS
24 hrs
Live AI Lab
(6 dept groups × 4 hrs)
6 hrs
Office hours
(3 sessions × 2 hrs, common)
5 wks
Total rollout,
all 6 departments together
Track B · Capstone Structure
One capstone, flexible teamEvery Track B participant completes one applied capstone, built on a real, sponsored task from their own work – solved individually, or as a group formed either within or outside their department, whichever fits the task best.
Individual
Completed solo, entirely by one participant, on a task they own.
Team – within department
3–4 participants from the same department take on one shared task together.
Team – outside department
3–4 participants spanning two or more departments team up on a shared task.
Where capstone ideas come from
Capstone tasks aren't picked freely by participants – they're drawn from the same ranked opportunities produced by Opportunity Screening. Each HOD consolidates their function's ranked list and hands Track B a curated set of sponsored opportunities to build from.
HOD role in Track B — RACI
Accountable
HODs are formally embedded in Track B, not just Track A
Each HOD is the Accountable owner of their function's capstones – consolidating and assigning the ranked opportunities, and signing off that submitted work maps to a real sponsored task. Champions are Responsible for day-to-day delivery support; Mellone is Consulted on rubric and evaluation; Founders stay Informed on outcomes.
Track B · Evaluation Framework
Evaluation isn't a survey at the end – it's built into the same touchpoints participants already move through. Certification is earned on capstone pass plus the data-rules test, never on attendance alone.
1. Baseline
Relevance & confidence per module / lab
Short pulse survey before and after each recorded module and after the live AI Lab
2. Learning
Prompting skill & data-rules comprehension
Gating quiz after every module (pass required to unlock the next) plus a final prompting-task + data-rules scenario test before capstone eligibility
3. Application
Capstone evaluation
M6 capstone scored against a shared rubric, two-stage review
Standard capstone submission format
Two-stage review on the capstone
Champion scores domain correctness.
Mellone moderates AI-usage quality.
Agency-moderated for the first two cohorts, then champion-led.
Track B · Capstone (M6) Evaluation Rubric
Two stages: hard gates that must all pass before scoring begins, then five weighted dimensions scored 1–4. Mellone will supply one sample capstone project, one sample submission and one sample evaluation to make the process clear.
Stage 1 – Eligibility Gates
Pass / fail · all four required before scoring
G1 · Task Authenticity (Champion) – real work, pre-approved before the capstone starts.
G2 · Submission Completeness (Agency) – standard format supplied in full.
G3 · Data-Rules Compliance (Agency) – any charter violation is an automatic Not Certified.
G4 · Prerequisite Assessment (Agency) – Level 2 pre/post assessment already passed.
Stage 2 – Scored Dimensions
1–4 scale · weights sum to 100%
Domain Correctness & Business Value
Champion
Prompting Craft
Agency
Verification & Human-in-the-Loop
Agency
Data-Rules Compliance
Agency
Efficiency & Time Impact
Champion + Agency
Belt Competency Ladder
Status that means something Suggested — pending approvalTwo tracks share one five-belt sequence – White, Yellow, Green, Blue, Black. White and Yellow are Track B-only; Green and Blue are shared. Black sits above Blue in both tracks – not a rung either track's structure guarantees, but a separate, discretionary tier.
Sustain Layer
The programme has to survive after we leave. Champions are the mechanism – and their preparation starts inside Track B itself, not in a separate room afterward.
Who champions are
1–2 per department, nominated by HODs during Track A's closing session – drawn from within that department's own Track B cohort, not hired in externally.
How they're prepared
Co-facilitating their department's live AI Lab alongside the mentor is the apprenticeship – they're already applying rubric-thinking to real cases before being asked to run it solo.
Half-day train-the-champion session
Commercial Summary — Track B
Available as a follow-on phase — see annexure for the full curriculum.
Meet Some of our Mentors
Practitioners first – every mentor has built and delivered AI work across sectors before teaching it.

Divij Bajaj
Data & Applied Scientist II, Microsoft · AI Educator & Consultant, Thinklytics · Ex-VMware
~7 years building and productionising ML/GenAI systems at enterprise scale; published author on LLMs and Generative AI.
Prior clientele sectors

Jitesh Dugar
Founder, Mediajade (Authorised Zoho Partner) · Top 10 Global n8n Creator · AI & Automation Specialist
Builds custom AI-powered automations end-to-end across CRM, workflow, and orchestration tools; prior Senior Product Manager background at Wati and Drivezy.
Prior clientele sectors

Sukin Shetty
Enterprise AI Architect · Vice President of AI, Kambaa Inc. · Creator, Nemp Memory · AI Educator
Designs agentic AI systems and enterprise AI architecture; trained 10,000+ individuals across corporate workshops and technical bootcamps; background in manufacturing operations.
Prior clientele sectors
Thank you
We'd love to bring this to I.EVO – leadership conviction, practitioner capability, and a sustain layer that keeps working long after we leave.
MELLONE