QgenticQgentic
Qgentic / partners
Partner programme · consultancies and practices

Your engagement, our engine.

You bring the domain expertise and the client relationship; Qgentic brings the deterministic engine. It is the technical layer that turns advisory work into verifiable, regulator-ready evidence, delivered under your brand.

From spreadsheets to validated evidence

Engagement deliverables usually mean spreadsheet registers and scattered document folders, with nothing that validates them and nothing that records who changed what. Qgentic replaces the manual collation with deterministic processing, so you deliver structured, verifiable compliance evidence and your client never has to buy a GRC platform.

Assembly and validation, automated

Data aggregation, schema validation and evidence packaging move from your team's hours to the engine.

Output anyone can verify

Validated registers with hashed manifests and tamper-evident audit trails, which your client can verify independently.

One way of working

DORA, OpRes and the AI Act run on the same data structures and the same approval mechanism, so one technical skill set covers all three.

Who partners with us

Compliance and risk consultancies

You advise on DORA, OpRes or AI governance; Qgentic supplies the register generation, rule validation and evidence packaging.

DORA, OpRes, AI Act

Accountancy practices

Making Tax Digital (VAT and ITSA) across a client portfolio, with strict tenant isolation, scheduled bulk runs, identity-bound approvals and a separate audit trail per client.

The MTD module

Systems integrators and MSPs

You already hold the client's ERP access. Point the standard connectors at it and the engine extracts and validates the regulatory data.

Integration and data

Prerequisite: Partners must own and manage the end-client relationship. Qgentic operates strictly as a technology provider in these engagements.

What partners get

Strict tenant isolation

Each client is its own tenant: data, cryptographic audit chains, usage telemetry and IAM approval profiles are isolated per client.

Every module

The complete suite (DORA, UK OpRes, MTD VAT and ITSA, the EU and UK AI modules) under one framework, without licensing module by module.

Any deployment

Multi-tenant SaaS, an isolated single-tenant instance, or the air-gapped edition where data residency is strict and sub-processors are ruled out.

White-label deliverables

Reports and evidence packages carry the partner's brand as its own work product, with Qgentic underneath as the technical layer.

Volume discounts

The standard multi-module discounts apply: 10% off base fees for two modules and 15% for three or more, with metering at standard rates. See pricing.

Technical enablement

Short-lived demonstration tenants, technical documentation, dedicated engineering support and access to preview environments for roadmap planning.

Where the line is

Enforced in every deployment

The client approves, by name

Partners run configuration, execution cycles and package preparation, but they cannot approve a final submission. IAM controls require the final approval to come from an authorised, named person in the client's own organisation, and that control cannot be delegated.

Three terms sit in every partnership contract:

Licences come from Qgentic

Software licences and air-gapped entitlements are issued only by Qgentic. Partners manage deployment but cannot generate or sub-license keys.

One codebase

There are no per-partner forks. Functionality a partner needs goes into the core platform, as configuration.

Accurate claims

Partners represent the platform as it is: “prepare-only” where an API is prepare-only, “pending” where the HMRC directory listing is pending. Accuracy is a condition of the programme.

How a partnership starts

  1. ScopeSettle the modules, the deployment (SaaS or air-gapped), the approval structure and the commercial model (referral or delivery partner).
  2. EvaluationA 30-day tenant for technical validation. The in-browser demos are worth seeing first.
  3. ContractThe standard Master Terms, the Partner Schedule and explicitly scoped Order Forms.
  4. ImplementationA tenant per client. Partners manage data integration and execution cycles, with data and identity isolated per tenant.
  5. ReconciliationQuarterly billing is read from the cryptographic meter, so the invoice provably matches the usage.

The goal of enablement is independence: after the first client, a partner runs its deployments on its own.

Frequently asked questions

Is this a reseller or referral programme?

Both. A Delivery Partner contracts directly with the client and carries the billing and credit risk. A Referral Partner introduces the client, and Qgentic contracts, bills and pays a referral commission. The Order Form sets the model for each engagement.

How are partner margins structured?

Margins are negotiated per partner and written into the Order Form. The standard volume discounts (10% for two modules, 15% for three or more) apply to base platform fees and leave metered charges at standard rates. They are volume pricing, separate from the partner margin.

How is client ownership managed?

Non-circumvention clauses protect the partner's client relationship. Qgentic will not solicit a partner-introduced client for active modules during the contract term or for 12 months after it ends. In return, partners represent Qgentic accurately, as the technology underneath.

Are white-label deliverables supported?

Yes, for external reports and extracted packages. The audit chains, hashed manifests and internal evidence keep their Qgentic identifiers, because removing them would break the verification an auditor relies on.

What are the capacity limits for new partners?

Intake is limited, so every partner gets proper enablement and engineering support. Each engagement is assessed for technical and operational fit before onboarding.

What is the continuity plan for end-clients?

Client evidence (registers, audit chains) is written in open, documented formats and kept on the client's infrastructure, so verifying old runs needs no Qgentic service at all. Air-gapped deployments run on their own, and source code escrow and NDA-bound source reviews are available on request.