I didn’t join Meritocrat because I was looking for another startup idea. I joined because the problem felt real.
When Ram first shared what he was building, I could immediately connect with it. Immigration is one of the most important journeys in a person’s life, but the process often feels fragmented, unclear, and heavily dependent on scattered documents, delayed communication, and individual interpretation.
Coming from an enterprise architecture background, I have seen how complex systems can either create clarity or create confusion. The immigration process has complexity, but the user experience should not feel chaotic.
What stood out to me about Meritocrat was that it was not trying to replace attorneys or oversimplify immigration. It was trying to bring structure, transparency, and collaboration into a process that badly needs all three.
At first, Ram and I were just discussing ideas. We spoke about workflows, user journeys, attorney collaboration, document organization, merit evaluation, and how applicants could better understand where they stand.
Over time, those conversations became deeper. I realized Ram was not just building a product. He was building from lived experience, frustration, and a strong belief that this process can be better.
Where Ram brings the product vision, immigration experience, and founder intensity, I bring enterprise architecture, execution discipline, and practical systems thinking. He thinks deeply about what Meritocrat should become. I focus on how we can build it in a way that is scalable, usable, and reliable.
That balance started to matter.
There was a point where it no longer felt like I was advising or helping from the side. It felt like I was part of the foundation.
Meritocrat is not just a software platform to us. It is a structured way to help applicants, attorneys, and advisors work with more clarity around high-stakes immigration decisions.
If I imagine Meritocrat without Ram’s vision, it loses its soul. If I imagine building it without strong execution and architecture, it loses its structure.
That is why this works.
We are not just dividing responsibilities. We are solving the same problem from two sides.
And that is what makes this a founding team.
