Masereka Adorable Kimulya

Masereka Adorable Kimulya grew up with limited financial resources in Kasese, western Uganda. Their early fascination with technology began with phones: devices that were valuable, difficult to obtain, and full of things to discover. Before there was a business plan, there was the curiosity of wanting to understand how something worked.

In the manuscript, Kimulya resists turning that curiosity into a perfect origin story. Wanting a phone also meant wanting to play games and own something that felt out of reach. Over time, a childhood wish became a savings goal—and then a way into a much wider world of information.

Kimulya describes saving small amounts over several years before buying a Samsung S8 in 2024, while in secondary school. Owning a device was different from borrowing one: it created more room to explore, learn, and return to questions without waiting for someone else’s phone.

Access still had a cost. Mobile data, time, family expectations, and the limits of the device shaped what was possible. Learning did not begin with a well-equipped workspace or a clear route into the technology industry. It began by making use of what was available.

An interest in ICT, mathematics, and physics led to an important conversation with an elder brother during secondary school. The suggestion to become a programmer introduced a new idea: apps and websites were not simply things that existed. People made them, and those skills could be learned.

A school peer later demonstrated HTML, CSS, and JavaScript. Kimulya tried learning apps and searched for instruction, eventually finding longer programming lessons on YouTube. Downloading lessons helped make the most of limited internet access. The more they learned, the clearer it became that a computer would open possibilities a phone could not.

Some of the earliest business lessons came from practical work, not software. Around the family furniture business, Kimulya saw the relationship between materials, a useful product, a customer, and a sale. They describe learning to make wooden clothes hangers and experimenting with designs people would buy.

Carpentry income, savings, and eventually selling the phone helped fund a laptop. It was a difficult trade-off: giving up one hard-earned tool to obtain another. The computer made more kinds of development possible, but limited hardware and unfamiliar software brought new obstacles.

Early calculator, news, and movie projects often followed tutorials closely. Seeing something run was encouraging; understanding enough to build independently took much longer. That gap became one of the most persistent lessons in the manuscript.

MixifyHub began as an idea for bringing social-media accounts, scheduling, and feeds together. Kimulya invested time and scarce money in the domain, hosting, data, and development. The ambition was much larger than their experience at the time.

After months of work, the prototype still contained mocked content and unfinished interactions. A demonstration on other devices exposed problems with mobile layouts. Building a page that looked right on one laptop had not produced a reliable service for other people.

The manuscript is candid about those shortcomings. It describes learning the importance of responsive design, reading documentation, understanding AI APIs, and testing beyond a familiar screen. It also records a harder discovery: publishing a website does not mean that customers will arrive.

Feedback suggested that the AI feature interested people more than the original social-media concept. Kimulya describes shifting through MixifyHub AI, Mixi AI, and Easy AI, exploring text and image capabilities along the way.

Interest was not the same as a sustainable business. Hosting and service costs continued while advertising brought in very little. Easy AI was eventually shut down. Later chatbot, e-commerce, and school-office experiments brought more practice, but the available chapters do not present a simple breakthrough into financial success.

Work on EasyShop and SchoolOffice also brought practical constraints into focus: payment-gateway access in Uganda, unreliable or unaffordable tools, messaging integrations, and an ageing laptop. AI-assisted development helped, but it did not remove the need to understand the work or make difficult choices about scope and cost.

Today, Kimulya is the founder of Atai. Their stated ambition is to help reduce poverty by giving more people practical support to create and run businesses of their own. The early experiences in the manuscript explain why access matters, and why writing software is only one part of the problem.

Atai’s focus is the whole business journey: shaping an offer, creating the website or digital product it needs, hosting it, managing customers and daily operations, and working on marketing and growth. Specialized AI teams are intended to help with that work while the business owner stays in charge.

This is a mission to expand opportunity, not a promise of automatic income. The distinction matters: a working product still needs useful value, customers, care, and a way to sustain itself. Those are the challenges Atai is being built around.