Partner programme

Build, deploy and resell on-premise document AI across the GCC

DocxIntel is deployed inside customer infrastructure, which means implementation, hardware and regional relationships matter more than a marketplace listing. The partner programme is open, early and structured around four tracks — and we will tell you plainly what it does and does not include yet.

Open and early — no waiting list
Deal registration in writing
Sandbox deployment for partners
Fixed licence, predictable margin

A DocxIntel deployment running inside a customer private cloud environment delivered by an implementation partner

4
Partner tracks: GCC
Primary focus: Sandbox
Provided to every partner: Fixed
Underlying licence model

We do not publish partner counts, tier names or logos, because the programme is new and inventing a mature channel would be the first thing an experienced partner manager would see through. Everything below describes what is actually available today.

Four tracks

The kinds of partner an on-premise platform actually needs

Because the product installs inside the customer perimeter, the channel looks different from a SaaS channel. Delivery capability, hardware and regional presence carry the weight that a marketplace listing would carry elsewhere.

Track 1

System integrators and implementation partners

You already deliver core-banking, insurance, health-information or content-management projects for regulated customers in the region. DocxIntel becomes the document understanding layer inside those programmes — scoped, integrated and supported by your team.

What you do: scoping, deployment, integration into DMS, core and case-management systems, first-line support
What you get: implementation margin, technical training and certification, deal registration, sandbox access, joint architecture support
What we expect: certified engineers, honest scoping, and claims that stay inside what we publish

Track 2

Infrastructure and hardware partners

GPU vendors, server manufacturers and infrastructure distributors whose customers need a document AI workload to justify and size the hardware. DocxIntel is a well-defined, GPU-bound workload with published sizing behaviour.

What you do: reference configurations, sizing guidance, bundled hardware-plus-software proposals, on-site capacity planning
What you get: joint sizing collateral, engineering access for validation, deal registration, sandbox access for benchmarking
What we expect: validated configurations and sizing figures that are measured rather than extrapolated

Track 3

Cloud and platform partners

Sovereign cloud operators, private-cloud providers and managed platform teams who deploy into a customer's own tenancy. DocxIntel runs on bare metal, virtual machines or Kubernetes, so it fits the platform you already operate.

What you do: deployment into customer private or sovereign cloud, platform operations, availability and capacity management
What you get: reference architectures, deployment enablement, deal registration, sandbox access, joint operational runbooks
What we expect: deployments that preserve the residency and isolation guarantees the customer bought

Track 4

Regional resellers and distributors

Value-added resellers and distributors with established procurement relationships across the UAE and wider GCC, including public-sector frameworks where the contracting route matters as much as the product.

What you do: commercial relationship, procurement navigation, framework and tender positioning, renewals
What you get: reseller margin, deal registration, commercial and technical enablement, Arabic and English sales collateral
What we expect: accurate representation of the deployment model, pricing structure and accuracy methodology

Why partner with us

A fixed annual licence makes partner economics predictable

Metered products push partners into a position where the customer's success raises the customer's bill. A fixed licence removes that tension: once a deployment is in and working, growing its usage costs the customer nothing extra and the relationship stops being a negotiation about volume.

The licence is fixed and annual, so the renewal conversation is about value delivered, not pages consumed
Implementation, integration and change work stay with you rather than being absorbed into a vendor cloud service
Air-gapped and private-cloud deployments need on-the-ground engineers, which is work a remote vendor cannot do
Hardware sits inside the deal, which matters for infrastructure partners and distributors
Direct access to the engineers who build the platform, not a tiered support queue between you and an answer
The product argument is architectural, so you are not competing on per-page price in every renewal

Commercial terms, margin structure and territory are set in the partner agreement rather than published here, because they differ by track and by market.

DocxIntel sorting and classifying a mixed batch of business documents during a partner-led deployment

Side by side

What each track gets, and what each track is expected to bring

A summary you can take into an internal discussion before applying. Specific commercial terms are agreed per partner and per territory.

What each track gets, and what each track is expected to bring
Criterion	System integrator	Infrastructure / hardware	Cloud / platform	Reseller / distributor
Primary role	Deploy and integrate	Size and supply the hardware	Operate the platform	Own the commercial relationship
Commercial model	Implementation margin plus services	Hardware margin plus referral	Platform and managed-service margin	Resale margin on the licence
Enablement provided	Deployment, tuning and integration training	Sizing, benchmarking and reference configurations	Reference architectures and operational runbooks	Commercial and solution training, AR and EN collateral
Deal registration	Yes, with a written protection period	Yes, with a written protection period	Yes, with a written protection period	Yes, with a written protection period
Sandbox access	Full evaluation deployment	Benchmarking deployment	Deployment in your own platform	Demonstration deployment
Support model	You hold first line, we hold second	We hold software, you hold hardware	Shared, defined per deployment	We hold support, you hold the relationship
Certification expected	Certified deployment engineers	Validated reference configurations	Certified platform engineers	Trained commercial team
Claims discipline	Only what we publish	Measured figures, not extrapolated	Residency guarantees preserved	Accurate pricing and deployment description

Primary role

System integrator: Deploy and integrate
Infrastructure / hardware: Size and supply the hardware
Cloud / platform: Operate the platform
Reseller / distributor: Own the commercial relationship

Commercial model

System integrator: Implementation margin plus services
Infrastructure / hardware: Hardware margin plus referral
Cloud / platform: Platform and managed-service margin
Reseller / distributor: Resale margin on the licence

Enablement provided

