Automate.
AI & workflow automation
If someone does it forty times a month, software should be doing it.
- n8n & custom API pipelines
- AI agents that draft, sort & summarise
- RAG over your own documents
000%
Frames 000 / 170
Built for businesses,
teams & founders.
Automation engineer.
Shipping to production.
04
Apps live on Google Play
03
SaaS products & systems shipped
04
Service lines, one point of contact
965+
Followers on LinkedIn, X & YouTube
(01) — About
Developer and AI automation engineer. I build the systems, apps and automations small teams run their day on, and I stay on after launch.
01
Problem first
What's costing you time or money comes before any tech.
02
Plain answers
What I'm building, why, and the price, before I start.
03
One owner
Scoping to support, one person accountable.
04
Built in public
My work is on LinkedIn and YouTube. Check it first.
(02) — What I do
AI & workflow automation
If someone does it forty times a month, software should be doing it.
Business systems + websites
One system instead of twelve spreadsheets, and a website that brings in the enquiries.
Android apps, idea to Google Play
Four of my own apps are live. I know exactly where launches break.
(03) — Selected work
Real clients, real users, running in production today. Each one started as a problem somebody was tired of.
In production01 · AI chatbot platform
An AI widget that learns your website and answers visitors instantly, with sources.
My role: Solo developer. A complete platform end to end: auth, billing, RAG pipeline, and a widget ready to drop onto any site. Shapes how I scope AI chatbot work for clients now.
Live02 · Client website
A live client website, used every day, that I built and still maintain.
My role: Designer, developer & maintainer. Parents and staff use it every day. I still maintain it: updates, fixes, and uptime.
Live03 · Course hosting SaaS
Headless course hosting infrastructure, built so creators own their platform.
My role: Solo developer. Live, full-stack SaaS shipped solo from idea to production. Shipping was never the bottleneck, distribution was, and that lesson now shapes how I plan every launch.
(04) — My own apps
Built, published and maintained by me, from the first commit to store review and every update after it.

Fully offline reader with an on-device journal and a tap-to-define dictionary.

A whole content platform brought into one app, with text-to-speech, highlights and bookmarks.

Tamil-language calendar app on Firebase, with announcements pushed from the cloud.

Gamified learning app with XP, streaks and a simulated stock market, all offline.
(05) — The stack
30 tools on three rings. Hover or tap a bubble to see what I use it for.
Everything I build with, in one system.
(07) — Before you ask
Price, timelines, ownership, and whether I can handle real work. Asked often, answered plainly.
I price on the work involved and the value it delivers to your business, not by the hour, so there's no rate card. An automation that saves your team ten hours a week is worth more to you than one that saves ten minutes, and a full operations system is a bigger job than a single workflow. Tell me the problem and I'll come back with the scope, what it's worth to you, and a clear price before you commit to anything.
Most automations ship in one to three weeks. Websites usually take two to four weeks. Full systems and Android apps take longer, typically six to twelve weeks depending on how much data has to be moved over. You get the timeline in writing before work starts, and you can watch progress as it happens.
A client website that families and staff use every day, an operations system I co-developed that runs a client's daily operations, four Android apps live on Google Play, plus an AI chatbot platform and a course-hosting SaaS I built solo end to end. Judge me on what's actually shipped.
Yes. Once the project is paid for, the source code, the accounts, and the data are all yours. Everything comes with documentation, and nothing is locked to a platform only I can access.
You get a handover session and written documentation so your team can run things day to day. If a bug turns out to be in my work, I fix it for free. Ongoing maintenance and new features are available, but optional. You never need a retainer just to keep your own system running.
Usually, yes, and it's often the cheaper option. Automations can often sit on top of the tools you already pay for. I'll tell you honestly when connecting what you have beats rebuilding, even when a rebuild would mean more work for me.
Yes. I work remotely with clients anywhere. Most of it happens over WhatsApp and email, with video calls when they're useful.
Book a call or send one message describing the problem. No forms, no two-week wait for a slot. I'll reply with how I'd approach it and whether I'm the right person for the job.
(08) — Your move
Or write to shalomarputhasinghbe@gmail.com. I usually reply the same day.