6 real work scenarios. Pick how you'd handle each one. Your score reveals exactly how much of your AI tool you're actually using, and where the gaps are costing you hours every week.
Takes about 2 minutes. No email required to see your score.
Scenario 1 of 6 · Content
You need to write a week of LinkedIn posts about your industry. What do you do?
AOpen ChatGPT or Claude. Type "write me 5 LinkedIn posts about [topic]." Copy the output. Edit until it sounds like me.
BPaste a detailed prompt with my audience, tone, and a few example posts. Get better output. Still takes 30-60 minutes.
COpen a saved Project that already knows my voice, audience, and content pillars. Type "next week's posts." Review in 5 minutes. Done.
Gap #1 identified
If you picked A or B, you're rebuilding context from scratch every time you write. The 4% who use AI as a system set up their voice, audience, and style once. Then every piece of content takes 5 minutes instead of 60. That's roughly 3 to 4 hours saved per week on content alone. How they do it? That's what the workshop covers in the first 35 minutes.
Scenario 2 of 6 · Meetings
You have a sales call in 30 minutes with someone you've never met. How do you prep?
AGoogle their name. Skim their LinkedIn. Check their company website. Wing the rest.
BAsk ChatGPT to research them and draft talking points. Copy into my notes. Takes 15-20 minutes.
CA workflow already prepped the brief: attendee research, company news, prior interactions, a draft agenda, and 3 sharp questions to ask. It was ready before I opened my laptop.
Gap #2 identified
If you picked A or B, you're spending 20 to 45 minutes per meeting doing what a pre-configured workflow does in zero. Multiply that by 8 to 12 meetings a week. That's up to 6 hours of prep that didn't need to happen. The people who close faster aren't smarter. They walk in better prepared because a system did the research overnight.
Scenario 3 of 6 · Email
It's 9 AM. You have 47 unread emails. What happens next?
AStart at the top. Read each one. Reply to what I can. Flag the rest. Takes about an hour.
BScan subjects for urgency. Batch-reply to the easy ones with AI help. Defer the rest. Still 30-40 minutes.
CPaste the batch into a system that sorts by priority, drafts replies for routine emails, and extracts action items with deadlines. Done in 8 minutes.
Gap #3 identified
The average professional spends 28% of their workday on email. That's 11 hours a week for someone working 40. Options A and B claw back some of that time. Option C restructures it entirely. The difference is a system that already knows your priorities, your reply style, and who gets answered first. That's 45 to 60 minutes back every single morning.
Scenario 4 of 6 · Reporting
Every Friday, your manager wants a status update. Same format, same data sources, same structure. What do you do?
AOpen a blank doc (or last week's report) and write it from scratch. Copy numbers from 3-4 tabs. Takes 45 minutes.
BCopy last week's report, update the numbers manually, ask AI to polish the summary paragraph. 20-30 minutes.
CPaste this week's raw data into a Project that knows the format, the audience, and what "good" looks like. Get a draft in 90 seconds. Review in 5 minutes.
Gap #4 identified
Any task that follows the same structure every week is a workflow waiting to happen. If you're still opening last week's doc and updating numbers by hand, you're spending 30 to 45 minutes on a 5-minute job. Every single week. That's over 30 hours a year on one recurring task. The system already knows what your manager wants. You just haven't built it yet.
Scenario 5 of 6 · Memory
You had a great AI conversation yesterday. It produced exactly the output you needed. Today you need something similar. What do you do?
AStart a new chat. Try to remember what I typed. Rephrase it. Hope for the same quality. Usually doesn't work as well.
BScroll through yesterday's conversation, find the prompt, copy-paste it into a new chat. Takes a few minutes of digging.
CI don't need to. My AI already has my preferences, voice, context, and past instructions saved permanently in a Project. Every conversation picks up where the last one left off.
Gap #5 identified
If you picked A or B, you're starting from zero every single day. No memory. No context. No continuity. It's like training a new intern every morning and wondering why the output is inconsistent. The 4% set up their AI with context, files, and instructions once. Then it gets better over time instead of resetting. That single shift changes everything about how useful AI feels.
Scenario 6 of 6 · The real question
Be honest. How many hours per week do you spend on repetitive tasks that follow a predictable pattern? Content, emails, reports, meeting prep, data formatting, follow-ups.
A10 or more hours. It's most of my week, honestly.
B5 to 10 hours. A solid chunk, but I've optimized some of it.
CLess than 5 hours. Most of my repetitive work is already handled by systems or delegation.
Gap #6 identified
Whatever number you picked, at least half of those hours can be handled by 3 to 5 configured AI workflows. Not by typing better prompts. Not by switching tools. By setting up systems that remember your context, your format, and your standards. Once. The math isn't subtle: if you reclaim even 5 hours a week, that's 260 hours a year. That's six and a half full work weeks. Gone. Back in your calendar.
Calculating your AI Fluency Score...
YOUR AI FLUENCY SCORE
--
--
--
--
--
estimated hours lost per week
--
Your #1 recommended workflow from the workshop
--
--
Fix all 6 gaps in 2 hours. ₹99.
Sunday, June 8. 11:00 AM IST. Live with the founder. You build the workflows in your own Claude account.
Outcome guarantee: leave without a working system, your ₹99 is refunded AND your next workshop is free.