Validate a case before investing
Agree the scope, deliverables and value measurement before starting integration.
See the relevant programmeDeploy NELSE
A measurable first outcome.A clearly defined scope.
Start with a real case: a patient journey, a regulatory dossier, an AI use or a decision inside your software. Define what must work, the evidence expected and the budget before expanding the deployment.
Scoped quote. Educational demonstrations are separate from customer deployments. No guaranteed audit outcome or automatic compliance.
Your need comes first
Four ways to start. Not eleven choices to untangle.
Turn AI policy into operational control
Select GATE, CONTROL or AGENT controls and connect them to the NELSPACE governance record.
See the relevant programmeEmbed NELSE in your software
Keep your interface and scope an API or OEM integration instead of imposing another product.
See the relevant programmePrepare for an audit or inspection
Organise evidence, versions, owners and gaps within an explicit scope.
See the relevant programmeA pilot that supports a decision
Measure first. Test together. Decide on evidence.
01 · Baseline
Measure current time, quality, rework and volume on representative cases.
02 · Agreed scope
Fix the corpus, policies, data, systems, roles and limits. Scope integration dependencies.
03 · Test and acceptance
Test expected cases, boundary cases, human hand-offs and the evidence actually produced.
04 · Value review
Compare with the baseline, record gaps and decide next steps without extrapolating one pilot to an entire group.
Prepare your buying decision
What value must your pilot demonstrate?
Your assumptions, not a savings promise. Include all costs: licence, usage, maintenance, support and additional internal work. Commercial amounts still require a scoped quote.
This calculator neither sends nor stores your values. No assumed customer result is prefilled.
Your business case scenario
Complete all six fields. Enter zero explicitly for a zero cost.
The complete catalogue
Eleven programmes, composed around your scope.
These programmes are delivery and industrialisation options, not eleven separate software products to buy. Selected deliverables, their availability and approval steps are specified in your proposal.
01
Regulatory Design Sprint
Close one use case, one perimeter and one business case before building.
Who is it for and what is delivered?
Legal/compliance, regulatory affairs, AI leadership, CIO/CTO, software vendors and business owners.
Service Charter · target perimeter · systems/data map · candidate sources · candidate reference cases · integration architecture · KPIs · pilot plan.
02
Private Normative Pack
Compose applicable regulation and internal policy into a versioned maintainable asset.
Who is it for and what is delivered?
Regulated groups, compliance teams, software vendors, professional firms and product teams with a repeatable perimeter.
Private normative pack · versioned corpus/policies · reference cases · source-to-requirement mapping · tests · deployable release.
03
Use-Case Accelerator
Industrialise one regulated decision or workflow ready for integration.
Who is it for and what is delivered?
Business teams, quality, compliance, operations, software vendors and integrators.
Use-case accelerator · executable demo · reference cases · input/output contract · evidence package · API/MCP integration where in scope.
04
NELSIA Launch
Move from declared AI governance to operational control.
Who is it for and what is delivered?
AI leadership, CIO/CISO, DPO/legal, Model Risk, AgentOps and regulated business teams.
AI Governance File · policy layer · Human Review paths · Evidence Pack · selected GATE/CONTROL/AGENT controls · incident/review pack.
05
Embedded / OEM
Keep your software and embed the NELSE regulatory layer.
Who is it for and what is delivered?
SaaS vendors, platforms, integrators and enterprises with internal products.
Integration contract · sandbox · fact/action mapping · typed errors · observability · source→rule→fact→result→human→proof trace.
06
Regulatory Change Intelligence
Turn regulatory monitoring into impact, release and reassessment.
Who is it for and what is delivered?
Regulatory affairs, compliance, legal, quality, product compliance and software vendors.
Targeted monitoring · triage · change review · impact report · affected dossiers · releases · history · SLA by criticality.
07
Control Ready / Evidence Readiness
Prepare for audit, inspection or due diligence with a structured dossier.
Who is it for and what is delivered?
Compliance, internal audit, legal, DPO, quality and executive teams.
Control pack · evidence map · gaps · owners · versioned export · remediation plan.
08
Replay & Verification Drill
Periodically verify that a dossier remains examinable and replayable.
Who is it for and what is delivered?
Risk, quality, audit, legal, security and regulated leadership functions.
Verification report · replay report · limitations · divergences · corrective actions · attestation where applicable.
09
Country / Framework Extension
Extend a service to a jurisdiction or framework without starting again.
Who is it for and what is delivered?
International groups, software vendors, MedTech, finance, pharma and European platforms.
Extension pack · regulatory delta · new tests · new approvals · new release.
10
Normative Conformance Challenge
Try to break the governed perimeter before an audit does.
Who is it for and what is delivered?
Risk, compliance, QA, security, technical leadership and enterprise procurement.
Challenge plan · adversarial cases · defect report · fixes · non-regression · residual limitations.
11
Policy Co-Authoring & Enablement
Give customer experts autonomy without making them maintain the law.
Who is it for and what is delivered?
Legal, compliance, DPO, quality, domain experts, partners and integrators.
Customer policy pack · business cases · structured internal rules · ownership map · change workflow · reviewer enablement.
Compose with NELSE
Your policies. Governed rules. Explicit responsibilities.
You define the need
Countries, regulations, internal policies, procedures, thresholds, business cases and existing software: the scope is composed with your experts.
Validation stays governed
A proposed internal rule does not become validated law. Sources, interpretations, tests and approvals remain distinct and versioned within the agreed scope.
You control what follows
Your assets, exports and usage rights are defined in the agreement. The engine, generic components and NELSE know-how remain protected. Every country extension requires its own scoping and approvals.
Before you commit
What your proposal must make explicit.
Scope and availability
Countries, corpus, product, version and capabilities: distinguish demonstrated features, configuration work and development needs. The agreement states exclusions.
Deliverables and acceptance
Sample cases, expected outputs, missing-information handling, human approvals and acceptance protocol are defined before the pilot.
Timeline and responsibilities
Schedule agreed after scoping, system access and reviewer availability. Identify who supplies data, approves outputs and maintains the deployment.
Complete budget
The quote separates setup, integration, licence, included volumes, any overages, maintenance and support. Website coverage is not a pricing commitment.
Security and exit arrangements
Hosting, access, retention, subprocessors and export arrangements are reviewed for your deployment. Health-data requirements are checked before any real data is used.
Decision to proceed
The review compares results with agreed criteria: proceed, remediate or stop. Licence, maintenance and extensions are explicitly defined; a demo is not production deployment.
Make the next conversation concrete
Bring one case. Scope the first outcome.
Describe the workflow, its volume, the countries involved and the software you need to keep. Do not send health data or confidential case material through the public form.