Pyrnova™ for investors and accelerators
Pyrnova is building intelligence software that tells an organization which outside changes affect it and why, starting with U.S. federal contractors. This page summarizes the problem, the product, the first market and the current evidence.
Inspect the product exampleWatch the product walkthroughExplore the platform
Company information updated 12 November 2026
The problem
Contractors already have data sources and procurement tools. The hard, repeated work is spotting which outside changes matter to their own organization, checking the reasoning and deciding what deserves attention.
How the product works
Pyrnova connects each change to the customer’s own programs and interests, keeps the source and the uncertainty with it, records the customer’s review separately, and keeps every version as new evidence arrives.
Follow the worked exampleEvidence for Recompete approaching on Programme Alder
Your authorized viewSource fact support · Recorded source for the observed event; inference remains assessed separately.
Independent origins · 1
Limit or gap · Coverage completeness is unknown: no recorded movement does not establish that nothing happened.
Version 1 basis
Period of performance ends 30 Jun 2027
- Source observation
- 1 Oct 2026
- Delivered
- 2 Oct 2026
Version 2 basis · Modification 07
Period of performance ends 31 Dec 2027
- Source observation
- 3 Nov 2026
- Delivered
- 4 Nov 2026
Claim
Period of performance on ALD-24-0117 extended to 31 Dec 2027
Support
Fictional procurement record
Recorded source for the observed event
Contradiction
None recorded.
Limits
Coverage completeness is unknown.
Gaps
- No independent corroboration: one source.
- Value at stake is not recorded for this change.
- No outcome has been observed.
The initial buyer
The operating focus is mid-market U.S. federal contractors, ordinarily around $50 million to $300 million in annual revenue, with lean capture, business development or strategy teams. This is a customer definition, not a claim of current sales.
The commercial model
A bounded initial engagement precedes an annual organizational relationship. The value hypothesis is more useful investigation and prioritisation for a defined customer scope. Prices and architecture alone do not establish customer demand or delivery margins.
The scale thesis
The same shared record of companies, evidence and dates can serve many customers, while each customer’s decisions stay private. Other sectors would still need their own sources, workflows and commercial testing.
Development evidence
Customer application surfaces are implemented and covered by dated pre-production verification records. Production access remains gated. Technical progress, customer validation, realized revenue and measured production scale are separate evidence categories.
| Category | Public statement | State |
|---|---|---|
| Technical progress | Customer application surfaces implemented, with dated pre-production verification records. | Recorded |
| Production access | The production application and customer access remain gated behind activation conditions. | Gated |
| Customer validation | Assessed separately from engineering progress. | Not stated |
| Realized revenue and production scale | Not inferred from architecture or pricing. | Not stated |
Support priorities
The immediate priorities are product qualification, customer discovery, pilot introductions, commercial development and access to suitable technical and founder networks. Accelerator support should advance those specific tasks.
Company and investment information
This page is a company overview. It does not offer securities or publish financing terms. Customer-specific information and confidential diligence material are outside the public website.