Three Websites. One New Home.
After all three of Raico Nextify's websites went down, I consolidated their web presence into a single company hub, designed in Figma and built from scratch in under three days.
Client Name:
Tools Used:
Role:
Date:
Raico Nextify Business Solutions
Figma, Codex
Design, Development
The Problem
Raico Nextify came to me with a pretty simple problem: their website had been hacked, and it was completely unrecoverable.
The slightly bigger problem was that they actually had three websites, and all three had gone down at roughly the same time.
They initially wanted me to rebuild one of them and get it live as quickly as possible. But instead of rebuilding one website and leaving the other two disconnected, I suggested we use the situation as an opportunity to rethink the whole thing.
Why rebuild one site when we could bring everything together?
The idea was to turn the three separate websites into one central company hub, giving Raico Nextify a single place to represent its sister companies, TeamLYH and AI Nextify.
The main constraint was time. This wasn't a project where I could spend weeks exploring concepts. They needed something live, and they needed it fast.
Finding a Direction
With the original websites gone, I didn't have much existing material to work from.
I started by going through Raico Nextify's LinkedIn, Instagram, and Facebook pages, pulling together whatever information I could find about the company, its services, messaging, and visual identity.
From there, I used that information alongside AI to quickly establish a structure and visual direction.
The first version of the design took roughly two and a half to three hours to put together in Figma.
It was intentionally simple. The priority was getting something concrete in front of the client instead of spending hours trying to perfect something they hadn't even seen yet.
They liked the direction, but felt that it was too static.
So the next round focused on adding movement and making the site feel more alive without completely changing the underlying design.
Once the base direction was established, I got on a call with one of the founders and went through the website section by section. We worked through the content, changed sections, replaced images, and made the smaller design decisions needed to bring the three different parts of the business together.
The tricky part was that each of the original websites had its own colour palette and slightly different visual language. Bringing those together without making the new website feel like three unrelated websites stuck together became an important part of the design.
Building Under Pressure
The rough wireframe was created in Figma, but the website itself wasn't built in Framer.
I coded it.
This was also the first client project where I used AI heavily as part of my development workflow. I used ChatGPT's Codex to speed up the implementation and get through the build much faster than I normally would.
The biggest challenge wasn't the complexity of the website. It was the clock.
The entire project went from a completely dead web presence to a functioning replacement in less than three days, with around 13 hours of actual work.
There were no major technical disasters along the way. Most of the later changes were exactly what you'd expect from a fast client project: changing a paragraph, swapping an image, moving a section, or making a small visual adjustment.
Even the AI workflow had its own problems. My credits kept running out, so eventually I had to stop leaning on AI and just build parts of the site myself.
In retrospect, that probably made me faster.
Reflection
I'm happy with how the project turned out, especially considering how quickly it came together.
The decision to merge the three websites was probably the most valuable part of the project. It turned what could have been a straightforward rebuild into a much more useful solution for the company.
It was also my first time properly integrating AI into a client workflow. Codex helped me move through the development process considerably faster, while still leaving me in control of the actual decisions.
That said, the design is definitely more basic than I'd normally want it to be.
The time constraint didn't leave much room for exploring different visual directions or obsessing over smaller details. If I were doing the project again with more time, I'd spend considerably longer on the design and build the site in Framer instead of coding it from scratch. That would give me more control over the interactions and make iteration easier.
But that's also what makes this project useful to me.
It wasn't a perfect, meticulously planned project. It was a real problem with a short deadline, limited information, and a website that simply needed to exist.
And sometimes, getting the right solution out the door matters more than getting every pixel perfect.
