Overview / Flows
How it all fits together

From "hello" to a
live app on your domain

This is the whole system in motion: an expert signs up, IQ learns who they are, they ask for something, the agent builds it, the platform previews it, and one approval ships it live to cliniciq.com. Every box below is implemented.

The macro flow

Four stages, one continuous path

1 · Onboard
expert → offer → knowledge
2 · Build
IQ generates the app
3 · Preview
live, editable, verified
4 · Deploy
live on cliniciq.com

Stage 1

Onboarding — IQ learns the expert

Before anything is built, the platform builds a model of the expert: who they are, what they sell, and what they know. This is what makes the generated outputs actually good.

  1. Session & dossierExpert starts a session; IQ captures their background, story, and positioning into a structured dossier.
  2. Offer stackThe agent generates the business offer and pricing tiers — editable, section by section.
  3. Context profile & avatarsICP and market positioning are modeled; FAL generates a portrait per avatar.
  4. Knowledge baseFiles, URLs, and pasted text are extracted, embedded, and indexed — with a manual review checkpoint.
  5. QA checkpoint → handoffAn LLM validation pass; the expert approves; a default workspace is created and the engines are selected.

Stage 2 & 3

Build & preview — the agent does the work

The expert asks IQ for something — "build me a treatment cost estimator." IQ picks the right tools, spins up a sandbox, writes the app, and returns one clean preview URL.

Prompt
"Build me a cost estimator landing page"
IQ decides
mode: buildtool: build_appgrounded in knowledge base
Sandbox
create microVMwrite filesrun dev serververify port
Preview
slug.sandbox.cliniciq.com → returned to chat
Workspace panel
Preview tab shows it liveedits hot-reload, same URL

Stage 4

Publish & deploy — one approval, live

When the expert is happy, publish freezes the build into an immutable release and deploy promotes it to a stable production URL on cliniciq.com. Production never changes until they republish.

Approve preview
expert clicks publish
Release
immutable artifact + env manifest
Deploy
slug.cliniciq.com · TLS auto
Rollback ready
re-point to prior release

The data plane, in parallel

When an app needs a database

For full-stack apps, the same flow provisions managed data and wires it in automatically — proven in the end-to-end test on the Infrastructure page.

Provision DB
managed Postgres
Issue credentials
verified DATABASE_URL
Wire at boot
sandbox + deployment
Same DB, prod
read/write live

The point of all this

Once you have the env and we're on Zoom, you can run this whole loop yourselves — prompt IQ, generate as many landing pages and apps as you want, and watch them go live. Then we tune the outputs together until they're exactly right. That's the next-steps plan →