AI Automation Consultant & Builder · Thailand / APAC
CRM and workflow automation for sales and marketing teams.
I map, build, and hand over focused automations for lead intake, CRM updates, routing, approvals, campaign preparation, reporting, and internal requests. The work connects the tools your team already uses and gives operators a clear way to run and maintain the process.
Choose the right starting scope
The final scope is agreed after reviewing the workflow, connected systems, and access constraints.
Workflow assessment
For a team that knows where work is slow but needs a clear automation plan.
You receive
- Current-state workflow map
- Prioritised opportunities, dependencies, and risks
- Recommended first scope and estimate inputs
- What I need from your team
- A process owner, workflow walkthrough, sample records, tool list, and business rules.
- Outside this scope
- Production build, paid tool setup, and ongoing operation.
One working flow pilot
For one recurring process with a clear trigger, output, and owner.
You receive
- One configured workflow
- Agreed integrations, rules, and approval path
- Test results and handover notes
- What I need from your team
- System access, sample data, field rules, test users, and timely review.
- Outside this scope
- Additional workflows, major data cleanup, custom platform development, and ongoing operation.
Connected sales or marketing process
For a process spanning several steps, teams, or systems.
You receive
- Connected workflows for the agreed process
- CRM or campaign-tool integration
- Monitoring, exception handling, documentation, and handover
- What I need from your team
- A named process owner, API or admin access, data definitions, approval owners, test cases, and stakeholder availability.
- Outside this scope
- Work outside the agreed process, licence fees, unsupported vendor changes, historical data migration, and ongoing managed service unless scoped separately.
How the quote is prepared
The quote is based on the number of connected tools, API and permission readiness, data and business-rule complexity, approval paths, exception handling, test environments, and handover needs. Platform subscriptions, API usage, model usage, and other recurring vendor fees are listed separately from implementation work.
Handover and support
Handover includes the agreed documentation, ownership and access notes, test cases, and operating guidance. Post-launch fixes, monitoring, changes, and ongoing support are defined in the proposal so the owner and scope are clear.
See how the work fits together.
Two systems built in an in-house role: the problem, my contribution, and the decisions behind the build.
In-house project
Marketing Automation Engine
A shared campaign operating system turns one structured brief into channel-ready work while marketers retain control of audience, localisation, and every live send.
Read the case study
In-house project
B2B Sales Platform
One controlled flow connects prospect sourcing, CRM deduplication, enrichment, human-approved outreach, reply handling, and contract handoff across multiple APAC markets.
Read the case studyA clear path from current workflow to handover
We agree what the workflow should do, who approves key actions, how it will be tested, and who will own it after launch.
Map the current workflow
Review the trigger, data, tools, rules, approvals, delays, and common exceptions.
Agree the first scope
Define the output, included systems, responsibilities, acceptance checks, and exclusions.
Build and test
Configure the workflow and test expected cases, missing information, duplicates, permissions, approvals, and failures.
Run a team pilot
The people who do the work try agreed cases and identify changes needed before wider use.
Hand over
Deliver operating notes, ownership and access details, test cases, and guidance for common problems.
Frequently asked questions
What kind of AI automation project is a good starting point?
Start with a recurring task that has a clear trigger, repeated steps, a known output, and an owner who can test it. Lead routing, CRM updates, research preparation, structured content operations, internal requests, and reporting alerts are common starting points.
Do you only build with n8n?
No. n8n is often a strong orchestration layer because it is flexible and understandable, but I also work with APIs, CRM automation, Slack, Google Workspace, databases, lightweight interfaces, and the tools already used by the team.
Can you integrate with an existing CRM and workflow?
Yes. Most projects connect to an existing process rather than replace everything. I first check API access, permissions, data quality, duplicate rules, ownership, and failure handling so the automation does not create a second source of truth.
How are price and delivery estimated?
I estimate after defining the systems, access, rules, approvals, exception cases, testing, and handover. Recurring platform and usage fees are shown separately from implementation work.
Will our team be able to maintain it?
Handover is part of the project. I document the flow, important credentials or ownership boundaries, common failures, and safe areas to change. Where appropriate, I also add operational alerts and a lightweight interface so users do not need to read workflow logs.
Can you work with teams in Thailand and across APAC?
Yes. I am based in Bangkok and have built operating systems used across Thailand, Malaysia, Hong Kong, the Philippines, Taiwan, and Singapore. Project communication and documentation can be in Thai or English.