The challenge
Telecom sites fail in a predictable way. Every product goes on every page, because internally every department wants to be on the homepage. Meanwhile two completely different visitors arrive wanting opposite things. A family wants to know the price, whether it reaches their street, and how soon someone can install it. A business wants reliability, support, and who they call at 9pm when the office goes dark. The visitor who came to answer one question leaves without an answer.
What I did
Split residential and business early and stop apologising for the split. That decision drove the information architecture, and the architecture drove everything else: visual design that keeps packages readable instead of decorative, a responsive build for the phones most people were actually checking on, and SEO set up at the foundation rather than bolted on later. I did both the design and the build, because designs that cannot be built are drawings.
Results
- Two separate journeys for residential and business customers, instead of one page trying to serve both
- A responsive build aimed at the phone, where most of the traffic was arriving
- Package and pricing pages a visitor can actually read and compare
- Technical SEO in the foundation, so the site turned up for the service questions people were already typing into Google
- Measured on inquiries rather than on looking good
Kujtesa sells internet, cable, and business connectivity in Kosovo. I designed and built their web presence, doing both jobs, which I prefer. Designs that cannot be built are drawings.
Telecom sites fail in a predictable way. They put every product on every page, because internally every department wants to be on the homepage. The visitor, who came to answer one question, leaves without an answer.
Two people show up here and they want opposite things. A family wants to know what it costs, whether it reaches their street, and how soon someone can install it. A business wants to know about reliability, support, and who they call at 9pm when the office goes dark. Same company, different conversations. So we split them early and stopped apologizing for the split.
That decision drove the information architecture, and the architecture drove everything else. Visual design that keeps packages readable instead of decorative. A responsive build, because most people were checking on a phone. SEO set up properly at the foundation, so the site turned up for the service questions people were already typing into Google.
The goal was never a beautiful site. It was inquiries. Somebody understands what they can get where they live, and asks for it.