Skip to content
Open to founders, consulting & leadership roles

I build AI-powered products, automation systems & software businesses.

I’m Lakmal — an engineer who became a founder and AI automation architect. I turn hard engineering problems into products people rely on: browser automation, AI customer operations, and platforms built for outcomes.

Software EngineerProduct BuilderFounderAI Automation Architect
The Journey

A path from engineer to founder.

Tap any milestone to open the full story, challenges, and outcomes.

Things I Built

A wall of products, not a list of repos.

Each of these started as a problem worth solving. Hover to peek at the architecture; click to go deep.

Engineering Toolbox

Not a skills list — a map of what I’ve built.

Every technology here earned its place by shipping something real. Explore the ecosystem to see how the pieces connect across products, platforms, and businesses.

TypeScript
Primary engineering language

The backbone of nearly everything I ship — frontend, backend, agents, and tooling.

Go
Performance-focused backend

High-throughput services, automation platforms, and systems where latency matters.

React & Next.js
Product & frontend

How I turn ideas into fast, polished products people actually want to use.

AI & Automation
Agents & workflows

LLM agents, browser automation, and workflows that delete real human drudgery.

Terraform
Infrastructure as Code

Reproducible infrastructure, ephemeral environments, and GitOps pipelines.

Google Cloud
Cloud architecture

Designing and operating scalable, cost-aware systems — twice GCP-certified.

Product Engineering

Turning ideas into fast, polished products across web and mobile.

TypeScript

My primary language across the entire stack — type-safe products, services, and agents.

Where it shows up
SnappitQA CopilotCRM IntegrationsCochapp

Outcome: Type safety end-to-end keeps fast-moving products refactorable and reliable.

How I Work

A small set of principles, applied relentlessly.

Not a manifesto — an operating system. These are the defaults I return to when the path isn’t obvious.

Build for outcomes

Not features.

A feature shipped is a cost until it changes a number that matters. I start from the outcome — cost saved, time returned, revenue unlocked — and work backwards to the smallest thing that moves it.

Let’s talk

Have a product idea, engineering challenge, or opportunity?

I’m always up for a conversation with founders, teams, and people building ambitious things. Tell me what you’re working on.

This opens your email client, pre-filled. Prefer direct? Email me.