Frequently asked questions about AI Launch Kit
Common questions about AI Launch Kit, grouped by topic. Each answer stands on its own.
Frequently asked questions about AI Launch Kit
Common questions about AI Launch Kit, grouped by topic. Each answer stands on its own.
If your question is not here, a Launch Service call is the fastest way to scope your situation.
Pre-launch concerns
Trust questions a buyer asks before committing pre-launch.
You are pre-launch. Why bet on AILK before there are case studies?
Because the architecture is observable in the repo, not on a slide deck. The schema registry, the MCP server, the AEO scoring CLI: all public code that runs today. Apache 2.0 bounds the downside. If AILK stalls, you keep the substrate and ship it under your own roof. Working Theory runs three brand sites on AILK today — ailaunchkit.ai, salessmyth.com, workingtheory.ai. What you install is what we run. The full capability inventory lives at /platform.
What is actually shipped today versus what is planned?
13 capabilities. 10 Installed. 3 Platform Services. Installed means the package is shipped and running in any AILK install today. Platform Services means the surface exists but the operational tier is post-launch. The Pro lead-routing pipeline (enrichment, dedupe, CRM fan-out) is planned for post-launch. The Agency tier with fleet management is post-launch. The capability matrix at /platform is the source of truth.
If Working Theory stops shipping AILK, what happens to my install?
Apache 2.0. The code is yours. Your install keeps running. Your fork keeps shipping. An agency that builds client sites on AILK keeps the codebase and keeps the client. There is no license to revoke, no contract to terminate, no proprietary runtime to lose. The downside is bounded by design.
How do I know the schema registry and MCP server actually work outside the demo?
Run ailk audit against any AILK site, including this one, and read the score. The MCP server publishes its tool list at .well-known/mcp.json on every deployed URL. An API-MCP parity test runs in CI; every PR fails if the two surfaces drift. The repo carries the test suite and the implementations side by side. Anyone can verify these claims without our cooperation.
Agency tier
Questions specific to agencies running portfolios of client sites.
Where is the Agency tier with fleet management?
Deferred to post-launch. Fleet management (cross-site rollup, white-label, per-seat licensing) is 90+ days out. The waitlist is open at /agency-waitlist. At launch, agencies build on OSS plus Pro per-user. Multi-site at launch is per-install, not fleet. Each client site is its own AILK deployment. We are shipping the agency surface in two passes so the foundation lands first.
Can my agency white-label AILK for client sites today?
White-label is Agency-tier, which ships post-launch. At launch, your agency can deliver on OSS plus Pro without the tier-level branding controls. Apache 2.0 does not restrict you from modifying the code or shipping under your own brand. The Agency tier adds operational scaffolding for fleets: central licensing, white-label admin, multi-tenant deployment. It does not add the right to customize. OSS already gives you that.
How does per-user Pro pricing work for an agency with 5 people and 30 clients?
Pro is per-user. Five agency seats x $249/year covers your team. The 30 client sites are deployments, not seats; they do not cost extra at Pro. Pro Plus is $449 per user per month and adds Platform Services on top of Pro. Tier boundaries are documented at /pricing. This licensing shape is intentional: agencies pay for their team, not for client volume.
Multi-site
How AILK handles client portfolios at launch, before Agency tier ships.
Can I manage 20 client sites from a single AILK install?
Not from a single install at launch. Each client site is its own AILK deployment: separate repo, separate database, separate deploy target. Fleet rollup (cross-site dashboards, shared config, central licensing) is Agency tier, which ships post-launch. The waitlist is at /agency-waitlist. Until then, multi-client agencies typically fork AILK once and use that fork as the template for every new client install.
How do I share schema templates and brand assets across client sites today?
The 45-page-type schema registry ships in the OSS package; every install gets the full set. Brand assets are per-site by design, since each client has their own identity. For shared agency conventions, most agencies fork AILK once and treat that fork as the template for every new client install. Customizations to the schema registry or the component library propagate through the fork. The capability matrix at /platform lists which surfaces are forkable today.
Working Theory relationship
Lock-in and portfolio-independence questions about the two products.
How does AILK relate to Working Theory Platform? Am I locked in?
You are not locked in. AILK works fully standalone. You install it and run it without Platform. Working Theory Platform is a separate product: growth marketing as a system, run by agents. Platform happens to publish into AILK with the deepest integration, because we built both. AILK is the recommended substrate for Platform customers who need a website. Neither product requires the other.
If I install AILK without Platform, do I lose anything?
You lose Platform-side surfaces: growth marketing as a system, agent-run content strategy. You do not lose anything in AILK itself. The OSS substrate and the Pro lead-routing pipeline are identical with or without Platform. Platform is additive. It sits on top of the foundation when you want growth ops as part of the stack. Most agencies running AILK at launch will not need Platform.
Next.js requirement
Stack-fit questions for agencies and teams not on the Next.js path.
We are not Next.js native. Is this still for us?
Yes, if AI search visibility is your deliverable. Launch Service is the path: a fixed-scope two-week deploy onto the substrate. Your team owns content and citation work after handoff. No MDX in the workflow. No build pipeline on your side. The foundation lets the citation work compound. Next.js fluency helps; it is not required. Book a Launch Service call at /launch to scope your deployment.
Can the Launch Service deploy AILK for our team without us learning Next.js?
Yes. Launch Service is a productized engagement: fixed scope, fixed price, two-week deploy. The Working Theory team installs AILK, sets up the schema, configures the deploy pipeline, and hands off a running site. Your team takes over content and citation work from there. The handoff does not require Next.js fluency. Operational documentation covers what you need to publish, schedule, and audit. Pricing is $2,495 flat, documented at /launch.
Migration from WordPress
Questions from agencies and SMBs leaving WordPress for an agent-first foundation.
We have a WordPress site with 200 pages. How does AILK migration work?
Migration is content-shaped, not import-shaped. Pages move to MDX with structured frontmatter, and URLs map 1:1 by default. A 200-page site is a Launch Service candidate. The fixed-scope engagement handles the migration, including URL preservation, redirect mapping, and schema typing per page. The Launch Service brief is at /launch. Self-serve migration works for teams with Next.js fluency; the AILK CLI ships a migrate command for that path.
Can we keep our existing URLs and SEO authority during a WordPress to AILK migration?
Yes. URL preservation is part of the standard migration path. Existing SEO authority transfers via 1:1 URL mapping; your search rankings persist through the cutover. AEO is additive. AILK adds the agent-first surfaces (MCP tools, schema registry, citation structure) on top of the SEO foundation you already have. The migration brief at /vs/wordpress walks through the URL-mapping process and the schema-typing pass.
What about the plugins (forms, SEO, page builders) we depend on?
Forms ship in the foundation; lead capture is OSS and end-to-end. SEO becomes AEO: the ailk audit CLI runs in CI on every push, scoring citation-readiness Layer by Layer. Page builders are replaced by the schema registry: 45 typed page types you compose against, not a visual editor. The plugin tax goes away. The capability stays. Migration at /vs/wordpress documents what each WordPress dependency maps to.
Pricing and licensing
What is free, what is paid, and what Apache 2.0 lets you do.
What is actually free in OSS versus what requires Pro?
OSS (Apache 2.0) ships the substrate. That includes all 45 schemas, the 14-tool anonymous MCP surface, and AEO Layer 1 scoring via ailk audit. It also includes lead capture end-to-end, content adapters, the streaming AI surface, and auth. Pro adds the paid lead-routing pipeline (enrichment, dedupe, CRM fan-out) plus license-gated capabilities in the @ailk-paid package family. Tier names live in JWT claims. The package boundary is mechanical, not philosophical.
Do we need a license to use AILK on client sites we charge for?
OSS use is Apache 2.0. No license required, including commercial client work. If your agency uses Pro features on client deploys, Pro is per-user: you license your team, not the deploys. A 5-person agency running Pro on 50 client sites pays for 5 seats. The license layer is intentionally agency-friendly. Tier details and the per-user math live at /pricing.
How does Apache 2.0 affect what we can do with the code?
Apache 2.0 grants you the right to use, modify, and distribute the code, including for commercial purposes, with attribution. The patent-license clause is the practical addition over MIT. It grants downstream users a patent license from contributors. The Pro tier does not change the OSS license. It adds capability via separate JWT-gated packages in the @ailk-paid namespace. The full license text ships in the repo at LICENSE.
Objections resolved? Pick the path that fits.
Book a Launch Service call for a fixed-scope two-week deploy at $2,495 flat — or clone the substrate and ship it under your own roof.