Building a global Software-as-a-Service platform from the ground up requires more than just code; it demands a fundamental shift in how one approaches structural problems and scalability. Our SaaS and Software expert, Vijay Raina, brings two decades of experience in enterprise technology and software architecture to this discussion. Having transitioned from a traditional engineering background into the high-stakes world of digital infrastructure, he provides a unique perspective on managing technical debt, navigating international markets, and the evolution of cloud-based communication. This conversation explores the nuances of bootstrapping a tech venture to the point of delivering two billion emails annually while maintaining a lean, efficient team.
Transitioning from mechanical engineering to IT requires a specific problem-solving approach. How did an engineering mindset help you navigate early technical gaps when building your first venture, and what specific methods did you use to teach yourself complex system architecture from scratch?
The most valuable asset I carried over from my mechanical engineering studies was the belief that every complex structure can be broken down into its core components. In engineering, if you don’t know how to build a bridge, you go to the library, read the technical manuals, and learn the physics behind the load-bearing requirements. I applied this exact logic to IT; when I lacked the technical knowledge for my first venture, I treated the software like a physical engine that needed to be assembled. It was a process of rapid self-education where I sat in coffee shops for a year, drafting business plans and studying how data centers functioned during my time at Keppel T&T. This disciplined approach allowed me to move from being an “average boy” with a scholarship to someone who could architect a content management system long before platforms like WordPress were the industry standard.
Reaching a threshold of 10 million emails can reveal hidden bottlenecks in a database and server bandwidth. What were the immediate technical steps taken to “change the wings of the plane mid-flight” during your first major scale-up, and how did that experience change your long-term philosophy on technical debt?
The moment a client actually hit that 10-million-email mark, our entire system felt the strain, and we realized that sending 10 million is nothing like sending a thousand. We had to scramble immediately, which involved three team members literally copying millions of files across servers overnight to keep the service from collapsing under the weight of the data. We were forced to rebuild our databases and reengineer our delivery processes in real-time while the platform was still live, which was an incredibly stressful and tactile lesson in the dangers of technical debt. Now, my philosophy is rooted in the idea that if you haven’t designed for scale from day one, you are simply waiting for your architecture to fail. This experience pushed us to eventually move away from virtual machines and toward microservices, ensuring each challenge served as a blueprint for a more robust, mature platform.
Serving SMEs often presents content creation hurdles, while enterprise clients demand heavy customization. How did you balance these conflicting market needs early on, and what specific architectural shifts allowed you to eventually return to the SME market with a scalable, self-service cloud model?
Early on, we struggled because we made assumptions about SMEs that weren’t backed by data; specifically, we found they couldn’t produce enough content to actually use our tools, forcing us to do that work for them at no extra cost. To survive, we shifted to enterprise clients like banks and media companies who already had high-volume needs of 30 to 50 million emails, but this led to the “problem” of heavy customization that made scaling a nightmare. The breakthrough came in 2018 when we completely rebuilt Enginemailer as a cloud-based SaaS platform with automated onboarding and self-service sign-ups. By moving away from on-premise, highly customized setups to a standardized cloud model, we could finally serve both ends of the spectrum—the SME looking for a “free-forever” plan and the enterprise paying RM20,000 per month—using the same scalable infrastructure.
Expanding into international markets can expose issues where resellers capture the majority of the value. How did you restructure your pricing and collection models to regain control over your revenue, and what are the strategic benefits of charging based on email volume rather than contact counts?
Our 2017 expansion into Indonesia was a wake-up call because we found ourselves earning only US$0.25 for every 1,000 emails while middlemen were charging the end customer up to US$2.00. We realized we had almost no control over our revenue or collections, so we pivoted to a direct-to-consumer cloud model where everything is automated and payments are handled within the platform. By charging based on the volume of emails sent—our current rate is roughly RM1 for a certain volume—rather than the number of contacts in a database, we provide a much fairer value proposition. This allows our clients to keep their full history and templates without being penalized for growing their list, which is a significant differentiator from competitors like Mailchimp who charge more as your database expands.
Utilizing AI for 24/7 international support and spam detection can significantly leverage a lean team of fewer than ten people. How does this technology currently impact your operational efficiency, and what is your step-by-step roadmap for integrating agentic AI bots into conversational platforms?
AI is the primary reason we can manage a global platform with just eight full-time staff members while delivering two billion emails annually. It handles our around-the-clock international support and performs critical, high-speed tasks like spam detection and campaign optimization that would otherwise require dozens of manual reviewers. Our roadmap for the future is quite specific: we integrated WhatsApp at the end of 2025, and our next major milestone is the launch of an agentic AI bot in Q2 2026. This bot will move beyond simple responses to actually participating in conversational platforms, allowing our users to engage their audiences in real-time without increasing their overhead or ours.
Compliance standards like PDPA and GDPR are often seen as hurdles for growing companies. How did you integrate these privacy requirements into your core database management strategy, and what advice do you have for businesses struggling to maintain data integrity while scaling their reach?
We viewed compliance not as a hurdle, but as a core feature that builds the trust necessary to handle sensitive client data. By being an early adopter of Malaysia’s PDPA and Europe’s GDPR, we built automated consent tracking and secure data handling directly into our database architecture from the start. For businesses struggling with this, my advice is to stop viewing data privacy as an afterthought and start treating it as a foundational element of your product-market fit. When you scale from one client paying RM1 million to a million clients paying RM1, you cannot manually manage compliance; it must be baked into your automated systems so that every upgrade or downgrade handles data integrity seamlessly.
Many startups rush for venture capital, yet bootstrapping offers a different level of control. Why do you believe premature funding often leads to organizational chaos, and what practical cash-flow strategies allowed you to fund global expansion entirely through reinvested profits?
Rushing for VC funding often forces a company to chase revenue before the product is actually ready, which leads to taking on custom requests from every client and losing your core focus. This creates massive technical debt and organizational chaos because you are scaling a broken or inefficient process rather than a refined product. We avoided this by using the revenue from our existing digital business to fund Enginemailer’s growth, essentially acting as our own investors. This bootstrapping approach meant we only grew when the product was stable, and today, 20% of our revenue comes from overseas—all achieved without giving up equity or control to external partners.
Email marketing is often described as a middle-of-the-funnel strategy rather than a tool for instant sales. How can businesses better use their existing databases to build long-term engagement, and what metrics should they prioritize to ensure they aren’t paying repeatedly for the same leads?
A major mistake businesses make is constantly paying for new ads to reach the same people they’ve already encountered. Email marketing allows you to own that relationship; for example, an F&B business can collect emails over several months and then launch a major holiday campaign without spending a single cent on additional advertising. The key metric to watch is not just the size of the subscriber list, but the volume and quality of engagement over time, which is why we don’t charge for the number of contacts. By focusing on database management and long-term retention rather than instant sales, businesses can turn a one-time lead into a lifetime customer, creating lasting value that ads simply cannot replicate.
What is your forecast for the future of email marketing and AI integration?
I believe we are entering an era where email marketing will become more about personalized, automated ecosystems rather than just “sending blasts.” My forecast is that by 2026, the industry will shift toward agentic AI that doesn’t just suggest subject lines but actually manages entire conversational workflows across email and platforms like WhatsApp. We will see a doubling of volume—our goal is to hit 4 billion emails annually—driven by AI’s ability to make every communication feel bespoke to the recipient. Ultimately, the successful marketers will be those who use these tools to solve the customer’s problems first, because as we’ve learned over twenty years, if you achieve that, the scale and the revenue will naturally follow.
