{
  "$schema_note": "Leapshot's single source of truth. The pages, the Ask Leapshot chat, /llms.txt and the JSON-LD on leapshot.design are all generated from this file.",
  "updated": "2026-10-10",
  "brand": {
    "name": "Leapshot",
    "domain": "leapshot.design",
    "tagline": "Your team, multiplied.",
    "positioning": "The studio that builds creative automation systems.",
    "promise": "We build creative automation systems that let your team do the work of a much bigger one: brand, content, ads, site, chat and ops, all running from one source of truth.",
    "about": "Leapshot is a Melbourne studio for design, web and AI automation, led by Fagan Wilcox. It spun out of PopCandi in October 2026.",
    "manifesto": "Not a campaign and not a one-off website. A system: your brand written down as rules, a content and ad engine that follows them, a site that people and AI agents can both read, a front door that answers, and a team that knows how to run all of it.",
    "location": "Melbourne, Australia",
    "founded": "2026-10",
    "founder": "Fagan Wilcox",
    "sister_studio": {
      "name": "PopCandi",
      "url": "https://popcandi.tv",
      "scope": "Film and video, colour grading, editing and VFX. Anything shot lives at PopCandi."
    },
    "pricing_model": "A setup fee to build the system, then a monthly retainer to run and improve it. Not hours.",
    "area_served": ["Melbourne", "Australia"]
  },
  "seo": {
    "title": "Leapshot | Creative automation studio, Melbourne",
    "description": "Leapshot is a Melbourne studio that builds creative automation systems: agent-ready websites, AI chatbots and automation, and local SEO, GEO and AEO.",
    "image": "/og.png",
    "image_alt": "Leapshot: your team, multiplied. The studio that builds creative automation systems.",
    "logo": "/icon-512.png"
  },
  "stats": [
    { "id": "source", "value": "1", "label": "Source of truth", "note": "Change it once and every surface follows." },
    { "id": "layers", "value": "5", "label": "Layers, built in order", "note": "Brand, engine, site, front door, training." },
    { "id": "packages", "value": "4", "label": "Packages", "note": "Each one a setup fee plus a monthly retainer." },
    { "id": "hours", "value": "0", "label": "Hours sold", "note": "We sell systems that keep working." }
  ],
  "process": [
    {
      "id": "brand-system",
      "step": 1,
      "name": "Brand system",
      "summary": "Tokens, logo, type, motion recipes and rules, built so AI tools can read and follow them.",
      "outputs": ["Design tokens", "Logo and type", "Motion recipes", "Rules AI tools can follow"]
    },
    {
      "id": "content-engine",
      "step": 2,
      "name": "Content and ad engine",
      "summary": "Motion ads, social creative and AI UGC produced from the brand system, with approvals built in.",
      "outputs": ["Motion ads", "Social creative", "AI UGC", "Approvals"]
    },
    {
      "id": "site-agent-layer",
      "step": 3,
      "name": "Site and agent layer",
      "summary": "Structured content that feeds your site, ads, email and AI assistants from one place.",
      "outputs": ["Structured content", "Schema and llms.txt", "An /ask or MCP endpoint"]
    },
    {
      "id": "chat-ops",
      "step": 4,
      "name": "Chatbot and ops",
      "summary": "A conversational front door wired to live data, plus the automations behind it.",
      "outputs": ["Chatbot on live data", "Escalation rules", "Ops automations"]
    },
    {
      "id": "training",
      "step": 5,
      "name": "Team training",
      "summary": "Your people learn to run, approve and extend the system. The system multiplies them; it does not replace them.",
      "outputs": ["Workshops", "Approval gates", "An operating model"]
    }
  ],
  "packages": [
    {
      "id": "agent-ready-site",
      "name": "Agent-ready site",
      "line": "A site people and AI agents can both read",
      "summary": "A lean, fast site that people and AI agents can both read and act on.",
      "for": "Businesses whose website is their main sales tool, and who want it read and quoted by AI assistants as well as people.",
      "description": "We design and build the site in Astro or Next.js on a headless CMS, so every page is drawn from structured content. The same content is published as schema, llms.txt and an endpoint that AI agents can query.",
      "service_type": "Website design and development",
      "page": "/websites/",
      "includes": ["Structured content in a headless CMS", "Schema (JSON-LD) across the site", "llms.txt", "An /ask or MCP endpoint for agents"],
      "pricing": "Setup fee + monthly retainer",
      "cta": "Enquire",
      "keywords": ["agent ready", "agent-ready", "site", "website", "schema", "json-ld", "llms", "mcp", "ask endpoint", "headless", "structured"]
    },
    {
      "id": "conversational-front-door",
      "name": "Conversational front door",
      "line": "A chatbot wired to your live data",
      "summary": "A chatbot wired to your live data, so customers ask instead of clicking around.",
      "for": "Teams that answer the same customer questions every day, and whose booking, stock or product data already lives in a system.",
      "description": "We build a chatbot that answers from your live data and your knowledge base, in your brand voice. It comes with written rules for when it hands over to a person, and the automations that carry out what a conversation starts.",
      "service_type": "AI chatbot and automation",
      "page": "/ai-automation/",
      "includes": ["A chatbot connected to live inventory or booking data", "Escalation rules and risk policy", "Knowledge base and brand voice", "The workflows behind it"],
      "pricing": "Setup fee + monthly retainer",
      "cta": "Enquire",
      "keywords": ["chatbot", "chat", "bot", "conversational", "front door", "live data", "support", "escalation", "voice", "assistant"]
    },
    {
      "id": "product-experience",
      "name": "Product experience builds",
      "line": "Try the product in the browser",
      "summary": "Let people experience the product in the browser instead of reading about it.",
      "for": "Brands whose product is easier to understand by trying it than by reading about it.",
      "description": "We build interactive product experiences that run in the browser: 3D demos, configurators and try-before-you-buy flows. Each one is scoped to the product and the devices it has to run on.",
      "service_type": "Interactive product experience development",
      "page": "/websites/",
      "includes": ["3D or interactive product demos", "Configurators", "Try-before-you-buy experiences"],
      "pricing": "Scoped per build",
      "cta": "Custom quote",
      "keywords": ["3d", "interactive", "configurator", "experience", "demo", "product", "try", "three.js", "immersive"]
    },
    {
      "id": "geo-aeo-ongoing",
      "name": "Ongoing GEO and AEO",
      "line": "Get cited when people ask AI for answers",
      "summary": "Getting your business cited when people ask AI assistants for answers.",
      "for": "Businesses that want to be named when customers ask Google, ChatGPT or Perplexity who to use.",
      "description": "A monthly programme that makes your business clear to search engines and AI assistants: entity and structured data work, pages worth citing built on your own data, third-party mentions, and tracking of where you appear in AI answers.",
      "service_type": "SEO, GEO and AEO",
      "page": "/seo-geo/",
      "includes": ["Entity clarity and structured data", "Cite-worthy pages built on original data", "Third-party mentions", "Monitoring your visibility in AI answers"],
      "pricing": "Monthly retainer",
      "cta": "Enquire",
      "keywords": ["geo", "aeo", "seo", "ai search", "chatgpt", "perplexity", "cited", "citations", "visibility", "rank", "ranking", "google"]
    }
  ],
  "pages": [
    {
      "id": "websites",
      "path": "/websites/",
      "label": "Websites",
      "title": "Agent-ready website design, Melbourne | Leapshot",
      "description": "Leapshot designs and builds agent-ready websites in Melbourne: Webflow, Astro and Next.js on a headless CMS, structured so people and AI agents can read them.",
      "service_name": "Agent-ready website design and build",
      "service_type": "Website design and development",
      "eyebrow": "Websites",
      "meta": "Webflow, Astro, Next.js, headless CMS",
      "h1": "Websites people and AI agents can both read.",
      "lede": "Leapshot is a Melbourne studio that designs and builds websites in Webflow, Astro and Next.js on a headless CMS. Every page is drawn from structured content, so the same facts reach search engines, AI assistants and your own chatbot.",
      "points_title": "What agent-ready means.",
      "points_lede": "A site is agent-ready when a machine can read the same facts a person can, and act on them.",
      "points": [
        {"id": "structured", "name": "Structured content first", "summary": "Products, services, offers and FAQs are modelled as records in a headless CMS before a page is designed. The site is one screen drawing from them."},
        {"id": "schema", "name": "Schema on every page", "summary": "JSON-LD describes the business, its services and its answers, so search engines and AI assistants do not have to guess."},
        {"id": "endpoints", "name": "Files and endpoints for agents", "summary": "An llms.txt file, a public content model and an /ask or MCP endpoint let AI agents read the site and act on it."},
        {"id": "stack", "name": "The stack that fits", "summary": "Webflow when your team wants to edit pages visually. Astro or Next.js when speed, integrations or a custom front end matter more. We choose with you."},
        {"id": "system", "name": "A design system, not templates", "summary": "Design tokens and components are built once and reused, so every new page stays on brand. Ours is published in full on this site."},
        {"id": "lean", "name": "Lean and accessible", "summary": "Pages that work without JavaScript, self-hosted fonts, and colour contrast checked every time the site is built."}
      ],
      "service_ids": ["websites", "headless", "brand-systems"],
      "package_ids": ["agent-ready-site", "product-experience"],
      "faqs": [
        {"id": "platforms", "q": "Which platforms do you build websites on?", "a": "Webflow, Astro and Next.js, usually with a headless CMS behind them. Webflow suits teams that want to edit pages visually. Astro and Next.js suit sites that need speed, a custom front end or deeper integrations. We recommend one after mapping your content and tools."},
        {"id": "agent-ready", "q": "What makes a website agent-ready?", "a": "Its content is structured so AI assistants can read it and act on it: schema (JSON-LD) on every page, an llms.txt file, and an /ask or MCP endpoint. People get a fast, clear site. Agents get the same facts as data."},
        {"id": "headless", "q": "What is a headless CMS?", "a": "A content system that stores your products, services, offers and FAQs as structured records, separate from any one page design. The website draws from it, and so can your chatbot, ads, email and AI agents."},
        {"id": "rebuild", "q": "Can you rebuild our existing website?", "a": "Yes. We map your current content into a structured model first, then rebuild the site on top of it. Existing URLs are kept or redirected one to one, so links to the old site keep working."},
        {"id": "cost", "q": "How much does a website cost?", "a": "Every build is quoted individually. The Agent-ready site package is a setup fee to build the site and a monthly retainer to run and improve it. Enquire and we will come back with a custom quote."}
      ]
    },
    {
      "id": "ai-automation",
      "path": "/ai-automation/",
      "label": "AI automation",
      "title": "AI automation and chatbots, Melbourne | Leapshot",
      "description": "Leapshot builds AI automation from Melbourne: chatbots on live data, ops automation, integrations, knowledge systems and training for Australian teams.",
      "service_name": "AI automation and chatbots",
      "service_type": "AI automation",
      "eyebrow": "AI automation",
      "meta": "Chatbots, ops, integrations, knowledge, training",
      "h1": "AI automation your team can run.",
      "lede": "Leapshot builds chatbots wired to live data, the ops automation and integrations behind them, governed knowledge systems, and the training your team needs to run it all. We are based in Melbourne and work across Australia.",
      "points_title": "What we automate.",
      "points_lede": "Automation takes the repeated work. Your people keep the judgement calls and approve what goes out.",
      "points": [
        {"id": "chatbots", "name": "Chatbots", "summary": "A conversational front door that answers from your live booking, stock or product data, in your brand voice, with rules for when it hands over to a person."},
        {"id": "ops", "name": "Ops automation", "summary": "The repeated work behind the front door: routing enquiries, updating records and drafting replies, with an approval step wherever a person should decide."},
        {"id": "integrations", "name": "Integrations", "summary": "Wiring between the tools you already use, including the older systems that have no tidy way in."},
        {"id": "knowledge", "name": "Knowledge systems", "summary": "A governed source of truth that your AI tools draft from, so answers stay accurate and on brand."},
        {"id": "training", "name": "Agent training", "summary": "Workshops, approval gates and a written operating model, so your people can run, check and extend the system."},
        {"id": "ownership", "name": "No vendor lock-in", "summary": "AI models sit behind swappable adapters. The knowledge base, the rules and the workflows stay yours."}
      ],
      "service_ids": ["chatbots", "ops-automation", "knowledge-systems", "agent-ops"],
      "package_ids": ["conversational-front-door"],
      "faqs": [
        {"id": "small-team", "q": "What can AI automation do for a small team?", "a": "It takes on repeated work: answering common customer questions, routing enquiries, updating records and drafting first versions. Your team keeps the judgement calls and approves what goes out."},
        {"id": "accuracy", "q": "Will a chatbot make things up?", "a": "We build it to answer from your knowledge base and live data, and to follow escalation rules that hand the conversation to a person when it is unsure or the topic is sensitive. We write that risk policy with you before launch."},
        {"id": "tools", "q": "Which tools do you integrate with?", "a": "We start from the tools you already use for bookings, stock, customers, email and messaging. Where a system has an API we connect to it. Where it does not, we look for a workable route and tell you plainly what we find."},
        {"id": "training", "q": "Do you train our team?", "a": "Yes. Training is one of the five layers we build. Your people learn to run, approve and extend the system through workshops and a written operating model."},
        {"id": "cost", "q": "How is AI automation priced?", "a": "A setup fee to build the system, then a monthly retainer to run and improve it. Every build is scoped to your tools and data, so enquire for a custom quote."}
      ]
    },
    {
      "id": "seo-geo",
      "path": "/seo-geo/",
      "label": "SEO and GEO",
      "title": "Local SEO, GEO and AEO, Melbourne | Leapshot",
      "description": "Local SEO, GEO and AEO from a Melbourne studio. Leapshot makes your business clear to Google and AI assistants, and works to get it cited in AI answers.",
      "service_name": "Local SEO, GEO and AEO",
      "service_type": "Search engine optimisation",
      "eyebrow": "SEO, GEO and AEO",
      "meta": "Local SEO, GEO, AEO, AI citations",
      "h1": "Found in search. Cited in AI answers.",
      "lede": "Leapshot does local SEO, GEO (generative engine optimisation) and AEO (answer engine optimisation) for Australian businesses, from Melbourne. The work is the same at heart: make the business clear, publish pages worth citing, and earn mentions elsewhere.",
      "points_title": "What the work is.",
      "points_lede": "Search engines and AI assistants lean on the same things: clear facts, real proof and what others say about you.",
      "points": [
        {"id": "local", "name": "Local SEO", "summary": "Google Business Profile, reviews, photos and local pages, built on real proof that AI cannot fake."},
        {"id": "entity", "name": "Entity clarity", "summary": "Who you are, where you are and what you do, stated the same way in your pages, your schema and your profiles."},
        {"id": "data", "name": "Structured data", "summary": "JSON-LD for the organisation, its services and its FAQs, so machines read facts instead of inferring them."},
        {"id": "pages", "name": "Cite-worthy pages", "summary": "Pages built on your own data and direct answers, written so an assistant can quote them."},
        {"id": "mentions", "name": "Third-party mentions", "summary": "Assistants draw on what other sites say about you, so we work on earning mentions in the places that matter to your field."},
        {"id": "monitoring", "name": "Monitoring", "summary": "We track where your business appears in search and in AI answers, and adjust the work from what we see."}
      ],
      "service_ids": ["local-seo", "geo-aeo"],
      "package_ids": ["geo-aeo-ongoing"],
      "faqs": [
        {"id": "geo", "q": "What is GEO?", "a": "GEO stands for generative engine optimisation: making a business easy for AI assistants such as ChatGPT, Perplexity and Google's AI answers to understand, trust and cite. It builds on SEO rather than replacing it."},
        {"id": "aeo", "q": "What is AEO?", "a": "AEO stands for answer engine optimisation: structuring content as direct questions and answers so search engines and AI assistants can quote it. Clear definitions, FAQ content and schema do most of the work."},
        {"id": "cited", "q": "How do you get a business cited in AI answers?", "a": "There is no switch. We make the business clear with structured data, publish pages built on original data that are worth citing, earn third-party mentions, and monitor what assistants say. Nobody can guarantee a citation, and we do not promise one."},
        {"id": "still-seo", "q": "Do we still need SEO?", "a": "Yes. AI assistants lean on the same signals search engines do: clear pages, structured data, reviews and mentions. For a business that serves a place, local SEO and Google Business Profile remain the base."},
        {"id": "cost", "q": "How is ongoing GEO and AEO priced?", "a": "As a monthly retainer, quoted individually. Enquire and we will come back with a custom quote."}
      ]
    }
  ],
  "engine": {
    "id": "wildfield",
    "name": "Wildfield",
    "url": "https://wildfield.io",
    "status": "Launching November 2026",
    "line": "Launching November 2026",
    "operator": {
      "name": "PopCandi Creative Studio",
      "url": "https://popcandi.tv"
    },
    "summary": "Wildfield is a creative platform operated by PopCandi Creative Studio, Leapshot's sister studio, and Leapshot works with it. It makes AI motion and multi-format ads from a brand system, with an API and MCP surface.",
    "principle": "Own the layer that is hard to copy, rent everything else.",
    "principle_detail": "Your brand system, content model and approvals stay yours. AI models sit behind swappable adapters.",
    "features": [
      { "id": "motion", "name": "AI motion", "summary": "Motion built from your brand's own recipes, so every piece moves like you." },
      { "id": "formats", "name": "Multi-format ads", "summary": "One idea, resized and versioned for every placement." },
      { "id": "surface", "name": "API and MCP surface", "summary": "Your tools and AI agents can call Wildfield directly." }
    ],
    "cta": "Enquire",
    "keywords": ["wildfield", "tool", "software", "platform", "models", "launch", "november", "api", "mcp", "who runs wildfield", "who operates wildfield", "who owns wildfield", "who is behind wildfield"]
  },
  "services": [
    { "id": "brand-systems", "name": "Brand identity and design systems", "summary": "Positioning, naming and the system that AI tools consume.", "keywords": ["brand", "identity", "logo", "design system", "tokens", "branding"] },
    { "id": "motion-ads", "name": "Motion graphics and multi-format ads", "summary": "Brand motion language and ads resized and versioned for every placement.", "keywords": ["motion", "animation", "resize", "formats", "ads", "video ads"] },
    { "id": "social-creative", "name": "Social creative at volume", "summary": "Content systems with strategy, approvals and community voice baked in.", "keywords": ["social", "content", "instagram", "tiktok", "posts", "volume"] },
    { "id": "ai-ugc", "name": "AI UGC ads", "summary": "Offer, angle and test discipline, with disclosure and compliance handled.", "keywords": ["ugc", "creator", "ai ugc", "testimonial"] },
    { "id": "paid-media", "name": "Paid media on Meta and Google", "summary": "Offer, landing scent, measurement, budget calls and creative judgement.", "keywords": ["paid", "meta", "facebook", "google ads", "ppc", "media", "advertising", "campaigns"] },
    { "id": "websites", "name": "Websites in Astro and Next.js", "summary": "A lean trust layer focused on conversion, content and integrations.", "keywords": ["website", "webflow", "astro", "nextjs", "next.js", "web", "site"] },
    { "id": "headless", "name": "Headless CMS and ecommerce", "summary": "The content model that feeds site, chatbot and ads from one source of truth.", "keywords": ["headless", "cms", "sanity", "ecommerce", "shop", "stripe", "store"] },
    { "id": "local-seo", "name": "Local SEO and Google Business Profile", "summary": "Real reviews, photos and local proof that AI cannot fake.", "keywords": ["local", "seo", "gbp", "google business", "maps", "reviews"] },
    { "id": "geo-aeo", "name": "GEO and AEO", "summary": "Original data, third-party mentions and cite-worthy pages so AI answers mention you.", "keywords": ["geo", "aeo", "chatgpt", "perplexity", "ai search", "cited", "answer engine"] },
    { "id": "chatbots", "name": "Chatbots and auto-replies", "summary": "Knowledge base, escalation rules, voice and risk policy, not just the build.", "keywords": ["chatbot", "bot", "auto reply", "messaging", "support", "chat"] },
    { "id": "ops-automation", "name": "Ops automation and integrations", "summary": "Workflow automation and the legacy wiring that still needs a person.", "keywords": ["automation", "n8n", "integration", "workflow", "ops", "zapier", "api"] },
    { "id": "knowledge-systems", "name": "AI knowledge and content systems", "summary": "A governed source of truth your AI tools draft from, with approvals built in.", "keywords": ["knowledge", "compliance", "governance", "governed", "approvals"] },
    { "id": "agent-ops", "name": "Agent ops and team training", "summary": "Operating model, approval gates, workshops and training for your team.", "keywords": ["training", "workshop", "agents", "team", "teach", "upskill", "agent ops"] }
  ],
  "faqs": [
    { "id": "pricing", "q": "How is Leapshot priced?", "a": "A setup fee to build the system, then a monthly retainer to run and improve it. We do not sell hours. Every build is scoped to your tools and data, so enquire and we will come back with a custom quote.", "keywords": ["price", "pricing", "priced", "cost", "how much", "fee", "retainer", "budget", "rates", "expensive", "quote", "monthly"] },
    { "id": "replace", "q": "Is this about replacing my team?", "a": "No. The point is your team, multiplied. We build the system, then train your people to run it, approve it and extend it.", "keywords": ["replace", "replacing", "jobs", "staff", "team", "people", "redundant", "headcount"] },
    { "id": "agent-ready", "q": "What does agent-ready actually mean?", "a": "Your content is structured so AI assistants can read it and act on it: schema (JSON-LD) on every page, an llms.txt file, and an /ask or MCP endpoint. This site is a small example. Switch on Agent view in the menu to see what an agent reads.", "keywords": ["agent ready", "agent-ready", "agents", "ai agents", "machine readable", "what is", "mean", "what does agent-ready mean"] },
    { "id": "headless", "q": "What is a headless website?", "a": "Your content lives in one structured source, and the website is just one screen drawing from it. The same products, offers and FAQs also feed your chatbot, ads, email and AI agents. Change it once and it changes everywhere.", "keywords": ["headless", "source of truth", "one place", "cms", "single source"] },
    { "id": "llms", "q": "Is llms.txt worth it?", "a": "It costs very little to add, and the benefit is not proven yet. We include it because it is cheap insurance, but we put the real effort into schema, cite-worthy content and agent endpoints.", "keywords": ["llms.txt", "llms", "llm txt"] },
    { "id": "lock-in", "q": "Will I be locked into one AI vendor?", "a": "No. You own the brand system, content model and approval flow. AI models, speech and language tools sit behind adapters, so we can swap them when a better or cheaper one appears.", "keywords": ["lock", "locked", "vendor", "openai", "own", "ownership", "switch", "model"] },
    { "id": "website-still", "q": "Do you still build normal websites?", "a": "Yes, as a lean trust layer. We just do not lead with it. People increasingly want to ask, try or experience a product rather than click through ten pages.", "keywords": ["normal website", "brochure", "pages", "still build", "regular site"] },
    { "id": "examples", "q": "Can we see examples of your work?", "a": "We don't show client work. Most of our builds are covered by NDAs, so we keep them private. The working example is the site itself: it runs on the same layers we build, from design tokens and a component library to structured content, this chat and an agent layer. The systems we build include chatbots wired to live booking data, sites and ads fed from one content source, and approval flows that keep a person in the loop. Enquire and we will walk you through what fits.", "keywords": ["case studies", "case study", "clients", "client", "proof", "portfolio", "examples", "your work", "who have you worked with", "results", "references"] },
    { "id": "design-system", "q": "Is your own brand built this way?", "a": "Yes. Every page here is composed from one set of design tokens and one component library, published at /system/. The same tokens are readable by AI tools at /tokens.json.", "keywords": ["design system", "style guide", "tokens", "components", "brand guidelines", "own brand"] },
    { "id": "film", "q": "Do you shoot video or do colour grading?", "a": "That is PopCandi, our sister studio, at popcandi.tv. Film, video, colour, editing and VFX live there. Leapshot handles the systems, design and automation.", "keywords": ["film", "shoot", "video production", "colour", "color", "grading", "edit", "vfx", "popcandi", "tvc"] },
    { "id": "start", "q": "How do we start?", "a": "Enquire. We map your current tools and data, pick the first layer that will make the biggest difference, and scope the setup and monthly from there.", "keywords": ["start", "begin", "next step", "onboard", "how does it work", "timeline", "how long"] },
    { "id": "who", "q": "Who is behind Leapshot?", "a": "Leapshot is a Melbourne studio led by Fagan Wilcox. It spun out of PopCandi in October 2026 to focus on design, web and AI automation.", "keywords": ["who", "founder", "fagan", "about", "behind", "company", "where", "melbourne", "based", "location"] }
  ],
  "enquiry": {
    "label": "Enquire",
    "page": "/enquire/",
    "email": "fagan@popcandi.tv",
    "subject": "Leapshot enquiry",
    "note": "Tell us about the business and what you would like to multiply. We reply with next steps and a custom quote.",
    "sent": "Thanks. Your enquiry is on its way to us, and we reply by email with next steps and a custom quote.",
    "keywords": ["book", "call", "meeting", "contact", "talk", "chat with", "email", "get in touch", "hire", "enquire", "enquiry", "inquire", "consult", "custom quote"]
  },
  "agent_layer": {
    "content": "/content.json",
    "llms": "/llms.txt",
    "tokens": "/tokens.json",
    "design_system": "/system/",
    "manifest": "/site.webmanifest",
    "sitemap": "/sitemap-index.xml"
  }
}
