AI automation consulting · Zyntopia

I build automations that save your team hours every week.

Working systems that live in Slack, WhatsApp, email, and your CRM — built against your actual workflow, then handed over for you to own.

How I work

01

Scope it

We look at your actual workflow and find the one bottleneck worth automating first. No audit theatre — a real decision about what pays off.

02

Build it

I build the system against an agreed scope. Usually n8n, APIs, and a well-placed agent. You see it working as it comes together.

03

Ship it

It goes live in your tools, your team starts getting time back, and I hand over something you actually own — not a subscription to me.

The way I prefer to work

Finished systems are the point. Sometimes the right first step is a 90-minute map of where automation pays off. But the destination is always something working — not a 40-slide report on what could be automated someday.

No custom software unless it's the right answer. Most of the time, wiring up the right tools does the job. If you genuinely need more, I'll tell you.

I work solo and stay close. The person who scopes it builds it. You're not handed off to a junior after the first call.

Three things I build most often

These aren't a service menu — they're the shapes the work usually takes. Most engagements end up a mix.

SLACKEMAILDOCSWHATSAPP

A team assistant that lives where your team already works

Slack, WhatsApp, email. It answers questions from your internal docs, summarises the day, and stops the constant "where's the file?" messages. Your team leads stop being a help desk.

LEADCRMFOLLOW-UPLOG

Automation pipelines that move data so humans don't

A lead comes in, lands in the CRM, triggers a follow-up, and logs itself. Reports that took two days build themselves. Data that lived in silos finally talks to the rest of your stack.

INCOMINGAGENTANSWERHUMAN

Customer-facing agents that deflect the questions you shouldn't be answering

FAQs, order status, routing — on the channels your customers actually use, 24/7. Your people handle the conversations that need a human, not the ones that don't.

What I've actually built

Anonymised — the work is real, the names aren't. Each one shipped and used.

Corporate slide generator

time returned
n8nLLMSlides API

What it was: A team was spending hours every week assembling the same status deck.

What I built: A system that pulls the underlying data, assembles the slides, and leaves only the human judgment to humans.

What it did: The weekly deck that used to eat an afternoon now builds itself.

[Preview]

Influencer vetting agent

funnel narrowed
AgentRAGLLM

What it was: A marketing team was manually reviewing hundreds of creator profiles.

What I built: An agent that reads each profile, scores it against the team's criteria, and produces a shortlist with reasoning.

What it did: The team reviews the shortlist, not the pile — and the pile was the bottleneck.

[Preview]

Company knowledgebase assistant

interruptions cut
AgentRAGSlack

What it was: The same questions landing in Slack every single day.

What I built: An assistant that answers from internal documentation, with sources, directly in the channels people already use.

What it did: Repetitive questions get answered instantly. The team gets their focus back.

[Preview]

Something on your workflow look familiar?

Let's talk about it →

Not sure where to start?

I also do short strategy engagements — a working session to map where automation will actually pay off in your business, and just as importantly, what to leave alone.

It's the same 15-minute call as a build conversation; if it turns into a scope, it turns into a scope. If it doesn't, you leave with a map.

Book a call
[Photo]

A few words about me

I'm Hashan. I've spent the last few years building AI agents and automation systems in production — the kind that actually get used every day, not demos that look good in a pitch.

I started Zyntopia as a solo practice because I kept seeing the same gap: teams losing real hours every week to work a system could handle. I'd rather ship one automation that does the job than talk about transformation.

I build in the open. Most of what I make lives on my GitHub. If you want to know whether I can actually do this, that's the honest place to look.

See my GitHub ↗

Questions I get asked

What's eating your team's time?

Tell me. Book a call and we'll look at your actual workflow together. If there's something worth automating, we'll see it in fifteen minutes.

30 minutes. No prep, no deck, no obligation.

Prefer email? hashanwickramasinghe@gmail.com