How do you demonstrate the relevance of software built from scratch?

For the EB-2 NIW, there is no single official checklist that proves the relevance of software built from scratch. What matters is assembling a consistent body of evidence showing the tool’s real-world impact and its contribution to the field, something assessed on a case-by-case basis by the competent authority.

The goal is to go beyond a technical description and document how the software was used, by whom, and to what effect. Proof of adoption, peer recognition, and originality tend to carry more weight than the volume of code itself.

• Technical reports, project documentation, and use-case studies.
• Publications, conference presentations, or citations of your work.
• Patents, awards, and certifications tied to the tool.
• Letters from experts detailing the importance and novelty of the solution.
• Adoption data and metrics that demonstrate use in real-world contexts.

Organizing this material coherently helps build a strong case for merit and relevance. Because each profile is assessed individually, it is worth reviewing the updated requirements on the USCIS website and evaluating your documentation with a specialist before filing a petition.

About the author

Victoria Harper

Editor-in-Chief

Meet the author

As a journalist and lead editor at Visto n’ Visa, Victoria helps ensure that immigration topics are covered in a clear, trustworthy, and easy-to-understand way. Her focus is on delivering useful, human, and relevant content for people exploring new paths abroad.