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 security 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.
A lot of small tweaks over a lot of time
The site stayed broadly the same for a while but never really sat still. A product image updated here, a description rewritten there, a layout tweak when something looked off on mobile. The kind of maintenance that does not feel like work until you look back and realise how much of it there was.
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. The home page got a dark hero section with gradient backgrounds and animated glow effects. The navigation became a shared component that starts transparent over the hero and transitions to a solid glass header on scroll. The footer went deep navy, similar to what I was doing on another project at the same time. Each page got its own metadata, structured JSON-LD data for search engines, a sitemap, and a robots.txt that explicitly lets AI crawlers index the content.
The bones stayed the same. The surface changed a lot.
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, 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.