Zalos built an AI-reader layer: an llms.txt and a Markdown homepage served to tools that ask for it. That layer has not kept up with the November relaunch. The Markdown homepage still leads with the old headline "Computer Agents for Finance Operations", not "The finance agent factory". llms.txt lists only the homepage and careers. When we fetched the site with an AI reading tool on November 9, 2026, nine of the sixteen sitemap URLs returned "404 Not Found": /platform, all four solution pages (order-to-cash, procure-to-pay, record-to-report, cost-to-serve), /about, /security and /newsroom. The homepage, blog, contact and careers pages loaded. A CFO who asks an AI assistant "what does Zalos do for procure-to-pay?" or "is Zalos secure?" gets an answer built from a page that is a year out of date, or from nothing.
First action
Request /platform and /solutions/order-to-cash with an "Accept: text/markdown" header and confirm the 404.
How to measure it
Sitemap URLs answering Markdown requests with 200
- Now
- –
- Target
- 16 of 16, with assistant answers naming the four solution areas
- By
- 2 weeks
Steps
Reproduce
Request all 16 sitemap URLs as HTML and as Markdown and log the status codes.
Founding Product Engineer 1 hour
Add the fallback
Serve HTML (or generated Markdown) whenever no Markdown version exists, so no page returns 404.
Founding Product Engineer 1 day
Regenerate Markdown
Build Markdown versions of the homepage, platform, four solutions, security and about from the live content, with the new headline.
Founding Product Engineer 2 days
Rewrite llms.txt
List every page and post with a one-line summary, the supported ERPs and how to book a call.
Co-Founder and CEO 2 hours
Guard the build
A deploy check that fails on any 404 or on mismatched titles between the HTML and Markdown versions.
Founding Product Engineer half a day
Test the answers
Ask three AI assistants ten buyer questions (security, P2P, SAP, pricing) before and after, and keep the answers.
Co-Founder and CEO 2 hours
Repeat monthly
Re-run the questions after each site change.
Founding Product Engineer monthly
Why it works
Make every URL in the sitemap answer AI readers. Either serve a Markdown version of each page or fall back to the normal HTML when a Markdown version doesn't exist, so these pages never return 404. Regenerate the Markdown homepage from the live page so the headline, description and four solution areas match. Rewrite llms.txt to list every page with a one-line summary: platform, the four solutions, security, about, newsroom, blog posts and contact. Add a check to the deploy pipeline that requests every sitemap URL both as HTML and as Markdown and fails the build on any 404.
Enterprise finance buyers increasingly shortlist vendors by asking AI assistants, and those assistants read what the site serves to them. Zalos sells agents that operate software for finance teams. Its own site should be the clearest example of a site that agents can read. The fix is a few hours of engineering on pages the team relaunched four days earlier.
Ready to use
ChecklistAI-reader site check
[ ] Every sitemap URL returns 200 for Accept: text/html [ ] Every sitemap URL returns 200 for Accept: text/markdown (or falls back to HTML) [ ] Markdown homepage headline = "The finance agent factory" [ ] llms.txt lists platform, 4 solutions, security, about, newsroom, blog posts, contact [ ] llms.txt names supported ERPs and how to book a call [ ] Build fails on any 404 [ ] Ten buyer questions re-asked monthly
Risks and how to handle them
Two versions of every page drift apart again
Generate the Markdown from the same source as the HTML and let the build check catch mismatches.
Assistants update their answers slowly
Measure fetch-time answers first; indexed answers follow.
Evidence
- Your websiteSitemap (16 URLs, updated November 5, 2026): homepage, /platform, four solution pages (order-to-cash, procure-to-pay, record-to-report, cost-to-serve), /about, /security, /newsroom, /blog and two posts, /contact-us, /careers, /privacy-policy and /terms-conditions. Fetched with an AI reading tool on November 9, 2026 (/about twice), /platform, all four solution pages, /about, /security and /newsroom returned "404 Not Found"; the homepage, /blog, both posts, /contact-us, /careers, /privacy-policy, robots.txt and llms.txt loaded.Source
- Your websiteAI-reader files (fetched November 9, 2026): llms.txt lists only the homepage and careers as key pages and offers "a Markdown version of the homepage (request with Accept: text/markdown)". That Markdown homepage still leads with the old headline "Zalos: Computer Agents for Finance Operations", describes Connect, Act and Audit stages, names Oracle, NetSuite, SAP and QuickBooks, and ends with the contact page and a founder's email. Neither mentions the finance agent factory, the four solution areas, the platform, security or the blog.Source
- Your websiteHomepage (as served to browsers, checked November 9, 2026): title "Zalos - The finance agent factory"; description "Build AI workforces that run finance workflows across fragmented systems. Zalos computer agents log into your ERP, map your processes, then automate them and get better every month." The headline changed from "Computer Agents for Finance Operations" to "The finance agent factory." and the site moved from Webflow and HubSpot to Next.js. No pricing page, case studies, testimonials or live chat; a strip of 12 logos.Source