What MiniApps are

MiniApps are small hosted tools you build by describing them to Kai. A booking flow, a client portal, a calculator, an intake form, a private gallery, a progress tracker. Things an enterprise version of the same business already has, and a solo professional never did, because the gap between "no app" and "hire a developer" was unbridgeable.

Code is the substrate. You never see it. You describe what you need. Kai builds and deploys it on your workspace, on your domain, wired to your already-connected calendar, payments, email, and clients.

Page builders make pages. MiniApps run workflows.

A Squarespace page says "here is my business." A MiniApp says "here is a working client experience for my business." The difference is whether your client can do something, submit, book, pay, view their data, see their status, or just read.

One workspace, one source of truth.

Your clients, calendar, payments, content, emails, and MiniApps live in the same workspace. The data is shared by default, not glued together with Zapier. Your intake form writes to the same Business contact your invoice reads from.

You iterate by talking.

"Add a question about budget to the intake form". Kai changes the app in a minute. On any other platform that's a feature request, a Zapier rebuild, or a developer ticket. The cost of changing the app drops to near-zero, which means you will actually keep improving it.

The pattern that repeats across personas: a workflow that exceeds what Calendly + forms can express, but never justified hiring a developer.

• Photographer. Client galleries with proofing, tier-priced session bookers, wedding shot-list intakes.
• Coach. Per-client portals with session notes and goal trackers, scored intake quizzes, weekly auto-check-ins.
• Lawyer / accountant. Matter intake with case-type routing, secure document collection portals, flat-fee service storefronts.
• Fitness trainer. Personalized workout-of-the-day apps, progress trackers with photos.
• Consultant. ROI calculators, audit questionnaires, proposal generators, client dashboards.
• Real estate agent. Buyer preference quizzes, mortgage calculators, property comparison tools.

See Use cases by persona for full examples.

The end-to-end flow, in plain language:

• 1. You describe what you want. "Build me a booking portal for my photography clients."
• 2. Kai uses your business context. Brand, services, pricing, availability, existing documents, current clients.
• 3. Kai picks a starting template. One of the prebuilt MiniApp templates. See Templates.
• 4. Kai customizes the code in a sandbox. You watch the changes pile up as a draft PR.
• 5. You preview it. The app runs in your runtime under a preview URL.
• 6. You ask for changes in plain language. Kai edits and redeploys.
• 7. You publish on your domain. Tell Kai the hostname (e.g. book.menoru.com). If the domain isn't connected yet, Kai walks you through the DNS records, verifies the certificate, and tells you when HTTPS is live. See Add a domain.
• 8. You iterate. "Add a premium package option". Done in a minute.

MiniApps aren't sandboxed pages. They're first-class citizens of your workspace. Via the MiniApp SDK, your app can:

• Read and write its own data (namespaced Mongo collection per app).
• See who the visitor is (your team or your client, with auth-checked identity).
• Send email from your domain.
• Store and serve files (private or public).
• Hold per-company secrets (Stripe keys, third-party tokens) without exposing them in code.
• Call Kai from inside the app. Draft a quote, generate a follow-up email, summarize a submission.

The contract is small and stable. See MiniApp SDK.

That's bigger than landing pages. Landing pages help you market yourself. MiniApps help you run, sell, and deliver your services.