A focused pilot should answer a practical question: can a connected evidence workflow help your team move forward with more clarity? Agree on the collection, the work and the outcomes before committing.
Pricing is agreed after scoping. Preparing a brief creates no subscription or agreement.These are scoping paths, not purchasable plans. Product volume, workflow complexity, technical requirements and support shape an eventual proposal.
For a team that wants a clearer view of product records and the evidence behind them.
For a team evaluating evidence requests, ownership and review across a supplier workflow.
For organisations that need to establish data, governance and integration requirements before a deployment.
Define the questions the pilot should answer. A representative collection and a named owner keep the work focused.
Identify the products, intended markets, available evidence and the person responsible for the evaluation.
Specify the product fields, evidence checklist, supplier steps, review responsibilities and technical boundaries.
Choose concrete measures, such as visible evidence gaps, assigned ownership or a documented review process. Agree on the timing and price.
Evaluate the agreed outcomes. Decide whether to continue, change the scope or conclude the pilot, including data export and retention arrangements.
Understand the demonstration, the scope and the decisions that belong in a pilot agreement.
Pricing depends on the product collection, workflow complexity, technical requirements and support needed. Scope, price, timing and responsibilities must be agreed before starting. There are no published numerical fees on this website.
A representative collection, a description of your available evidence, a named owner and an initial objective. Include any security or integration requirements. Share real documents only after data handling arrangements are agreed.
The pilot enquiry form records your message for review. A received enquiry is not an accepted pilot agreement and does not create a paid subscription. Account registration is a separate action.
The separate browser demo uses fictional records and local page interactions. The authenticated workspace stores your organisation’s records on the server. Hosting, storage, email, AI and billing must be configured and reviewed for the intended deployment.
No. It indicates evidence completeness within the demonstrated checklist. It is not a legal assessment, certification or guarantee of market access. Applicable requirements and supporting evidence need qualified review.
No. Workspace CSV and draft JSON exports are implemented. Email, AI and billing depend on configured providers. Spreadsheet imports and ERP/PIM connectors are not currently available and require separate technical discovery. See the integration availability matrix for the current boundaries.
The pilot agreement should define an outcome review, next-step decisions, data export and retention or deletion arrangements. A wider deployment requires a separate decision; no automatic subscription is created here.
Explore a product record, register a supplier request and inspect a draft export using fictional data in the local workspace.