Monomyth Comics: the system I built so the side business would run itself.

The problem

Reselling comics profitably is a data problem wearing a hobby’s clothes. You’re sourcing inventory, pricing against a market that moves daily, cataloging at volume, and tracking what actually sells. Done by hand, every step quietly eats the margin and the evening. I wanted the business to run on spare time, which meant the busywork had to go somewhere other than me.

The system I built

So I built the machinery. All of it with AI assistance, Claude as the collaborator, me as the one deciding what to build and why:

• Comic Bundle Finder. A public web app (Next.js, deployed on Vercel) built against the eBay developer API that surfaces underpriced comic lots. Placeholder: a sentence on what it does for other collectors and a link/screenshot.
• Cataloging and pricing. Placeholder: describe the API integrations (eBay, ComicVine, Airtable) and what they automate.
• The data layer. Airtable as the backend, with automations handling the repetitive moves so the human part stays human.

Why it belongs here

I’m not a software engineer, and I won’t pretend the AI-assisted projects would survive a take-home interview without the AI. Here’s the honest claim, and it’s the one that matters for a marketing operations team: I can scope a real problem, design the system that solves it, ship working software against a live API, and fix it when it breaks. A marketer who builds his own tools instead of waiting on a developer is a different kind of generalist. This is the project that proves the “marketing ops” line isn’t a stretch.

Placeholder: outcomes to add once I write them up. What the stack handles unattended, and what the business looks like as a result.