Order and payment trigger
Stripe checkout creates the website order, customer record, package scope, asset credits, publishing mode, and internal build queue.
Factory architecture
The order-to-live-site engine.
MasterEngine.ai is the automated website factory: payment starts the build, AI generates the site and media, SEO/pSEO gates shape the structure, and deployment plus indexing status are handled by the platform.
Website Factory
Generates brand direction, sitemap, page structure, templates, copy, page modules, metadata, schema, and deployable package output.
Content Factory
Creates images, videos, prompts, social assets, blog/post media, page upgrades, and brand-matched creative customers can buy later.
SEO and pSEO Engine
Builds keyword intent, page clusters, internal links, structured data, canonical policy, sitemap rules, and indexing-ready pages.
QA and review gate
Runs automated quality checks and routes risky builds to admin review before deployment, indexing, or customer-facing publication.
Deploy and Index Engine
Publishes the site, stores deployment records, attaches analytics, updates sitemap/robots, and submits indexing signals when configured.
Customer portal
Lets customers view their site, drafts, assets, extra media purchases, publish status, invoices, and requested updates in one account.
Internal advisory board
A protected board-of-directors layer critiques strategy, margins, quality, compliance, growth, and scale decisions for the company.
Launch path
Every customer order should become a traceable production run.
The site factory needs one durable record for order scope, generation inputs, QA status, assets, deploy target, indexing state, and customer handoff.
- Paid order creates a site build job and customer portal workspace.
- Factory creates a brand brief, sitemap, SEO map, pSEO candidates, and media requirements.
- Content Factory generates copy, images, videos, metadata, schema, and supporting assets.
- Quality gates check content usefulness, duplicate risk, performance, missing metadata, accessibility, and policy exposure.
- Auto-publish jobs deploy immediately after passing QA; review-mode jobs wait for admin approval.
- Deploy records, sitemap URLs, indexing submissions, analytics IDs, and customer notifications are stored for traceability.
Portal commerce
The portal is where customers keep buying value.
The first sale is the website. The recurring opportunity is updates, pages, posts, images, videos, local SEO pages, pSEO expansions, and publishing support.
Buy extra images
Customers can purchase additional brand-matched hero images, product images, page visuals, or ad/social creatives from the portal.
Buy extra videos
Video orders can use the same brand brief, page context, approved prompts, and generation budget controls as the original site.
Finalize drafts
Draft pages and posts can receive AI-generated copy, SEO recommendations, media, schema, and publish-or-review controls.
Internal controls
The board runs the company-side engine.
The 12-member advisory board is private. It should act like an internal board of directors for quality, strategy, risk, capital allocation, growth, and operational discipline.
Compliance and search honesty
The system can make sites index-ready and technically optimized, but it should never promise guaranteed rankings or traffic.
Cost and margin control
Generation cost, media spend, hosting cost, order revenue, retry count, and manual review time need to be visible per site.
Production reliability
The old Python deploy scripts become a governed deploy service with retries, logs, status records, and failure recovery.
Operating standard
The next build step is integration, not another side project.
The standalone deploy scripts, Content Factory service, Stripe billing, Supabase registry, and private review board need to become one pipeline: paid order, generated website, media assets, SEO QA, deploy, indexing, and portal handoff.
- Promote the website factory to the primary product workflow.
- Move deploy scripts behind a production API with status records and retries.
- Connect Content Factory outputs to pages, posts, assets, and customer upsells.
- Keep automatic publishing optional and review-gated publishing available for riskier categories.