Before there was a company to run, there was a friend’s Commodore 64. Yasir Drabu remembers coding small games and making things move on its screen in India, where access to such a machine was unusual. A few instructions could produce something visible. The attraction was immediate, and it survived several changes of programming language, a long university education, and the discovery that running a software business involves considerably more than writing software.
Today, Drabu is the founder and CEO of Taazaa, based in Hudson, Ohio. He is also the co-founder and CTO of Innago, which helps independent landlords manage their properties. One role puts him among teams building systems for other organizations. The other puts him inside a product with a very concrete monthly deadline: the rent. Together, they make an interesting test of his recurring conviction that technical sophistication should make life easier for the person using it.
A professor’s route, with an exit
His education took him from an engineering bachelor’s degree at Bangalore University to graduate study in computer science at Kent State University. He completed his master’s in 2003, with a project on dynamic bandwidth management in networks and Hassan Peyravi as his advisor. Even the title suggests an early appetite for problems that do not announce themselves politely to the people experiencing them.
In 2010, his doctoral dissertation examined gateway placement and fault tolerance in wireless mesh networks. These networks offer flexibility, but their performance depends on decisions about where connections go, how much traffic they carry, and what happens when something fails. Drabu studied ways to plan those connections and recover from failures while preserving service quality. It was a technical education in the consequences of arrangement: the same components can produce very different experiences depending on how they work together.
He had expected to become a professor. Teaching and research interested him; building products gradually offered another outlet. The move into entrepreneurship brought an additional curriculum, including sales and business management, learned while doing the work. His account of the transition contains little founder theatre. There were problems to solve, people to help, and unfamiliar jobs that eventually became his responsibility. The organizational chart had acquired a rather energetic catch-all department.
The rent was due. The founders went unpaid.
Innago brought Drabu together with Dave Spooner, whom he met through a business accelerator in Cleveland. Spooner had previously worked on a student housing business. When that venture ended, he carried his knowledge of landlords and their needs into a new partnership. Drabu supplied the software-building experience. There was a market problem to investigate before there was much of a company to describe.
The early operation was small: Spooner and colleagues in Cincinnati, with people from Drabu’s development company in Hudson working on the software. Landlords could track payments; tenants could pay online and find their leases. The appeal lay in getting necessary work done without a prohibitive bill. The story’s stakes were bookkeeping, navigation, and whether a small property owner could manage the month without another administrative headache.

Spooner later recalled that neither founder initially took a salary. Drabu was building the product and bought inexpensive servers with his own money. Spooner worked at a nearby restaurant to cover his bills and rented a closet large enough for a bed. The details are worth keeping in their proper proportions: the closet was Spooner’s; the servers were Drabu’s. Bootstrapping had assigned each partner a different line item.
There is a useful corrective here to the immaculate founding story. A product can begin with a clear purpose and still require deeply ordinary sacrifices. Someone must find the equipment. Someone must pay for it. Someone must answer a customer. The ability to keep doing those things gives an idea time to become a business.
Innago dates its founding to 2017. It now describes its audience as independent landlords and reports coverage across all 50 states. Drabu’s responsibilities include architecture, product development, planning, and building teams. The original problem remains recognizable even as the operation expands: give a smaller landlord useful tools without requiring the budget or administrative machinery of a large property company.
The user is allowed to be confused
Listen to Drabu discuss design and he becomes particularly interested in a familiar engineering reflex. A user struggles. The engineer thinks the task is obvious. Impatience arrives before investigation. Drabu asks the engineer to step back and look at the person’s actual journey through the product.
A misleading prompt may be enough to cause trouble. A crowded screen can do the same. The person buying a system may also be far removed from the person expected to use it every day. A successful demonstration in the executive’s office therefore leaves a substantial piece of the job unfinished. The person handling the daily queue deserves a vote.
His answer is observation and empathy, extended to colleagues as well as customers. In a team working across cultures, apparent difficulty may include a language barrier or a perspective that has not yet been heard. This puts a practical obligation on technical expertise: spend enough time understanding the difficulty to make something easier. Cleverness earns its keep when another person can use the result.
“I keep saying I’m a builder, so I like building things that actually help people.”
Yasir Drabu, in conversation with Jeff Bullas
Another kind of housing problem
In April 2021, Taazaa completed the acquisition of Lexington Solutions, bringing the Fusion platform into its portfolio. Fusion served the affordable housing asset management market, including Low-Income Housing Tax Credit work. It occupied a different part of the property business from Innago, with its tenant and landlord interactions. Drabu saw a relationship between the two products and their capacity to ease work for property managers.
The stated plan included modernizing Fusion and making it cloud-native. Such projects involve an awkward balance. Existing customers depend on the present system, while the product’s future requires changes underneath it. An acquisition announcement can fit comfortably on a page; the patient work of carrying a functioning product forward tends to take rather longer.
His professional connections also extend into advice and investment. Gammite Ventures lists him as an advisor. Venera Technologies, which develops tools for digital media quality control, names him as a technology advisor. He has also worked as an angel investor and product development partner. They show a career that includes helping other builders, alongside the executive responsibilities attached to his own companies.
Four appearances, then a larger conversation
Taazaa’s founding year is 2007. Its later growth has a visible sequence: appearances on the Inc. 5000 in 2023, 2024, 2025, and 2026. In the 2026 list, the company sits at No. 3,400. Four consecutive appearances provide a record of sustained eligibility and growth recognition, rather than a single celebratory afternoon.
Drabu’s response to the fourth appearance emphasized customer trust and the work of employees. He also set out an ambition to double the company’s size and extend its global reach before the end of 2026. That was an ambition, with the practical demands of execution still attached. Growth acquires meaning through the teams, commitments, and customer work it creates.
Consecutive Inc. 5000 appearances for Taazaa.
In September 2026, Taazaa announced its acquisition of NetEffect, a management and technology consulting and systems integration firm. The transaction followed a year-long partnership. It brought a wider set of enterprise capabilities into the company’s work, including experience with complex platforms and the systems businesses already rely on.
Drabu framed the opportunity around connecting intelligence, automation, data, and human judgment within existing workflows. The emphasis is revealing. Enterprise software has to live among other software, established habits, and operational obligations. A new capability must find its place in that crowded household. NetEffect adds people accustomed to working with the furniture already in the room.
A faster tool, the same responsibility
Artificial intelligence gives Drabu a new way to pursue an older interest. In a January 2024 essay, he asked how AI could support human creativity and productivity. By April 2026, his discussion with Taazaa colleagues focused on faster delivery, better informed decisions, and helping people gain access to knowledge that had previously required specialist assistance.
He described AI as an accelerant for a company still organized around people. The distinction matters in everyday management: employees remain responsible for choices even when a tool helps assemble the information. His leadership discussion also described contributors, owners, and leaders as different levels at which those tools could help people do their jobs.
That view leaves room for his original enthusiasm about computers. He still describes the pleasure of building things, and his interests include science fiction and ping-pong. There is something pleasingly proportionate about the combination: imagined futures, complex systems, and a small ball that refuses to stay where anyone puts it.
The career now spans university research, client software, property products, acquisitions, and advice to other businesses. The most consistent thread is a question about consequences. When a network fails, when a landlord needs a record, when an employee cannot understand a screen, what does the engineering actually do for them? Drabu’s work keeps taking that question out of the abstract and putting it in front of a person with something to finish.