create-ailk 0.1.0

package/templates/content/en/HomePage/launch-service.mdx

@@ -0,0 +1,475 @@
+---
+type: "HomePage"
+slug: "launch-service"
+title: "Ship an AI-search-ready website in two weeks. Fixed scope. Fixed price: $2,495."
+description: "Deploy your website on AILK in two weeks. Fixed scope, fixed price: $2,495. The open-source, agent-ready foundation — built by the team that runs it."
+sections:
+  [
+    {
+      "id": "hero-launch-service",
+      "type": "hero",
+      "data":
+        {
+          "headline": "Ship an AI-search-ready website in two weeks. Fixed scope. Fixed price: $2,495.",
+          "subheadline": "The same open-source foundation Sam Henry, Working Theory, and SalesSmyth publish on — deployed for your business by the team that built it.",
+          "body": "AILK Launch Service is the fixed-scope, two-week deploy of the AI Launch Kit foundation: schema-typed, agent-callable, already audited before it ships.",
+          "primaryCta":
+            { "label": "Book your intro call", "href": "/book-call" },
+          "secondaryCta":
+            {
+              "label": "See common questions",
+              "href": "/faq",
+              "variant": "ghost",
+            },
+        },
+    },
+    {
+      "id": "insight-foundation-is-the-bottleneck",
+      "type": "content-block",
+      "data":
+        {
+          "headline": "Why does your website's foundation decide whether AI search cites you?",
+          "body": "AI search doesn't send someone to your homepage first. It reads a page, decides whether to trust it, and quotes the sentence that answers the question — often without the reader ever visiting the rest of your site. That page is the unit of citation, not the site.\n\nFor a model to cite your business, it has to read a page it can parse: structured, marked up, and clearly attributed to your brand. Most SMB sites weren't built with that requirement in mind. They were built when a search engine, not a chatbot, decided what a buyer saw next — so the words on the page were written for people scanning a results list, not for a system extracting a fact.\n\nThat gap is now a business cost. Every quarter, another competitor's page gets cited instead of yours, in an answer your buyer never sees you compete for. The foundation your site runs on decides whether your pages are even eligible to be quoted — before a single word of content gets written.",
+        },
+    },
+    {
+      "id": "alternatives-to-two-week-launch",
+      "type": "comparison-table",
+      "data":
+        {
+          "eyebrow": "Compare the paths to a modern SMB site",
+          "headline": "What are the alternatives to a two-week AILK launch?",
+          "description": "Four paths exist for a modern SMB website in 2026, and each trades speed, cost, or control for something you'll notice within a year. WordPress plus AEO and schema plugins runs an estimated 40% of the web — familiar and cheap to host, but the plugins don't integrate, they break on updates, and your AI-search readiness depends on whichever combination happens to be installed this month. Closed builders like Squarespace, Wix, and Webflow trade the plugin problem for a different one: fast templates, but weak schema control, no agent-callable surface, and a vendor that owns the substrate you're renting. A custom development build gives you full control and often the strongest final result — at three to six months and $15,000 to $50,000-plus, timelines and budgets that don't fit most SMB engagements. AILK Launch Service is the fourth path: the same Apache 2.0 foundation the Working Theory team runs its own brands on, deployed for your business in a fixed two-week scope, for a fixed $2,495. Every option below is measured against the same four dimensions: timeline, price, AI-search structure, and who owns the code when the engagement ends.",
+          "columns":
+            [
+              {
+                "key": "ailk",
+                "name": "AILK Launch Service",
+                "highlighted": true,
+              },
+              { "key": "wordpress", "name": "WordPress + Plugins" },
+              { "key": "closed", "name": "Closed Builders" },
+              { "key": "custom", "name": "Custom Dev Build" },
+            ],
+          "groups":
+            [
+              {
+                "groupName": "Timeline & Cost",
+                "rows":
+                  [
+                    {
+                      "featureName": "Timeline",
+                      "values":
+                        {
+                          "ailk": "2 weeks, fixed",
+                          "wordpress": "4–8 weeks, variable",
+                          "closed": "1–3 weeks, template-bound",
+                          "custom": "3–6 months",
+                        },
+                    },
+                    {
+                      "featureName": "Price",
+                      "values":
+                        {
+                          "ailk": "$2,495 fixed",
+                          "wordpress": "$3k–$15k + plugin costs",
+                          "closed": "$200–$500/yr subscription",
+                          "custom": "$15k–$50k+",
+                        },
+                    },
+                  ],
+              },
+              {
+                "groupName": "AI Search Readiness",
+                "rows":
+                  [
+                    {
+                      "featureName": "Schema & AEO structure",
+                      "values":
+                        {
+                          "ailk": true,
+                          "wordpress": "Requires 3+ plugins",
+                          "closed": "Weak, not controllable",
+                          "custom": "Depends on the developer",
+                        },
+                    },
+                    {
+                      "featureName": "Agent-callable (MCP)",
+                      "values":
+                        {
+                          "ailk": true,
+                          "wordpress": false,
+                          "closed": false,
+                          "custom": "Rare",
+                        },
+                    },
+                    {
+                      "featureName": "You own the codebase",
+                      "values":
+                        {
+                          "ailk": true,
+                          "wordpress": true,
+                          "closed": false,
+                          "custom": true,
+                        },
+                    },
+                  ],
+              },
+            ],
+          "footnote": "Timeline and price ranges reflect typical SMB engagements as of 2026; AILK Launch Service pricing is fixed at $2,495.",
+        },
+    },
+    {
+      "id": "what-a-foundation-must-do",
+      "type": "content-block",
+      "data":
+        {
+          "headline": "What should a modern website foundation actually do?",
+          "body": "A website foundation built for how AI search actually works has to do five specific things — none of them are AILK features, they're requirements any foundation has to meet.\n\nIt has to be read correctly: a model reading the page should know what it's about and which business it belongs to, without guessing from unstructured text.\n\nAgents now research on a buyer's behalf, so the foundation also needs to work for non-human visitors — exposing itself to them as a first-class audience, not a scraped afterthought.\n\nIt has to surface its own gaps. AEO problems don't crash a site; they quietly stop it from getting cited. The foundation needs to catch structural gaps the way a linter catches type errors — before launch, not three months after.\n\nA foundation that locks you in shapes its roadmap around that lock-in, not around your business, which is why it has to belong to the people running on it.\n\nAnd it has to fit inside a real engagement: an SMB site project runs weeks, not quarters — a foundation that demands a multi-month custom build breaks the economics before it starts.\n\nAny foundation can be measured against these five. Most fail at least three.",
+        },
+    },
+    {
+      "id": "introducing-launch-service",
+      "type": "feature",
+      "data":
+        {
+          "headline": "The AILK Launch Service: your site, deployed on the AI-search-ready foundation, in two weeks",
+          "description": "Launch Service is the productized version of what AILK ships as open source: a schema-typed, agent-callable website, deployed onto your domain by the Working Theory Labs team instead of self-served through the CLI. It's the path for businesses and agencies who want the foundation without doing the build themselves.",
+          "features":
+            [
+              {
+                "title": "Fixed scope, fixed price",
+                "description": "$2,495, one time. No hourly billing, no scope creep — the deploy is defined before you book the call.",
+              },
+              {
+                "title": "Built by the team that built AILK",
+                "description": "The same engineers who ship the open-source foundation deploy your site directly onto it — not a reseller layer, not a template shop.",
+              },
+              {
+                "title": "Two weeks, start to finish",
+                "description": "From intro call to a live, schema-typed, agent-callable site — a timeline that fits an SMB engagement instead of a custom-build budget.",
+              },
+              {
+                "title": "You own the code",
+                "description": "Apache 2.0, same as the open-source project. Nothing about Launch Service changes that — the codebase is yours the day it ships.",
+              },
+            ],
+        },
+    },
+    {
+      "id": "capabilities-delivered-in-two-weeks",
+      "type": "items",
+      "data":
+        {
+          "headline": "What capabilities does Launch Service deliver in two weeks?",
+          "description": "Every AILK Launch Service deploy ships the same five structural capabilities that make the open-source foundation different — the ones that determine whether your pages are readable, citable, and interactable by both people and AI agents.",
+          "items":
+            [
+              {
+                "title": "A typed schema registry, live on your pages",
+                "description": "Sixty page types ship with per-type schema validation and JSON-LD generated directly from your content — FAQ markup, entity markup, and identity markup (Organization, Person, LocalBusiness) included by default. On WordPress this normally takes three or four plugins that don't integrate cleanly; on AILK it's native to the page you publish.",
+              },
+              {
+                "title": "Peer surfaces for humans and agents",
+                "description": "Your site ships as three matched surfaces sharing one codebase: a web UI for the people who visit, an MCP server for the AI agents now researching on their behalf, and an HTTP API for programmatic callers. Parity between all three is enforced in continuous integration — whatever a person can do on your site, an agent can do too.",
+              },
+              {
+                "title": "A pre-launch AEO audit",
+                "description": "The `ailk audit` CLI runs against your site before it launches, scoring the schema and structural readiness the way a linter scores code for type errors. Enterprise AEO platforms charge $295 a month to measure this after a site has already lost citations. Your Launch Service deploy ships already measured, before it's public.",
+              },
+              {
+                "title": "An Apache 2.0 codebase, complete",
+                "description": "Nothing in your deploy is source-available, feature-gated, or dependent on a subscription to keep working. It's Apache 2.0 — the same license, the same codebase, that the open-source AILK project ships. If you ever leave the Working Theory team, you leave with the code.",
+              },
+              {
+                "title": "Agent-assisted scaffolding for what comes next",
+                "description": "The `.claude/` skill bundle that ships with every AILK project — `scaffold-page`, `add-schema`, `audit-site`, and five more — comes with your deploy. Adding a new service page or a new section next quarter is a guided agent session, not a re-engagement with a developer.",
+              },
+            ],
+        },
+    },
+    {
+      "id": "what-changes-after-launch",
+      "type": "items",
+      "data":
+        {
+          "headline": "What does a two-week AILK launch change for your business?",
+          "description": "Each capability above pays off as a concrete change in how your site performs and how much it costs to keep improving it.",
+          "items":
+            [
+              {
+                "title": "The citation work compounds instead of resetting",
+                "description": "On a WordPress-plus-plugins stack, every new campaign re-fights plugin conflicts and weak markup. On AILK, every page you publish is already structured for citation — the content work you do next builds on what's already there instead of fighting it.",
+              },
+              {
+                "title": "Enterprise-grade architecture at SMB pricing",
+                "description": "A human UI, an MCP server, an API kept in parity by CI — that peer-surfaces architecture used to require a six-figure CMS contract and a dedicated engineering team. It's the same schema-typed, agent-callable structure enterprise buyers pay Sitecore-tier budgets for. Your deploy ships it as the default, not an upsell.",
+              },
+              {
+                "title": "Structural gaps get caught before launch, not three months in",
+                "description": "A citation gap discovered after launch costs months of content work to recover. The same gap caught by `ailk audit` before launch costs nothing but the audit run. The cost of an AEO mistake shifts from 'after your customers notice' to 'before you go live.'",
+              },
+              {
+                "title": "You own the relationship, not a vendor",
+                "description": "No platform takes a percentage, and no closed builder reshapes your roadmap. If you leave the Working Theory team a year from now, the codebase leaves with you — Apache 2.0 means nobody else holds the keys. Your business relationship is with a team, not a subscription you can't cancel without losing your site.",
+              },
+              {
+                "title": "The marginal cost of your next page approaches zero",
+                "description": "Once your site is live, adding a new service page, updating a schema, or responding to a citation gap is a Claude Code session — an hour, not a sprint. The two-week deploy is the expensive part; everything after gets cheaper.",
+              },
+            ],
+        },
+    },
+    {
+      "id": "proof-the-architecture-is-in-the-repo",
+      "type": "content-block",
+      "data":
+        {
+          "headline": "What proof backs the AILK Launch Service claims?",
+          "body": "The clearest proof of the Launch Service claims is the architecture itself. You can verify it directly instead of taking our word for it: AILK is Apache 2.0 on GitHub, built as three peer apps (`apps/web`, `apps/mcp`, `apps/api`), with a parity test running in continuous integration and a `.well-known/mcp.json` file at the deployed URL of every AILK site, including this one. The `ailk audit` CLI runs against any AILK deploy and returns the same score a stranger would get.\n\nWe run on it ourselves. Sam Henry, Working Theory, and SalesSmyth all publish on AILK, and that's the actual reason the schema registry and the peer-surfaces architecture exist in their current shape. We hit the structural problems Launch Service solves before we sold anyone else a solution to them.\n\nWe're also honest about what's still ahead. There are no public install counts, no case studies from outside the founding team, and no third-party benchmarks yet — those come from the first cohort of Launch Service customers over the next several months, not from a launch-day claim. What you can verify today is the codebase, the CI, and the audit tool. What you can't verify yet, we're not pretending to have.",
+        },
+    },
+    {
+      "id": "launch-service-pricing",
+      "type": "pricing",
+      "data":
+        {
+          "headline": "How much does the AILK Launch Service cost?",
+          "description": "Launch Service is $2,495, one time, fixed scope — the deploy, not a subscription. If your team wants ongoing access to the AILK Pro tooling after launch, Pro and Pro Plus are priced separately, per user.",
+          "variant": "features-and-plans",
+          "plans":
+            [
+              {
+                "key": "launch-service",
+                "name": "Launch Service",
+                "price": { "custom": "$2,495" },
+                "priceSubhead": "one-time, fixed scope",
+                "description": "A fixed two-week deploy of your site onto the AILK foundation, delivered by the Working Theory Labs team.",
+                "features":
+                  [
+                    "Two-week deploy, start to finish",
+                    "Schema-typed, agent-callable site",
+                    "Pre-launch `ailk audit` pass",
+                    "Apache 2.0 — you own the code",
+                  ],
+                "cta": { "label": "Book intro call", "href": "/book-call" },
+                "highlighted": true,
+              },
+              {
+                "key": "pro",
+                "name": "Pro",
+                "price": { "annual": "$249/user/year" },
+                "priceSubhead": "per user, billed annually",
+                "description": "Ongoing Pro tooling for teams publishing and iterating on an AILK site after launch.",
+                "features":
+                  [
+                    "Per-user access to Pro tooling",
+                    "For teams managing an active AILK site",
+                  ],
+                "cta": { "label": "See Pro pricing", "href": "/pricing" },
+              },
+              {
+                "key": "pro-plus",
+                "name": "Pro Plus",
+                "price": { "monthly": "$449/user/month" },
+                "priceSubhead": "per user, billed monthly",
+                "description": "Pro tooling plus ongoing care for teams that want a managed relationship after launch.",
+                "features": ["Everything in Pro", "Ongoing managed support"],
+                "cta": { "label": "See Pro Plus pricing", "href": "/pricing" },
+              },
+            ],
+        },
+    },
+    {
+      "id": "launch-service-objections",
+      "type": "faq",
+      "data":
+        {
+          "headline": "Common questions about the AILK Launch Service",
+          "items":
+            [
+              {
+                "question": "You're pre-launch. Why bet on this?",
+                "answer": "The architecture is observable in the repo, not on a slide deck. The schema registry is a directory with sixty typed entries. The parity test runs in CI. The `ailk audit` CLI works against any AILK site today. The team ships this foundation and runs three other brands on it — Sam Henry, Working Theory, and SalesSmyth. Apache 2.0 bounds your downside: if AILK never grows past today, you keep the code and you keep your site.",
+              },
+              {
+                "question": "We run a portfolio of client sites. Where's fleet management?",
+                "answer": "It's deferred. Fleet management, cross-site rollup, and white-label licensing for agencies are planned as a future Enterprise multi-tenant entitlement, not a separate tier, and not shipped yet. At launch, agencies deliver client sites through Launch Service plus per-user Pro — one site per engagement, not a fleet dashboard.",
+              },
+              {
+                "question": "We're not Next.js native. Is this still for us?",
+                "answer": "Yes — if what you need is AI-search visibility, not a codebase you maintain yourselves. Launch Service is built for exactly this: a fixed two-week deploy where our team owns the build, and you own the content and the citation work from there. No MDX, no build pipeline, no Next.js fluency required on your side.",
+              },
+              {
+                "question": "How does this relate to Working Theory Platform? Am I locked in?",
+                "answer": "You're not locked into anything. AILK works fully standalone, and Launch Service delivers a complete, independent site. Working Theory Platform is a separate product for growth marketing as a system; it publishes into AILK with the deepest integration for customers who want both, but neither product requires the other.",
+              },
+            ],
+          "supportLink": { "label": "Read the full FAQ", "href": "/faq" },
+        },
+    },
+    {
+      "id": "book-intro-call-close",
+      "type": "cta",
+      "data":
+        {
+          "headline": "Book your intro call",
+          "description": "Fifteen minutes to confirm scope, timeline, and price — then a two-week deploy onto the foundation built for the AI-search era. No obligation until you book the engagement.",
+          "primaryCta": { "label": "Book intro call", "href": "/book-call" },
+          "secondaryCta":
+            {
+              "label": "Read common questions",
+              "href": "/faq",
+              "variant": "outline",
+            },
+        },
+    },
+  ]
+status: "Approved"
+pageKey: "Service"
+entity: "ailaunchkit"
+urlSlug: "service"
+lastUpdated: "2026-07-06"
+pageLevelSchemaType: "HomePage"
+---
+
+import { JsonLd } from "@/components/JsonLd";
+
+<JsonLd
+  data={{
+    "@context": "https://schema.org",
+    "@graph": [
+      {
+        "@type": "Product",
+        "@id": "https://ailaunchkit.ai/#product",
+        name: "AI Launch Kit",
+        alternateName: [
+          "AI Launch Kit by Working Theory",
+          "AILK by Working Theory",
+          "AILK",
+          "@ailaunchkit",
+          "@ailk",
+          "@working-theory",
+          "ai-launch-kit",
+        ],
+        url: "https://ailaunchkit.ai",
+        description:
+          "AI Launch Kit is the open-source website foundation for the agent-first internet — Apache 2.0, agent-ready, AEO-scored, deployable in days.",
+        sameAs: [
+          "https://github.com/working-theory-labs/ai-launch-kit",
+          "https://x.com/ailaunchkit",
+          "https://www.npmjs.com/org/ailk",
+          "https://youtube.com/@working-theory",
+          "https://linkedin.com/company/working-theory",
+        ],
+        foundingDate: "2026",
+        category: "Open-source website foundation",
+        applicationCategory: "DeveloperApplication",
+        operatingSystem: "Cross-platform (Node.js)",
+        license: "https://www.apache.org/licenses/LICENSE-2.0",
+        codeRepository: "https://github.com/working-theory-labs/ai-launch-kit",
+        manufacturer: {
+          "@type": "Organization",
+          name: "SalesSmyth LLC",
+          url: "https://ailaunchkit.ai",
+        },
+        brand: {
+          "@type": "Brand",
+          name: "Working Theory",
+          url: "https://workingtheory.ai",
+        },
+        creator: { "@type": "Person", name: "Sam Henry" },
+        offers: [
+          {
+            "@type": "Offer",
+            name: "Free (OSS)",
+            price: "0",
+            priceCurrency: "USD",
+          },
+          {
+            "@type": "Offer",
+            name: "Pro",
+            price: "249",
+            priceCurrency: "USD",
+            description: "Per user, per year",
+          },
+          {
+            "@type": "Offer",
+            name: "Pro Plus",
+            price: "449",
+            priceCurrency: "USD",
+            description: "Per user, per month",
+          },
+          {
+            "@type": "Offer",
+            name: "Launch Service",
+            price: "2495",
+            priceCurrency: "USD",
+            description: "Fixed-scope, two-week productized deploy engagement",
+          },
+        ],
+      },
+      {
+        "@type": "Service",
+        "@id": "https://ailaunchkit.ai/launch-service#service",
+        url: "https://ailaunchkit.ai/launch-service",
+        name: "AILK Launch Service",
+        description:
+          "Deploy your website on AILK in two weeks. Fixed scope, fixed price: $2,495. The open-source, agent-ready foundation — built by the team that runs it.",
+        isPartOf: { "@id": "https://ailaunchkit.ai/#product" },
+        provider: { "@id": "https://ailaunchkit.ai/#product" },
+        areaServed: "Global",
+        serviceType: "Website foundation deployment service",
+        offers: {
+          "@type": "Offer",
+          name: "Launch Service",
+          price: "2495",
+          priceCurrency: "USD",
+          description:
+            "One-time, fixed-scope, two-week deploy of your site onto the AILK foundation, delivered by the Working Theory Labs team.",
+          url: "https://ailaunchkit.ai/launch-service",
+        },
+        mainEntity: {
+          "@type": "FAQPage",
+          "@id": "https://ailaunchkit.ai/launch-service#faq",
+          mainEntity: [
+            {
+              "@type": "Question",
+              name: "You're pre-launch. Why bet on this?",
+              acceptedAnswer: {
+                "@type": "Answer",
+                text: "The architecture is observable in the repo, not on a slide deck. The schema registry is a directory with sixty typed entries. The parity test runs in CI. The `ailk audit` CLI works against any AILK site today. The team ships this foundation and runs three other brands on it — Sam Henry, Working Theory, and SalesSmyth. Apache 2.0 bounds your downside: if AILK never grows past today, you keep the code and you keep your site.",
+              },
+            },
+            {
+              "@type": "Question",
+              name: "We run a portfolio of client sites. Where's fleet management?",
+              acceptedAnswer: {
+                "@type": "Answer",
+                text: "It's deferred. Fleet management, cross-site rollup, and white-label licensing for agencies are planned as a future Enterprise multi-tenant entitlement, not a separate tier, and not shipped yet. At launch, agencies deliver client sites through Launch Service plus per-user Pro — one site per engagement, not a fleet dashboard.",
+              },
+            },
+            {
+              "@type": "Question",
+              name: "We're not Next.js native. Is this still for us?",
+              acceptedAnswer: {
+                "@type": "Answer",
+                text: "Yes — if what you need is AI-search visibility, not a codebase you maintain yourselves. Launch Service is built for exactly this: a fixed two-week deploy where our team owns the build, and you own the content and the citation work from there. No MDX, no build pipeline, no Next.js fluency required on your side.",
+              },
+            },
+            {
+              "@type": "Question",
+              name: "How does this relate to Working Theory Platform? Am I locked in?",
+              acceptedAnswer: {
+                "@type": "Answer",
+                text: "You're not locked into anything. AILK works fully standalone, and Launch Service delivers a complete, independent site. Working Theory Platform is a separate product for growth marketing as a system; it publishes into AILK with the deepest integration for customers who want both, but neither product requires the other.",
+              },
+            },
+          ],
+        },
+      },
+    ],
+  }}
+/>
+
+{/* Rendered from frontmatter `sections[]`; the MDX body is not read by the section-catalog renderer. Landed by land-section-catalog.py (#3111). */}

