0 of 4
The AI OS Architect

Your whole business.
One screen. Start here.

5 questions · ~90 seconds · Free

Stop renting your business one app at a time.

Answer five questions about how you run your business. This page turns your answers into the exact instructions that get AI to design — and then build — the first piece of your own AI OS: your business, on one screen, built around you.

You'll need
A Claude account (claude.ai — free to create). It works best with Claude Pro, but start with what you have. Your answers below save on this device only — nothing is sent anywhere.

1Who are you?

2Where are you in the business?

3What runs your business today?

4What do you go hunting for every week?

The three questions you keep having to dig through apps, emails, and spreadsheets to answer. These become the heart of your one screen.

5What would you do with the time back?

One more question

How do you want to build it?

Two ways up the mountain. Both free. Both yours. Pick your level.

Not sure? Start Rookie — you can come back and go Rockstar any time. It's the same business, just built deeper.

Rockstar · Step 1 of 4 · Your modules

Here's what your OS will do.

Pre-picked from your answers · turn off anything you don't need

Your modules

Each module you keep adds its data and its dashboard panels to your build spec. Toggle freely — your PRD updates to match.

Happy with your modules? Get your build spec.
Rookie · Step 1 of 3 · The 90-second payoff

Get your One-Screen Blueprint.

~5 min · Copy, paste, and watch

iWhat this does

The prompt below is already personalized with your answers. Paste it into Claude and it designs your one screen: what's on it, where each number lives today, and what it replaces you hunting for. Yours — not a template, not the average of everyone.

Stay in one conversation. Steps 1 and 2 happen in the same Claude chat, so it remembers your blueprint when it's time to build.

1Open Claude and paste this

Go to claude.ai (or the Claude app), start a new chat, and paste:

Prompt · personalized for you You are my AI OS Architect. I'm a real estate professional, and I'm done hunting through apps for answers about my own business. I want to see my whole business on one screen. About me: - Name: [AGENT_NAME][TEAM_LINE] - Market: [MARKET] - Stage: [STAGE] · People in the business: [TEAM_SIZE] - My CRM: [CRM] - Transactions & signing: [TC_TOOL] - Other tools I pay for or rely on: [OTHER_TOOLS] The questions I go hunting to answer every single week: [HUNT_LIST] Why I'm doing this: [WHY] Design my One-Screen Blueprint. Don't build anything yet — show me the design here in chat first: 1. Name it "[OS_NAME]" and lay out my screen as panels. 2. For every panel: what it shows me at a glance, which of my tools that information lives in today, and how often it should update. Each of my weekly hunting questions above must be answered by a panel instantly — no digging, no logins, no hunting. 3. Add up to 3 panels I didn't think to ask for, based on what someone at my stage in my market usually needs. Mark those as your suggestions. 4. Keep it to ONE screen. If something doesn't fit, cut the least important panel and tell me why. 5. Mark every panel either MANUAL (I paste fresh numbers in weekly — fine for version one) or CONNECTABLE (this could flow in automatically from my tools one day). 6. Plain language only. I'm not technical and I don't want to be. No jargon, no code talk. Then ask me a maximum of 3 sharpening questions, ONE at a time, and update the blueprint as I answer. When I say "build it," we build version one.

If a line still shows [brackets], go back and fill in that answer — the prompt updates automatically.

2Shape it

Claude will ask you up to three quick questions. Answer honestly — this is where the blueprint stops being generic and becomes yours. When the layout looks like a screen you'd actually open every morning, you're ready to build.

+Not sure what a "panel" should be?

Think of the five things you'd want to see before your first coffee: this month's closings and volume, leads that need attention today, every pending deal and its next deadline, this week's appointments, and money in the pipeline. If a panel wouldn't change what you do today, it doesn't earn a spot on the screen.

Step 2 of 3 · The build

Build version one.

~10 min · Same chat

iWhat this does

Same conversation — now you say "build it." Claude creates a working version of your one screen right in front of you: every panel from your blueprint, laid out, styled, ready for your real numbers. This is the moment it stops being an idea.

1Paste this in the same chat

