Resources

Buyer-facing resources in one place.

Use this static index to choose module routes, qualify buyer fit, prepare technical review, understand engagement paths and forward concise briefs.

Resource boundary

An index for navigation, not a gated library.

Every card links to an existing public route. The index does not create downloads, submissions or public source access.

Public limits

What this page preserves.

  • Static public resources only; no forms, backend, gated content or CRM workflow is added here.
  • No public source-code download, automatic access, checkout or public pricing is created by this index.
  • Synthetic previews remain synthetic; no buyer records are shown on the public site.
  • AI Approach explains deterministic-first modules, Claims Pro AI scope and tenant-specific ML upgrade paths.
  • Claims Pro AI Evidence and Claims Pro Demo routes are evidence-gated public explanations, not public eval packs, source access or live demos.
  • Intelligence resources explain ML-ready and ML-assisted review support with buyer-side validation required.
  • No validated predictive ML accuracy claim and no guaranteed ROI.
  • BOQ / Cost Intelligence and Tender Comparison & Award remain proposal-stage only.

Module selection

Choose the right module route first.

Use these pages to compare maturity, public status, buyer fit and data objects before requesting review.

Modules catalogue

The five public module routes split into review-ready source-package offers and proposal-stage modules.

Best user
Product, engineering, partnerships or commercial buyer doing the first module scan.
When to use
Start here when the buyer knows the workflow area but has not chosen a module route.
Open resource

Module comparison

A fast qualification table for status, workflow fit, inputs, outputs, integrations and disqualifiers.

Best user
Technical, product or commercial reviewer comparing multiple module paths.
When to use
Use before a call to decide whether Project Risk, Change/Claims, Subcontractor Cost Control, BOQ or Tender fits best.
Open resource

Data requirements

Module-by-module data object expectations, ML-readiness labels, sensitive-object boundaries and missing-data behavior.

Best user
Technical, data, workflow or integration owner preparing review context.
When to use
Use before sending a questionnaire, scoping technical review assumptions or preparing an ML/data readiness review.
Open resource

Buyer qualification

Route the conversation by buyer type.

These resources help decide whether the visitor has the right workflow, role and review expectation.

Buyer segment routes

Static pages for construction software vendors, ERP/system integrators, PMO teams, platforms and advisory buyers.

Best user
Outbound recipient, partner lead or buyer stakeholder trying to self-identify fit.
When to use
Use when a buyer type is clear but the strongest module route still needs narrowing.
Open resource

Technical review questionnaire

Copy-ready email fields for module selection, context, environment, data, integration assumptions and review format.

Best user
Buyer owner preparing a specific first email.
When to use
Use before contacting Nivorqa Labs so the first exchange has enough context.
Open resource

Contact paths

Email-only routes for technical review, source-package discussion, paid pilot scoping, proposal scoping and strategic inquiry.

Best user
Qualified buyer or internal champion ready to send a structured email.
When to use
Use after the buyer has module interest, workflow gap, intended use and timeline.
Open resource

Technical review preparation

Prepare the review without opening source access.

These pages explain what can be reviewed, what remains synthetic and how technical diligence starts.

Review pack

Forwardable diligence surface for maturity routes, synthetic previews, integration assumptions and disclosure boundaries.

Best user
Internal champion aligning technical, product, commercial and strategic stakeholders.
When to use
Use before a qualified review call or before forwarding the opportunity internally.
Open resource

Technical review path

A static explanation of fit check, maturity route, review-pack route, data assumptions and commercial path.

Best user
Technical or product owner deciding whether review is worth scheduling.
When to use
Use after initial module interest and before requesting deeper discussion.
Open resource

Architecture outlines

Buyer-facing module architecture pages covering inputs, processing, outputs, integration points and source-review boundaries.

Best user
Product, engineering, architecture or integration owner preparing technical review questions.
When to use
Use when the buyer needs technical structure before discussing source-package review.
Open resource

AI Approach

Deterministic-first AI strategy: evidence-gated Claims Pro AI evaluation path, with Risk and Subcontractor ML upgrade paths by tenant.

Best user
Product, engineering, data or governance owner asking what is implemented, eval-only, roadmap or buyer-data-dependent.
When to use
Use before discussing Claims Pro AI evidence status, provider configuration, audit logs, evaluation metrics or tenant-specific ML upgrade paths.
Open resource

Claims Pro AI evidence

Evidence-gated public page for Claims Pro extraction, structuring, semantic search, audit logging, evaluation metrics, deterministic fallback and claim boundaries.