package/templates/content/en/HomePage/launch-service.schema.json

@@ -0,0 +1,138 @@
+{
+  "@context": "https://schema.org",
+  "@graph": [
+    {
+      "@type": "Product",
+      "@id": "https://ailaunchkit.ai/#product",
+      "name": "AI Launch Kit",
+      "alternateName": [
+        "AI Launch Kit by Working Theory",
+        "AILK by Working Theory",
+        "AILK",
+        "@ailaunchkit",
+        "@ailk",
+        "@working-theory",
+        "ai-launch-kit"
+      ],
+      "url": "https://ailaunchkit.ai",
+      "description": "AI Launch Kit is the open-source website foundation for the agent-first internet — Apache 2.0, agent-ready, AEO-scored, deployable in days.",
+      "sameAs": [
+        "https://github.com/working-theory-labs/ai-launch-kit",
+        "https://x.com/ailaunchkit",
+        "https://www.npmjs.com/org/ailk",
+        "https://youtube.com/@working-theory",
+        "https://linkedin.com/company/working-theory"
+      ],
+      "foundingDate": "2026",
+      "category": "Open-source website foundation",
+      "applicationCategory": "DeveloperApplication",
+      "operatingSystem": "Cross-platform (Node.js)",
+      "license": "https://www.apache.org/licenses/LICENSE-2.0",
+      "codeRepository": "https://github.com/working-theory-labs/ai-launch-kit",
+      "manufacturer": {
+        "@type": "Organization",
+        "name": "SalesSmyth LLC",
+        "url": "https://ailaunchkit.ai"
+      },
+      "brand": {
+        "@type": "Brand",
+        "name": "Working Theory",
+        "url": "https://workingtheory.ai"
+      },
+      "creator": {
+        "@type": "Person",
+        "name": "Sam Henry"
+      },
+      "offers": [
+        {
+          "@type": "Offer",
+          "name": "Free (OSS)",
+          "price": "0",
+          "priceCurrency": "USD"
+        },
+        {
+          "@type": "Offer",
+          "name": "Pro",
+          "price": "249",
+          "priceCurrency": "USD",
+          "description": "Per user, per year"
+        },
+        {
+          "@type": "Offer",
+          "name": "Pro Plus",
+          "price": "449",
+          "priceCurrency": "USD",
+          "description": "Per user, per month"
+        },
+        {
+          "@type": "Offer",
+          "name": "Launch Service",
+          "price": "2495",
+          "priceCurrency": "USD",
+          "description": "Fixed-scope, two-week productized deploy engagement"
+        }
+      ]
+    },
+    {
+      "@type": "Service",
+      "@id": "https://ailaunchkit.ai/launch-service#service",
+      "url": "https://ailaunchkit.ai/launch-service",
+      "name": "AILK Launch Service",
+      "description": "Deploy your website on AILK in two weeks. Fixed scope, fixed price: $2,495. The open-source, agent-ready foundation — built by the team that runs it.",
+      "isPartOf": {
+        "@id": "https://ailaunchkit.ai/#product"
+      },
+      "provider": {
+        "@id": "https://ailaunchkit.ai/#product"
+      },
+      "areaServed": "Global",
+      "serviceType": "Website foundation deployment service",
+      "offers": {
+        "@type": "Offer",
+        "name": "Launch Service",
+        "price": "2495",
+        "priceCurrency": "USD",
+        "description": "One-time, fixed-scope, two-week deploy of your site onto the AILK foundation, delivered by the Working Theory Labs team.",
+        "url": "https://ailaunchkit.ai/launch-service"
+      },
+      "mainEntity": {
+        "@type": "FAQPage",
+        "@id": "https://ailaunchkit.ai/launch-service#faq",
+        "mainEntity": [
+          {
+            "@type": "Question",
+            "name": "You're pre-launch. Why bet on this?",
+            "acceptedAnswer": {
+              "@type": "Answer",
+              "text": "The architecture is observable in the repo, not on a slide deck. The schema registry is a directory with sixty typed entries. The parity test runs in CI. The `ailk audit` CLI works against any AILK site today. The team ships this foundation and runs three other brands on it — Sam Henry, Working Theory, and SalesSmyth. Apache 2.0 bounds your downside: if AILK never grows past today, you keep the code and you keep your site."
+            }
+          },
+          {
+            "@type": "Question",
+            "name": "We run a portfolio of client sites. Where's fleet management?",
+            "acceptedAnswer": {
+              "@type": "Answer",
+              "text": "It's deferred. Fleet management, cross-site rollup, and white-label licensing for agencies are planned as a future Enterprise multi-tenant entitlement, not a separate tier, and not shipped yet. At launch, agencies deliver client sites through Launch Service plus per-user Pro — one site per engagement, not a fleet dashboard."
+            }
+          },
+          {
+            "@type": "Question",
+            "name": "We're not Next.js native. Is this still for us?",
+            "acceptedAnswer": {
+              "@type": "Answer",
+              "text": "Yes — if what you need is AI-search visibility, not a codebase you maintain yourselves. Launch Service is built for exactly this: a fixed two-week deploy where our team owns the build, and you own the content and the citation work from there. No MDX, no build pipeline, no Next.js fluency required on your side."
+            }
+          },
+          {
+            "@type": "Question",
+            "name": "How does this relate to Working Theory Platform? Am I locked in?",
+            "acceptedAnswer": {
+              "@type": "Answer",
+              "text": "You're not locked into anything. AILK works fully standalone, and Launch Service delivers a complete, independent site. Working Theory Platform is a separate product for growth marketing as a system; it publishes into AILK with the deepest integration for customers who want both, but neither product requires the other."
+            }
+          }
+        ]
+      }
+    }
+  ]
+}