Prompt · same conversation Build it. Create version one of "[OS_NAME]" as an interactive page I can open every morning: 1. Follow my blueprint exactly. My weekly hunting questions get the biggest, most prominent panels — top of the screen. 2. Make it feel like MY brand, not a template. My brand colors: [BRAND_COLORS]. Headings font: [BRAND_FONTS]. [LOGO_LINE] Dark header with "[OS_NAME]" and "[MARKET]". Easy to read on my phone AND my desktop. 3. Fill every panel with realistic example numbers for a business like mine, each clearly labeled SAMPLE, so I can see exactly what it will look like alive. 4. Give me a dead-simple way to put my real numbers in: an "update my numbers" section where I type or paste this week's real figures and every panel updates. No code, no jargon, no settings. 5. At the bottom, add a small honest note: which panels I update by hand each week (MANUAL), and which ones could someday pull from [CRM] and my other tools automatically (CONNECTABLE). 6. Make my saved numbers survive anywhere: use Claude's artifact storage when it's available, and automatically fall back to the browser's own storage if I download this page and open it on my computer. My numbers should never silently disappear. When it's built, walk me through updating ONE panel with my real numbers so I've done it once with you. Then tell me how to get back to this page tomorrow morning.

2Put one real number in

Don't skip this. The moment one panel shows your real number instead of a sample, this stops being a demo and starts being your OS. That's the whole point of today.

Version one is the view, and that's by design. You'll update it by hand each week — that takes about five minutes and it already beats hunting through five apps. Making the data flow in automatically is the next level (Step 3 tells you how far that goes).
Step 3 of 3 · Make it yours

Own it. Grow it.

~5 min now · 5 min every Monday

1Make it your Monday habit

  • Bookmark the chat. Your OS lives in that conversation — pin it or favorite it so it's one tap away.
  • Every Monday, 5 minutes: open it, put in the week's real numbers, look at one screen instead of five apps.
  • Change it whenever you want. It's yours. Tell Claude: "add a panel for my open houses," "make the leads panel bigger," "track my listing appointments this quarter." No permission needed, no support ticket, no upgrade fee. That's the difference between owning and renting.

2Let Claude do some of the hunting for you

Even version one doesn't have to be all manual. In Claude's settings you can connect Gmail and your calendar — then, before you update your screen, ask Claude to pull what's already in your inbox: new leads that emailed in, this week's appointments, deadlines hiding in transaction emails.

+How to connect Gmail or Outlook
  1. In Claude: Settings → Connectors.
  2. Find Gmail (or Outlook) → Connect and sign in.
  3. Claude only reads — it won't send or delete anything.
  4. Then try: "Check my email for anything that should change my one screen this week."
Ready to go Rockstar?

You built the view. The next level is the engine.

Right now, you feed your screen. At the next level, your screen feeds you — your CRM, your transactions, your leads flowing in automatically, updated before you wake up. That's the Rockstar path: same five answers, but you get a complete build spec to drop into Lovable or Claude Code and build the real, connected app. Also free.

Done

You own the first piece.

One screen · Yours · Built in an afternoon

Remember this feeling.

An hour ago, "build your own software" sounded like something other people do. Now your business is on one screen that you own, that you can change any time, that nobody can raise the rent on. Scale means less now. You just proved it.

Three things this week:

  1. Monday: real numbers in, five minutes. The habit is the win.
  2. One improvement: ask Claude to add or sharpen one panel.
  3. Show one person. The look on their face will tell you what you just did.
Rockstar · Step 2 of 4 · The build spec

Get your build spec.

~5 min · Claude writes your full PRD

iWhat this does

The prompt below is already personalized with your answers. Paste it into Claude and it writes a complete PRD — a product spec for your entire OS: every panel, your data model, how it connects to your tools, the tech stack, and the exact build order. Detailed enough to paste straight into Lovable or hand to Claude Code.

This is the real thing. Not a mockup — the actual spec builders use. Yours, personalized, free.

1Open Claude and paste this

Go to claude.ai, start a new chat, and paste:

