Understand the operation
Before building anything, I want to understand how the work actually moves from one step to the next.
The trigger, the handoffs, the repeated checks, the messy inputs, and the exceptions all matter.
Background
I started in operations, not software engineering.
I spent years working inside ecommerce operations, especially Amazon.
That meant dealing with the things businesses deal with every day: product research, advertising, inventory, fulfillment, reporting, marketplace issues, spreadsheets, handoffs, and processes that only worked because someone remembered to check them.
Over time, I started noticing the same pattern.
A lot of work was not difficult because it required deep judgment. It was difficult because the same steps had to be repeated again and again.
- 01Download the report.
- 02Compare the records.
- 03Copy the data.
- 04Send the follow-up.
- 05Update the sheet.
- 06Check whether something changed.
- 07Prepare the next report.
Eventually, I stopped only working around those processes and started building systems to handle them.
Today, I work on AI automation, workflow systems, API integrations, AI agents, and operational tools using platforms such as n8n, Make, Google Workspace, OpenAI, Claude, Gemini, Supabase, and code when the workflow needs it.
But the tool is not where I start. I start with the work.
- What actually happens?
- What repeats?
- What can safely be automated?
- What happens when the normal path breaks?
- And where does a person still need to make the decision?
That is the kind of automation I like building.
Not automation for the sake of saying something uses AI.
Systems that make the work easier to run.
How I work
Automate the repetitive parts
Once the process is clear, I automate the parts that do not need someone making the same decision every time.
That can include data collection, routing, report preparation, record creation, analysis, notifications, follow-ups, and system-to-system updates.
Handle the exceptions
The happy path is usually the easy part.
I pay attention to what happens when information is missing, two systems disagree, an API fails, the AI is uncertain, or something needs review.
Keep judgment human
I do not think every decision should be automated.
When approval, business judgment, customer communication, or operational responsibility matters, the system should help the person make the decision instead of pretending the person is unnecessary.
Capabilities
- Automation
- n8n · Make · Zapier · APIs · Webhooks · Google Workspace
- AI
- OpenAI · Claude · Gemini · AI Agents · Structured AI Workflows
- Development
- JavaScript · TypeScript · Next.js · Supabase · PostgreSQL · Internal Tools
- Operations
- Amazon · Ecommerce · Inventory · Advertising · Fulfillment · CRM · Reporting
How I can help
Workflow Automation
Turn repetitive processes into structured workflows using n8n, Make, APIs, webhooks, and business tools.
- Lead intake and routing
- Follow-up workflows
- Reporting
- Data synchronization
- Approval flows
- Inventory monitoring
- Operational alerts
- Document workflows
AI-Assisted Operations
Use AI where it actually adds value inside a workflow.
- Analysis
- Classification
- Structured extraction
- Investigation
- Recommendation generation
- Content preparation
- Multi-agent workflows
AI output does not have to become an automatic decision. Human review can remain part of the system where it belongs.
API and System Integrations
Connect tools that currently require people to move information manually between them.
- Google Workspace
- CRMs
- Ecommerce platforms
- Logistics systems
- Advertising reports
- Databases
- Messaging platforms
- Internal tools
Internal Tools
Build focused tools for work that has outgrown spreadsheets or manual templates.
- Quotation builders
- Review queues
- Internal dashboards
- Operations utilities
- Approval interfaces
- Reporting tools
Workflow Review
Sometimes the first useful step is mapping the current workflow and identifying what is worth automating before building anything.
What I am looking for
I am most interested in work where automation is tied to a real business process.
That could mean joining a team as an AI Automation or Systems Specialist, helping improve an existing operation, or building a focused workflow for a business that is still doing too much manually.
If there is a process you think could run better, I would be interested in hearing about it.
Resume
My background combines ecommerce operations, Amazon account management, advertising, marketplace operations, and AI automation.
I have worked with real operational workflows involving inventory, fulfillment, PPC, reporting, product research, lead management, and marketplace systems, then gradually moved deeper into automation and systems building.