I love building products, solving real-world problems, and creating multiple income streams through technology.
Every figure on this page is counted from the projects listed on this site. Revenue is shown as a model — never an amount. See the underlying work.
Products, client work, infrastructure and tools — each one at a different stage, each one shipped or shipping.
SaaS Product
Immigration operations platform running a real visa consultancy — applicant CRM, document checklists, and case-stage tracking in one place.
Client Websites · Freelance
Conversion-focused brand and marketing sites for real businesses — solar, agri-machinery, construction, events and organic retail. 8 shipped so far.
Startup Product
Tech career network that matches student developers to startups on verified skills instead of broadcasting jobs into a feed nobody reads.
Cloud Consulting
Dockerized deploys behind Nginx, automated through GitHub Actions, on AWS and Azure — the delivery pipeline under other people's products.
Portfolio Templates · UI Kits
Executive and personal sites built as reusable templates — the same 3D/motion system this portfolio runs on, adapted per client.
Freelance Project
Intra-college house championship portal — live scores, standings and athlete registration, built for an actual on-campus launch.
Digital Product · Open Source
A deliberately minimal pomodoro timer for deep work. Free, open source, and shipped to GitHub Pages by its own Actions pipeline.
SaaS Product
A production-grade CRM that takes a freelancer from first lead to final payment. Built on an 18-phase roadmap with a gate at every phase.
Startup Product
Real-time drone telemetry for crop spraying — live flight data streamed from the field to operator dashboards over WebSockets.
AI Tools · Automation Services
LLM-backed tooling and automation services — the layer that removes the repetitive half of a workflow rather than replacing the person doing it.
Some of these are delivering today, some are still being built, and one hasn't started. They're labelled honestly.
Multi-tenant products people log into — CRMs and platforms billed per seat, per month.
0
products built
Subscription · Gaining traction
Scoped builds for businesses that need a site or product shipped end to end, not a team hired.
0
client projects delivered
Project fee · Delivering work
Advising on architecture and delivery — what to provision, how to automate it, and what to stop paying for.
0
engagements with infra work
Retainer · Hourly · Delivering work
Conversion-focused marketing and brand sites — the most repeatable thing I build, and the fastest to ship.
0
sites shipped
One-time build · Delivering work
Provisioning and running the infrastructure underneath — VPCs, pipelines, containers, and the monitoring around them.
0
builds with cloud infra
Retainer · Delivering work
Small, self-contained tools built once and given away or sold — no client, no scope creep, no invoicing.
0
tools published
One-time · Free · Gaining traction
LLM integrations and automation layered onto existing workflows — currently experiments, not yet a product.
0
experiments running
Usage-based · Gaining traction
Not started. Listed because it is on the roadmap for 2027, once there is an audience worth recommending anything to.
0
planned for 2027
Commission · Not started yet
Idea to scale, seven stages. Nothing skips a step — the ones that did are the ones that didn't ship.
A problem I've actually hit, or watched someone else lose hours to. If I can't name the person it hurts, it doesn't get built.
What already exists, what it costs, and why people still complain about it. The gap is the brief.
Information architecture before pixels. Every screen gets a job before anything gets styled.
Typed, componentised, and deployed from day one — so 'it works locally' never becomes the release note.
Shipped behind a real domain with CI, health checks and rollback in place. A launch is a pipeline, not an event.
Watch what people actually use, cut what they don't, and let the roadmap follow the behaviour rather than the plan.
Infrastructure that grows without a rewrite — containers, IaC, and boundaries drawn before they're needed.
A snapshot rather than a highlight reel — including the goals that aren't met yet.
The freelancer CRM — lead to invoice in one product. Phase-gated build, currently through the core pipeline and records layer.
Moving past single-host Docker into orchestration, and building the metrics/logs/traces layer that answers why something broke.
Active engagements across solar, agri-machinery, immigration and construction — marketing sites plus the operations platform behind one of them.
Turn one of the two CRMs from a working product into a billed one — pricing, onboarding, and a support loop that doesn't need me awake.
LancerFlow's first public release, followed by the automation layer — LLM-backed tooling for the repetitive half of client work.
Hover or tab through any tool to see how long I've used it and how many builds it's in.
The problem, what I actually shipped, what it cost me in lessons — and a link to the full case study.
Immigration operations platform for a visa consultancy
Production-grade CRM taking freelancers from lead to payment — live as LancerFlow
Tech career networking platform connecting students, professionals, and startups
Each of these came out of a specific build, not a course. The build is named on every card.
Scoping a whole product before styling any of it — deciding what ships in v1 and what is honestly a v2.
Multi-role auth, tenant separation, and the billing-shaped hole you have to leave in the schema from day one.
Wiring LLM APIs into real workflows — prompt design, cost per call, and when a deterministic function is simply better.
Multi-AZ VPCs with isolated tiers, load balancing, and DNS that fails over instead of falling over.
Turning every manual chore into a pipeline step, so releasing stops being an event somebody has to be present for.
Type scales, spacing rhythm, and motion that guides attention — the difference between built and finished.
Static exports, edge hosting, custom domains, and GitHub Pages pipelines that deploy on merge.
Docker, Terraform and GitHub Actions — infrastructure reviewed in a pull request rather than clicked in a console.
Scoping, expectation-setting, and the phase-gate habit that keeps a project from quietly doubling in size.
Positioning, conversion copy and SEO structure — building the thing is only half of getting it used.
Five of these six figures are counted straight from the projects on this site. The one that isn't says so.
0
| 2023 | 2024 | 2025 | 2026 |
|---|---|---|---|
| 2 | 5 | 10 | 16 |
0
| 2023 | 2024 | 2025 | 2026 |
|---|---|---|---|
| 1 | 3 | 8 | 13 |
Reachable on a real domain today
0
| 2023 | 2024 | 2025 | 2026 |
|---|---|---|---|
| 8 | 18 | 30 | 31 |
Distinct tools across every build
0
| 2023 | 2024 | 2025 | 2026 |
|---|---|---|---|
| 1 | 3 | 6 | 7 |
Builds with source open on GitHub
0
| 2023 | 2024 | 2025 | 2026 |
|---|---|---|---|
| 0 | 1 | 3 | 4 |
Streams with delivered work behind them
0+
| 2023 | 2024 | 2025 | 2026 |
|---|---|---|---|
| 300 | 800 | 1600 | 2400 |
Self-reported, outside the 9-5
Counted from the projects listed on this site — nothing is rounded up. Where a figure can't be counted, it is marked self-reported rather than dressed up as data.
A roadmap, not a prediction. The 2026 column is the only one with anything already in motion.
Clients, founders and collaborators — the part of side work that doesn't show up in a repo.
“Mahesh took our idea from a rough sketch to a polished product faster than we thought possible. His attention to detail on the UI is genuinely rare.”
“Mahesh keeps the team unblocked and the architecture clean. Clients specifically ask for him on their projects.”
“Working with Mahesh levelled up my own engineering. His code reviews teach you something new every time.”
“He delivered our cloud migration ahead of schedule and cut our hosting costs. Communication was clear from day one.”
Whether it's a product to launch, a site that has to convert, or infrastructure that keeps falling over — tell me what you're building and I'll tell you what it actually takes.
Or go straight to the inbox — kolim5263@gmail.com
See the full body of work