AI Launch Kit — Frequently Asked Questions
Straight answers, no marketing spin — pre-launch risk, fleet management, Working Theory, Next.js, WordPress migration, licensing. What ships today. What's still ahead.
Pre-launch concerns
You're pre-launch. Why bet on this?
The architecture is observable in the repo, not a pitch deck. The typed schema registry is a directory of 60 entries, the parity test runs in CI, and the audit CLI runs today. You're not taking our word for any of it.
Is the architecture real, or just a pitch?
It's real and checkable. `apps/web`, `apps/mcp`, and `apps/api` run as peer apps in one repo, with a CI-enforced parity test and a live `.well-known/mcp.json` endpoint. Clone the repo and verify it yourself — the `ailk audit` CLI runs against any AILK site, including this one.
What happens if AILK doesn't find traction?
You keep everything. AILK ships under Apache 2.0, so the codebase belongs to you regardless of what happens to the company behind it. No lock-in, no dependency on a vendor's survival — the license itself bounds the downside.
Do you have customer proof yet?
Not yet from outside the founding team, and we're not pretending otherwise. Sam Henry, Working Theory, and SalesSmyth all publish on AILK today — that's real dogfooding, not a case study. Independent customer proof builds over the next 90–180 days as Launch Service and Pro customers come on.
Fleet management
We run a portfolio of client sites. Where's fleet management?
Deferred. Fleet management, cross-site rollup, white-label, and per-seat licensing are planned as a future Enterprise multi-tenant entitlement, not a separate tier. At launch, agencies deliver on OSS plus Pro, managed per-site rather than as a fleet.
When will Fleet Management ship?
No fixed date. It lands in that same post-launch window, and the exact timing depends on demand for the entitlement. It ships once the core substrate is proven at single-site scale first.
Multi-site management
How do I manage multiple client sites today, before fleet management ships?
Per-site, on OSS or Pro. Each client site is its own AILK deploy with its own repo, schema registry, and audit run. There's no fleet dashboard yet — that's the gap fleet management closes. Nothing stops you from running several client sites in parallel today.
Is there a discount for managing many sites on Pro?
Not currently. Pro is priced per user per year ($249), not per site, so an agency running several client sites on one Pro seat pays the same rate regardless of site count. Volume-based agency pricing arrives with the Enterprise multi-tenant entitlement.
Working Theory relationship
How does this relate to Working Theory Platform? Am I locked in?
You're not locked in. AILK works fully standalone. Working Theory Platform is a separate product — growth marketing as a system that publishes into AILK with the deepest integration available. Neither product requires the other.
Do I need Working Theory Platform to use AILK?
No. Clone AILK, deploy it, run it — none of that touches Working Theory Platform. Platform is the recommended layer for customers who also want ongoing growth marketing; it isn't a requirement to use AILK.
Next.js requirement
We're not Next.js native. Is this still for us?
Yes, if AI search visibility is the deliverable you're selling. Launch Service is the path — a fixed-scope two-week deploy onto the substrate. Your team owns content and citation work from there. Next.js fluency helps. It isn't required.
Do I need to write MDX myself?
No. Launch Service handles the build; your team works in content and citation strategy from there, with no MDX or build pipeline required on your end. Teams that want to write MDX directly can — it's the foundation's native content format.
Migration from WordPress
Can I migrate my existing WordPress site to AILK?
Yes, though AILK isn't positioned as a migration tool — it's a foundation you rebuild on. Content and schema get recreated on AILK's typed page structure rather than imported wholesale, since the underlying data models don't match a plugin-based WordPress stack.
What happens to my existing SEO rankings during a move off WordPress?
Rankings depend on redirect discipline and content parity, not the platform switch itself. A well-executed move preserves URLs where possible and 301s the rest. It typically improves the schema and entity markup that WordPress plugin stacks handle inconsistently.
How long does a WordPress migration take?
Launch Service runs a fixed two-week scope for a new AILK deploy. Actual migration timeline depends on how much existing content needs to be recreated. A small brochure site fits inside two weeks; larger content libraries take longer to fully port over.
Pricing & licensing
What's the difference between Free, Pro, and Pro Plus?
Free is the Apache 2.0 OSS foundation — complete, not crippled. Pro adds capability at $249 per user per year. Pro Plus adds ongoing care at $449 per user per month. Paid tiers build on the free foundation; they never gate access to it.
Is the OSS version really free forever?
Yes. AILK's OSS layer is Apache 2.0 — not source-available, not "free until you make money," and not deliberately crippled to push a paid tier. It's structurally complete today, and it stays that way regardless of what paid tiers add later.
What license does AILK use?
Apache 2.0, the permissive open-source license, published on GitHub with no dual-licensing traps. Clone it. Modify it. Deploy it commercially — no royalty obligations back to Working Theory.
Still have questions?
Talk to us directly about Launch Service, Pro, or Enterprise fleet management — or skip the conversation and clone the OSS foundation yourself.