top of page

How I Started My Own NYC Personal Injury Law Firm: A Story of Integrity, Justice, and Relentless Commitment

  • Writer: BLITZ LAW GROUP
    BLITZ LAW GROUP
  • 3 hours ago
  • 2 min read


How I Started My Own NYC Personal Injury Law Firm


Starting a law firm is never easy. But for Justin Blitz, the decision to build Blitz Law Group wasn’t about ambition—it was about integrity.


In the latest video from our “Behind the Blitz” series, Justin shares the pivotal moment in his career when he made the bold choice to leave his father’s law firm. What pushed him to walk away? The discovery that one of the firm’s managing partners was secretly stealing money from the rest of the team. When the truth came out, Justin did what many others wouldn’t: he fought back.


Justin sued the partner. He won. But that was only the beginning.

Building a new personal injury law firm in NYC from the ground up meant long hours, big risks, and a relentless pursuit of justice. And as fate would have it, the final case tied to that former partner—a personal injury case against the City of New York—would become one of the most significant moments in Justin’s career. After years of litigation and a commitment to see it through, that case settled for $34 million, one of the largest known settlements against the City.


This story is more than just a legal victory. It’s a reminder of what Blitz Law Group stands for:

    •    Integrity even when it’s inconvenient.

    •    Accountability even when no one else is watching.

    •    Unshakable dedication to the people we serve.


If you haven’t yet, watch the full video now on our YouTube channel (https://www.youtube.com/@blitzlawgroup) to hear Justin tell the story in his own words. It’s a powerful reminder of why we fight so hard for our clients—and why we’ll never stop.


Need an attorney who will go the distance for you?


Call us at (212) 871-1300 or get a free consultation (https://blitzlawgroup.com/contact). You don’t pay unless we win.


Comments

Couldn’t Load Comments
It looks like there was a technical problem. Try reconnecting or refreshing the page.
bottom of page