Build your AI Editor + Learn Claude Code.
Just you and me.
Two live sessions, one on one. We install the editor I use every day onto your machine and tune it to your footage: six years of short-form editing, distilled into Claude skills that cut the way I cut. It removes your retakes, writes your captions, and hands you the finished edit in Premiere Pro. You get every editing skill I have built, and it stays yours.
The seat is closed.
I am not taking new bookings for this. If you already messaged me about it, you will still get a reply — nothing changes for you.
And here is the long version, if you want to see all of it: two client videos, start to finish, in 17 minutes.
More of what it makes
Real reels off my own account, all cut by the editor.
To be straight with you: the two sessions cover the cut, the captions and the hook. Motion graphics is where people go next once they are posting consistently, and I will show you where to start. I am not going to promise you will be animating by the end of session two, because you will not be.
This is for you if
- You want to build your own AI agent that edits videos.
- You want to learn AI video editing.
- You have wanted to learn Claude Code but needed a real project, not a toy tutorial.
- You want to upskill with AI, not keep using Claude or ChatGPT like a beginner.
- You want to create content, but editing takes a lot of time.
- You run a marketing agency and want to upskill your editors.
- You want to post more without the cost of every extra video, in money or in evenings, going up with it.
- You want an unfair advantage in your market.
It is not for you if
- You have never invested in your own skills. This asks for money and two sessions of your full attention, and neither one works without the other.
- You are looking for something free.
- You are not willing to pay $20 a month for the Claude plan the editor runs on. That is its only running cost, and you pay it to Anthropic, not to me.
- You do not record videos and do not plan to start. The editor needs footage.
- You want someone to edit for you. That is a service, and it is not this.
- You will not do a 20-minute pre-flight check before session one. That check is where we confirm your machine and time your baseline, and it is what makes the guarantee something I can actually stand behind.
Watch it work
What the editor actually does to a recording, step by step.
A dump straight off the phone. Retakes, false starts, the lot.
With me, this is not a diagram. It is running on your laptop, on your own footage, before session one is over.
The old way and the new way
Two ways to stop editing being the bottleneck. One of them ends.
the work yourself.
Months of tutorials, or a course like the one I used to teach. Then years getting fast.
A skill that only works while you are sitting at the machine doing it.
Costs more hours, or more money to an editor. The thing that grows you is the thing that bills you.
More output means another editor on payroll. Growth is a hiring problem.
You are competing with people whose editor does the first pass in twenty minutes.
that does the work.
Three days, once, starting from the Claude skills I already use on client work.
An editor running on your machine, plus knowing how to change it. It does not quit and it does not forget.
Costs nothing extra. The tenth video this week is the same price as the first.
One person learns it and your existing editors get faster. Growth stops meaning payroll.
You are one of those people, and you have been building with Claude Code for two years.
I taught the old way for two batches and 27 students, and I meant every hour of it. Our two sessions are better spent on the right side of this table now.
The editor you leave with
Eight steps from camera to finished timeline. You do three of them. This is what we build across the two sessions, working on your own footage.
Record your talking-head videos
Straight to camera, retakes and all. Say the line four times if you need to. Nobody will ever see the bad ones.
Dump them in a folder
Drag the files off your phone into one folder. No naming, no sorting. That is the whole handover.
Names and files everything
IMG_4027.MOV gets named, dated and filed into a project before a single cut happens.
Transcribes it
On your machine, in English. No per-video bill.
Cuts the retakes and false starts
Keeps the last clean attempt of every line. Cuts the circling, the "wait, let me say that again", the abandoned starts.
Checks its own cut, word by word
It re-transcribes the cut audio and compares it against what it meant to keep. If a word went missing, it moves the cut and tries again.
Adds captions and the hook
In your style, once you teach it. Two of the styles it ships with are below, on my real reels.
Review and render
The cut, captions and hook arrive in Premiere Pro on stacked, editable tracks. Disagree with an edit? Change it. Nothing ships until you say so.
A 10-minute recording becomes a tight vertical reel in one sitting. Depending on how much you circled, 30 to 75 percent of the footage goes. The good parts stay.
The two sessions
Install, and your editor working
Claude Code on your machine, every one of my editing skills installed, and a real video of yours cut by it before we log off. Not a demo file. Yours. You leave session one with an editor that works — session two is about making it cut like you.
Your style, and the full pipeline
You teach it how you caption and how you open. Then you run the whole thing yourself — record, drop, review, render — while I watch and fix whatever breaks. You finish having shipped a reel your own editor cut, on your own machine, with me on the call.
Along the way you learn Claude Code itself: skills, agents, and how to change the editor after we are done. You walk away more confident using and building AI agents, with your editor as the first one you built. You own this. You do not rent it from me.
The captions are the real thing
Two of the styles your editor ships with, on my own reels. Tap either to watch.
How this runs. Read this part.
There is one seat. When it is taken this page comes down until I open another. There is no cohort to wait for and no minimum number of people — you book, we start.
We pick both session dates together once you book, around your week rather than a fixed date I chose before I met you. They usually sit a few days apart on purpose, so you have time to run the editor on your own footage alone and come back to session two with real questions instead of polite ones.
One at a time is the ceiling, not a target I quietly raise. It is the only way I can promise your editor is running by the end of the first session — on your machine, with your footage, watching your screen.
What you need before session one
- A laptop running macOS 13 or later, or Windows 10 or later. 8 GB of RAM is the floor, 16 GB is comfortable. Claude Code itself is light and needs only 4 GB. It is Premiere Pro that wants the rest.
- Premiere Pro installed and working before we start. This is Premiere Pro only.
- A paid Claude plan, about $20 a month. The free Claude account does not include Claude Code, so this one is not optional. You pay it to Anthropic, not to me, and Nepal is supported.
- A steady internet connection. The editor runs on your machine, but Claude needs to be online to think.
- A 20-minute pre-flight check with me before session one. We confirm your machine can run all of it, and you edit one video the way you edit now while I time it. That timing is your baseline — not for the refund, but so that at the end you have a real before-and-after instead of a feeling.
- Videos of your own to work on. Bring your real footage. The editor is built around the way you cut, and session one ends on a video of yours, not a sample file.
The pre-flight is where we find out about your laptop before you have paid for anything, not during session one. If you are unsure whether your machine is up to it, message me first and we will check together.
The guarantee
Your editor cuts your own footage by the end of session one, or you get a full refund. Not part of it. All of it.
Not a demo file, not my footage. A video you shot, cut by the editor on your machine, while we are both still on the call. If that has not happened by the time we log off, you do not owe me anything and I refund you the same day.
The conditions are only what it takes to get there anyway: do the 20-minute pre-flight so we know your machine is capable before you pay, turn up to session one, and bring your own footage.
Why I can promise this now. I could not promise it to ten people at once across ten different laptops, so I stopped. One person, one machine, one screen I am watching the whole time — that is a promise I control. It is the whole reason there is only one seat.
What happens after is bigger than the guarantee. My own edits now take about a fifth of the time they used to. That is what the pre-flight timing is for: at the end you have your own before-and-after, in your own numbers, instead of my word for it.
Fair question: has anyone else done this? I have run a 3-day workshop twice before — 27 people paid, and they finished. But that was manual editing, not this. Nobody has built an AI editor with me yet. You would be the first, and that is exactly why the guarantee is written the way it is: you are not being asked to take my word for it.
That is what I will put money behind. What you actually walk away with is bigger than that: an AI editor that works, and the confidence to change it. To build your own assets, add your own steps, and shape a workflow that adapts to the way you work rather than the way I do.
Who's teaching
I'm Nishang. I have edited short-form video for six years, for American clients, from Nepal.
I used to teach a three-day editing workshop. Two batches, 27 paid students, and I know how to get a room from zero to shipping in three days, because I have done it.
I do not teach that workshop any more. Almost everything I spent those three days on, the editor now does by itself. That is not a sad story. It means the time goes somewhere better, and it no longer takes three days: instead of learning to do the work, you spend two sessions building the thing that does it.
You do not start from an empty folder either. You start with every Claude editing skill I have already built and use daily on real client work — all of them, installed on your machine, not a stripped-down teaching version. The two sessions are me handing over the judgment that sits on top of them: which cut is the right cut, and how to make the thing edit like you.
There are more examples of the work on my Instagram. And before you decide anything, watch the editor work: the two videos at the top of this page are real cuts, and the long one is my actual screen while the pipeline runs on two client videos. Judge it for yourself.
Questions you should ask
- Why is there only one seat?
- Because of the guarantee. I am promising your editor is cutting your own footage by the end of the first session, and the only way I can promise that is by watching one screen instead of ten. I tried to promise it to a group earlier this year and pulled it, because across ten different laptops it was not mine to promise.
- I'm not technical. Can I do this?
- If you can install an editing app and follow instructions, yes. Claude Code looks like chatting, not like programming. The pre-flight check exists so we find out about your machine before session one, not during it.
- Does it support Nepali?
- Yes. Nepali captions need a couple of workarounds rather than working straight out of the box, and they land around 95 percent accurate, so you fix a word here and there. We build that part of the editor together, briefly, so you leave with it working.
- I edit in CapCut, not Premiere Pro. Can I still do this?
- No. The editor hands its work off as an editable Premiere Pro timeline, and that hand-off is the part I can stand behind — so Premiere Pro is a requirement, not a preference. I would rather tell you that now than take your money and have you find out in session one. Message me and I will let you know when a CapCut version exists.
- What happens if something breaks afterwards?
- You will be able to fix most of it yourself, which is exactly why we spend real time on Claude Code rather than only on the editor. It is your machine, your install and your skills — nothing phones home to me, and nothing stops working if I disappear.
- When is it?
- Whenever suits you. There is no cohort to wait for — we pick both session dates together once you take the seat, usually a few days apart so you have time to run the editor on your own footage in between and come back with real questions.
- Is it in person?
- No, fully virtual, live on a call. Because it is just the two of us, the time is whatever works for you rather than for a room. That is also why the pre-flight check matters: your machine is the classroom.
- Has anyone done this with you before?
- Not this. I have run a three-day editing workshop twice, and 27 people paid and finished — but that was manual editing. Nobody has built an AI editor with me yet, and you would be the first. That is the honest reason the guarantee is written the way it is.