Back to blog

The story behind my AI Site Editor

Why I started this project, what I got wrong early, and what finally made it useful.

  • AI
  • Editor
  • Product
  • Founder Notes

Why I Started

I kept seeing the same problem: people wanted to change a website quickly, but the path from idea to implementation was still too technical.

I wanted an editor where someone could describe intent in plain language and still get predictable, structured results.

What I Got Wrong First

My first versions optimized for the “wow” moment. They looked smart in demos but failed in real usage.

Free-form AI output created inconsistent edits, and trust dropped fast when users could not predict what would happen next.

What Changed

I moved from raw generation to structured actions. Instead of asking the model to rewrite everything, I started translating intent into bounded operations.

That shift made the editor feel less magical for five minutes, but far more reliable over weeks.

What I Care About Now

I treat the AI as a collaborator, not the source of truth. Every meaningful change should be inspectable, reversible, and safe to apply.

For me, that is the real bar: not just impressive output, but a product people can trust while building real sites.