Find it in the files, not the field.
Machine-speed analysis of technical specifications. Find contradictions, gaps, and duplicates before sign-off.
Find it in the files, not the field.
Machine-speed analysis of technical specifications. Find contradictions, gaps, and duplicates before sign-off.
Defense requirements & acquisition analysis
GAO tracks it every year: unsettled requirements are a recurring driver behind cost growth and schedule slip on major defense acquisition programmes. Wyzer Detective checks a requirements baseline (a Capability Development Document, a System Requirements Document, a specification annex) for the internal contradictions and gaps that turn "unsettled" into an overrun.
Applied to the defense requirements you already write, in the review step you already run.
Checks a Capability Development Document against the System Requirements Document it feeds, and both against their amendment annexes, for the conflicting requirement that survives an independent review of each document alone.
Flags capability requirements with no corresponding system requirement, and system requirements with no traceable capability need. That is what a milestone decision authority asks about, and it surfaces ahead of the review rather than in it.
Multi-year programmes accumulate restated and re-numbered requirements across baseline changes. Wyzer finds where the same requirement exists twice, worded just differently enough to hide it from a text search.
Every requirement scored for measurability and completeness, which is what catches the unverifiable "shall support" language a Test and Evaluation Master Plan has nothing to test against.
Wyzer Detective doesn’t replace the process. It checks the requirement set the process depends on.
A System Requirements Document is amended twice during a five-year programme, each amendment reviewed against the section it changes. Neither review checks whether the amendment still agrees with an untouched section elsewhere in the document. Wyzer Detective re-checks the full baseline, original text plus every amendment, as one document at each revision, catching the contradiction between an amended section and an untouched one that a section-scoped review cannot see.
Wyzer’s infrastructure runs in the EU. For ITAR-controlled or classified requirements this may not fit your data-residency constraints. Tell us what you need and we’ll be straight about whether it’s a fit.
Yes. Upload the full baseline including amendments, and Wyzer checks all of it together for contradictions between original text and later changes, not just within each amendment.
Wyzer’s infrastructure runs in the EU. If that does not fit an ITAR-controlled or classified requirement set, get in touch and we’ll tell you plainly whether Wyzer is a fit before you send anything.
Same day. Export a ReqIF baseline, upload it, and Sherlock returns quality scores, contradictions, and coverage gaps within minutes. No configuration, no training data, no integration project.
No. Customer data is not used to train the system and is not exposed to other customers or external models. Data is encrypted at rest.
In the EU. Wyzer's infrastructure runs in an EU region, isolated to your environment, with standard retention capped at 90 days by default.
No practical one. Sherlock has been tested to tens of thousands of requirements with no degradation in output quality: it processes specifications in parallel batches rather than reading them end to end.
No. Reviewers keep working in the requirements tool they already use. Wyzer Detective runs before or alongside the existing review, and relevant findings get applied back into that review. It's a quality-gate step, not a new system to adopt.
Credit-based pricing that scales with the number of requirements in your specification and how complex they are (plain text vs. requirements with tables or diagrams). There's no fixed per-seat licence. Get in touch for a quote sized to your specification. Searching a finished analysis with a defect or failure description (the Requirement Scan API, in beta) costs one credit per query, whatever the size of the specification.
Yes. Any ReqIF export works as the reference: a published standard, an internal template, last year's baseline, whatever you want the current spec measured against. The comparison runs requirement by requirement, not as a single aggregate score, so you can see exactly which ones fall short.
Export a ReqIF baseline and get a full Wyzer Detective analysis within minutes: quality scores, contradictions, and coverage gaps.
← Back to all industries