Once I had a few successful projects under my belt—an app sale, a few websites, and design work for some local businesses—I realized I needed to formalize what I was doing. I wasn’t just freelancing anymore. I was running a business. And that business needed a name.
At the time, I was still heavily involved in electronic music. I DJed, produced, and performed under the moniker “Keese”—a nod to my middle name (Keys) and a subtle homage to the bat-like creatures from The Legend of Zelda, one of my favorite video game franchises. My love for music production, especially in the electronic space, was still going strong, even as my tech career was taking off.
So, when it came time to name my freelance operation, I leaned into that hybrid identity.
Introducing: Byte Jockeyz
I wanted a name that reflected the way I blended different digital skills—web development, coding, graphic design, and audio production—to create what clients needed. The name “Byte Jockeyz” felt fitting: part computer science (bytes), part music (jockey), and altogether unconventional.
It was memorable. It had personality. It was me.
For a few years, I ran with it. Under Byte Jockeyz, I built websites, designed packaging, consulted on digital marketing, and continued landing bigger clients. I worked with agencies and took on white-label projects. The work was steady, and the brand gave me a kind of alter ego—someone who could mix tech and creativity into tangible results.
Outgrowing the Name
But as time went on, I started to notice something.
Whenever I introduced myself or shared my business name, I’d hesitate a little. I didn’t love saying it out loud. It felt more like a nickname than a business. And as I started doing more formal work with larger organizations and agencies, the name didn’t quite carry the professionalism I wanted it to.
It had served me well—but I was evolving, and my brand needed to evolve with me.
That’s when I began thinking about a rebrand.
Why “Alkalyne”?
Rebranding wasn’t just about picking a cooler name. It was about creating something that could grow with me—something flexible, professional, and open-ended enough to encompass all the work I was doing and the directions I might go.
I landed on Alkalyne Solutions.
The name is a bit abstract, and intentionally so. I liked that it wasn’t locked into a specific service. It sounded like a real business—not just a side project or creative handle—and it rolled off the tongue more easily than Byte Jockeyz ever had. Plus, it carried some subtle connotations of balance, energy, and innovation—ideas I wanted to associate with the work I did.
I also wanted to challenge the traditional expectations that come with a name. Just like how companies like Uber and Amazon don’t directly describe what they do, I wanted Alkalyne to be a brand that grew into its own identity. One that felt just as at home designing a small business website as it did collaborating with a global tech company.
A New Chapter
Since rebranding, Alkalyne Solutions has become more than just a portfolio or a freelance alias. It’s a brand that represents the full scope of what I offer—web development, design, SEO, automation, and strategic support for businesses, agencies, and creative teams.
The name shift also gave me a new sense of ownership and confidence. I wasn’t just doing projects anymore—I was building partnerships. Helping small businesses get seen. Helping agencies scale. Helping teams bring digital ideas to life.
Looking back, it’s wild to think how far things have come—from blowing on SNES cartridges to coding in a lab full of sand, to building an app that kickstarted my career. The path wasn’t straight, and it definitely wasn’t fast. But every detour taught me something. Every setback pointed me somewhere new.
And every skill—whether from music, marine science, or tech—ended up playing a part in the business I run today.
Final Thoughts: Origins and Intentions
This blog series has been a way for me to reflect on where it all started. If you’re someone trying to figure out your path—whether you’re switching careers, learning to code, or launching your first freelance gig—just know this: the long way around isn’t a waste. Sometimes, it’s the best route.
Thanks for reading.
