<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:image="http://www.google.com/schemas/sitemap-image/1.1">
  <url>
    <loc>https://www.leeonex.com/services/website-development</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/website-development.webp</image:loc>
      <image:title>Website &amp; Landing Page Development</image:title>
      <image:caption>Analytics dashboard on a laptop illustrating a marketing website workflow</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/web-design.webp</image:loc>
      <image:title>Website &amp; Landing Page Development</image:title>
      <image:caption>Browser windows showing a website design layout</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/laptop-desk.webp</image:loc>
      <image:title>Website &amp; Landing Page Development</image:title>
      <image:caption>Laptop on a desk used for website content work</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/workspace.webp</image:loc>
      <image:title>Website &amp; Landing Page Development</image:title>
      <image:caption>Team workspace with screens for digital product design</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/mvp-development</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/mvp-development.webp</image:loc>
      <image:title>MVP / SaaS Product Development</image:title>
      <image:caption>SaaS analytics charts on a screen during product planning</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/web-application-development.webp</image:loc>
      <image:title>MVP / SaaS Product Development</image:title>
      <image:caption>Smartphone showing a SaaS-style mobile interface</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/custom-web-app-development.webp</image:loc>
      <image:title>MVP / SaaS Product Development</image:title>
      <image:caption>Laptop with code editor open during an MVP build</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/meeting.webp</image:loc>
      <image:title>MVP / SaaS Product Development</image:title>
      <image:caption>Team reviewing product scope around a table</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/ai-automation-services</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/ai-automation-services.webp</image:loc>
      <image:title>AI Automations &amp; AI-Powered Features</image:title>
      <image:caption>Robot and human collaboration illustrating practical AI workflows</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/engineer.webp</image:loc>
      <image:title>AI Automations &amp; AI-Powered Features</image:title>
      <image:caption>Engineer working on systems that can host AI features</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/laptop-code.webp</image:loc>
      <image:title>AI Automations &amp; AI-Powered Features</image:title>
      <image:caption>Code on a laptop during automation development</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/mvp-development.webp</image:loc>
      <image:title>AI Automations &amp; AI-Powered Features</image:title>
      <image:caption>Charts that often sit behind AI-assisted reporting</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/web-application-development</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/web-application-development.webp</image:loc>
      <image:title>Full-Stack Web Applications</image:title>
      <image:caption>Mobile and web application interfaces on a dark display</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/custom-web-app-development.webp</image:loc>
      <image:title>Full-Stack Web Applications</image:title>
      <image:caption>Full-stack development environment on a laptop</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/collab.webp</image:loc>
      <image:title>Full-Stack Web Applications</image:title>
      <image:caption>Product and engineering collaboration on a web app</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/mobile-app-development</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/mobile-app-development.webp</image:loc>
      <image:title>Mobile App Development</image:title>
      <image:caption>Smartphone held in hand showing a mobile app interface</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/web-application-development.webp</image:loc>
      <image:title>Mobile App Development</image:title>
      <image:caption>App screens on a device during design review</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/workspace.webp</image:loc>
      <image:title>Mobile App Development</image:title>
      <image:caption>Product team workspace supporting mobile delivery</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/dashboard-development</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/dashboard-development.webp</image:loc>
      <image:title>Dashboards &amp; Analytics</image:title>
      <image:caption>Business analytics charts on a widescreen monitor</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/mvp-development.webp</image:loc>
      <image:title>Dashboards &amp; Analytics</image:title>
      <image:caption>Detailed analytics charts for operational reporting</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/laptop-desk.webp</image:loc>
      <image:title>Dashboards &amp; Analytics</image:title>
      <image:caption>Laptop used to review reporting dashboards</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/dedicated-development-team</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/dedicated-development-team.webp</image:loc>
      <image:title>Dedicated Development Teams</image:title>
      <image:caption>Engineering team collaborating around laptops</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/collab.webp</image:loc>
      <image:title>Dedicated Development Teams</image:title>
      <image:caption>Cross-functional team working through a delivery plan</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/meeting.webp</image:loc>
      <image:title>Dedicated Development Teams</image:title>
      <image:caption>Standup-style meeting for ongoing development support</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/team-board.webp</image:loc>
      <image:title>Dedicated Development Teams</image:title>
      <image:caption>Team reviewing work on a shared board</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/landing-page-development</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/landing-page-development.webp</image:loc>
      <image:title>Landing Page Development Services</image:title>
      <image:caption>Leeonex landing page development campaign layout on a laptop screen</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/web-design.webp</image:loc>
      <image:title>Landing Page Development Services</image:title>
      <image:caption>Landing page layout exploration on screen</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/laptop-desk.webp</image:loc>
      <image:title>Landing Page Development Services</image:title>
      <image:caption>Campaign page content work on a laptop</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/landing-convert/research.png</image:loc>
      <image:title>Landing page research and heatmap insights</image:title>
      <image:caption>Leeonex landing page development research illustration with heatmap and analytics insights</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/landing-convert/copywriting.png</image:loc>
      <image:title>Landing page conversion copywriting</image:title>
      <image:caption>Leeonex landing page development copywriting illustration focused on messaging and CTAs</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/landing-convert/branding.png</image:loc>
      <image:title>Landing page brand integration</image:title>
      <image:caption>Leeonex landing page development branding illustration across campaign devices</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/landing-convert/testing.png</image:loc>
      <image:title>Landing page conversion testing</image:title>
      <image:caption>Leeonex landing page development testing illustration with layout variants</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/landing-convert/intelligence.png</image:loc>
      <image:title>Landing page optimization intelligence</image:title>
      <image:caption>Leeonex landing page development analytics and optimization illustration</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/landing-convert/reporting.png</image:loc>
      <image:title>Landing page performance reporting</image:title>
      <image:caption>Leeonex landing page development reporting illustration with performance charts</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/landing-lead-delivery/landing-lead-delivery.png</image:loc>
      <image:title>Landing page lead delivery integrations</image:title>
      <image:caption>Leeonex lead delivery diagram routing form submits to Email, WhatsApp, Slack, Notion, CRM, and more</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/landing-convert/cta-mascot.png</image:loc>
      <image:title>Leeonex landing page conversion CTA</image:title>
      <image:caption>Leeonex mascot celebrating landing page development conversions</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/workspace.webp</image:loc>
      <image:title>Landing page development event concept</image:title>
      <image:caption>Leeonex concept event landing page development workspace mockup</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/landing-works/work-01.png</image:loc>
      <image:title>Architecture studio landing page concept</image:title>
      <image:caption>Leeonex concept architecture studio landing page development design</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/landing-works/work-02.png</image:loc>
      <image:title>Contract SaaS landing page concept</image:title>
      <image:caption>Leeonex concept SaaS contract management landing page development</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/landing-works/work-03.png</image:loc>
      <image:title>Marketing talent landing page concept</image:title>
      <image:caption>Leeonex concept marketing talent marketplace landing page</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/landing-works/work-04.png</image:loc>
      <image:title>Cargo logistics landing page concept</image:title>
      <image:caption>Leeonex concept logistics and cargo landing page development</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/landing-works/work-05.png</image:loc>
      <image:title>Fitness app landing page concept</image:title>
      <image:caption>Leeonex concept fitness app landing page development</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/landing-works/work-06.png</image:loc>
      <image:title>Budgeting app landing page concept</image:title>
      <image:caption>Leeonex concept budgeting app landing page development</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/landing-works/work-07.png</image:loc>
      <image:title>Mental health AI landing page concept</image:title>
      <image:caption>Leeonex concept AI mental health landing page development</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/landing-works/work-08.png</image:loc>
      <image:title>Travel planner landing page concept</image:title>
      <image:caption>Leeonex concept travel planning landing page development</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/landing-works/work-09.png</image:loc>
      <image:title>Travel destinations landing page concept</image:title>
      <image:caption>Leeonex concept travel destinations landing page development</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/landing-works/work-10.png</image:loc>
      <image:title>Online pharmacy landing page concept</image:title>
      <image:caption>Leeonex concept online pharmacy landing page development</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/website-development/company-website-development</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/company-website-development.webp</image:loc>
      <image:title>Company Website Development</image:title>
      <image:caption>Company website design shown on a desktop display</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/workspace.webp</image:loc>
      <image:title>Company Website Development</image:title>
      <image:caption>Company website design workspace</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/meeting.webp</image:loc>
      <image:title>Company Website Development</image:title>
      <image:caption>Stakeholders reviewing website structure</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/website-development/cms-website-development</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/cms-website-development.webp</image:loc>
      <image:title>CMS Website Development</image:title>
      <image:caption>Editable CMS marketing website interface</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/collab.webp</image:loc>
      <image:title>CMS Website Development</image:title>
      <image:caption>Editors collaborating on CMS content</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/custom-web-app-development.webp</image:loc>
      <image:title>CMS Website Development</image:title>
      <image:caption>CMS template development in a code editor</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/mvp-development/mvp-scoping</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/mvp-scoping.webp</image:loc>
      <image:title>Product Ideation &amp; MVP Scoping</image:title>
      <image:caption>Product ideation notes and scope planning workspace</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/team-board.webp</image:loc>
      <image:title>Product Ideation &amp; MVP Scoping</image:title>
      <image:caption>Product ideation on a shared planning board</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/meeting.webp</image:loc>
      <image:title>Product Ideation &amp; MVP Scoping</image:title>
      <image:caption>Founders aligning on MVP scope</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/mvp-development/rapid-mvp-development</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/rapid-mvp-development.webp</image:loc>
      <image:title>MVP Development</image:title>
      <image:caption>MVP product interface under development on a laptop</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/custom-web-app-development.webp</image:loc>
      <image:title>MVP Development</image:title>
      <image:caption>MVP engineering work in a code editor</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/web-application-development.webp</image:loc>
      <image:title>MVP Development</image:title>
      <image:caption>Early product UI on a device</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/mvp-development/saas-platform-development</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/saas-platform-development.webp</image:loc>
      <image:title>SaaS Platform Development</image:title>
      <image:caption>Multi-user SaaS platform dashboard on screen</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/web-application-development.webp</image:loc>
      <image:title>SaaS Platform Development</image:title>
      <image:caption>Multi-user SaaS interface on a device</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/mvp-development.webp</image:loc>
      <image:title>SaaS Platform Development</image:title>
      <image:caption>Platform metrics used after launch</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/ai-automation-services/ai-workflow-automation</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/ai-workflow-automation.webp</image:loc>
      <image:title>AI Workflow Automation</image:title>
      <image:caption>AI workflow automation board on a laptop</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/engineer.webp</image:loc>
      <image:title>AI Workflow Automation</image:title>
      <image:caption>Engineer implementing automation systems</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/laptop-code.webp</image:loc>
      <image:title>AI Workflow Automation</image:title>
      <image:caption>Workflow automation logic under development</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/ai-automation-services/ai-feature-development</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/ai-feature-development.webp</image:loc>
      <image:title>AI Product Feature Development</image:title>
      <image:caption>AI product feature UI with assistant-style panel</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/laptop-code.webp</image:loc>
      <image:title>AI Product Feature Development</image:title>
      <image:caption>AI feature integration in a product codebase</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/web-application-development.webp</image:loc>
      <image:title>AI Product Feature Development</image:title>
      <image:caption>In-product AI surface on a device</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/ai-automation-services/ai-consulting</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/ai-consulting.webp</image:loc>
      <image:title>AI Consulting</image:title>
      <image:caption>Team reviewing AI feasibility notes in a meeting</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/meeting.webp</image:loc>
      <image:title>AI Consulting</image:title>
      <image:caption>Consulting session on AI feasibility</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/collab.webp</image:loc>
      <image:title>AI Consulting</image:title>
      <image:caption>Team reviewing AI use-case priorities</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/web-application-development/custom-web-app-development</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/custom-web-app-development.webp</image:loc>
      <image:title>Custom Web App Development</image:title>
      <image:caption>Custom web application screens on a developer desk</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/workspace.webp</image:loc>
      <image:title>Custom Web App Development</image:title>
      <image:caption>Full-stack product workspace</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/web-application-development/admin-panel-development</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/website-development.webp</image:loc>
      <image:title>Portal &amp; Admin Panel Development</image:title>
      <image:caption>Admin portal tables and role-based controls</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/laptop-desk.webp</image:loc>
      <image:title>Portal &amp; Admin Panel Development</image:title>
      <image:caption>Admin portal work on a laptop</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/mvp-development.webp</image:loc>
      <image:title>Portal &amp; Admin Panel Development</image:title>
      <image:caption>Operator views inside an admin panel</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/web-application-development/api-integration-services</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/api-integration-services.webp</image:loc>
      <image:title>API &amp; Integration Development</image:title>
      <image:caption>API integration diagrams and connected systems</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/engineer.webp</image:loc>
      <image:title>API &amp; Integration Development</image:title>
      <image:caption>Engineer connecting systems and APIs</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/laptop-code.webp</image:loc>
      <image:title>API &amp; Integration Development</image:title>
      <image:caption>Integration code and connector logic</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/mobile-app-development/native-app-development</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/native-app-development.webp</image:loc>
      <image:title>Native iOS &amp; Android App Development</image:title>
      <image:caption>Native mobile app interface on a smartphone</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/mobile-app-development.webp</image:loc>
      <image:title>Native iOS &amp; Android App Development</image:title>
      <image:caption>Native mobile app UI close-up</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/workspace.webp</image:loc>
      <image:title>Native iOS &amp; Android App Development</image:title>
      <image:caption>Native app product team workspace</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/mobile-app-development/cross-platform-app-development</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/cross-platform-app-development.webp</image:loc>
      <image:title>Cross-Platform App Development</image:title>
      <image:caption>Cross-platform mobile app UI on phone and tablet</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/web-application-development.webp</image:loc>
      <image:title>Cross-Platform App Development</image:title>
      <image:caption>Cross-platform app screens during review</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/custom-web-app-development.webp</image:loc>
      <image:title>Cross-Platform App Development</image:title>
      <image:caption>Shared mobile codebase in development</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/mobile-app-development/app-maintenance-and-support</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/app-maintenance-and-support.webp</image:loc>
      <image:title>Mobile App Support &amp; Maintenance</image:title>
      <image:caption>Mobile app maintenance and release checklist on screen</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/mobile-app-development.webp</image:loc>
      <image:title>Mobile App Support &amp; Maintenance</image:title>
      <image:caption>Live app UI under maintenance review</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/team-board.webp</image:loc>
      <image:title>Mobile App Support &amp; Maintenance</image:title>
      <image:caption>Support cadence board for a live app</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/dashboard-development/analytics-dashboard-development</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/mvp-development.webp</image:loc>
      <image:title>Analytics Dashboard Development</image:title>
      <image:caption>Analytics dashboard with charts and KPI filters</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/dashboard-development.webp</image:loc>
      <image:title>Analytics Dashboard Development</image:title>
      <image:caption>Widescreen analytics dashboard</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/dashboard-development/operations-reporting</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/dashboard-development.webp</image:loc>
      <image:title>Operations Reporting Tools</image:title>
      <image:caption>Operations reporting board with status queues</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/laptop-desk.webp</image:loc>
      <image:title>Operations Reporting Tools</image:title>
      <image:caption>Ops reporting reviewed on a laptop</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/team-board.webp</image:loc>
      <image:title>Operations Reporting Tools</image:title>
      <image:caption>Operations status tracked on a shared board</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/dashboard-development/data-visualization</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/data-visualization.webp</image:loc>
      <image:title>Data Visualization Design</image:title>
      <image:caption>Data visualization charts for executive review</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/mvp-development.webp</image:loc>
      <image:title>Data Visualization Design</image:title>
      <image:caption>Data visualization charts for complex data</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/web-design.webp</image:loc>
      <image:title>Data Visualization Design</image:title>
      <image:caption>Visual system exploration for chart layouts</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/dedicated-development-team/it-staff-augmentation</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/it-staff-augmentation.webp</image:loc>
      <image:title>Staff Augmentation Developers</image:title>
      <image:caption>Developers collaborating in a shared product standup</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/collab.webp</image:loc>
      <image:title>Staff Augmentation Developers</image:title>
      <image:caption>Augmented engineer joining an existing team</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/custom-web-app-development.webp</image:loc>
      <image:title>Staff Augmentation Developers</image:title>
      <image:caption>Developer delivering inside a client stack</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/dedicated-development-team/dedicated-development-squads</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/heroes/dedicated-development-team.webp</image:loc>
      <image:title>Dedicated Development Squads</image:title>
      <image:caption>Dedicated product squad reviewing a roadmap board</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/meeting.webp</image:loc>
      <image:title>Dedicated Development Squads</image:title>
      <image:caption>Dedicated squad delivery cadence meeting</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/team-board.webp</image:loc>
      <image:title>Dedicated Development Squads</image:title>
      <image:caption>Squad roadmap tracked on a shared board</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/services/dedicated-development-team/software-project-rescue</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/services/offerings/software-project-rescue.webp</image:loc>
      <image:title>Software Project Rescue</image:title>
      <image:caption>Engineering team diagnosing a delayed software project</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/engineer.webp</image:loc>
      <image:title>Software Project Rescue</image:title>
      <image:caption>Engineer diagnosing a troubled codebase</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/services/gallery/collab.webp</image:loc>
      <image:title>Software Project Rescue</image:title>
      <image:caption>Rescue team aligning on stabilization priorities</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/landing-page-or-mvp-first</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/landing-page-or-mvp-first/landing-page-or-mvp-first-featured.webp</image:loc>
      <image:title>Landing page or MVP first</image:title>
      <image:caption>The right first version depends on the uncertainty you need to reduce—not the amount of product you can build.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/landing-page-or-mvp-first/evidence-before-build.webp</image:loc>
      <image:title>Evidence before product scope</image:title>
      <image:caption>Different artifacts answer different questions: interest, comprehension, delivery, and repeated use are not interchangeable evidence.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/landing-page-or-mvp-first/landing-page-or-mvp-decision-map.svg</image:loc>
      <image:title>Landing page or MVP decision map</image:title>
      <image:caption>Match the first version to the next decision: landing page, prototype, manual pilot, or focused MVP.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/landing-page-or-mvp-first/first-version-scope-checklist.svg</image:loc>
      <image:title>First-version scope checklist</image:title>
      <image:caption>A useful first version proves one hypothesis, works along one core path, and defers everything that does not strengthen the evidence.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/ai-workflow-automation-readiness-checklist</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ai-workflow-automation-readiness-checklist/ai-workflow-automation-readiness-featured.webp</image:loc>
      <image:title>AI workflow automation readiness audit</image:title>
      <image:caption>A useful workflow audit separates work that is ready for narrow automation from decisions that need people—or a process that needs repair first.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ai-workflow-automation-readiness-checklist/ai-automation-readiness-scorecard.svg</image:loc>
      <image:title>AI automation readiness scorecard</image:title>
      <image:caption>Score one workflow across repeatability, inputs, volume, outcomes, failure containment, and integration access.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ai-workflow-automation-readiness-checklist/human-approval-workflow.webp</image:loc>
      <image:title>Human approval inside an AI workflow</image:title>
      <image:caption>Human review is most useful when it is a designed routing state with clear context—not an informal promise that someone will check later.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ai-workflow-automation-readiness-checklist/human-in-the-loop-architecture.svg</image:loc>
      <image:title>Controlled human-in-the-loop AI architecture</image:title>
      <image:caption>A production workflow validates inputs, constrains the AI step, routes by risk, records decisions, and keeps high-impact actions under human control.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/dashboard-data-readiness-checklist</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/dashboard-data-readiness-checklist/dashboard-data-readiness-featured.webp</image:loc>
      <image:title>Dashboard data readiness audit</image:title>
      <image:caption>A useful dashboard project validates definitions, sources, quality, and ownership before investing in the interface.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/dashboard-data-readiness-checklist/dashboard-data-readiness-scorecard.svg</image:loc>
      <image:title>Dashboard data readiness scorecard</image:title>
      <image:caption>Score one dashboard use case across decision clarity, metric definition, source authority, data quality, refresh fitness, and ownership.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/dashboard-data-readiness-checklist/disconnected-sources-to-trusted-data.webp</image:loc>
      <image:title>From disconnected sources to trusted dashboard data</image:title>
      <image:caption>The reporting layer becomes trustworthy only after each source is mapped, validated, reconciled, and assigned an owner.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/dashboard-data-readiness-checklist/metric-contract-template.svg</image:loc>
      <image:title>Dashboard metric contract template</image:title>
      <image:caption>A metric contract turns a familiar KPI label into an implementable, testable definition shared by business and development teams.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/replace-spreadsheet-with-internal-tool</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/replace-spreadsheet-with-internal-tool/spreadsheet-to-internal-tool-featured.webp</image:loc>
      <image:title>From spreadsheet workflow to internal tool</image:title>
      <image:caption>Replace a spreadsheet only when the operating requirements—not the appearance of rows and columns—justify a more controlled system.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/replace-spreadsheet-with-internal-tool/spreadsheet-workflow-pressure-scorecard.svg</image:loc>
      <image:title>Spreadsheet workflow pressure scorecard</image:title>
      <image:caption>Score the operating pressure around one workflow. A high score starts a replacement assessment; it does not automatically justify custom software.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/replace-spreadsheet-with-internal-tool/spreadsheet-migration-map.svg</image:loc>
      <image:title>Spreadsheet-to-internal-tool migration map</image:title>
      <image:caption>A safe migration preserves the workbook as evidence, validates rules and records, reconciles a parallel run, and names one system of record at cutover.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/replace-spreadsheet-with-internal-tool/internal-tool-first-release-worksheet.svg</image:loc>
      <image:title>Internal tool first-release worksheet</image:title>
      <image:caption>Define one operating loop before listing screens. The worksheet turns a familiar workbook into testable product requirements.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/native-vs-cross-platform-app</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/native-vs-cross-platform-app/native-vs-cross-platform-featured.webp</image:loc>
      <image:title>Native and cross-platform mobile architecture paths</image:title>
      <image:caption>Platform choice follows the product&apos;s real pressure points: shared workflows, device dependencies, experience differences, and the team that will maintain both releases.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/native-vs-cross-platform-app/mobile-platform-pressure-matrix.svg</image:loc>
      <image:title>Mobile platform pressure matrix</image:title>
      <image:caption>Score the features that create platform pressure. Investigate the highest-pressure items before choosing a framework.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/native-vs-cross-platform-app/mobile-architecture-sharing-map.svg</image:loc>
      <image:title>What a mobile product can and cannot share</image:title>
      <image:caption>Cross-platform is a sharing strategy, not a promise that every layer is identical. Backend services, product rules, interface code, and device adapters can have different boundaries.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/native-vs-cross-platform-app/mobile-architecture-spike-worksheet.svg</image:loc>
      <image:title>Mobile architecture spike worksheet</image:title>
      <image:caption>Test the riskiest device and experience requirements in a small technical spike before the architecture becomes expensive to reverse.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/website-redesign-or-rebuild</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/website-redesign-or-rebuild/website-redesign-or-rebuild-featured.webp</image:loc>
      <image:title>Website redesign or rebuild decision</image:title>
      <image:caption>A website decision becomes clearer when the surface, content structure, and technical foundation are assessed separately.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/website-redesign-or-rebuild/website-constraint-audit.svg</image:loc>
      <image:title>Website redesign and rebuild constraint audit</image:title>
      <image:caption>Audit evidence by layer. Surface problems lean toward redesign; structural and system blockers create a stronger case for a rebuild or staged hybrid.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/website-redesign-or-rebuild/website-preserve-replace-map.svg</image:loc>
      <image:title>Website preservation and migration map</image:title>
      <image:caption>A rebuild should not mean starting from zero. Preserve proven pages, assets, URLs, data, and integrations while replacing only the constraints.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/website-redesign-or-rebuild/website-rebuild-brief-worksheet.svg</image:loc>
      <image:title>Website redesign or rebuild brief worksheet</image:title>
      <image:caption>Complete one evidence-led brief before requesting estimates so every delivery option is solving the same business problem.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/refactor-or-rewrite-web-application</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/refactor-or-rewrite-web-application/refactor-or-rewrite-web-app-featured.webp</image:loc>
      <image:title>Refactor or rewrite a web application</image:title>
      <image:caption>A rescue decision should isolate the failing constraints and prove a safe migration slice before committing the whole product to a rewrite.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/refactor-or-rewrite-web-application/software-rescue-decision-matrix.svg</image:loc>
      <image:title>Software rescue decision matrix</image:title>
      <image:caption>Score the evidence, then investigate every severe constraint. The matrix frames a rescue review; it does not automate the architecture decision.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/refactor-or-rewrite-web-application/incremental-recovery-map.svg</image:loc>
      <image:title>Incremental web application recovery map</image:title>
      <image:caption>A safe recovery creates observable behaviour, stabilizes production, proves one boundary, and keeps rollback available while old and new paths coexist.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/refactor-or-rewrite-web-application/rescue-slice-worksheet.svg</image:loc>
      <image:title>Software rescue slice worksheet</image:title>
      <image:caption>Define a recovery slice around one business capability with explicit evidence, dependencies, verification, ownership, and rollback.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/staff-augmentation-vs-project-outsourcing</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/staff-augmentation-vs-project-outsourcing/staff-augmentation-vs-project-outsourcing-featured.webp</image:loc>
      <image:title>Staff augmentation and project delivery ownership paths</image:title>
      <image:caption>The useful distinction is not where the developers work. It is who owns priorities, team coordination, quality, acceptance, and the delivery outcome.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/staff-augmentation-vs-project-outsourcing/software-delivery-ownership-matrix.svg</image:loc>
      <image:title>Software delivery ownership matrix</image:title>
      <image:caption>Map each responsibility to the buyer, supplier, or a named shared decision before comparing rates or team profiles.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/staff-augmentation-vs-project-outsourcing/buyer-supplier-responsibility-map.svg</image:loc>
      <image:title>Buyer and supplier responsibility map</image:title>
      <image:caption>A workable engagement assigns decision rights across the full delivery system instead of assuming that accountability follows the contract label.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/staff-augmentation-vs-project-outsourcing/delivery-model-selection-worksheet.svg</image:loc>
      <image:title>Delivery model selection worksheet</image:title>
      <image:caption>Complete one page before procurement: it exposes whether the business needs capacity, a managed squad, a defined outcome, or discovery first.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/web-app-vs-mobile-app-first</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/web-app-vs-mobile-app-first/web-app-vs-mobile-app-first-featured.webp</image:loc>
      <image:title>Web app and mobile app first-release paths</image:title>
      <image:caption>Choose the first product surface from the user’s critical journey and the evidence you need—not from a default belief that every launch needs both.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/web-app-vs-mobile-app-first/first-platform-pressure-scorecard.svg</image:loc>
      <image:title>First-platform pressure scorecard</image:title>
      <image:caption>Score the critical journey, not the whole roadmap. One non-negotiable device or distribution constraint can outweigh several softer preferences.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/web-app-vs-mobile-app-first/web-mobile-release-sequencing-map.svg</image:loc>
      <image:title>Web and mobile release sequencing map</image:title>
      <image:caption>A first-platform decision should preserve the shared product foundation and define the evidence required before adding another client surface.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/web-app-vs-mobile-app-first/platform-spike-worksheet.svg</image:loc>
      <image:title>Web or mobile platform spike worksheet</image:title>
      <image:caption>Test the requirement that could reverse the platform decision, then stop the spike and decide using recorded evidence.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/ai-agent-vs-workflow-automation</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ai-agent-vs-workflow-automation/ai-agent-vs-workflow-automation-featured.webp</image:loc>
      <image:title>AI agent and workflow automation execution paths</image:title>
      <image:caption>The useful choice is rarely automation or autonomy everywhere. Keep the known path deterministic and give an agent only the bounded decisions that genuinely need interpretation.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ai-agent-vs-workflow-automation/automation-autonomy-pressure-matrix.svg</image:loc>
      <image:title>Automation autonomy pressure matrix</image:title>
      <image:caption>Score the task, not the technology. Ambiguity can justify model judgment, while consequence and reversibility should narrow what the system may do alone.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ai-agent-vs-workflow-automation/bounded-agent-execution-map.svg</image:loc>
      <image:title>Bounded agent execution map</image:title>
      <image:caption>A production design can place one adaptive step inside deterministic permissions, validation, escalation, and recording boundaries.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ai-agent-vs-workflow-automation/ai-automation-pilot-worksheet.svg</image:loc>
      <image:title>AI automation pilot worksheet</image:title>
      <image:caption>Define the pilot around representative cases and observable limits before connecting an agent to production actions.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/ipaas-vs-custom-api-integration</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ipaas-vs-custom-api-integration/ipaas-vs-custom-api-integration-featured.webp</image:loc>
      <image:title>iPaaS and custom API integration paths</image:title>
      <image:caption>Choose per integration boundary. Standard connectors and visible orchestration favor iPaaS; specialized rules, product-critical behavior, and deeper control can justify custom code.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ipaas-vs-custom-api-integration/integration-ownership-matrix.svg</image:loc>
      <image:title>Integration ownership matrix</image:title>
      <image:caption>The decision changes who owns connectors, orchestration, reliability controls, deployment, observability, and platform portability.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ipaas-vs-custom-api-integration/reliable-integration-boundary-map.svg</image:loc>
      <image:title>Reliable integration boundary map</image:title>
      <image:caption>A connector is only one part of the system. Reliable integration also needs identity, mapping, duplicate handling, recovery, reconciliation, and an operator path.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ipaas-vs-custom-api-integration/integration-decision-brief-worksheet.svg</image:loc>
      <image:title>Integration decision brief worksheet</image:title>
      <image:caption>Complete one brief per business-critical flow before comparing platforms, implementation estimates, or connector lists.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/how-to-scope-an-mvp</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/how-to-scope-an-mvp/how-to-scope-an-mvp-featured.webp</image:loc>
      <image:title>A focused MVP path through a larger product backlog</image:title>
      <image:caption>A useful MVP is not the product with the fewest cards. It is the smallest release that completes one valuable job, can be trusted and operated, and produces evidence for the next decision.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/how-to-scope-an-mvp/mvp-scope-boundary-scorecard.svg</image:loc>
      <image:title>MVP scope boundary scorecard</image:title>
      <image:caption>Judge every candidate against four inclusion tests. A feature belongs in v1 only when it enables the core job or makes that job safe, operable, or measurable.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/how-to-scope-an-mvp/mvp-first-release-flow-map.svg</image:loc>
      <image:title>Complete MVP first-release flow</image:title>
      <image:caption>Scope the product as one end-to-end path. Identity, failure recovery, operator visibility, and learning sit underneath the visible customer journey.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/how-to-scope-an-mvp/mvp-scope-brief-worksheet.svg</image:loc>
      <image:title>MVP scope brief worksheet</image:title>
      <image:caption>Use this brief to make version-one boundaries reviewable before estimates or implementation begin.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/bi-tool-vs-custom-dashboard</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/bi-tool-vs-custom-dashboard/bi-tool-vs-custom-dashboard-featured.webp</image:loc>
      <image:title>BI, custom dashboard, and embedded analytics paths</image:title>
      <image:caption>The useful question is not build or buy in isolation. Decide who needs to explore, who needs to act, and which layers your team is prepared to own.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/bi-tool-vs-custom-dashboard/dashboard-ownership-decision-matrix.svg</image:loc>
      <image:title>Dashboard ownership decision matrix</image:title>
      <image:caption>The three paths differ less in chart types than in who owns the semantic model, exploration experience, application workflow, permissions, and support surface.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/bi-tool-vs-custom-dashboard/bi-custom-hybrid-architecture-map.svg</image:loc>
      <image:title>BI, custom, and embedded dashboard architecture map</image:title>
      <image:caption>A hybrid works when the seam is explicit: governed metrics and exploration can stay in BI while the product owns identity, workflow, and action-specific interface.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/bi-tool-vs-custom-dashboard/dashboard-decision-brief-worksheet.svg</image:loc>
      <image:title>Dashboard delivery decision brief</image:title>
      <image:caption>Complete the brief with real users, questions, actions, and data constraints before comparing platforms or development estimates.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/customer-portal-requirements-checklist</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/customer-portal-requirements-checklist/customer-portal-requirements-featured.webp</image:loc>
      <image:title>A trusted customer portal boundary</image:title>
      <image:caption>A useful portal is a governed exchange between customers and the internal operating system—not a second, prettier place to copy the same records.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/customer-portal-requirements-checklist/customer-portal-requirements-matrix.svg</image:loc>
      <image:title>Customer portal requirements matrix</image:title>
      <image:caption>Start with the shared customer job, then define the access, data, operating, trust, and measurement requirements that make that job dependable.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/customer-portal-requirements-checklist/trusted-customer-portal-boundary-map.svg</image:loc>
      <image:title>Trusted customer portal boundary map</image:title>
      <image:caption>Keep identity, authorization, source records, files, notifications, and internal exception handling visible as separate responsibilities.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/customer-portal-requirements-checklist/customer-portal-release-brief.svg</image:loc>
      <image:title>Customer portal release brief</image:title>
      <image:caption>Use this one-page brief to turn a feature wish list into a testable first release with named owners and exclusions.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/fixed-price-vs-time-and-materials-software-development</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/fixed-price-vs-time-and-materials-software-development/software-contract-models-featured.webp</image:loc>
      <image:title>Software contract paths through uncertainty</image:title>
      <image:caption>A contract model does not remove delivery risk. It decides what must be known now, how change is handled, what evidence controls spend, and where uncertainty sits.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/fixed-price-vs-time-and-materials-software-development/software-contract-uncertainty-matrix.svg</image:loc>
      <image:title>Software contract uncertainty matrix</image:title>
      <image:caption>Evaluate uncertainty before choosing the payment mechanism. Fixed scope becomes more credible as the problem, solution, dependencies, and acceptance evidence become clearer.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/fixed-price-vs-time-and-materials-software-development/software-commercial-governance-map.svg</image:loc>
      <image:title>Software commercial governance map</image:title>
      <image:caption>Each model needs a different control loop: acceptance and change control for fixed price, evidence and spend cadence for time and materials, and an explicit decision gate for phased delivery.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/fixed-price-vs-time-and-materials-software-development/software-contract-decision-brief.svg</image:loc>
      <image:title>Software contract decision brief</image:title>
      <image:caption>Complete this brief before comparing proposals so suppliers price the same boundary and buyers can see what will control change and spend.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/website-migration-checklist</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/website-migration-checklist/website-migration-featured.webp</image:loc>
      <image:title>A controlled website migration</image:title>
      <image:caption>A redesign is safe when every valuable route, content asset, conversion path, and measurement signal has an explicit destination and acceptance check.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/website-migration-checklist/website-migration-control-ledger.svg</image:loc>
      <image:title>Website migration control ledger</image:title>
      <image:caption>Track each meaningful URL as a business asset with one disposition, one owner, and evidence that the destination works.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/website-migration-checklist/website-migration-route-map.svg</image:loc>
      <image:title>Website migration route map</image:title>
      <image:caption>Preserve strong URLs where possible; otherwise map each old route directly to the most relevant new destination and make removals intentional.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/website-migration-checklist/website-migration-launch-gate.svg</image:loc>
      <image:title>Website migration launch gate</image:title>
      <image:caption>Launch only when the team can prove search, content, conversion, measurement, operations, and recovery paths—not when the new screens merely look complete.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/single-tenant-vs-multi-tenant-saas</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/single-tenant-vs-multi-tenant-saas/single-vs-multi-tenant-saas-featured.webp</image:loc>
      <image:title>Pooled and isolated SaaS tenancy</image:title>
      <image:caption>Tenancy is a layer-by-layer product and operating decision: a SaaS platform can share some resources while isolating others behind one managed experience.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/single-tenant-vs-multi-tenant-saas/saas-isolation-pressure-matrix.svg</image:loc>
      <image:title>SaaS isolation pressure matrix</image:title>
      <image:caption>Assess the pressures that require separation before choosing a database or deployment pattern.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/single-tenant-vs-multi-tenant-saas/saas-tenancy-boundary-map.svg</image:loc>
      <image:title>Hybrid SaaS tenancy boundary map</image:title>
      <image:caption>A bridge model can keep onboarding, identity, releases, and operations shared while isolating specific data or workloads for defined tenants.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/single-tenant-vs-multi-tenant-saas/saas-tenancy-decision-brief.svg</image:loc>
      <image:title>SaaS tenancy decision brief</image:title>
      <image:caption>Use the brief to make the isolation promise, operating cost, acceptance evidence, and future migration triggers explicit.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/api-integration-requirements-checklist</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/api-integration-requirements-checklist/api-integration-requirements-featured.webp</image:loc>
      <image:title>Reliable API integration requirements</image:title>
      <image:caption>A reliable integration is an operated boundary: the main data path needs a contract, and the exception paths need equally explicit ownership.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/api-integration-requirements-checklist/api-integration-requirements-matrix.svg</image:loc>
      <image:title>API integration requirements matrix</image:title>
      <image:caption>Use the seven layers to turn a vague connection request into decisions that engineering, operations, security, and the business can verify.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/api-integration-requirements-checklist/api-failure-recovery-loop.svg</image:loc>
      <image:title>API failure and recovery loop</image:title>
      <image:caption>Retries handle temporary transport failures. Reconciliation and operator review handle uncertain outcomes, rejected records, and state drift.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/api-integration-requirements-checklist/api-integration-brief-worksheet.svg</image:loc>
      <image:title>API integration brief worksheet</image:title>
      <image:caption>Complete one brief per business-critical flow. Different records or consequences may need different timing, controls, and release gates.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/legacy-application-modernization-roadmap</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/legacy-application-modernization-roadmap/legacy-modernization-roadmap-featured.webp</image:loc>
      <image:title>Phased legacy application modernization roadmap</image:title>
      <image:caption>Modernization can move capability by capability while the current application keeps serving the business and each new boundary earns its cutover.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/legacy-application-modernization-roadmap/modernization-slice-scorecard.svg</image:loc>
      <image:title>Modernization first-slice scorecard</image:title>
      <image:caption>The best first slice is valuable enough to matter, bounded enough to learn from, and reversible enough to protect operations.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/legacy-application-modernization-roadmap/phased-modernization-boundary-map.svg</image:loc>
      <image:title>Phased modernization boundary map</image:title>
      <image:caption>Coexistence is temporary architecture with real operating cost. Define routing, data authority, validation, rollback, and the condition for removing each legacy path.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/legacy-application-modernization-roadmap/modernization-first-slice-brief.svg</image:loc>
      <image:title>Modernization first-slice brief</image:title>
      <image:caption>A useful first-slice brief describes the capability and its operating boundary—not merely a target framework or cloud service.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/mobile-app-requirements-checklist</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/mobile-app-requirements-checklist/mobile-app-requirements-featured.webp</image:loc>
      <image:title>Mobile app requirements planning</image:title>
      <image:caption>A useful mobile brief connects the user journey to the backend, device behavior, platform obligations, release evidence, and ongoing ownership.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/mobile-app-requirements-checklist/mobile-requirements-decision-matrix.svg</image:loc>
      <image:title>Mobile app requirements decision matrix</image:title>
      <image:caption>Use the nine requirement layers to expose decisions that a screen list or feature backlog usually hides.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/mobile-app-requirements-checklist/mobile-app-system-boundary-map.svg</image:loc>
      <image:title>Mobile app system boundary map</image:title>
      <image:caption>The app is one client inside a larger service. Map every external dependency and the team that owns it before estimating the build.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/mobile-app-requirements-checklist/mobile-app-build-brief-worksheet.svg</image:loc>
      <image:title>Mobile app build brief worksheet</image:title>
      <image:caption>Complete the worksheet around one end-to-end journey. Unknowns become discovery tasks instead of silent assumptions in a quote.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/software-project-handover-checklist</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/software-project-handover-checklist/software-project-handover-featured.webp</image:loc>
      <image:title>Software project handover</image:title>
      <image:caption>A software handover transfers operating control: the receiving team should be able to build, release, diagnose, recover, secure, and change the system.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/software-project-handover-checklist/software-handover-control-matrix.svg</image:loc>
      <image:title>Software handover control matrix</image:title>
      <image:caption>Collecting an asset is not the same as controlling it. Pair each handover area with access, evidence, and a receiving owner.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/software-project-handover-checklist/software-handover-proof-loop.svg</image:loc>
      <image:title>Software handover proof loop</image:title>
      <image:caption>Run the proof loop before final acceptance. Each exercise turns documentation into demonstrated operating capability.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/software-project-handover-checklist/software-handover-acceptance-worksheet.svg</image:loc>
      <image:title>Software handover acceptance worksheet</image:title>
      <image:caption>Record every gap as accepted, remediated, or explicitly deferred. The final milestone is independence from the outgoing supplier.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/headless-cms-vs-traditional-cms</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/headless-cms-vs-traditional-cms/headless-cms-vs-traditional-cms-featured.webp</image:loc>
      <image:title>Headless CMS versus traditional CMS architecture</image:title>
      <image:caption>A traditional CMS couples content and presentation; a headless CMS separates them so structured content can serve independently built channels.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/headless-cms-vs-traditional-cms/cms-publishing-model-decision-matrix.svg</image:loc>
      <image:title>CMS publishing model decision matrix</image:title>
      <image:caption>Choose the smallest model that supports the real publishing workflow. Hybrid boundaries can preserve page control while structuring the content that genuinely needs reuse.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/headless-cms-vs-traditional-cms/cms-content-delivery-boundary-map.svg</image:loc>
      <image:title>CMS content delivery boundary map</image:title>
      <image:caption>The platform choice affects every boundary between drafting and delivery. Test ownership and failure behavior across the whole path.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/headless-cms-vs-traditional-cms/cms-selection-brief-worksheet.svg</image:loc>
      <image:title>CMS selection brief worksheet</image:title>
      <image:caption>Write the operating contract before comparing vendors. A real draft-to-publish pilot reveals more than a generic feature checklist.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/ai-feature-production-readiness-checklist</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ai-feature-production-readiness-checklist/ai-feature-production-readiness-featured.webp</image:loc>
      <image:title>AI feature production readiness gates</image:title>
      <image:caption>A useful demo becomes an operable feature only after the team can measure it, constrain it, recover from failure, observe it, and own it.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ai-feature-production-readiness-checklist/ai-feature-readiness-gate.svg</image:loc>
      <image:title>Five-gate AI feature readiness model</image:title>
      <image:caption>Each gate needs evidence and an owner. A feature should be narrowed or held when a critical gate cannot be accepted safely.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ai-feature-production-readiness-checklist/ai-feature-control-loop.svg</image:loc>
      <image:title>AI feature evidence and control loop</image:title>
      <image:caption>The model call is one step inside a larger product boundary. Production evidence should flow back into version and scope decisions.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ai-feature-production-readiness-checklist/ai-feature-launch-brief.svg</image:loc>
      <image:title>AI feature launch acceptance brief</image:title>
      <image:caption>Record the supported task, evidence, controls, residual risk, approver, and review trigger so launch is a decision rather than a feeling.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/custom-crm-vs-off-the-shelf-crm</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/custom-crm-vs-off-the-shelf-crm/custom-crm-vs-off-the-shelf-crm-featured.webp</image:loc>
      <image:title>Configured, extended, and custom CRM paths</image:title>
      <image:caption>The useful decision is rarely buy or build everything. First locate the workflow boundary that standard configuration cannot support cleanly.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/custom-crm-vs-off-the-shelf-crm/crm-fit-gap-matrix.svg</image:loc>
      <image:title>CRM fit-gap decision matrix</image:title>
      <image:caption>Score the operating constraint, not the number of requested features. One critical blocker can matter more than several cosmetic gaps.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/custom-crm-vs-off-the-shelf-crm/crm-system-boundary-map.svg</image:loc>
      <image:title>CRM core and custom boundary map</image:title>
      <image:caption>A hybrid can preserve a vendor-run customer-data core while custom code owns only the differentiating workflow or experience.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/custom-crm-vs-off-the-shelf-crm/crm-decision-brief.svg</image:loc>
      <image:title>CRM decision brief worksheet</image:title>
      <image:caption>Capture the real customer journey, unavoidable gaps, ownership boundary, and trial evidence before approving a platform or build.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/rag-vs-fine-tuning</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/rag-vs-fine-tuning/rag-vs-fine-tuning-featured.webp</image:loc>
      <image:title>Retrieval and fine-tuning adaptation paths</image:title>
      <image:caption>Retrieval changes the context available for this request; fine-tuning changes learned model behavior. Evaluation decides whether either path improved the product task.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/rag-vs-fine-tuning/rag-fine-tuning-failure-matrix.svg</image:loc>
      <image:title>RAG and fine-tuning failure diagnosis matrix</image:title>
      <image:caption>Classify failed cases before selecting architecture. The same weak answer can come from missing evidence, poor retrieval, unclear instructions, or a behavior gap.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/rag-vs-fine-tuning/rag-fine-tuning-architecture-map.svg</image:loc>
      <image:title>RAG, fine-tuning, and evaluation boundary map</image:title>
      <image:caption>RAG and fine-tuning sit inside a larger product boundary. Permissions, validation, fallback, monitoring, and versioned evaluations still need explicit owners.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/rag-vs-fine-tuning/rag-fine-tuning-pilot-brief.svg</image:loc>
      <image:title>RAG versus fine-tuning pilot brief</image:title>
      <image:caption>Write the failure, candidate intervention, acceptance test, operating owner, and stop condition before funding a more complex AI stack.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/website-requirements-checklist</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/website-requirements-checklist/website-requirements-checklist-featured.webp</image:loc>
      <image:title>From website notes to a testable build brief</image:title>
      <image:caption>A useful website brief connects business outcomes, user journeys, content, system requirements, and acceptance evidence before visual production begins.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/website-requirements-checklist/website-requirements-matrix.svg</image:loc>
      <image:title>Seven-layer website requirements matrix</image:title>
      <image:caption>Treat the brief as seven connected requirement layers. A page list alone cannot define how the website should work or how launch will be accepted.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/website-requirements-checklist/website-content-system-map.svg</image:loc>
      <image:title>Website content and system boundary map</image:title>
      <image:caption>Map the visitor journey through content and conversion into the systems and owners that must handle the result.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/website-requirements-checklist/website-acceptance-brief.svg</image:loc>
      <image:title>Website launch acceptance worksheet</image:title>
      <image:caption>Turn subjective expectations into named owners, observable behavior, and evidence the team can review before launch.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/no-code-vs-custom-software-development</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/no-code-vs-custom-software-development/no-code-vs-custom-software-development-featured.webp</image:loc>
      <image:title>No-code, hybrid, and custom software boundaries</image:title>
      <image:caption>The useful choice is not a platform identity. It is the smallest system boundary that fits the workflow and can be governed over time.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/no-code-vs-custom-software-development/no-code-custom-pressure-matrix.svg</image:loc>
      <image:title>No-code and custom software pressure matrix</image:title>
      <image:caption>Score the hardest operating constraints. A few critical boundary failures matter more than a long list of convenient platform features.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/no-code-vs-custom-software-development/hybrid-software-boundary-map.svg</image:loc>
      <image:title>Hybrid no-code and custom software boundary</image:title>
      <image:caption>A hybrid keeps commodity workflow work configurable while custom code owns only the rules, experience, or reliability boundary that differentiates the operation.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/no-code-vs-custom-software-development/no-code-custom-pilot-brief.svg</image:loc>
      <image:title>No-code versus custom pilot worksheet</image:title>
      <image:caption>Use a representative workflow, an exception, a permission boundary, and an export or recovery test before committing to the platform path.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/ai-automation-vendor-selection-checklist</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ai-automation-vendor-selection-checklist/ai-automation-vendor-selection-featured.webp</image:loc>
      <image:title>Inspect the AI automation system behind the demo</image:title>
      <image:caption>A credible AI automation proposal connects a defined workflow to evaluation evidence, narrow permissions, human controls, recovery paths, and accountable ownership.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ai-automation-vendor-selection-checklist/ai-vendor-evidence-matrix.svg</image:loc>
      <image:title>Seven-part AI vendor evidence matrix</image:title>
      <image:caption>Score what a vendor can demonstrate for your workflow. Sales claims and generic certifications are context, not substitutes for task-level evidence.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ai-automation-vendor-selection-checklist/ai-automation-pilot-control-map.svg</image:loc>
      <image:title>Bounded AI automation pilot control map</image:title>
      <image:caption>A useful pilot tests the whole operating loop: representative inputs, acceptance rules, permissions, review, action, monitoring, and fallback.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/ai-automation-vendor-selection-checklist/ai-vendor-selection-brief.svg</image:loc>
      <image:title>AI automation partner selection brief</image:title>
      <image:caption>Use one decision brief to compare vendors against the same workflow, evidence request, control boundary, responsibilities, and pilot exit conditions.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/mobile-app-maintenance-checklist</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/mobile-app-maintenance-checklist/mobile-app-maintenance-checklist-featured.webp</image:loc>
      <image:title>A release-ready mobile app maintenance loop</image:title>
      <image:caption>Mobile app maintenance is a recurring operating system: observe production, triage risk, update deliberately, test the complete journey, release safely, and learn from the result.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/mobile-app-maintenance-checklist/mobile-maintenance-operating-matrix.svg</image:loc>
      <image:title>Seven-lane mobile maintenance operating matrix</image:title>
      <image:caption>Give every maintenance lane an observable signal, review rhythm, named owner, and release consequence instead of relying on an unprioritized bug backlog.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/mobile-app-maintenance-checklist/mobile-release-evidence-loop.svg</image:loc>
      <image:title>Evidence-led mobile release loop</image:title>
      <image:caption>A calm release process connects production evidence to a scoped change, representative device testing, controlled rollout, monitoring, and rollback or hotfix readiness.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/mobile-app-maintenance-checklist/mobile-maintenance-brief.svg</image:loc>
      <image:title>Mobile app maintenance ownership brief</image:title>
      <image:caption>Use this brief when handing a live app to an internal or external maintenance team so access, risk, cadence, and acceptance are explicit.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/software-discovery-phase-checklist</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/software-discovery-phase-checklist/software-discovery-phase-checklist-featured.webp</image:loc>
      <image:title>Evidence converging into a software build decision</image:title>
      <image:caption>Good discovery compresses uncertainty into a decision: build, narrow, test a risky assumption, choose an existing product, or stop.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/software-discovery-phase-checklist/software-discovery-evidence-matrix.svg</image:loc>
      <image:title>Seven-part software discovery evidence matrix</image:title>
      <image:caption>Treat every discovery lane as an evidence question with an owner and an exit decision, not as a meeting topic to mark complete.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/software-discovery-phase-checklist/discovery-decision-funnel.svg</image:loc>
      <image:title>Software discovery decision funnel</image:title>
      <image:caption>Discovery should reduce the option space. Unresolved high-consequence assumptions become small tests before they become development scope.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/software-discovery-phase-checklist/software-discovery-exit-brief.svg</image:loc>
      <image:title>Software discovery exit brief</image:title>
      <image:caption>Use one compact exit brief to make the recommendation, remaining uncertainty, first release, acceptance evidence, and ownership reviewable.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/admin-panel-requirements-checklist</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/admin-panel-requirements-checklist/admin-panel-requirements-checklist-featured.webp</image:loc>
      <image:title>A controlled admin action path</image:title>
      <image:caption>The real admin-panel scope is not the number of screens. It is the set of privileged actions, their safeguards, evidence, and recovery paths.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/admin-panel-requirements-checklist/admin-action-risk-matrix.svg</image:loc>
      <image:title>Admin action risk and control matrix</image:title>
      <image:caption>Classify actions by consequence and reversibility. Higher-risk actions need tighter permission, clearer context, stronger confirmation, and better recovery.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/admin-panel-requirements-checklist/trusted-admin-action-path.svg</image:loc>
      <image:title>Trusted admin mutation path</image:title>
      <image:caption>A safe admin workflow enforces permission and validation on the server, records the outcome, and gives operators a defined way to recover.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/admin-panel-requirements-checklist/admin-panel-release-brief.svg</image:loc>
      <image:title>Admin panel first-release brief</image:title>
      <image:caption>Scope the first release around the smallest complete operating loop, including permissions, auditability, error handling, and acceptance evidence.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/software-development-rfp-checklist</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/software-development-rfp-checklist/software-development-rfp-checklist-featured.webp</image:loc>
      <image:title>Evidence-led software proposal comparison</image:title>
      <image:caption>A useful RFP gives every credible partner the same decision context while leaving room for them to challenge the proposed solution.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/software-development-rfp-checklist/software-rfp-evidence-matrix.svg</image:loc>
      <image:title>Eight-part software RFP evidence matrix</image:title>
      <image:caption>Ask for an artifact, example, owner, or stated assumption in every evaluation lane so claims can be compared consistently.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/software-development-rfp-checklist/comparable-proposal-flow.svg</image:loc>
      <image:title>Comparable software proposal flow</image:title>
      <image:caption>A shared context, a visible question period, and a normalized response format reduce assumption drift before scoring begins.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/software-development-rfp-checklist/software-rfp-brief-worksheet.svg</image:loc>
      <image:title>Software development RFP brief worksheet</image:title>
      <image:caption>Use the worksheet as a compact RFP for a focused project or as the front page of a deeper procurement package.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/blog/saas-permissions-requirements-checklist</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/saas-permissions-requirements-checklist/saas-permissions-requirements-checklist-featured.webp</image:loc>
      <image:title>Tenant-aware SaaS authorization</image:title>
      <image:caption>Permissions are a product model: who may do what, to which resource, inside which tenant and conditions, with what evidence afterward.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/saas-permissions-requirements-checklist/saas-permission-domain-matrix.svg</image:loc>
      <image:title>Eight-part SaaS permission domain matrix</image:title>
      <image:caption>Define the permission domain before naming roles; roles should package tested permissions rather than substitute for the model.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/saas-permissions-requirements-checklist/authorization-decision-path.svg</image:loc>
      <image:title>Tenant-safe authorization decision path</image:title>
      <image:caption>Every protected request needs the same decision sequence, including explicit tenant context, deny-by-default behavior, and auditable outcomes.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/blog/saas-permissions-requirements-checklist/saas-permissions-release-brief.svg</image:loc>
      <image:title>SaaS permissions first-release brief</image:title>
      <image:caption>Use one reviewable brief to connect product rules, policy enforcement, administrative workflow, and acceptance evidence.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/case-studies/ai-opportunity-portfolio-prioritization-concept</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/ai-opportunity-portfolio-prioritization-concept/ai-opportunity-prioritization-hero.webp</image:loc>
      <image:title>How to prioritize an AI opportunity backlog without funding the loudest idea</image:title>
      <image:caption>Concept diagram by Leeonex. It illustrates a proposed portfolio-to-pilot decision system; it is not a client backlog, live product screen, or measured result.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/ai-opportunity-portfolio-prioritization-concept/ai-opportunity-decision-funnel.webp</image:loc>
      <image:title>How to prioritize an AI opportunity backlog without funding the loudest idea</image:title>
      <image:caption>Illustrative decision funnel. Each route is a planning choice, not evidence that a particular tool or AI system will succeed.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/ai-opportunity-portfolio-prioritization-concept/ai-pilot-evidence-contract.webp</image:loc>
      <image:title>How to prioritize an AI opportunity backlog without funding the loudest idea</image:title>
      <image:caption>Illustrative pilot evidence contract. Thresholds and controls must be defined from the buyer&apos;s real workflow, data, consequences, and risk obligations.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/case-studies/saas-activation-retention-dashboard-concept</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/saas-activation-retention-dashboard-concept/saas-activation-retention-dashboard-hero.webp</image:loc>
      <image:title>How to scope a SaaS activation and retention dashboard when the numbers disagree</image:title>
      <image:caption>Original Leeonex educational concept diagram. It proposes a measurement system for SaaS activation and retention; it is not a client dashboard, production dataset, or measured result.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/saas-activation-retention-dashboard-concept/saas-metric-contract-chain.webp</image:loc>
      <image:title>How to scope a SaaS activation and retention dashboard when the numbers disagree</image:title>
      <image:caption>A dashboard can only compare cohorts after the eligibility, activation, retention, and exclusion rules are explicit. Original Leeonex worksheet; illustrative only.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/saas-activation-retention-dashboard-concept/saas-cohort-reconciliation-loop.webp</image:loc>
      <image:title>How to scope a SaaS activation and retention dashboard when the numbers disagree</image:title>
      <image:caption>Reconcile representative accounts before publishing trends, then version definitions instead of silently changing history. Original Leeonex architecture diagram; illustrative only.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/case-studies/live-mobile-app-release-control-concept</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/live-mobile-app-release-control-concept/live-mobile-app-release-control-hero.webp</image:loc>
      <image:title>How to maintain a live mobile app when bugs, store deadlines, and features compete</image:title>
      <image:caption>Original Leeonex educational concept diagram. It proposes a release-control system for a live mobile app; it is not a production dashboard, client record, or measured result.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/live-mobile-app-release-control-concept/mobile-maintenance-triage-matrix.webp</image:loc>
      <image:title>How to maintain a live mobile app when bugs, store deadlines, and features compete</image:title>
      <image:caption>Classify work by user harm, deadline, evidence, reversibility, and release path—not by whoever asks most loudly. Original Leeonex worksheet; illustrative only.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/live-mobile-app-release-control-concept/mobile-release-control-loop.webp</image:loc>
      <image:title>How to maintain a live mobile app when bugs, store deadlines, and features compete</image:title>
      <image:caption>A release is a feedback loop: reproduce, decide, change, verify, stage, observe, and feed evidence back into the queue. Original Leeonex diagram; illustrative only.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/case-studies/quote-to-delivery-workflow-web-app-concept</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/quote-to-delivery-workflow-web-app-concept/quote-to-delivery-web-app-hero.webp</image:loc>
      <image:title>How to scope a quote-to-delivery web app without rebuilding the CRM</image:title>
      <image:caption>Original Leeonex educational concept diagram. It shows a proposed system boundary, not a client application, real quote, customer record, delivery, invoice, or measured result.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/quote-to-delivery-workflow-web-app-concept/quote-to-delivery-control-loop.webp</image:loc>
      <image:title>How to scope a quote-to-delivery web app without rebuilding the CRM</image:title>
      <image:caption>The proposed workflow preserves scope versions, approvals, owners, delivery evidence, and exceptions across one complete operating loop. Original Leeonex diagram; illustrative only.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/quote-to-delivery-workflow-web-app-concept/quote-to-delivery-system-boundary.webp</image:loc>
      <image:title>How to scope a quote-to-delivery web app without rebuilding the CRM</image:title>
      <image:caption>The boundary map assigns one source of truth to each important record and limits the custom app to the differentiating workflow. Original Leeonex architecture worksheet; illustrative only.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/case-studies/managed-service-marketplace-mvp-concept</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/managed-service-marketplace-mvp-concept/two-sided-service-marketplace-mvp-hero.webp</image:loc>
      <image:title>How to scope a two-sided service marketplace MVP without building both sides at once</image:title>
      <image:caption>Original Leeonex educational concept diagram. It shows a proposed managed marketplace boundary, not a client product, real buyer request, provider network, launch, transaction, or measured result.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/managed-service-marketplace-mvp-concept/managed-marketplace-request-workflow.webp</image:loc>
      <image:title>How to scope a two-sided service marketplace MVP without building both sides at once</image:title>
      <image:caption>The proposed workflow keeps matching judgment and exceptions visible while the product records one complete request-to-outcome path. Original Leeonex diagram; illustrative only.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/managed-service-marketplace-mvp-concept/marketplace-mvp-scope-control-board.webp</image:loc>
      <image:title>How to scope a two-sided service marketplace MVP without building both sides at once</image:title>
      <image:caption>The scope board protects the first learning loop by separating required product state from deliberate operator work and evidence-triggered expansion. Original Leeonex worksheet; illustrative only.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/case-studies/multi-location-cms-content-model-concept</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/multi-location-cms-content-model-concept/multi-location-cms-website-hero.webp</image:loc>
      <image:title>How to scope a multi-location CMS website without cloning every location page</image:title>
      <image:caption>Original Leeonex educational concept diagram. It shows a proposed multi-location CMS boundary, not a client website, live content model, indexed page set, ranking result, lead result, or measured system.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/multi-location-cms-content-model-concept/multi-location-content-model-map.webp</image:loc>
      <image:title>How to scope a multi-location CMS website without cloning every location page</image:title>
      <image:caption>The proposed model composes pages from governed entities instead of copying complete pages. Original Leeonex diagram; illustrative only.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/multi-location-cms-content-model-concept/cms-editorial-publishing-workflow.webp</image:loc>
      <image:title>How to scope a multi-location CMS website without cloning every location page</image:title>
      <image:caption>The proposed workflow separates contribution, verification, publishing, and revalidation. Original Leeonex workflow; illustrative only.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/case-studies/permission-aware-semantic-search-concept</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/permission-aware-semantic-search-concept/permission-aware-semantic-search-hero.webp</image:loc>
      <image:title>How to scope semantic search for a B2B knowledge product without hiding weak retrieval</image:title>
      <image:caption>Original Leeonex educational concept diagram. It shows a proposed semantic-search boundary, not a client product, production index, live content, relevance score, accuracy result, or measured system.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/permission-aware-semantic-search-concept/semantic-search-retrieval-loop.webp</image:loc>
      <image:title>How to scope semantic search for a B2B knowledge product without hiding weak retrieval</image:title>
      <image:caption>The proposed loop keeps authorization, retrieval quality, visible evidence, and evaluation connected. Original Leeonex diagram; illustrative only.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/permission-aware-semantic-search-concept/semantic-search-scope-evaluation-matrix.webp</image:loc>
      <image:title>How to scope semantic search for a B2B knowledge product without hiding weak retrieval</image:title>
      <image:caption>The worksheet protects a narrow first release by separating required retrieval controls from later generative features and unsafe assumptions. Original Leeonex worksheet; illustrative only.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/case-studies/saas-billing-entitlements-concept</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/saas-billing-entitlements-concept/saas-billing-entitlements-hero.webp</image:loc>
      <image:title>How to scope SaaS billing and entitlements without access drift</image:title>
      <image:caption>Original Leeonex educational concept diagram. It shows a proposed billing-to-access boundary, not a client platform, payment record, product screen, launch, revenue result, or measured system.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/saas-billing-entitlements-concept/billing-to-access-control-loop.webp</image:loc>
      <image:title>How to scope SaaS billing and entitlements without access drift</image:title>
      <image:caption>The proposed control loop makes retries, ordering, policy, access enforcement, and reconciliation explicit. Original Leeonex diagram; illustrative only.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/saas-billing-entitlements-concept/saas-entitlement-scope-matrix.webp</image:loc>
      <image:title>How to scope SaaS billing and entitlements without access drift</image:title>
      <image:caption>The worksheet protects the smallest useful billing scope by separating required controls from later commercial complexity and unsafe shortcuts. Original Leeonex worksheet; illustrative only.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/case-studies/dedicated-squad-roadmap-stream-concept</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/dedicated-squad-roadmap-stream-concept/dedicated-development-squad-hero.webp</image:loc>
      <image:title>How to add a dedicated development squad without splitting product ownership</image:title>
      <image:caption>Original Leeonex educational concept diagram. It shows a proposed squad boundary and shared delivery path, not a client team, delivered engagement, product screen, timeline, or measured result.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/dedicated-squad-roadmap-stream-concept/dedicated-squad-delivery-loop.webp</image:loc>
      <image:title>How to add a dedicated development squad without splitting product ownership</image:title>
      <image:caption>The proposed delivery loop keeps product and technical decisions connected to implementation, release, and retained knowledge. Original Leeonex diagram; illustrative only.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/dedicated-squad-roadmap-stream-concept/squad-ownership-scope-matrix.webp</image:loc>
      <image:title>How to add a dedicated development squad without splitting product ownership</image:title>
      <image:caption>The concept separates decision authority from delivery responsibility and names the shared interfaces that need evidence. Original Leeonex worksheet; illustrative only.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/case-studies/human-reviewed-invoice-intake-automation-concept</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/human-reviewed-invoice-intake-automation-concept/ai-invoice-intake-automation-hero.webp</image:loc>
      <image:title>How to scope AI invoice intake automation without auto-approving bad data</image:title>
      <image:caption>Original Leeonex educational concept diagram. It shows a proposed invoice-intake control path, not a client workflow, live financial data, accounting advice, or a measured result.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/human-reviewed-invoice-intake-automation-concept/invoice-intake-review-workflow.webp</image:loc>
      <image:title>How to scope AI invoice intake automation without auto-approving bad data</image:title>
      <image:caption>The proposed workflow separates AI-assisted extraction from deterministic validation and accountable approval. Original Leeonex diagram; illustrative only.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/human-reviewed-invoice-intake-automation-concept/invoice-automation-scope-control-matrix.webp</image:loc>
      <image:title>How to scope AI invoice intake automation without auto-approving bad data</image:title>
      <image:caption>The concept keeps source retention, review, duplicate checks, and audit history in v1 while delaying workflow breadth and excluding autonomous payment or accounting decisions. Original Leeonex worksheet; illustrative only.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/case-studies/live-saas-product-handover-concept</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/live-saas-product-handover-concept/live-saas-product-handover-hero.webp</image:loc>
      <image:title>How to take over a live SaaS product without losing release control</image:title>
      <image:caption>Original Leeonex educational concept diagram. It shows a proposed live-product handover path, not a client system, production release, or measured rescue result.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/live-saas-product-handover-concept/saas-handover-control-path.webp</image:loc>
      <image:title>How to take over a live SaaS product without losing release control</image:title>
      <image:caption>The proposed handover closes eight control gates before custody is accepted. Original Leeonex diagram; illustrative only.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/live-saas-product-handover-concept/product-custody-evidence-worksheet.webp</image:loc>
      <image:title>How to take over a live SaaS product without losing release control</image:title>
      <image:caption>The worksheet separates evidence to verify now from improvements to plan later and shortcuts to exclude. Original Leeonex worksheet; illustrative only.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/case-studies/secure-multi-role-customer-portal-concept</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/secure-multi-role-customer-portal-concept/secure-multi-role-customer-portal-hero.webp</image:loc>
      <image:title>How to scope a secure multi-role customer portal without permission leaks</image:title>
      <image:caption>Original Leeonex educational concept diagram. It shows a proposed portal access model, not a client system, production interface, security test, or measured result.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/secure-multi-role-customer-portal-concept/customer-portal-request-workflow.webp</image:loc>
      <image:title>How to scope a secure multi-role customer portal without permission leaks</image:title>
      <image:caption>The proposed first release closes one request loop while preserving ownership and history at every state. Original Leeonex diagram; illustrative only.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/secure-multi-role-customer-portal-concept/portal-permission-and-scope-worksheet.webp</image:loc>
      <image:title>How to scope a secure multi-role customer portal without permission leaks</image:title>
      <image:caption>The worksheet makes role decisions and scope boundaries reviewable before screens multiply. Original Leeonex worksheet; illustrative only.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/case-studies/offline-first-field-inspection-app-concept</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/offline-first-field-inspection-app-concept/offline-first-field-inspection-app-hero.webp</image:loc>
      <image:title>How to scope an offline-first field inspection app that does not lose work</image:title>
      <image:caption>Original Leeonex educational concept diagram. It shows a proposed offline inspection workflow, not a client app, production screen, live field record, or measured result.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/offline-first-field-inspection-app-concept/offline-inspection-workflow.webp</image:loc>
      <image:title>How to scope an offline-first field inspection app that does not lose work</image:title>
      <image:caption>The proposed first release closes one inspection loop: assign, cache, capture, validate, queue, sync, and review. Original Leeonex diagram; illustrative only.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/offline-first-field-inspection-app-concept/field-app-scope-and-sync-states.webp</image:loc>
      <image:title>How to scope an offline-first field inspection app that does not lose work</image:title>
      <image:caption>The concept keeps offline reliability inside v1 while delaying breadth and excluding unsafe sync shortcuts. Original Leeonex worksheet; illustrative only.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/case-studies/two-way-crm-operations-sync-concept</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/two-way-crm-operations-sync-concept/two-way-crm-operations-sync-hero.webp</image:loc>
      <image:title>How to scope a two-way CRM and operations sync without duplicate records or silent conflicts</image:title>
      <image:caption>Original Leeonex educational concept diagram. It shows a proposed two-way integration boundary, not a client system, production data flow, or measured result.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/two-way-crm-operations-sync-concept/controlled-two-way-sync-workflow.webp</image:loc>
      <image:title>How to scope a two-way CRM and operations sync without duplicate records or silent conflicts</image:title>
      <image:caption>The proposed first loop observes, validates, matches, decides, writes, and reconciles. Original Leeonex diagram; illustrative only.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/two-way-crm-operations-sync-concept/integration-scope-and-conflict-worksheet.webp</image:loc>
      <image:title>How to scope a two-way CRM and operations sync without duplicate records or silent conflicts</image:title>
      <image:caption>The concept builds one accountable handoff now, validates broader synchronization later, and excludes unsafe conflict shortcuts. Original Leeonex worksheet; illustrative only.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/case-studies/exception-first-operations-dashboard-concept</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/exception-first-operations-dashboard-concept/exception-first-operations-dashboard-hero.webp</image:loc>
      <image:title>How to scope an exception-first operations dashboard that helps teams act</image:title>
      <image:caption>Original Leeonex educational concept diagram. It shows a proposed operations workflow, not a client dashboard, live business data, or measured result.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/exception-first-operations-dashboard-concept/operations-dashboard-decision-loop.webp</image:loc>
      <image:title>How to scope an exception-first operations dashboard that helps teams act</image:title>
      <image:caption>The proposed first version closes one loop: collect, validate, calculate, prioritize, assign, and record. Original Leeonex diagram; illustrative only.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/exception-first-operations-dashboard-concept/dashboard-scope-now-later-exclude.webp</image:loc>
      <image:title>How to scope an exception-first operations dashboard that helps teams act</image:title>
      <image:caption>The concept protects the first decision loop by delaying broad analytics and excluding unsafe shortcuts. Original Leeonex worksheet; illustrative only.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/case-studies/leeonex-website-product-foundation</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/leeonex-website-product-foundation/leeonex-website-og.webp</image:loc>
      <image:title>How Leeonex turned a broad software offer into a structured product website</image:title>
      <image:caption>The production Leeonex homepage presents the full offer through one direct promise and a service-led journey.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/leeonex-website-product-foundation/services.webp</image:loc>
      <image:title>How Leeonex turned a broad software offer into a structured product website</image:title>
      <image:caption>The services page lets buyers browse by category or by the goal they need to accomplish.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/leeonex-website-product-foundation/content-system.svg</image:loc>
      <image:title>How Leeonex turned a broad software offer into a structured product website</image:title>
      <image:caption>Typed sources of truth keep service positioning, page rendering, internal discovery, and search metadata aligned.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/leeonex-website-product-foundation/insights.webp</image:loc>
      <image:title>How Leeonex turned a broad software offer into a structured product website</image:title>
      <image:caption>The insights library supports buyers before the sales conversation with practical decision tools.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/case-studies/landing-page-development-system</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/landing-page-development-system/landing-page-system-hero.webp</image:loc>
      <image:title>How Leeonex structured a landing-page service around the decisions buyers need to make</image:title>
      <image:caption>The production service-page hero establishes the offer, intended outcome, and next actions before presenting implementation detail.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/landing-page-development-system/landing-page-conversion-system.webp</image:loc>
      <image:title>How Leeonex structured a landing-page service around the decisions buyers need to make</image:title>
      <image:caption>The conversion-system sequence starts with research, then connects copy, brand, testing, intelligence, and reporting to the page build.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/landing-page-development-system/landing-page-lead-delivery.webp</image:loc>
      <image:title>How Leeonex structured a landing-page service around the decisions buyers need to make</image:title>
      <image:caption>The lead-delivery section makes the post-submit workflow visible instead of treating the form as the end of the landing-page job.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.leeonex.com/case-studies/ai-support-saas-mvp-concept</loc>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/ai-support-saas-mvp-concept/ai-support-saas-mvp-concept.webp</image:loc>
      <image:title>How to scope an AI-assisted support SaaS MVP without automating away human judgment</image:title>
      <image:caption>Original Leeonex educational concept diagram. It illustrates a proposed workflow and does not represent a client product, production deployment, or measured result.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/ai-support-saas-mvp-concept/human-in-the-loop-workflow.webp</image:loc>
      <image:title>How to scope an AI-assisted support SaaS MVP without automating away human judgment</image:title>
      <image:caption>The concept keeps one accountable decision path: capture, classify, draft, human review, and record. Original Leeonex diagram; illustrative only.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://www.leeonex.com/case-studies/ai-support-saas-mvp-concept/mvp-scope-and-guardrails.webp</image:loc>
      <image:title>How to scope an AI-assisted support SaaS MVP without automating away human judgment</image:title>
      <image:caption>The proposed v1 prioritizes a usable learning loop and postpones autonomous replies, channel expansion, predictive scoring, and multilingual voice features. Original Leeonex diagram; illustrative only.</image:caption>
    </image:image>
  </url>
</urlset>
