Automating work that teams need to go faster.
I help organizations automate internal knowledge, security-sensitive, and content workflows using AI, software, and workflow systems.
The work is about designing practical systems that reduce operational friction, remove repetitive tasks, and make complex workflows easier to run.
Based in Bangkok · Working with clients worldwide
Operational automation
A consulting and systems-building practice focused on three operational areas.
Internal knowledge systems: company access, retrieval, assistants, internal workflows
Secure local AI: privacy, on-premise inference, private documents, controlled deployments
Content operations: editing, publishing, asset pipelines, media workflows
Describe the workflow
Share the bottleneck or repetitive process you want to fix.
Operational domains
Three ways I help organizations remove friction from daily work
- Company knowledge access
- Internal knowledge assistants
- Document-based answers
- Workflow integration
- Local AI deployments
- Private document workflows
- On-premise inference
- Security-first AI systems
- Content pipelines
- Automated editing
- Publishing workflows
- Media infrastructure
How I work
Most organizations do not have a technology problem.
They have a workflow problem.
My work focuses on identifying bottlenecks, repetitive tasks, and operational friction, then designing systems that eliminate them.
The goal is not more software. The goal is better operations.
Systems designed for real operating constraints
- Cloud systems when speed and flexibility matter most.
- Local-first and on-premise deployments when privacy, compliance, or data control require a different approach.
- Integrations built around the tools teams already use, not abstract demos disconnected from operations.
Process
A practical path from manual work to reliable systems
Projects in practice
Examples of operational automation across customer, knowledge, and content workflows
Problem
Teams were losing time hunting through documents, internal notes, and scattered tools to find the information they needed.
Approach
Centralize company knowledge, structure access around real internal workflows, and make answers available in natural language.
System
An internal knowledge assistant grounded in company documents, policies, and operating context, with search and retrieval built for day-to-day team use.
Outcome
Faster access to internal knowledge, fewer repeated questions, and less time wasted switching between tools and documents.
Problem
Some organizations need AI capabilities, but cannot send sensitive data, internal records, or operational context to external AI providers.
Approach
Design local-first AI systems that keep the workflow useful while keeping data under the company's control.
System
Secure local AI infrastructure for on-premise inference, private document handling, and internal workflows built for security-conscious teams.
Outcome
Organizations can use AI in real operations without compromising privacy, compliance requirements, or control over sensitive information.
Problem
Content teams lose time to repetitive editing, publishing coordination, and manual asset handling across channels.
Approach
Treat content production as an operational system rather than a sequence of one-off creative tasks.
System
Automated content pipelines for generation, editing, rendering, asset management, and scheduled publishing across media workflows.
Outcome
More consistent output, less manual coordination, and infrastructure that scales content operations without scaling admin overhead.
Tell me what's manual today
If a customer workflow, internal knowledge process, or content operation is creating friction, send it over. I'll reply within 24 hours with whether it's a fit and what a sensible next step looks like.