Engagement Delivery Architecture.
Your domain expertise and client relationships; our deterministic engine. Qgentic is the technical layer that turns advisory output into verifiable, regulator-ready evidence — delivered under your brand.
Demos run entirely in-browser. No account required for technical evaluation.
Transitioning from Manual Processes to Automated Validation
Traditional engagement deliverables (e.g., spreadsheet-based registers, disjointed document repositories) lack programmatic validation and cryptographic auditability. Qgentic replaces manual evidence collation with deterministic processing, allowing partner organisations to deliver structured, verifiable compliance assets without requiring clients to procure enterprise GRC platforms.
Automated Assembly & Validation
Shift data aggregation, schema validation, and evidence packaging from manual tasks to programmatic workflows, optimising resource allocation.
Cryptographically Verifiable Output
Deliver validated registers bundled with hashed manifests and tamper-evident audit trails. Clients receive independently verifiable compliance artifacts.
Unified Operational Framework
Standardize delivery across DORA, OpRes, and the AI Act. A single technical competency translates across multiple regulatory domains using identical data structures and approval mechanisms.
Supported Partnership Topologies
Compliance & Risk Consultancies
Provide DORA, OpRes, or AI governance advisory. Qgentic supplies the technical infrastructure for register generation, rule validation, and evidence packaging.
Accountancy Practices
Manage Making Tax Digital (VAT/ITSA) obligations across client portfolios. Features include strict tenant isolation, scheduled bulk processing, mandatory identity-bound approvals, and segregated audit trails.
Systems Integrators & MSPs
You already hold the client's ERP access. Point the standard connectors at it and the engine extracts and validates the regulatory data.
Prerequisite: Partners must own and manage the end-client relationship. Qgentic operates strictly as a technology provider in these engagements.
Platform Capabilities for Partners
Strict Tenant Isolation
End-clients are segregated into distinct tenant environments. Data, cryptographic audit chains, usage telemetry, and IAM approval profiles are strictly isolated per client.
Full Module Access
Partners access the complete compliance suite (DORA, UK OpRes, MTD VAT/ITSA, EU/UK AI Act) under a unified framework, rather than modular licensing.
Flexible Deployment Topologies
Deploy via multi-tenant SaaS, isolated single-tenant instances, or the air-gapped edition for environments with strict data residency and zero-subprocessor requirements.
White-Label Deliverables
Generated reports and evidence packages are branded as the partner's work product. Qgentic operates as a transparent technical foundation.
Tiered Pricing Structure
Standard multi-module discounting applies: 10% base fee reduction for two modules; 15% for three or more. Execution metering is billed at standard rates. See Pricing.
Technical Enablement
Includes ephemeral demonstration tenants, technical documentation, dedicated engineering support, and access to preview environments for roadmap planning.
Mandatory System Boundaries
Identity-Bound Client Approvals
While partners manage configuration, execution cycles, and package preparation, they cannot cryptographically approve a final submission. IAM controls enforce that final approval must originate from an authorised, named identity within the end-client's organisation. This non-delegable control maintains the integrity of the compliance boundary.
Standard contractual constraints for partnership engagements:
Centralised Entitlement Management
Software licences and air-gapped cryptographic entitlements are provisioned exclusively by Qgentic. Partners manage deployment but cannot generate or sub-license keys.
Unified Codebase
The platform operates on a single codebase. Per-partner code forks are unsupported; required functionality is integrated into the core platform via configuration options.
Marketing Compliance
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.
Partnership Lifecycle
- Scope DefinitionDetermine target modules, deployment architecture (SaaS vs. Air-gapped), IAM approval structures, and commercial model (Referral vs. Delivery Partner).
- Technical EvaluationAccess a 30-day ephemeral tenant for technical validation. We recommend reviewing the in-browser demonstrations prior to initialisation.
- Contractual AgreementExecution of standard Master Terms, Partner Schedule, and explicitly scoped Order Forms.
- ImplementationTenant provisioning per end-client. Partners manage data integration and execution cycles, maintaining strict data and identity isolation per tenant.
- ReconciliationQuarterly billing read from cryptographic meter streams — the invoice matches the usage, provably.
Our enablement objective is operational independence. Partners should be fully autonomous in executing subsequent client deployments.
Commercial & Operational Details
Is this a reseller or referral programme?
We support both models. Delivery Partners contract directly with the end-client and manage billing/credit risk. Referral Partners introduce the client; Qgentic contracts and bills directly, issuing a referral commission. The model is specified per engagement on the Order Form.
How are partner margins structured?
Margins are negotiated per partner and documented in the Order Form. Standard volume discounts (10% for two modules, 15% for three+) apply to base platform fees, but do not apply to metered execution charges. These discounts are structural volume pricing, separate from the negotiated partner margin.
How is client ownership managed?
Contractual non-circumvention clauses protect the partner's client relationship. Qgentic will not directly solicit partner-introduced clients for active modules during the contract term and a defined 12-month post-termination period. Conversely, partners must accurately represent Qgentic as the underlying technology provider.
Are white-label deliverables supported?
Yes, for external reports and extracted packages. However, cryptographic audit chains, hashed manifests, and internal evidence artifacts retain Qgentic identifiers. Removing these would invalidate the cryptographic verification properties required by auditors.
What are the capacity limits for new partners?
Partner intake is strictly controlled to ensure high-quality technical enablement and support engineering availability. Engagements are evaluated for architectural and operational fit prior to onboarding.
What is the continuity plan for end-clients?
Client evidence (registers, audit chains) is generated in open, documented formats and resides within the client's infrastructure, requiring no active Qgentic service for historical verification. Air-gapped deployments function autonomously. Source code escrow and NDA-bound source reviews are available upon request.
Technical Evaluation Available. Interactive module demonstrations execute in-browser without account creation. Review the generated cryptographic evidence packages against your audit requirements. To proceed, contact sales.