Start with what you have.
We'll tell you what fits, what's custom, and what's missing.

Fit, gaps, and effort — line by line.

Drop in a statement of work or scope document. The Neural Engine benchmarks every line against the platform corpus and tells you what's standard out-of-the-box, what's genuinely custom and worth paying for, what's missing from the scope entirely, and where effort estimates drift from peer benchmarks — in either direction.

Standard vs. custom, before you negotiate.

Paste a requirements list or process spec. Every requirement is classified as standard (configurable out-of-box), custom (needs development), or absent from the corpus. Use the breakdown to shape what belongs in your SoW — or feed it directly into the Scope + SoW analysis for a fully grounded picture.

A single requirement is fine — you don't need a list.

From existing SOPs to RFQ requirements.

Drop in SOPs from your current system. Specforge maps each procedure to what the target platform handles natively versus what requires custom work. The output becomes requirements language for your RFQ — and a validation baseline to check any SoW you receive against it.

Have a BPD? See an independent assessment.

Drop in a business process design — your own, or one your integrator wrote for you. You get back the requirements it carries, laid out as a traceability matrix, and the parts of the process it has not covered. Each requirement is checked against the platform corpus: standard, configuration, or custom. Then the test cases and end-to-end scenarios that would prove the design, in one workbook.

Sign in to run an assessment.

A freeform RFP, read as scope.

Drop in an RFP as it was issued — prose, tables, whatever arrived. Specforge pulls out the deliverables and requirements buried in it and classifies each against the corpus, so you can see what the RFP is actually asking for before you price a response to it.

What actually changed between releases.

Pick the release you run today and the one you're considering. Specforge lists what changed in between — new, changed, deprecated, removed, and what becomes mandatory — drawn from the release's own documentation, so the upgrade conversation starts from the delta rather than a summary of it.