Money leaks through process gaps
Unfiled claims, missed reimbursements, unbilled work, late penalties. Nobody owns it because it is tedious.
An agent reads every document and drafts the claim. Your team approves.
I build production AI agents for operations teams, on Claude, ChatGPT, Gemini or whichever model fits the job: voice, WhatsApp, email, creative, video and ads. Every figure traces back to its source, and anything that sends, spends or files waits for a human yes.
30 minutes with Prasad. You leave with a build plan, whether or not we work together.
agent ›
Sample run: /laytime-claims --batch q3-voyages. Read 214 documents: statements of facts, NORs, charter parties. Laytime computed for 37 voyages. 6 demurrage claims drafted, every figure cites page and line. Review gate: 6 claims waiting for ops approval.
Sample run: agent whatsapp-concierge --live. 128 conversations today, 11 handed to a person. Product cards pulled live from Shopify. Answers grounded in the brand knowledge base. Complaint detected, routed to support with the full thread.
Sample run: /ads-optimiser --accounts meta,google --window 7d. 42 ad sets scanned, 5 fatigued creatives flagged. Proposed: move 18% of budget from prospecting to retargeting. 12 new hooks drafted from last month’s winners. Review gate: budget change waits for your approval.
Sample run: brandops make "why RPA breaks on PDFs". Script written in the founder’s voice. Voice, avatar, b-roll and captions assembled. One approval screen before render. 1080×1920 reel rendered, captions burned in.
The problem
If two of these sound like your week, the work is ready for agents. Not a chatbot bolted on top: agents inside the process, with your team approving what matters.
Unfiled claims, missed reimbursements, unbilled work, late penalties. Nobody owns it because it is tedious.
An agent reads every document and drafts the claim. Your team approves.
Every 2x in orders or tickets means hiring again, training again, and managing again.
Agents absorb the volume. People handle the exceptions.
Bots handle clean fields. They fail on PDFs, emails and judgment calls.
The agent reads the messy inputs RPA could not, and flags what it is unsure of.
Leadership will not trust output it cannot trace. Fair.
Every figure links to the page and line it came from.
Your in-house team could build it. Just not this year.
I ship it, then hand your team the code, the skills and the runbook.
When the ops lead goes on leave, the process stops.
Their judgment becomes a written skill the agent follows every time.
What I build
Each one is a set of written skills, a model, your systems as tools, and a review gate. Pick the one closest to your problem; most builds combine two or three.
Answers and places calls in a natural voice. Qualifies leads, confirms orders, books appointments and chases payments.
Guardrail. Hands the call to a person the moment it hears frustration or a question outside its brief.
A concierge on WhatsApp, SMS and web chat that knows your catalogue and your policies.
Guardrail. Answers only from your knowledge base. Says “let me get someone” instead of guessing.
Triages the shared inbox and drafts replies your team only has to approve.
Guardrail. Nothing sends until a person approves, until you decide a category is safe to automate.
On-brand statics, carousels and banners from a one-line brief.
Guardrail. Never invents people, products or claims. Real-photo slots go on a shot list.
One prompt to a finished reel: script, voiceover, avatar, b-roll and captions.
Guardrail. Every word on screen is a word that is spoken. No invented statistics.
Angles, hooks, scripts and variants for Meta and Google, built from what already wins.
Guardrail. A category compliance check runs before a creative reaches your review.
Watches your Meta and Google campaigns around the clock and proposes the next move.
Guardrail. Spend changes wait for your approval. Caps and one-click rollback are built in.
Turns PDFs, scans and email attachments into structured data and drafted claims.
Guardrail. Low-confidence fields are flagged for a person, never guessed.
Work
Client names are withheld. Every card says what stage it is at: live, building, or scoped. Two of these run our own business, because we use the method before we sell it.
The brand wanted shoppers answered on WhatsApp and the website at any hour, without a support hire.
What it provesA commerce agent that answers, recommends and sells around the clock, running on the client’s own infrastructure.
Orders arrived across channels and were re-keyed into the store by hand.
What it provesAgents writing into a live commerce system, not just reading from it.
Founder-led B2B teams need warm conversations, not spray-and-pray sequences.
What it provesWe run agents on ourselves first. The grounding checks exist because we caught the failure.
Running SEO and delivery for many clients without the work living in one person’s head.
What it provesThe same method we sell, used every day on our own revenue.
Publish video every week without a shoot, an editor or a studio.
What it provesAn AI video pipeline with a human gate, built and used by the person selling it.
Claims go unfiled because computing laytime from vessel paperwork is slow and tedious.
What it provesEnterprise-grade claims automation, designed for a GCC team that answers to audit.
An agency running a portfolio of client ad accounts wanted creative and reporting to scale without hiring.
What it provesCreative, media buying and reporting designed as one loop with approvals.
Receipts, not vibes
Click any highlighted figure. Every number an agent writes carries a pointer to the document, page and line it came from, so a reviewer checks it in seconds instead of redoing the work.
Sample output · demurrage claim, voyage 31
The vessel tendered notice of readiness at 06:10 on 14 August1. Laytime commenced six hours after NOR2. Discharge completed at 18:40 on 22 August3. Allowed laytime was 4 days 12 hours4. Demurrage due: 2 days 3 h 50 m at $18,000 per day, $38,8755.

