Five Lessons From Building New Inventions Inside Established Technology Companies
By James Borzilleri | July 5, 2025 | Updated October 2026
Most companies past their first few years of revenue have engineers who invent things every quarter. Very little of it gets written down, and even less becomes a new product line or a filed application. The work ships, the team moves on, and the idea quietly becomes common knowledge in the market.
I have spent a long time on both sides of this problem, as an inventor and as someone helping teams turn engineering work into owned assets. These are the lessons that keep coming up.
1. The roadmap will always win unless invention has its own time
Engineering leaders rarely say no to invention work. They just never schedule it. Sprint commitments, customer escalations and release dates fill every available hour, so new concepts and invention records keep slipping to next quarter.
The teams that make progress treat invention as a separate track with its own owner, its own calendar and a short, fixed time box. A few focused sessions a quarter tends to produce more than a standing promise to do it when things calm down.
2. Start with what the business needs to own
Ideation without a business brief produces clever ideas nobody will fund. Before generating anything, write down the markets you want to enter, the competitors you expect to face and the parts of your product a rival could copy most easily. Those inputs shape which concepts are worth developing.
3. Existing code hides more inventions than people expect
Engineers tend to dismiss their own work as routine. In practice, the workaround someone built for a performance problem, or the way a system handles an unusual data condition, is often where the most defensible technical ideas sit. A structured, read-only review of existing systems frequently surfaces candidates the team never thought to mention.
4. Screen for commercial use before anyone writes claims
A patentable idea that nobody would pay for, license or design around is an expensive trophy. Each candidate should face a few plain questions early:
- Would a customer pay for this, or would a competitor need it?
- Could we detect if someone else used it?
- Does it support a product, a service or a process we plan to run?
- Is it better protected as a patent, kept as a trade secret, or published defensively?
5. Keep the legal work with counsel, and keep counsel close
Patentability, inventorship and claim strategy are legal questions. The most efficient programs prepare clean technical material, prior-art notes and a clear commercial rationale, then hand that package to licensed patent counsel who make the legal calls. Counsel spends their time on judgment rather than on reconstructing what the engineers meant.
None of this produces a predictable result on any single idea. What it does produce is a repeatable pipeline, so the business is choosing among real options instead of hoping someone remembers to file.
This article is general information, not legal, tax or investment advice. Idea Partnership is not a law firm and does not provide legal opinions. Patentability, inventorship, filing strategy and disclosure questions should be reviewed with licensed patent counsel for your specific facts.