# ASO Studio — Enterprise Deployment & Use-Case Blueprints (`use-cases/industry-guides.md`)

> Production implementation blueprints for B2B SaaS engineering and growth teams deploying **ASO Studio** (`https://asostudio.dev`). Verified 2026-11-01.

## Use Case 1: Zero-Backend 14-Route Edge Agent Layer (`<15ms`, 5 Supported Stacks)

**Problem:** Series A–C B2B SaaS marketing sites built as client-side React/Next.js/Astro SPAs ship 2–5 MB of JavaScript and return HTTP 404 (or HTML soft-404s) on `/llms.txt`, `/llms-full.txt`, `/.well-known/ai.txt`, `/pricing.md`, `/.well-known/mcp.json`, `/.well-known/server.json`, `/.well-known/agent-card.json`, and `/ai/summary.json`. AI search retrieval bots time out or skip unstructured bundles.

**Solution:** ASO Studio deploys a lightweight Edge Router (`$1,490` + `$490/mo` Drift Guard, delivered first and paid after the agreed technical checks) across **Cloudflare Workers**, **Vercel Next.js (`middleware.ts`)**, **Astro / SvelteKit / Remix (`src/middleware.ts`)**, **Python FastAPI**, or **AWS CloudFront / Nginx**. It serves all 14 deterministic plain-text and JSON-LD endpoints in under 15ms and injects `RFC 8288` `Link` discovery headers without touching origin application logic.

## Use Case 2: Capturing `[Brand] vs [Incumbent]` Bottom-of-Funnel Buyer Prompts

**Problem:** When enterprise buyers prompt ChatGPT Search, Claude, or Perplexity with *"[Your Company] vs [Incumbent] pricing and architecture"*, the model executes 5–10 retrieval sub-queries. Missing machine-readable comparison tables cause LLMs to default to the incumbent.

**Solution:** The Category Saturation Engine (`$6,500`, 30-day sprint) deploys 25 criteria-driven `[Brand] vs [Competitor]` Markdown matrices, 20 industry use-case specs, and linked Schema.org `@graph` JSON-LD so crawlers can read structured product comparisons.

## Use Case 3: CI/CD Regression Protection Against Marketing Site Redesigns

**Problem:** Frontend redesigns routinely strip JSON-LD blocks, overwrite `robots.txt` crawler rules, or break `/llms.txt` and `/.well-known/mcp.json` routes.

**Solution:** Every ASO Studio 26-file bundle includes `.github/workflows/aso-score-gate.yml`, blocking pull requests if any of the 27 AI crawler permissions or 47 HTTP/HTML readiness checks regress below the configured CI threshold.
