Web Studio Business Tools

An AI OS hosted site is a working business system, not a brochure: the platform provides the capture, wiring, and reporting, and every site offers its owner a management dashboard. Contact forms feed a real CRM and a per-site lead inbox, a Funnel site type wires purchase buttons to your Stripe checkout, dynamic pages turn one template into a page per city or product, and every site carries its own Site Manager dashboard. This page documents the four business tools; the build pipeline itself (sections, templates, guided briefs) is covered in the platform overview.

Lead capture → CRM

Contact sections on platform-hosted sites render a real lead form (name, email, message) instead of a bare email link. Submissions are plain HTML form posts — no JavaScript required on the visitor's side, so even script-blocking visitors convert — protected by a strict rate limit and a hidden honeypot field that silently absorbs bot submissions.

Each submission lands in two places:

• The operator's CRM — a contact (source site-lead) plus an activity carrying the message, the site, and the page it came from
• The site's own lead inbox — on the Manage tab, visible to the site's owner (including managed clients), with a mailto link per lead

Sites exported off-platform keep a graceful email-link fallback, and a per-site setting can disable the form entirely. After submitting, visitors return to the page with a confirmation message — no redirect to a foreign domain, ever.

Sales funnels

Choose the Funnel site type and paste your checkout URL (a Stripe Payment Link or any https checkout). The generated funnel has a fixed three-page shape, and the platform wires the links deterministically — this is never left to the AI:

1. / — the landing page: core promise, proof (testimonials or stats), and a call to action leading to the offer
2. /offer — the decision page: pricing or a strong offer presentation plus an objection-handling FAQ; every purchase button (including individual pricing-tier buttons) points at your checkout link
3. /thanks — the post-purchase confirmation with next steps; created automatically if the plan omitted it. Set your payment link's success URL here

The wiring re-applies on every rebuild, so later content edits cannot break the purchase path. The platform points buttons at your checkout — it never handles the payment itself.

Dynamic pages

One template page plus a dataset produces N static pages at build time — the classic local-business play of a service page per suburb, or a page per menu item, per product, per practice area.

1. In the editor's content tab, pick a template page and a path prefix (pages land at /prefix/slug)
2. Paste rows as simple CSV — a header line that includes a slug column, then one row per page
3. Any {{column}} placeholder in the template's text is substituted per row; apply and rebuild

Generated pages join the sitemap, llms.txt, structured data (including per-page FAQPage markup when the template has a FAQ section), and the site's knowledge bundle automatically. Hand-written pages win path collisions, slugs are sanitized, and generation is capped at 200 pages per site.

Site Manager

Every site's editor has a Manage tab — the per-site business dashboard:

• Overview cards — status, domain, 30-day pageviews, AI-crawler hits, AI-referred visits, and lead count
• Lead inbox — everyone who submitted the contact form, newest first, with message previews and mailto links
• Quick actions — view the live site, download a ZIP export, jump to the content editor, open full analytics, or run an SEO/AEO audit

There is deliberately no separate backend per generated site: sites stay static (fast, minimal attack surface) while management lives in the platform dashboard behind one authenticated login. For managed clients everything on this tab is scoped server-side to the sites they own.

API Endpoints

Frequently asked questions