Platform
AI Website Builder
Central Only
Central management only
Launch-ready lead capture and builder orchestration module for luperiq.com. It powers the public /get-started experience, stores builder leads in the journal, and gives the central team an admin queue for reviewing incoming preview-site requests.
What it covers
This module belongs on the LuperIQ management server and is not meant to ship on customer or demo sites.
- Public /get-started landing page
- Journal-backed builder lead capture
- Preview slug generation for new requests
- Central admin leads queue
- Builder settings for notifications and expiry
Where AI Website Builder belongs
AI Website Builder sits in the Platform layer of LuperIQ and focuses on Public AI website builder funnel with lead capture and preview launch workflow. For a site owner, the practical value is not the module name by itself; it is whether Public /get-started landing page, Journal-backed builder lead capture, and Preview slug generation for new requests becomes easier to manage in the real customer or admin path.
For pricing and setup, the useful context is Management server only and the place the owner will likely manage it is AI Builder. Those details help the reader understand the module without turning the page into a technical inventory.
Setup checks for AI Website Builder
- Verify that "Public /get-started landing page" is represented in the live setup before treating AI Website Builder as ready for customers or staff.
- Verify that "Journal-backed builder lead capture" is represented in the live setup before treating AI Website Builder as ready for customers or staff.
- Verify that "Preview slug generation for new requests" is represented in the live setup before treating AI Website Builder as ready for customers or staff.
- Verify that "Central admin leads queue" is represented in the live setup before treating AI Website Builder as ready for customers or staff.
- Verify that "Builder settings for notifications and expiry" is represented in the live setup before treating AI Website Builder as ready for customers or staff.
- Open the AI Builder admin section during setup so the owner knows exactly where this module is managed after launch.
Dependencies and AI connections
AI Website Builder works best when Site Blueprint are already understood, because those surrounding tools shape where the data, settings, or customer actions will land.
AI Website Builder is documented as a practical module first. If the owner is evaluating AI help around the same area, the safer next step is to start in the AI Builder admin area and only add AI when there is a real task to run.
Related AI workflows
This module is documented first around the module itself. Public AI workflow pages are focused on the currently fixed-price credit jobs registered in Nexus.
Copyright © 2026 LuperIQ. All rights reserved. LuperIQ, Verified Source, ForgeVec, forge-embed, AI Cortex, and the LuperAI Dictionary are trademarks of LuperIQ.