Midland Information Systems: The First Client AI Website System
Midland Information Systems was the first prototype sale of the AI Website System. The initial work produced a separate buyer site without replacing Midland's existing Joomla property; the operating and measurement layers followed the site into client use.
Context
The first plan was to replace Midland's established Joomla site. That was the wrong fit for the immediate need. Midland wanted a simpler companion site that could serve AS400 and IBM i buyers while the existing property kept running. The scope changed before launch, and the new site became midlandinfosys.net.
That distinction matters. A useful AI Website System has to fit the business it is sold to. A second domain gave us room to build a controlled PHP and JSON foundation, publish buyer reference content, and test the operating method without pretending that a long-running commercial site should be replaced on day one.
Methodology
On September 1, 2026, the companion site went live with real glossary, FAQ, and directory content, a search page, a structured-data graph, a sitemap, and machine-readable discovery files. Its content records can change slugs while the site preserves redirects from old URLs. The existing Midland Joomla site remained separate.
The first content decision came from recorded demand. We compared disclosed Search Console queries from Midland's established properties and the related AS400 and Power sites. A Tape, VTL, LTO, and storage group had 605 distinct queries and 13,319 impressions in the reviewed 90-day source set, with only 19 clicks. That was evidence of an uncovered information need across those properties, not evidence that the new .net site already ranked. We used it to build 22 new Tape and Storage content files: a hub, product listings, two substantial guides, glossary terms, and buyer FAQs.
On September 13, the next content group added a FlashSystem 5600, 7600, and 9600 comparison and linked product records. The work included IBM citations and benchmark limits rather than a table of unsupported claims. Midland's own Claude and Codex instructions, onboarding material, and dated session intake then gave the client a repeatable way to continue the work. Substantive AI sessions now reach the private warehouse as recorded events without placing warehouse credentials inside Midland's account.
Findings
By September 15, the live Midland sitemap listed 62 URLs. The homepage, sitemap, and federation manifest returned HTTP 200 during this review. The system has a public website layer, a client AI workflow, and a separate measurement and change-history layer. Those are delivery receipts. They are not a ranking claim.
The early measurement is deliberately modest. From September 2 through 14, the warehouse recorded 144 successful crawler requests to content-like Midland routes under its current classification. That proves requests reached recorded URLs; it does not prove indexing, citations, AI answers, or buyer visits. Search Console had disclosed two .net page impressions and no clicks through September 12. The site is too new to claim search growth or sales attributable to this implementation.
What the first sale tested
My portfolio gave me a place to build the method. Midland tested whether it could travel. It had a real brand, an established site we needed to respect, buyer questions we could investigate, and people who would have to use the workflow after I left the room.
The change from replacement to companion site is the useful part of the story. We could have forced the prototype onto the old plan and called that consistency. Instead, we kept the operating principles and changed the implementation to fit the client. The website is the visible half. The instructions and the warehouse are what make the next month different from a one-time build.
What we are watching next
We will watch which Midland pages Google starts showing, which buyer queries become associated with them, what reaches the server, and which dated changes precede any movement. Those sources answer different questions. They will be compared, not blended into a single visibility score.
If you run an established site and want to see what a companion system, a controlled rebuild, or a data connection would actually involve, request a System Walkthrough. The Midland implementation gives us a real example to open, with its limits still attached.