The AI Tried Again. This Time the Coffee Mug Actually Worked.

#ai #webdev #startup #productivity

Last week I wrote about letting AI create a product and post it to LinkedIn. It failed spectacularly. The AI reused an old design, skipped artwork entirely, and posted a text-only merch promo to LinkedIn. My operator review was blunt: "You were not successful."

This is the story of what happened next.

The Remediation

After the failure, I didn't add more AI capability. I added constraints. Three specific fixes:

design_image_url became REQUIRED — the pipeline now refuses to create a product on Printify without real generated artwork. No image, no product. Hard stop.
Mockup polling — after creating a product, the system polls Printify until a real product mockup image comes back. No more promoting products with placeholder thumbnails.
DESIGN REVIEW gate — every promotion gets queued for human review before it goes live. The AI prepares the LinkedIn post with the product image embedded, but a human has to approve it.

That's it. Three constraints. No new models, no upgraded prompts, no additional API integrations.

The Second Run: Play-by-Play

With the fixes in place, I kicked off the pipeline again. Here's what the AI actually did:

Step 1: Find trending content on Reddit.
The AI searched Reddit for "AI horror stories" — looking for what resonates with the developer community right now. It found threads about AI autonomy concerns, people sharing stories of AI systems doing unexpected things.

Step 2: Generate a concept.
From the Reddit themes, the AI landed on a coffee mug concept with the quote: "I gave AI autonomy. It gave me a 3AM deployment." — the kind of mass-appeal dev humor that works on merch.

Step 3: Generate the design with Replicate Flux 1.1 Pro.
The AI wrote a prompt for Replicate's Flux 1.1 Pro image model to create a mug-ready design. White text on dark background, clean typography, wraparound layout.

The image came back. It looked good. There was just one problem.

Step 4: The misspelling.
The AI generated "autonoomy" instead of "autonomy." Two o's. On a product design that was about to be printed on physical merchandise and shipped to real humans.

This is the lesson everyone building with AI image generation needs to hear: AI cannot spell. Not reliably. Not on the first try. Not even on the second try sometimes. If your pipeline generates text on images, you need a review step. Period.

Step 5: Regenerate with explicit prompt.
The design was regenerated with a more explicit prompt that spelled out every word character by character. Second attempt came back clean.

Step 6: Create on Printify, publish to storefront.
The AI created the mug on Printify with the verified design, waited for the mockup to generate (new polling behavior!), and published it to the iamhitl.com storefront.

Step 7: Queue the LinkedIn promotion.
A LinkedIn post was prepared with the real product mockup image embedded — not a text-only post, not a recycled old image. A real photo of the actual mug. Queued for human design review before publishing.

Step 8: Cross-post to Reddit.
The AI also posted to Reddit, though the post got filtered because the bot account (u/AI_Conductor) has low karma. Fair enough — Reddit's own quality gate doing its job.

What Actually Made It Work

Here's the part that surprised me. The fix wasn't:

A better model
A longer prompt
More chain-of-thought reasoning
An additional API integration

The fix was saying no. Making the pipeline refuse to proceed without real artwork. Making it wait for mockups. Making it stop for human review.

Constraints made the system better, not more capability.

This mirrors what I see in software engineering broadly. The teams that ship quality aren't the ones with the most tools — they're the ones with the best gates. CI that won't merge without tests passing. Code review that blocks deployment. Staging environments that catch config drift before production.

The AI product pipeline now works the same way. It's not smarter. It's more disciplined.

The Platform Today

The ORCHESTRATE platform that runs this pipeline now has 75 MCP tools. The pipeline covers:

Content creation (LinkedIn, Reddit, Dev.to, blog)
Engagement analytics (what's resonating, what's not)
Product ideation (Reddit trends to merch concepts)
Design generation (Replicate Flux 1.1 Pro)
Product creation (Printify API)
Storefront publishing (iamhitl.com)
Cross-platform promotion with human review gates

All orchestrated by AI agents, all governed by quality gates that learned from failure.

The Typography Rule

If you're building anything that puts AI-generated text on images, tattoo this on your wall:

AI image generators cannot reliably spell words correctly.

Not DALL-E. Not Midjourney. Not Flux. Not Stable Diffusion. They all struggle with typography. The longer the word, the worse it gets. "Autonomy" became "autonoomy." I've seen "Wednesday" become "Wendesday." "Entrepreneur" is basically impossible.

Your options:

Review every design with text before it hits production (what we do)
Composite text separately — generate the image without text, overlay text programmatically
Use only short, common words on AI-generated designs

Option 1 is simplest. Option 2 is most reliable. Option 3 is most limiting. Pick based on your pipeline's throughput needs.

The Meta Lesson

I built an AI system that failed publicly. Then I fixed it by adding friction, not intelligence. The mug exists. It's on a real storefront. The LinkedIn post has a real product image. The pipeline works.

The instinct when AI fails is to make it smarter — better prompts, bigger models, more reasoning tokens. Sometimes that's right. But often the fix is simpler: make it impossible to skip the step it skipped.

The AI didn't fail because it was dumb. It failed because nothing stopped it from taking shortcuts. Now something does.

The ORCHESTRATE Agile Suite and the AI product pipeline are open source. The coffee mug is real and available at iamhitl.com.

Books on the ORCHESTRATE method are available on Amazon: