Built and runs a $1M+ e-commerce operation. Every system on this site is one he uses himself.
I'm an operator who accidentally became a consultant.
I never planned to build automations for other businesses. I was too busy running my own. But every founder I met asked how I was doing it — so eventually I started answering with a build sheet instead of an email.
I started as a testing engineer.
I spent my first years out of school running structural and thermal tests on aerospace components — the kind of work where you write a test plan, you follow it exactly, and a bad shortcut kills a program. It's where I learned to think in systems, checklists, and repeatable procedures. Turns out most businesses want the same thing; they just don't have anyone writing the plan.
I built an e-commerce business from zero.
I started a direct-to-consumer bathroom vanity brand out of a spare bedroom in LA. No investors, no ad agency, no logistics partner. Just me, a Shopify store, and six supplier catalogs I'd figured out how to reconcile in Excel. In four years it crossed $1M in annual revenue with two people on payroll.
I automated the business out of necessity.
At around $500k I hit the wall every operator hits: I was working 15-hour days doing tasks nobody was going to promote me for. So I started automating — first the supplier feeds, then the freight quotes, then customer service, then reporting. Every automation gave me a day back. Every day back went into the next automation.
Other owners started asking how.
Contractor friends, dentist friends, an attorney across the shul — they all wanted to know what I'd built. I started sending them my own systems. Then rebuilding them for their businesses. Then billing for it. Yaakov.AI is what happens when I finally admit that's what I do now.
The stack.
I don't have a favorite framework. I have a favorite outcome. These are the tools I've shipped to production in real client environments — not the demo-Friday list.
- N8N
Workflow orchestration for anything that touches more than one system.
- MAKE + ZAPIER
For the shorter jobs where n8n is overkill.
- SUPABASE
Postgres + auth + storage. My default backend for anything custom.
- OPENAI · ANTHROPIC · GEMINI
Model per task, not per hype cycle.
- TWILIO
SMS, WhatsApp, and voice for every phone-based automation.
- POSTMARK · RESEND
Transactional email that lands in the inbox.
- SHOPIFY · WOO · BIGCOMMERCE
The e-commerce platforms I've actually shipped to production.
- QUICKBOOKS · XERO
Deep integrations for accounting and bookkeeping automation.
- SALESFORCE · HUBSPOT · MONDAY · CLICKUP
CRMs and PMs I write to daily.
- CALENDLY · CAL.COM
Scheduling APIs for every booking flow.
- CLOUDFLARE WORKERS · VERCEL
Where the automations actually run.
Why I only take four new builds a month.
Every consultant who scales past themselves eventually turns into an agency. The founder disappears from the calls, the work goes to junior contractors, and the client gets someone who's read the SOP instead of the person who wrote it. I've been on the receiving end of that trade too many times to sell it.
Four builds a month is the number where I can actually run the discovery call, write the code, ship the system, and answer the phone the day a customer says something's broken. It's also the number that keeps my own e-commerce business running well, because I'm still the operator there too.
If the calendar is full when you reach out, I'll tell you the honest wait — usually 2 to 4 weeks. If it's not the right fit at all, I'll tell you that on the audit call and point you somewhere better.