TechFoundry.io — Two Businesses, One Site, Built in a Week by Zahid HussainTechFoundry.io — Two Businesses, One Site, Built in a Week by Zahid Hussain

TechFoundry.io — Two Businesses, One Site, Built in a Week

Zahid Hussain

Zahid Hussain

1 collaborator

Overview

TechFoundry runs two businesses that share a name and almost nothing else. One builds AI agents and custom software. The other, Aerless™, supplies optical transceivers, fiber, passive components and telecom power to data centres and network operators across North America. The new site had to present both to two very different buyers — an operations lead evaluating an automation partner, and a network engineer looking up a part number — without either feeling they had landed in the wrong place. I designed and built it end to end as a custom WordPress theme and shipped it in one week.

The problem

The previous site was an ageing template: slow, not built for phones, and describing a company that no longer existed — one software shop, no Aerless, no catalogue. Two audiences meant two vocabularies and two calls to action: "start a project" on one side, "request a quote" on the other. And discovery itself has changed. Buyers now ask ChatGPT and Gemini before they search Google, so the site had to be as legible to a language model as to a person: every product, service and case study on its own indexable page, with structured data a model can cite.

The approach: one theme, three surfaces

I rejected the two obvious options — two separate websites, or a page-builder theme with the divisions bolted on — and built one hand-coded theme with a notion of "surface". The corporate hub, the Agentic Development microsite at /ai and the Aerless microsite at /aerless each get their own navigation, palette, hero and calls to action, but they share one design system (Geist, one set of tokens, dark hero into light content), one header and footer logic, and one content model. A visitor can move between them in one click, and the same codebase decides which company they are looking at.

What I built

Corporate hub. Who TechFoundry is, both divisions, the mission and commitments, client feedback from TELUS, Own the Podium and the Alberta Teachers' Retirement Fund, an Insights section, and a three-step "how to engage" flow.
Agentic Development (/ai). An animated agent-loop hero — work arrives, the system orchestrates, decides and acts, with guardrails and a review console in the loop — four service pages, and an "Our work" section with six case studies (TF-IMS, Own the Podium, OneHub, Glean, Document Intake, Agent Ops) mirroring the Contra portfolio.
Aerless™ (/aerless). A catalogue of 80 products as a custom post type, each with a spec sheet (part number, data rate, form factor, media, temperature range, compliance), part-number search, three product lines (optics and fiber, passive components, power), supplier pages, and a request-a-quote flow built around a parts list rather than a contact form.
Leads that go where the team is. Every form on the site — contact, quote, start a project — posts straight into a Microsoft Teams channel and creates a record in a lightweight CRM I built inside WordPress, so leads, status and follow-ups live in the same admin as the content. A quote request is in front of the team in seconds, with the part list attached, and never lives only in someone's inbox.
Built to be found by AI. Every page is server-rendered HTML with 750–1,100 words of real content. Structured data on every page: Organization site-wide, Product with SKU, MPN and brand on all 80 products, BlogPosting on articles, CreativeWork and breadcrumbs on case studies. Canonical URLs and Open Graph everywhere, XML sitemaps per content type, and a robots.txt that welcomes every crawler, AI bots included. When someone asks ChatGPT or Gemini for a 100G QSFP28 supplier in North America, there is a page with the exact part number, its specification and a quote button for the model to cite.

Results

Measured against the live site on 24 September 2026 with Lighthouse 12:
Homepage, desktop: Performance 98 · Accessibility 100 · Best practices 100 · SEO 100. Largest Contentful Paint 0.7 s, 564 KiB total.
Agentic Development, desktop: 99 · 96 · 96 · 100. LCP 0.6 s, 262 KiB.
Aerless, mobile: 99 · 97 · 100 · 100. LCP 1.8 s, 345 KiB.
110 indexable URLs live on launch day — 26 pages, 80 products, 4 articles — each with its own title, description and schema.
One week from first commit to launch, one person, no page builder and no front-end framework.

What I'd do differently

The animated heroes shift layout on mobile before they settle (the homepage scores 85 on mobile for that reason alone). Reserving their space up front is a small fix I'd make on day one next time. I'd also ship an llms.txt alongside the sitemap from the start — it costs nothing and tells AI crawlers exactly what to read first.

Tech

WordPress with a hand-coded theme: PHP templates, custom post types for the catalogue and case studies, one CSS design system and vanilla JavaScript — no page builder, no client-side framework. JSON-LD structured data, XML sitemaps, a Microsoft Teams integration and a lightweight in-WordPress CRM for lead capture. Built with Claude Code and ChatGPT alongside hand-written code.
Like this project

Posted Sep 24, 2026

Corporate hub, two division microsites, an 80-product catalogue, AI-search-ready markup and leads routed to Teams — a custom WordPress theme shipped in a week.