MISSIONBuilding AI workers for real business ops.

About

I'm Otto von Wachter — a full-stack developer, founder, and compulsive builder based in South Florida.

I've been shipping software since before I could explain what an API was to my parents. Over the past few years, I've built 50+ projects — some that made money, some that made sense, and some that did neither but taught me everything.

Right now I'm focused on Hiro AI — building AI workers that businesses can actually hire. Not chatbots. Not copilots. Workers. The kind that show up, do the job, and don't need a motivational poster.

Before that I built SkillBites (127 micro-courses generated with AI), NeuDelta (a marketplace for AI startups), and a tool that analyzed all 5,191 of my ChatGPT conversations to build a psychographic profile of how I think.

I write code mostly in TypeScript/React/Next.js with Python for ML pipelines. I use AI constantly — not as a novelty but as infrastructure. My development style is fast iteration, ugly first drafts, and relentless shipping.

When I'm not building: karaoke, probably.

// operator timeline

  1. 2022

    Built the shipping muscle

    Started treating every idea as a deployable product, not a notes app thought experiment.

  2. 2023

    From prototypes to systems

    Moved from one-off hacks to repeatable product patterns for launch, analytics, and iteration.

  3. 2024

    Distribution and scale

    Shipped SkillBites and NeuDelta while pressure-testing how to get products in front of real users.

  4. Now

    AI workers, not assistants

    Focused on Hiro AI to automate core business operations with AI employees that execute end-to-end.

Current Focus

Building Hiro AI — an AI ops worker platform where businesses hire AI employees for customer support, data entry, scheduling, and reporting. Currently in early access.

// what i believe

AI should own outcomes

Useful AI products are accountable for business results, not just nice interfaces and clever replies.

Shipping beats theorizing

The fastest way to clarity is launching, listening, and iterating with real users and real constraints.

Tools should compound leverage

Every workflow I build should reduce recurring effort so each week gets more strategic than the last.

// tech stack

TypeScriptReactNext.jsNode.jsPythonTailwindPostgreSQLOpenAIVercel