System integrator: Deployment, tuning and integration training
Infrastructure / hardware: Sizing, benchmarking and reference configurations
Cloud / platform: Reference architectures and operational runbooks
Reseller / distributor: Commercial and solution training, AR and EN collateral

Deal registration

System integrator: Yes, with a written protection period
Infrastructure / hardware: Yes, with a written protection period
Cloud / platform: Yes, with a written protection period
Reseller / distributor: Yes, with a written protection period

Sandbox access

System integrator: Full evaluation deployment
Infrastructure / hardware: Benchmarking deployment
Cloud / platform: Deployment in your own platform
Reseller / distributor: Demonstration deployment

Support model

System integrator: You hold first line, we hold second
Infrastructure / hardware: We hold software, you hold hardware
Cloud / platform: Shared, defined per deployment
Reseller / distributor: We hold support, you hold the relationship

Certification expected

System integrator: Certified deployment engineers
Infrastructure / hardware: Validated reference configurations
Cloud / platform: Certified platform engineers
Reseller / distributor: Trained commercial team

Claims discipline

System integrator: Only what we publish
Infrastructure / hardware: Measured figures, not extrapolated
Cloud / platform: Residency guarantees preserved
Reseller / distributor: Accurate pricing and deployment description

Indicative programme structure as of 2026. Actual terms, margin and territory are set in the partner agreement. The programme is new and the structure will develop — we will not pretend otherwise in a table.

Reference

What the partner programme provides

The practical contents of the programme as it stands today, stated without inflation.

Commercial

Margin: Set per track and per deal in the partner agreement
Deal registration: Written acknowledgement with a defined protection period, and immediate disclosure of any existing engagement
Pricing structure: Fixed annual licence sized by deployment footprint — no per-page component to reconcile
Proof of Value: Partner-led or joint, with the accuracy threshold and conversion price agreed in writing first
Renewals: Partner retains the relationship on partner-originated deals

Technical enablement

Training and certification: Deployment, sizing, tuning, exception handling and integration patterns, with engineer certification
Sandbox deployment: An evaluation deployment in your own environment for demonstrations and customer document testing
Architecture support: Joint design review on live opportunities, direct with the engineers who build the platform
Documentation: Deployment, API and operations documentation, plus the model manifest for security review
Sizing collaboration: Sizing exercises run against the customer real document mix rather than a generic specification

Go to market

Collateral: Solution and commercial material in Arabic and English, aligned to what this site publishes
Security pack: Architecture, control mapping and data-flow documentation, available to partners under NDA
Joint engagement: Our engineers attend customer technical sessions and security reviews with you
Use of names and logos: Agreed in writing in both directions — we publish no partner names without consent
Tenders and frameworks: Technical response support for public-sector and regulated procurement processes

This describes the programme as it exists today. It will develop as the partner base grows, and changes are communicated to partners directly rather than through a web page.

How to join

How to become a DocxIntel partner

Five steps, and the first conversation is a technical one. We would rather find out in week one that the fit is wrong than in month six.

Step 1
Get in touch with the track you have in mind
Send an enquiry to BizfyLabs describing your delivery capability, the customers and sectors you already serve, the territory you cover, and which of the four tracks fits. There is no application portal and no waiting list.
Step 2
A joint fit assessment
We look at your existing customer base, your engineering capacity and the deployment models your customers require. If your customers are cloud-permitted and low volume, we will say that DocxIntel is a poor fit for them rather than sign a partner who cannot sell it.
Step 3
Partner agreement and territory
Margin, territory, deal-registration terms, support responsibilities and the rules on claims and naming are agreed in writing. Nothing about the commercial arrangement is left to a slide deck.
Step 4
Enablement and sandbox deployment
Your engineers are trained and certified on deployment, sizing, tuning and exception handling, and a sandbox deployment goes into your own environment so you can demonstrate on real documents rather than a scripted demo.
Step 5
Register and run the first opportunity together
The first engagement is run jointly: our engineers attend the technical and security sessions with you, and the Proof of Value is scoped with the accuracy threshold and conversion price fixed in writing before it begins.

Questions partners ask before applying

Including the ones about how early the programme really is.

How established is the partner programme?

It is open and deliberately early. DocxIntel is a new product, so we are not going to describe a mature channel with tiers, quotas and a partner portal that does not exist yet. What exists is a working programme structure, deal registration, technical enablement and direct access to the engineers who build the platform — which is worth more at this stage than a badge scheme.

Do you publish a list of current partners?

What margin do partners earn?

How does deal registration work?

Can partners run their own demonstrations?

What do you expect from a partner?

Deployment modelsAir-gapped, private cloud, managed single-tenant and evaluation sandbox, in detail.Reference architecturesHow a deployment is laid out inside a customer network, for integrator and platform teams.Sizing and throughputGPU, CPU and storage requirements — the starting point for any hardware conversation.PricingThe fixed annual licence model that partner margin is built on.Proof of ValueThe paid pilot partners run with us, with the threshold agreed in writing up front.About BizfyLabsThe engineering company behind DocxIntel, and who you would be contracting with.

The programme is open. Tell us what you deliver.

Describe your delivery capability, your territory and the customers you already serve. If the fit is not there we will say so in the first conversation rather than the fourth.

Deal registration in writing
Sandbox deployment provided
No partner names published without consent

Partner programme

Build, deploy and resell on-premise document AI across the GCC

Open and early — no waiting list
Deal registration in writing
Sandbox deployment for partners
Fixed licence, predictable margin

4
Partner tracks: GCC
Primary focus: Sandbox
Provided to every partner: Fixed
Underlying licence model

Four tracks

The kinds of partner an on-premise platform actually needs

Track 1