It can, because knowledge of a proprietary internal platform is knowledge of the organization's own product and processes rather than general industry skill. Qualification still requires the year of employment abroad, a qualifying corporate relationship and evidence that the knowledge is genuinely distinctive.
Proprietary is a strong start, but it has to be shown rather than claimed
An internally built system is one of the better fact patterns for L-1B, because the distinction the statute draws between organizational knowledge and general skill maps cleanly onto software nobody else runs. The failures happen at the evidence stage. A petition that says the beneficiary has extensive knowledge of company systems has said nothing testable. One that says she designed the carrier settlement module, wrote its rating engine, is one of four people who have ever modified its integration layer, and led two prior terminal migrations, has given the adjudicator something to weigh. The company should also explain why sending her is necessary rather than convenient, in terms of what a locally hired person would need to learn and how long that would take. Convenience is not the test, but necessity is persuasive.
Hypothetical example: a seed-genetics data steward alone understands the firm’s validation protocol. The review should decide whether the knowledge is company-specific and required in the American role, using training logs, authored protocols, project history, and supervisor evidence. Ask for the missing primary record before selecting a filing or travel step. The usual error is that general praise for a capable worker does not demonstrate specialized knowledge. Put the conclusion in a dated fact sheet so later changes in duties, ownership, or qualification remain visible.