Why we started
Tribunus

My family has worked in real estate development for three generations. I’ve seen how an overlooked requirement or a misread policy can lead to redesigns, another round of municipal review, and months of additional carrying costs. Understanding what a site can support takes more than reading its zoning. It means understanding the policies, precedents, and concerns that shape an approval.

I met Usman through a commercial real estate project he was struggling to move forward. We started discussing his project and kept coming back to the same question: why was getting a clear picture so difficult? I brought experience in development. He brought an engineering background in the chips that power AI, along with firsthand experience of the problem we wanted to solve.

Gurinder later joined us, bringing his own background in chip design verification. He and Usman worked on finding design flaws before tapeout, when an undetected bug could lead to a costly silicon respin. They understood the depth of verification needed when complex requirements interact and errors are expensive to correct. In development, we saw a similar need to examine the assumptions behind a proposal before committing capital and months of design work to it.

That became the starting point for Tribunus. We’re bringing municipal rules, past decisions, and project evidence together so developers can understand what’s allowed, assess where there’s room to push, and build a stronger case for approval. It grew out of a project that brought us together and a problem we each had a reason to solve.