aiOS — the AI employee that runs your business
I founded AI Genesis to answer one question: what does software look like when the interface is a relationship? aiOS is the answer — an agentic AI platform spanning iMessage, web, and voice, designed and coded end-to-end by me, live in production with paying enterprise customers.
The walkthrough in four chapters — RTR's AI employee, the solo build, onboarding cinema, and AI over iMessage.
The challenge
AI tooling in 2024 was powerful and unusable: prompt boxes, settings pages, and workflow builders that assumed the user wanted to learn AI. Business owners don't. They want the work done.
The design thesis behind aiOS: the text box is a fallback, not the front door. The product reads intent, surfaces what matters, and acts — the way a great employee does. That meant designing for iMessage as a first-class surface, building onboarding as a conversation instead of a form, and making every AI action visible enough to trust.
Shipped, not staged
Three production surfaces, one brain.
RTR Vehicles — embedded AI employee
A digital employee on rtrvehicles.com (bottom-right, live now): product discovery, fitment answers, order tracking, and smart escalation trained on the team's real support history. It replaced the workload of four full-time support hires — about $15K/month — while resolving 92% of conversations without a human.
Onboarding as cinema
Signup is a conversation. aiOS reads your website live on screen — scraping your palette, voice, and market position while you watch it think. It's less important what AI can do; it's more important how it makes people feel. Watching the system understand your business builds more trust than any feature list.
iMessage-native AI
Gen — the aiOS commander — lives in your texts. Send a thought; get carousels, videos, websites, and campaigns back as finished deliverables. No app to open, no login, no prompt engineering. The most-used surface of the platform is the one users already had.
Live in production — screenshots from today
No mockups here. These were captured from the live product the day this page was last updated — click any of them and check.
Designer, engineer, founder — same person
Every layer of aiOS is mine: the liquid-glass design system, the React components, the agent architecture, the deployment pipeline. This isn't a designer handing off mockups — the design system and the codebase are the same artifact, which is why the product ships design improvements daily instead of quarterly.
It's also an AI-augmented practice in production: I run a fleet of specialized AI agents that handle everything from financial analysis to video editing, coordinated through shared memory and reviewed by me. The tooling I design for customers is the tooling I run my company on.
What I got wrong along the way
Real products earn their scars. Three that taught me the most:
I over-trusted guardrails.
Early versions wrapped the AI in deterministic middleware for every edge case. It made the product dumber, not safer. The fix was subtraction: one intelligent spine with a strong persona beats fifty patches.
My paywall punished excitement.
The first paywall appeared mid-conversation, right when users were most engaged — and read as a betrayal. Rebuilt it around delivered value: show what's been made for you, then ask.
Onboarding leaked at the top.
Most signups never started the experience. Instrumenting every step revealed the drop wasn't interest — it was friction sequencing. Verification moved up front, everything else became conversational.