PRD prompt · personalized for you You are my senior product architect and full-stack engineer. I'm a real estate professional and I'm building my own AI OS — my whole business on one screen, connected to the tools I already use, replacing the fragmented stack I rent today. Write me a complete, professional PRD (Product Requirements Document) I can hand to Claude Code to build, or paste into Lovable. Match the depth of a real engineering spec. About me: - Name: [AGENT_NAME][TEAM_LINE] - Market: [MARKET] - Stage: [STAGE] · People in the business: [TEAM_SIZE] - My CRM: [CRM] - Transactions & signing: [TC_TOOL] - Other tools I rely on: [OTHER_TOOLS] - Brand colors: [BRAND_COLORS] · Fonts: [BRAND_FONTS] · [LOGO_LINE] The questions I go hunting to answer every single week: [HUNT_LIST] Why I'm doing this: [WHY] FIRST, scale the whole PRD to my stage and team size: if I'm solo, keep it lean (skip roles, TCs, commission splits); if I'm a team, include role-based access and coordinator workflows. Ask me up to 3 clarifying questions before you write it if it would materially change the spec — otherwise use sensible real-estate defaults and note where I'd customize. Then write the PRD with these sections (plain language where you can — I'm an operator, not an engineer, but I'm going all in): 1. EXECUTIVE SUMMARY — name it "[OS_NAME]", one-line purpose, and a "What This Replaces" table mapping my current tools ([CRM], [TC_TOOL], [OTHER_TOOLS]) to what the OS does instead. 2. TECH STACK — recommend ONE with rationale: (a) Lovable, fastest no-code path, or (b) Next.js + Supabase (Postgres, Auth, Storage) + Vercel + my tools' APIs, for full control. List the integrations I'll need. 3. DATA MODEL — the core tables with key fields and relationships: contacts/clients (reusable, deduped by CRM id), properties (reusable), transactions/deals, listings, tasks, appointments, agents (if team), vendors, documents. Note computed fields. 4. THE ONE-SCREEN DASHBOARD — every panel, what it shows at a glance, which of my weekly questions it answers instantly, its data source, and refresh cadence. If I'm a team, define the dashboard per role (admin, agent, coordinator). 5. TASK & DEADLINE ENGINE — task templates per transaction type that auto-generate tasks anchored to key dates (contract, inspection, appraisal, financing, closing), with a cascade so moving one date shifts everything downstream. This is the heart of real-estate ops. 6. MILESTONE TRACKER + CLIENT PORTAL — a status tracker (Under Contract → Inspection → Appraisal → Financing → Clear to Close → Closing → Sold) and an optional client-facing "pizza tracker" page with plain-language updates. 7. INTEGRATIONS — for [CRM] and [TC_TOOL]: auth method, whether they support webhooks or need polling, what data flows in automatically vs. stays manual in v1. 8. NOTIFICATIONS — task due/overdue, milestone updates, new deal — over email and SMS; consolidated, not spammy. 9. BUILD PHASES — the exact sequence, starting with a Phase 1 MVP that's the one screen answering my #1 weekly question, so I have something usable on day one. 10. DEPLOYMENT — hosting, cron jobs for polling/reminders, the environment variables I'll need, and my custom domain. 11. BRAND — apply my colors, fonts, and logo throughout. 12. At the very end, write a single ready-to-paste Lovable prompt that summarizes the whole build in one block, so I can start the no-code route immediately if I choose. Make it detailed enough that Claude Code could start building from Phase 1 today, or I could paste your Lovable prompt in right now and get a real, working first version.

If a line still shows [brackets], go back and fill in that answer.

Rockstar · Step 3 of 4 · The build

Build the real thing.

Pick your route · ~30–60 min to a working app

ARoute A — Lovable (fastest)

Best if you want a real app without touching code.

  1. Go to lovable.dev and start a new project.
  2. Paste the ready-to-paste Lovable prompt from the end of your PRD.
  3. Let it build. Then refine by chatting: "make the leads panel bigger," "add my brand colors," "connect my CRM."
  4. Publish. You get a live URL — your OS, running on the web.

BRoute B — Claude Code + Vercel + database (full control)

Best if you (or someone on your team) want to own every line and connect deep into your tools.

  1. Open Claude Code in a new project folder.
  2. Give it your full PRD and say: "Build this. Next.js + Supabase. Start with the MVP build order."
  3. Deploy the front end to Vercel, the database on Supabase — both have free tiers to start.
  4. Connect your CRM's API so your data flows in automatically.
Not technical? Route A is for you. Lovable gets you 90% of the way with zero code. Come back to Route B when you want more.
Rockstar · Step 4 of 4 · Make it real

Connect it. Own it.

This is the engine the Rookie build only hinted at

1Connect your tools — the data flows in

This is what makes it a real OS instead of a dashboard you update by hand. Point it at your tools' APIs and your screen fills itself — before you wake up.

  • Your CRM — leads, contacts, pipeline stages, activity.
  • Your transaction platform — deals, deadlines, statuses.
  • Gmail / calendar — appointments and anything hiding in your inbox.
Ask your builder to do it. In Lovable or Claude Code: "Connect my CRM's API and pull leads and deals into the dashboard automatically." That one sentence is the difference between a view and an engine.

2Put it on your own domain

Publish it to a web address you own — os.yourbrand.com. Lovable and Vercel both let you connect a custom domain in a few clicks. Now it's not a chat, not a rental — it's your software, at your address.

Done — Rockstar

You built the real thing.

Your OS · connected · on your own domain

You own the engine now.

Not a rented app. Not fifteen logins. One system, built around you, running on its own — and nobody can raise the rent on it, sunset it, or sell it to a company that wrecks it. That's what owning looks like.

Keep going:

  1. Add one integration a week. Each one takes more off your plate.
  2. Bring your team in. Give each agent their own view.
  3. Show one person what you built. Then watch them ask you how.