The 6 cohorts and the 8.82 come from the corporate programmes I've run inside a Fortune 100 company. This founder-and-leader version is deliberately small so it stays hands-on.
Who's teaching this
I'm Arvindh Sundar, founder of Put The Player First. Training founders and leaders in five countries since 2019, and running corporate programmes for large organisations, including a Fortune 100. My programmes average 8.82 out of 10.
I am not an engineer. I am a founder who got thoroughly fed up of doing his own admin and built his way out of it. That is the version I am teaching you. Not the theory, the actual thing I use on a Tuesday.
This is not theory. This is how my day actually runs.
I mean it quite literally when I say I run my business on AI. A few things it does for me, every single day:
- Drafts my sales follow-ups - and tells me who's already replied - so I glance and hit send.
- Gives me one morning board of every decision and call I owe, and I just tap through it.
- Writes and schedules my content - posts and articles, in my voice, not a robot's.
- Edits my videos while I talk to it - cuts, subtitles, colour, the lot.
- Runs quiet background agents that build and stress-test my own systems while I get on with other things.
A couple of those lean on more advanced tooling - but the moves behind them are identical. Over the weekend you build the founder-grade version, in plain English, no code.
Enough founders have asked me how, that I finally thought - fine, let me just sit down and show people properly. On your work, not mine.
The quiet problem nobody says out loud
You run a business, or a team. You make the calls. And somewhere this year AI went from "nice to know about" to "I feel a beat behind every time it comes up in a meeting."
That is not a you problem. It is a translation problem. Everything out there is built for engineers, or for absolute beginners with no real work to do. Almost nothing is built for someone who has had a hard week and just wants the machine to take some actual load off it.
- You pay for an AI tool you've opened maybe twice.
- Someone junior demos something with AI and you smile, nod, and feel behind.
- You tried a course, watched three videos, and used none of it.
- You're not sure when it's making things up, so you don't fully trust it.
- You know it could save you hours - you just don't know where to point it.
What you'll actually be able to do by Sunday evening
Not "understand AI." Do things. Here's the leverage you leave with, on your own work:
- Hand it a two-hour reading pile - a long thread, a messy report, three PDFs - and get the decision-ready summary before your coffee's gone cold.
- The little "ask-it-to-ask-you" move that turns a blank, useless prompt into a sharp brief - and quietly doubles the quality of everything it hands back.
- Where you must never outsource the call - the exact line between "this made me faster" and "I just signed off on a confident lie."
- Delegate like you would to a sharp new hire - give it a goal and a definition of done, approve its plan, then let it run. No babysitting every keystroke.
- Your own saved setup that does one of your repeat tasks the same way every time - built by you, in plain English, live before we finish.
Before you ask it anything, type: "Ask me 3 questions before you start." That one habit fixes most of the junk answers people complain about, because now it is working from your context instead of its own guesses. Try it tonight. That is the smallest taste of what the whole weekend is built on :)
How the weekend runs
Short and deep on purpose. Four hours across two days, online, on your real tasks the whole way - not toy exercises. Saturday gets it running on your actual work. Sunday turns that into systems that scale. I'm on video throughout for your questions.
Get it running, the systems way
From "I get a wall of text" to running your real work through it - thinking in systems, not one-off prompts.
- The setup that makes it remember your world - so you stop re-typing who you are every single time
- Feeding it a two-hour reading pile and getting the decision-ready answer straight back
- The mindset gap between people who "use AI sometimes" and people who run their week on it - and why prompting is the wrong game
- Landing your first real win on your own work in the first hour - your actual Monday, not a demo
- The quiet tell that shows you when it's confidently lying
- The one thing to set up first that everything you build later secretly depends on
Build systems that scale
From "it helps me" to "I've built a thing that does this for me" - plus the repeatable method for the next ones.
- Handing it work the way you'd brief a sharp new hire - and stopping the babysitting
- Turning a weekly task into something that runs the same way every time, without re-explaining it
- The five-minute habit that catches mistakes before they ship - it once caught 18 errors in my own plan
- The leap from "it helps me" to "it runs this for me" - without a line of code
- Why most people's AI setup resets every Monday - and the principle that makes yours compound
- The map to your next systems, so you keep going long after the weekend
What you actually walk away with
- Your own setup, live - real tasks from your week now running through AI, not a demo.
- At least one repeat task fully handed over - saved so it runs the same way every time.
- The real systems I use to run my business, handed over for you to adapt.
- The skill to build the next ones yourself - so it scales as you do, no code.
- Working judgment - when to lean on it, and where you must not.
- Me on hand - on video throughout, and around afterwards for a nudge.
Honestly, who this is and isn't for
This is for you if
- You're a founder or leader who decides and runs things - but doesn't code.
- You feel AI is now table-stakes and you're quietly behind.
- You want real work off your plate, not another certificate.
- You'll bring your own actual tasks to the weekend.
This is not for you if
- You're an engineer after deep prompt-engineering theory.
- You want a watch-and-forget recorded course to skim.
- You're not willing to touch your own work during the weekend.
- You want a magic button, not a new way of working.
This is tested - on founders, and at a Fortune 100
I didn't just dream this up. I've refined this exact approach in pilot batches with real founders, and taught the underlying method inside a Fortune 100 company:
- Refined with founders first - the pilot batches are how it got sharp enough to land for non-technical people, not just techies.
- 8.82 out of 10 average satisfaction across six cohorts at the Fortune 100, from 113 respondents.
- Doing beat watching - in the two-day programme, the day they built things outscored the day they learned about them. 8.37 against 8.16.
- They came back - on the strength of the work, they commissioned a whole follow-on programme.
Grab a seat in the next cohort
One repeat task off your plate, saving you a couple of hours a week, pays this back inside a month.
Only 8 seats, so it stays properly hands-on and I can actually get to everybody. Message me and I will tell you the next dates and send the payment details. First paid, first confirmed. GST invoice if you need one, just ask.
One thing to know before you commit: you'll want your own paid AI plan so you don't hit limits mid-session. It's separate from the seat, and I'll help you get set up before we start.
And if after Saturday's session it's genuinely not for you - just tell me and I'll refund you in full, no fuss. You get to see it work before you're committed.
Not for you, but somebody came to mind while reading? Send them my way. I would really appreciate it 🙂
Straight answers
Do I need to be technical or know how to code?
How long is it, and when?
Is this programming, or developer tooling?
What will I actually walk away with?
Do I need to pay for an AI plan separately?
What does it cost?
What if it's not for me?
Is it recorded, or can I catch up later?
Can you run this for my whole team instead?
With love from Bengaluru, this is Arvindh saying over and out.