How it started
When I joined PT AIRES Technology the company was still finding its feet. One of the first tasks handed to me was straightforward on paper: acquire a domain. Every company needs one, and nobody had gotten around to it yet.
So I did that. Bought the domain, set it up, and then the natural next step was getting the company email running on it. That involved configuring DNS records, hooking everything up to Google Workspace, and making sure mail actually landed in inboxes and not spam folders. Not glamorous work, but useful work.
Once the emails were sending and receiving correctly, I looked at what we had: a real domain, professional email addresses, and absolutely nothing at the URL itself. A blank page. For a company trying to sell AI systems and robotics to enterprise clients, that felt like a problem.
Nobody asked me to fix it. I just figured I should.
The first version
I built the first version fast. Next.js, Tailwind CSS, a few shadcn/ui components. The goal was simple: tell people what AIRES Technology is, what we sell, and how to reach us. Three pages, nothing fancy.
The product list was the part that needed the most thought, not technically but editorially. The company distributes a genuinely mixed portfolio: agricultural drones, AI chat agents, service robots, smart locks, data center inspection robots. Getting that to read as a coherent company rather than a random catalogue took some work on the copy.
The contact form ran through EmailJS so submissions would land directly in the company inbox without needing a backend.
That was it. I pushed it live and we had a website.
The overhaul
The design was functional but dated from the start. Flat white backgrounds, generic card components straight out of the component library, nothing that felt like it belonged to a technology company specifically.
Eventually I did a proper overhaul, not just visual but structural.
My first instinct was to go modern: dark hero section, gradient backgrounds, animated glow effects, glass morphism navigation. It looked sharp. But after sitting with it, and thinking about who actually visits a B2B technology company's website (procurement managers, enterprise IT leads, operations directors), the dark aesthetic started to feel wrong for the audience. These are people evaluating whether to trust a company with serious infrastructure. Sleek and dramatic is not what signals reliability to them.
So I pulled back. The final design is bright white and blue: clean, maximalist, professional. The kind of site that reads as credible on first glance rather than trying to impress. The hero is bold but light. The typography is confident. Nothing fights for attention.
But the more meaningful change was structural.
Previously, adding a product meant editing multiple files and hoping nothing fell out of sync. Now every product is a single MDX file in content/products/. The slug, image path, category, tagline, highlights, and full feature descriptions all live in one place. The products page, the product detail pages, and the sitemap all read from those files dynamically — adding a new product is just dropping in a new .mdx and an image.
The site also serves a llms.txt file — a plain-text document that describes the company and its full product catalogue in a format AI assistants can reliably parse. That file is generated automatically at build time from the same MDX frontmatter, so it never goes stale. The idea is that when someone asks an AI assistant about industrial robotics or agricultural drones in Indonesia, AIRES Technology has a better chance of surfacing.
What this kind of work actually is
Building a company website for a startup is not a prestige project. You are not solving a hard technical problem. You are making sure that when someone Googles the company name, they find something that does not make the company look like it does not exist.
That matters more than it sounds. The domain and email setup, the initial site, the ongoing tweaks, the structural overhaul — it is all infrastructure. Background work that creates the conditions for everything else to function properly.
I am glad I took the initiative on it rather than waiting to be asked.