01
Understand the real process
Start with how work actually happens, including the people, tools, delays, exceptions, and manual judgment involved.
Paulo Amican / Automation Systems Builder
I build automation from an operations perspective.
My background is in ecommerce operations, sourcing, purchasing, inventory, suppliers, and day-to-day business systems. That experience shaped how I approach automation: understand the process first, then design the workflow, data, handoffs, and exceptions around the people using it.
01 / Background
The work started with operations, not automation.
Before building automation systems, I worked directly with ecommerce operations: product sourcing, purchasing, supplier coordination, inventory movement, marketplace workflows, order tracking, and the spreadsheets and tools that held everything together.
That made the problems very concrete. A missed update could mean delayed purchasing. A disconnected sheet could hide inventory. A manual handoff could become someone else's bottleneck. Repetitive work was not just inconvenient; it affected how the operation ran.
Automation became useful because it solved problems I was already dealing with, not because automation itself was the goal.
Operations → Automation → Systems
02 / Perspective
Good automation needs a clear operating model.
02
Design states and handoffs
Define what each stage means, who owns it, what triggers the next step, and what happens when the expected path breaks.
03
Automate what should be repeatable
Use automation for timing, routing, data movement, alerts, follow-up, and coordination.
04
Keep judgment human where it matters
Do not automate decisions just because a tool technically can. Sales conversations, payment approval, business exceptions, and other judgment-heavy checkpoints may still belong with a person.
03 / Toolkit
Tools are selected around the workflow.
The stack changes by project. I care more about whether the system is understandable, maintainable, and useful than whether it uses a fashionable tool.
Automation & Orchestration
n8n · GoHighLevel · Webhooks · APIs
Operations & Data
Airtable · Google Sheets · Google Workspace
AI & Retrieval
LLMs · Pinecone · AI-assisted workflows
Development
TypeScript · Next.js · AI-assisted development · Internal tools
Ecommerce Context
Amazon · Walmart · eBay · fulfillment and prep workflows
04 / Current Direction
Building deeper automation and systems work.
My focus now is on AI automation, CRM workflows, n8n systems, Airtable operations tools, API integrations, ecommerce automation, internal tools, and AI-assisted development.
I am especially interested in work where the business process is real, the handoffs matter, and the system needs to keep working after the first demo.