About
Marketer first, builder by necessity
I spent years running Amazon advertising and e-commerce marketing: budgets, launches, retail media, client reporting. The tools I needed didn't exist, so I built them. Building them turned out to be the part I'm best at, and it's the job I want.
Everything on this site started as a deliverable someone was doing by hand: a weekly client report, a listing that broke overnight and nobody noticed, a campaign build that ate an afternoon in spreadsheets. I sit with the person doing the work, map how it flows, and replace the mechanical parts with a system.
The design question I care most about is where the human checkpoint goes. Steps whose output can be verified mechanically (a diff, a count, a schema check) run on their own. Steps where a wrong answer lands on a client get a person. Each case study says where I drew that line and why.
Working fluency
- Agents
- Claude Code as a daily driver: custom slash commands, skills, subagents, and MCP servers (Apple Reminders/Calendar, Google Docs, Intentwise, custom). Multi-step agent loops with tool definitions, structured outputs, and validation gates.
- Code
- Python (pandas, openpyxl, API clients) and TypeScript/Node (SQLite, Slack Block Kit, schedulers). Tests where correctness matters; CLIs with docs where teammates take over.
- Marketing
- Amazon retail media end to end: Sponsored Products, budgets and TACOS targets, bulk sheets, Keepa/market data, listing operations, client reporting. Plus the surrounding stack: Asana, Slack, Box, Shopify, Zapier.
- Enablement
- SOPs and automation standards the team adopted as its defaults. Every tool ships with a quickstart and a cheatsheet, because a tool only I can run isn't finished.
Contact
github.com/michael13parker · linkedin.com/in/mparker1060 · @michaelbparker_ · Chicago, IL