Skip to main content
Moe Htet
ENမြန်မာ
Let’s talk
Moe Htet

MOE HTET / MYANMAR

Separate signals. Working systems.

I connect messages, data, AI, decisions, software, and human actions into systems a business can understand and use.

See selected workTalk about a system

SELECTED WORK

Systems, described with their limits.

The work below is source-backed course demonstration material. It shows the intended system route; it does not claim a production result.

Course demonstration2026
DOCUMENTED

Course project title, description, and image reference

Observed 2026-10-03 · app/n8n-class/page.tsx

AI Messenger Sales Agent

Customer questions, product context, and the next sales step need one understandable route.

01Customer message02Messenger + product context03Reply or request review04Prepare the next sales step05A clearer, reviewable conversation flow
Intended outcome

Make the sales conversation easier to follow and keep sensitive actions reviewable.

No measured business outcome or production execution evidence is published.
View case study
Course demonstration2026
DOCUMENTED

Course project title, description, and image reference

Observed 2026-10-03 · app/n8n-class/page.tsx

Facebook Automated Content Engine

Research, caption, image, and publishing steps become difficult to repeat when their handoffs are unclear.

01Content topic02Research + caption + image steps03Ready to publish or needs review04Prepare the Facebook post05A repeatable content pipeline
Intended outcome

Turn separate content tasks into a repeatable, reviewable flow.

No measured publishing volume, time saving, or production runtime evidence is published.
View case study

WHAT I BUILD

The handoffs matter as much as the tools.

  1. 01 / AUTOMATION

    n8n orchestration

    Connect the systems that already hold the work: APIs, data, messages, and the operational next step.

    ↗
  2. 02 / AI AGENTS

    Context before output

    Give AI a defined role, grounded context, and a visible boundary instead of treating a response as an action.

    ↗
  3. 03 / MESSAGING

    Conversations with a route

    Turn customer messages into an understandable path from request to reviewable reply or handoff.

    ↗
  4. 04 / BUSINESS SOFTWARE

    Operations people can inspect

    Shape the interface around the decisions, handoffs, and records a team needs to operate the system.

    ↗

DECISIONS BEFORE ACTIONS

A system should show where it stops.

A useful automation does not hide uncertainty. Missing data, review, approval, rejection, and the next action should remain visible.

Signal Loom

Sales conversation

Demonstration
Customer
Messenger
Data
Knowledge
Context joined
AIUnderstand the request
DecisionChoose the next step
Human review
Review required
No action taken
Automation
Business software
Action
Reply drafted

A product availability reply is ready for the customer.

Example complete
Design demonstration — not live activity

Routine route: Enough product context is available for a routine reply.

  1. A customer sends a product question through Messenger.

  2. Data and business knowledge join the request as context for AI.

  3. AI interprets the request; Decision chooses the next step.

  4. A routine request proceeds to automation without a sensitive action.

  5. Business software prepares a traceable reply for the customer.

Example ready.

ABOUT

Built around real operational work.

I design AI agents, n8n automation, messaging flows, API integrations, and business software for work that needs to be understandable, reviewable, and maintainable.

More about Moe Htet

CONTACT

Have a process that should be clearer?

Tell me where the work gets stuck, repeated, or hard to verify. We can map the next useful system.

hello@moehtet.info