The person behind the agents
Prasad Iyer co-founded TechDevs and leads its AI practice. He works with AI agents every day, has built more than 40 MCP servers for businesses and has written more than a hundred skills: tested, reusable playbooks that turn a judgment call into something an agent does the same way every time.
Before TechDevs took all his time, he spent two and a half years as an applications developer at Oracle, on machine learning projects top banks used for model governance. That is where the habits come from: every figure traceable, every release approved. The SEO audits, site builds, proposals, outreach and video TechDevs delivers come out of systems he built and still runs.
A slice of the 100+ skills and subagents in the working library.
How a build runs
I shadow the people doing the work and write down every judgment call they make.
Each judgment becomes a skill with examples and edge cases. Your ops lead signs it off.
Agents run on the skills. Anything that sends, spends or files waits in a review queue.
We run last month’s real inputs side by side with your team and measure accuracy before go-live.
Code, prompts, skills and runbooks are yours. A retainer keeps it running and improving.
Business ideas
Pick your industry. Each idea is a real pattern I would scope on a first call, with the agents it needs.
Calls every cash-on-delivery order before dispatch and holds the ones the customer will not accept.
Answers sizing, stock and shipping questions and sells from the live catalogue.
Spots fatigue in your ads and ships new on-brand variants before ROAS slides.
Calls every portal lead, qualifies budget and location, and books the site visit.
Sends the brochure, floor plans and payment plan, then answers the questions.
Turns photos and a floor plan into a walkthrough reel for every unit.
Books, reminds and reschedules on calls and WhatsApp so the front desk stops chasing.
Pulls the right documents from the record and assembles the pre-authorisation pack.
Answers only from clinician-approved content and escalates anything clinical.
Reads the voyage paperwork, computes what is owed and drafts the claim with citations.
Answers “where is my shipment” by email and WhatsApp from your tracking feeds.
Matches supplier invoices to POs and receipts and queues only the mismatches.
Finds prospects showing intent and drafts outreach that cites only verified facts.
Turns discovery-call notes into a priced, on-brand proposal for review.
Pulls the numbers, writes the narrative and drafts the monthly report.
Clears the routine invoices and hands people only the real exceptions, with reasons.
Finds duplicates, missing tax IDs and stale bank details, and proposes fixes.
Turns the SOP binder into an assistant that cites the clause it answers from.
Reads incoming RFQs, checks specs against your catalogue and drafts the quote.
Dealers order in a chat; the agent writes the order into your ERP.
Takes the breakdown call, captures the fault and books the right engineer.
Calls and messages every enquiry, answers fee and course questions, books the counselling slot.
Turns lessons into short videos for Instagram and YouTube every week.
Polite, persistent reminders by call and WhatsApp, logged against each student.
Fit check
I take a small number of builds at a time, so I would rather tell you now if this is early for you.
0 of 5 true
The skills and ebooks in the resources library are a better place to start.
Browse resourcesWays to work together
30 minutes on one workflow. You leave with a build plan and a fixed price, in writing.
Book it →One workflow, real volume, measured accuracy. Fixed scope, fixed price, review gates included.
Talk scope →Hosting, monitoring, new skills and fixes on a monthly retainer, three-month minimum.
Ask about retainers →Skills, agents and ebooks from my own library, ready to install in Claude, ChatGPT, Gemini or your own agents.
Browse resources →Resources · AI skills and agents
A basic prompt gets you a draft. These skills get you the deliverable: the steps, scripts and quality checks Prasad wrote while doing the same work for paying clients, packaged so Claude, ChatGPT, Gemini or any agent you use follows them every time.
Skills, agents and ebooks.
Install the same playbooks I use on client work, singly or as bundles.
FAQ
It is built not to. Agents answer from your documents and data, every figure carries a citation back to its source, and fields the model is unsure of are flagged for a person instead of guessed. On our own outbound agent, grounding checks block any message that states a fact about a prospect the research did not find.
In your own cloud account if you want it there, with compute and model costs billed to you directly. You own the code, prompts, skills and runbooks.
No. I pick the model per step: Claude for long documents, careful reasoning and tool use, ChatGPT or Gemini where they do a step better or cheaper, and small models for narrow, high-volume work. Skills and MCP servers are model-agnostic, so you are never locked to one vendor.
Pilots are fixed scope and fixed price, followed by a monthly retainer to run and improve them. The number depends on volume and the systems involved, and you get it in writing after the first call.
I design and review every build. A team I hired and trained maintains and extends it, and every agent ships with a runbook so the process never depends on one person, including me.
Yes. Many teams want the first agent built fast and then owned internally. I pair with your engineers, ship in your repository and leave the skills documented.
Yes. The skills, agents and ebooks in the resources library are the same playbooks I use on client work, packaged so you can install them yourself.