Non-technical AI builder & coach
I’m Lokesh, a non-technical builder. I create AI systems, automations and websites for businesses.
My story ↓
Before 2022
I made logos, slides, banners and marketing funnels. I also built chatbots where every reply and every path had to be planned in advance. I didn’t know how to code. I kept finding tools that helped me turn an idea into something people could use.
2022–2025
ChatGPT began with a simple shock: I could talk to a computer without choosing from predefined branches. Then the uses became ordinary in the best way — brainstorming an idea, researching a question, improving a draft, generating an image, summarizing a file, or making something I could share.
Some uses took five minutes. Others grew into websites, reusable skills, and workflows. They all began the same way: one real thing I wanted help with.
2026–Today
I stay in Chat when I want to think with AI: drafting, asking a quick question, or arguing an idea through. I open Work or Cowork when I want to hand over a bounded job and get a checked file back.
The tools overlap. Chat can read files, and Work and Cowork can hold a conversation. The rule is about how I want to work, and it tells me where to start.
The Loop
Before every repeat client meeting, I had to rebuild the client's history from scattered notes.
I would open the notes from the last call, then the call before that, then search my email for a deadline the client gave me three weeks ago. After five minutes I remembered the project. I still didn't remember what had happened in the relationship. I didn't need more notes. I needed the right ones, before the call.
I gave each client their own folder, and every meeting the same six headings. Granola listened in the background and wrote the summary. Then I connected it to Claude and told it which folder it was allowed to read. The rule that mattered most was the one about what it must not read.
Before the next meeting I asked for the last decision, every unfinished promise and its owner, the concerns the client had raised more than once, and three questions I had to ask. Then I took it into the call.
What the brief missed in the room told me what to ask for next time. A saved follow-up instruction came out of that: separate lists for decisions, my actions, the client's actions and dates — and anything the meeting never settled marked 'not agreed' instead of guessed.
I kept the instructions that worked. When a second client started, the same method worked, because each client's meetings stayed in their own folder.
The first meeting gave me good notes. The second meeting gave me the correct context. After four meetings, the system started to show repeated problems and changes.
The next time, I wasn't starting from zero.
I bring AI an unfinished idea and let it ask questions until the thought becomes clearer.
Brainstorming · Decisions · Research
I create a first version, react to what is actually there and carry the useful visual choices into the next attempt.
Images · Concepts · Creative direction
I explain the outcome, let AI uncover the decisions I haven’t made, test what it builds and keep the parts that should stay consistent.
Pages · Components · Websites
When a process works, I save the context, instructions and checks behind it. A useful conversation can become a reusable skill or workflow.
Notes · Content · Client work · Systems
Claude Code, ChatGPT Work and Cowork can work separately or hand work to each other inside the same project. Shared files carry the decisions forward.
Projects · Context · Skills · AI collaboration
From a brainstorm or image to a website or working system, every turn leaves something useful behind.
Watch one get built
LokeshMy desktop is buried in screenshots. Some matter, some don’t. Can you organize it without losing the useful ones?
AII’ll separate screenshots, documents, PDFs and obvious clutter. Where should new captures go?
LokeshCreate Documents/Screen Captures for screenshots and screen recordings.
AIDone. I also made a simple folder map so this setup can be reused in a new chat.
LokeshGood. But I don’t want to clean the same mess again next month.
AIThen make it maintenance: use the saved map to organize Documents every Sunday.
FILE SYSTEM RESET
Desktop — useful files separated
Screenshots — still saving to Desktop
Folder map — saved for the next chat
Screen Captures — new default
Documents cleanup — every Sunday
That saved version is Build 01, below ↓
Selected Builds
Personal and client work at different scales, each led by what it actually is.
01Personal AI system
A desktop buried in screenshots and loose files. AI organized what was already there, new captures now land in one folder, and a cleanup runs every Sunday.
02Client AI system
A complaint operations view for a client's support teams: SLA compliance, resolution time, and backlog by priority, age and category, with every open ticket traceable to an owner. Shown with prototype data.
03Video system
Built as a program in Claude Design rather than a render: named scenes, a shared design system, colour as a live parameter. The content creator's shorts came out of it, re-cut for YouTube Shorts, Instagram Reels and Facebook Reels.
04Multi-AI experiment
I used different AIs around the same project files — story, design system, motion direction, media and the finished site — without starting over at any handoff.
In their words
A small break
A tiny arcade moment, built the same way as everything else here — one real idea, improved until it worked, then kept. It stays silent and still until you tap it.
Work with me
Support agents, client reporting, lead follow-up, content workflows, websites. Plain-language outcomes on the front; the machinery is one flip away.