package/templates/content/en/HowTo/add-mdx-content.mdx

@@ -0,0 +1,38 @@
+---
+type: HowTo
+slug: add-mdx-content
+title: How to Add MDX Content to an AILK Site
+description: Create and manage MDX content files using the AILK content adapter — frontmatter conventions, directory layout, and locale support.
+publishedAt: "2026-05-05"
+---
+
+# How to Add MDX Content to an AILK Site
+
+AILK uses MDX files as the canonical content source. The content adapter reads them at build time and maps them to typed `ContentPage` objects the schema builders consume.
+
+## Step 1 — Create the content directory
+
+Each schema.org type gets its own directory under `content/<locale>/<Type>/`. For example, how-to articles live at `content/en/HowTo/`.
+
+## Step 2 — Author the frontmatter
+
+Every MDX file needs at minimum:
+
+```yaml
+---
+type: HowTo
+slug: my-guide
+title: My Guide Title
+description: One clear sentence explaining what this guide covers.
+---
+```
+
+Optional fields: `publishedAt`, `updatedAt`, `image`, and a `schema` override block for advanced structured data.
+
+## Step 3 — Write the body
+
+The MDX body renders below the frontmatter-driven heading and description on the detail page. Use standard Markdown headings, code blocks, and lists.
+
+## Step 4 — Add locale variants
+
+Duplicate the file into `content/es/<Type>/` (or any locale prefix) with translated frontmatter and body. The content adapter applies a fallback chain: requested locale → default locale → legacy non-prefixed layout.