Best user
Technical, product, data or governance owner asking what Claims Pro AI evidence can be reviewed after qualification.
When to use
Use before requesting eval reports, model cards or due diligence material through controlled technical review; buyer-side validation required.
Open resource

Claims Pro demo narrative

Synthetic architecture/demo narrative for Claims Pro clause extraction, change narrative structuring, analogous case search, human verification, audit logging and deterministic fallback.

Best user
Technical, product, data or governance owner who wants to understand the Claims Pro AI flow without buyer records or public downloads.
When to use
Use before technical review when the buyer needs a synthetic walkthrough rather than source files, eval files, live data or a public demo account.
Open resource

Intelligence Layer

Public explanation of deterministic workflow logic, construction signal extraction, ML-assisted review and governance boundaries.

Best user
Product, data, engineering or workflow owner reviewing intelligence architecture safely.
When to use
Use when the buyer asks how ML-ready and ML-assisted patterns fit the modules without validated ML or ROI claims.
Open resource

ML readiness

Architecture note explaining ML-ready data structures, buyer labels, evaluation design and what cannot be claimed publicly.

Best user
Technical, data or product owner preparing ML-assisted validation questions.
When to use
Use before discussing anomaly detection, similarity search, classification, ranking, embeddings/RAG or forecasting candidates.
Open resource

ML/data readiness review

Buyer-qualification route for deciding whether data, labels and governance boundaries are ready for paid technical review or pilot discussion.

Best user
Product, engineering, data or workflow owner with historical data and label-readiness questions.
When to use
Use when a buyer asks whether available data and labels are ready for ML-assisted review support without validated ML claims.
Open resource

Model governance

Human-in-the-loop review, traceable recommendations, confidence/completeness scoring, logging and drift/evaluation concepts.

Best user
Governance, product, engineering or buyer-side reviewer responsible for operational review boundaries.
When to use
Use when the buyer needs explainability, auditability or governance boundaries before deeper review.
Open resource

Commercial engagement paths

Understand the controlled next-step options.

These resources explain review, pilot, source-review and strategic paths without publishing prices or contracts.

Engagement models

Comparison of review pack, technical review, paid pilot, controlled source review, strategic discussion and proposal-stage scoping.

Best user
Commercial, partnership, product or strategic buyer choosing the next route.
When to use
Use when the buyer asks how engagement can proceed after initial qualification.
Open resource

Paid pilot scoping

Explains one-module pilot objectives, prerequisites, data expectations, outputs, buyer validation and no-go criteria.

Best user
Qualified workflow owner evaluating a bounded pilot around a review-ready module.
When to use
Use after module fit is plausible and the buyer wants a scoped commercial review path.
Open resource

Controlled source review

Clarifies buyer roles, qualification, agreement checkpoints, source disclosure boundary, exclusions and decision outcomes.

Best user
Technical, product, engineering, partnership or strategic buyer with a source-review question.
When to use
Use when a serious buyer asks what happens before any controlled source-package discussion.
Open resource

Forwardable briefs

Share concise pages with stakeholders.

Use these static pages when the buyer needs compact internal material rather than a broad site tour.

Module briefs

Print-friendly pages generated from the existing module data for each public module route.

Best user
Internal champion forwarding a specific module to technical or commercial stakeholders.
When to use
Use when one module needs a concise status, scope and next-step summary.
Open resource

One-page executive brief

A compact overview of module maturity, review paths, synthetic preview posture and disclosure boundaries.

Best user
Executive, partnership lead or strategic reviewer needing a short public summary.
When to use
Use when a buyer needs the shortest forwardable orientation before requesting the review pack.
Open resource

Claim boundaries and FAQ

Answer common buyer questions conservatively.

Use this page to resolve basic questions before a buyer asks for unsupported access, proof or claims.

FAQ

Answers common questions about Intelligence Layer, ML readiness, source-code access, sandbox expectations, pricing, previews, module status and claim boundaries.

Best user
Any buyer or internal stakeholder checking what the public site does and does not imply.
When to use
Use before replying to repeated qualification, access, pricing, proof or claims questions.
Open resource

Recommended next step

Prepare the review request after choosing the right resource.

If the buyer has module interest, workflow gap, intended use and timeline, use the review-pack email path.

Request review pack Open architecture

Direct line

labs@nivorqa.com

Use email for review-pack requests, module fit questions, licensing conversations and pilot scoping.