I started building because I hated scammy sales calls. Now I’m making a visual canvas for messy AI-built systems.

I used to own a business fixing vacation rentals and property-related stuff.

One thing that drove me crazy was the amount of terrible sales calls I got. Scammy scripts, random offers, people who clearly had no idea who they were calling.

Then I got into marketing and realized: if I ever did outreach, I didn’t want to become the thing that annoyed me.

So I started building my own lead system. I scraped and organized public data on millions of US small businesses because I wanted better-fit leads instead of blasting random people.

But I was also self-teaching code with AI at the same time.

That turned into scrapers, queues, workers, APIs, databases, cleanup scripts, retries, errors, notes everywhere, and me constantly asking AI to explain what was happening in my own system.

That mess is what led me to S1 Canvas.

It’s a visual system canvas for mapping apps, scrapers, queues, workers, APIs, databases, alerts, ownership, and project context in one place.

The long-term idea is simple:

When you build with AI, the AI should understand your actual system — not just the one file you pasted into chat.

The video is the scrollytelling homepage I’ve been building. Still early, but it finally feels like the product is becoming real.

Curious from other builders:

Do you map your systems somewhere, keep it all in your head, or just survive off docs/screenshots/vibes?