Structured Technical Disclosures from Code — In Minutes, Not Hours
Your clients' codebases contain strategic concepts worth evaluating. Our scanner surfaces them and delivers structured technical disclosures with evidence from the actual code, ready for your review.
Schedule a ConversationThe intake problem.
Software clients describe their innovations in vague, non-technical terms. Translating that into structured patent disclosures takes hours of billable time, and still misses innovations the client didn't know they built.
Hours per disclosure
Extracting technical details from developer conversations is slow and expensive for both sides.
Hidden inventions
Developers don't know what's novel in their code. Manual interviews miss inventions that live in the implementation details.
Innovation moved to code
With AI-assisted development, the real novel ideas are in the code itself, not in Confluence pages or meeting notes.
Your clients' unfiled inventions stay confidential.
Attorneys won't use AI tools that send unfiled inventions to third-party servers. We built our architecture around that constraint.
Local-first scanning
Our downloadable scanner runs entirely on your client's machine using a local LLM. Source code and analysis results never leave the device. No data transmitted to any external service.
Minimize exposure window
From scan to structured disclosure in minutes, not months. The less time an invention sits unprotected, the lower the risk. Speed-to-file is itself a security feature.
How it works for your practice.
Client connects their repo
Your client pastes a GitHub URL into our scanner. First scan is free. Takes minutes, not hours.
Scanner generates structured disclosures
AI analyzes the codebase and surfaces scored strategic concepts with evidence citations from the actual code. Each concept includes a distinctiveness score, prior art context, and technical detail for your patentability review.
You review and file
Every discovery traces back to specific files and code lines, giving you verifiable evidence to review against the actual implementation. You receive pre-structured disclosures anchored to technical implementations, not abstract concepts. Review, refine, and file.
Your clients are sitting on patents they don't know about.
Our scanner surfaces candidate inventions from codebases your clients already have. You turn those into filed patents. More discoveries, more filings, more value for your clients.
Surfaces
Scans repos, agent files, and PRs for novel concepts your clients missed
Structures
Formats discoveries as technical disclosures with evidence from the code
Delivers
You draft claims, assess eligibility, and file. The part that requires a patent attorney.
Why ObviouslyNot.
Alice/Mayo aware
Our scanner anchors discoveries to specific technical implementations, documents unexpected technical benefits, and identifies non-analogous field combinations. Built with Section 101 compliance in mind.
Scans where innovation lives
Existing IP tools scan Confluence and meeting notes. We scan Git repos, agent files, and PRs, where innovation actually happens now.
Attorney-first by design
Built with input from practicing patent attorneys at Am Law 100 firms and Fortune 500 in-house teams. The scanner handles technical analysis. You exercise the legal judgment that makes it count.
New client pipeline
Developers discover candidate inventions through our scanner and need attorneys to file. A new source of clients who already know what they want to protect.
Built for in-house teams, too.
In-house patent counsel face a unique challenge: engineers write code with patent potential but don't flag it. They don't know what's distinctive, and they don't have time for lengthy intake processes. Research from Nature (2025) shows that patents involving women score higher on novelty and disruption, and mixed-gender teams produce the most disruptive work. Broader invention surfacing is not just inclusive. It produces better IP.
Our Patent Representation Gap Index shows the gap company by company across 170 tech companies. At most organizations, the top 5% of inventors account for 40-70% of all filings. The rest of the engineering team is invisible to the patent program.
Accelerate invention surfacing
The scanner surfaces innovations from the codebase so attorneys can focus interviews on the highest-value discoveries. Faster intake, better coverage.
Systematic portfolio building
Scan across engineering orgs to systematically identify innovations. Turn reactive IP strategy into proactive portfolio building.
Runs inside your perimeter
Local-first scanning keeps source code within your corporate environment. No external API calls, no cloud uploads, no compliance review required.
Research for the prosecution side.
Recent USPTO policy, court decisions, and published data have direct implications for how attorneys structure responses, allocate budget, and counsel clients. Selected pieces from our research:
USPTO and §101 in 2026
Section 101 declaration strategy
The USPTO's April 30, 2026 SMED memo, the §132(a) new-matter constraint, and why the evidentiary opportunity lives at the drafting stage. What a SMED can and cannot do.
AI patent discovery & privilege
Baker Donelson, May 2026: GAI use may lack privilege protection. Why structured-disclosure tools with audit trails are categorically different in discovery.
Software patents after Alice (updated)
Patently-O's corrected §101 examiner data: rejection rate climbed to ~15.5% by mid-2025. Plus the TJTM v. Google Federal Circuit decision (May 5, 2026).
Prosecution outcomes research
The breakthrough penalty (PNAS 2026)
6.2M applications. 14.9 pp grant rate gap on unconventional inventions. Mediated by examiner experience, not bias. Direct implications for response strategy.
Where women's patents disappear
The prosecution funnel, stage by stage. Half the gap lives in differential abandonment after rejection. The highest-leverage budget point.
Closing strategies that work
The USPTO RCT: +12 pp grant rate from examiner-side procedural support. The four interventions with measured evidence.
Built by founders who understand IP.
Our team has contributed to patented systems, scaled a venture-backed SaaS platform to $50M ARR (acquired 2020), and built multi-region AWS architecture serving millions. We understand both the technology and the stakes.
Validated in conversations with practicing patent attorneys from Am Law 100 firms and Fortune 500 in-house teams.
Questions attorneys ask us.
Where is my client's code processed?
Our downloadable scanner runs entirely on your client's hardware using a local LLM. No code is transmitted to any external service. For the hosted scanner, analysis runs on US-region infrastructure only. We never store source code after analysis completes.
What about foreign filing license requirements?
Patent-related material processed on foreign servers can create compliance considerations under 35 U.S.C. 184 (foreign filing license) and applicable export controls. Our local scanner is designed to reduce that exposure by keeping processing on the user's machine. For the hosted scanner, processing runs on US-region infrastructure. Counsel should still evaluate the foreign-filing-license analysis, export-control obligations, client policy, and deployment details for each matter; the architecture reduces transmission concerns but does not eliminate the legal analysis.
Does this create unauthorized practice of law concerns?
The tool is designed to avoid UPL by producing structured technical disclosures (technical documentation), not legal advice, claim strategy, patentability opinions, or filing recommendations. Attorneys draft claims and make filing decisions; ObviouslyNot accelerates the intake step. As with any tool that touches client work, the practice's UPL analysis is jurisdiction-specific and remains the responsibility of counsel.
How does this handle Alice/Mayo eligibility issues?
Our scanner anchors discoveries to specific technical implementations, documents unexpected technical benefits, and identifies non-analogous field combinations. The output is structured to support Section 101 arguments, but eligibility analysis remains the attorney's responsibility.
Can I use this for office action responses?
Not yet, but it's on our roadmap. The underlying analysis capability that supports discovery can be applied to office action research. If this is important to your practice, let us know.
Let's talk about how this fits your practice.
Schedule a ConversationScanner output is structured technical analysis for your review. All patentability determinations remain with you.