Partners

Enhance your OpenText offering. Grow the revenue behind it.

Nuca looks after OpenText day to day, as a seamless extension of what you already deliver. Your customers get ongoing support you never have to staff. You keep the relationship, and you earn on every referral.

Become a referral partner See how it works

What you gain

Six reasons partners work with us.

Growth.

Recurring referral income from customers you already have, with no new business development required.

Completeness.

Offer ongoing OpenText support without building a team to deliver it. Answer the question your customers already ask you.

Retention.

A stable estate renews, expands and takes the next phase of work. It also answers the objection that OpenText is expensive to run, because the ongoing cost becomes a predictable monthly figure rather than an open-ended draw on the customer's own team.

Speed.

Thirty-day mobilisation, no build cost, and no delivery risk on your side. We contract directly and carry our own SLA.

Focus.

We look after live estates and nothing else. Implementation, migration, development and licences stay where they are, with you.

Reputation.

Senior specialists with decades in production OpenText environments, so the introduction reflects well on you.

You are probably thinking of an account already

Four situations you will recognise in your own customers.

Behind on versions.

The upgrade keeps slipping, and support-lifecycle pressure is building quietly in the background.

A stretched team, or a key person gone.

Change requests pile up, and the estate is running on what one person used to know.

Delivered, but nobody is running it.

The project went in well. Ongoing operations were never anyone's job, and it has started to show.

Recurring incidents nobody can crack.

It gets fixed, it comes back. The cause usually sits across a boundary rather than inside the thing everyone is looking at.

Each of these puts a customer relationship under pressure, and none of them has an obvious home. That is the gap we fill.

Where you fit

Three ways this works, depending on what you do.

Partner type 01

Systems integrators, implementation partners and software vendors

You deliver the project, the integration or the software, and then the customer asks who runs it day to day.

They have two obvious answers. Premium support, with the cost that comes with it. Or absorbing it into an internal team that is often already stretched across everything else it carries. Plenty of teams manage it well, but the day-to-day run rarely gets the focus it deserves when there is project work competing for the same people.

We are the option in between. With us behind you it becomes something else you can offer, and the stability the customer feels attaches to the solution you delivered.

How it usually works

Referral, and joint conversations when a customer raises ongoing support during a project.

Partner type 01

Partner type 02

Infrastructure and database managed service providers

You hold the infrastructure contract and run it well. OpenText sits on top of it and behaves differently from the rest of the stack. Its administration model is specific to the platform, and the database underneath it needs tuning for OpenText workloads rather than general ones.

Adding that specialism through us means the customer gets the depth they need while the relationship, and the contract, stay with you.

How it usually works

Co-sell, or named subcontract where you prefer to hold the whole contract.

Partner type 02

Partner type 03

Recruiters and staffing firms placing OpenText and ECM roles

This one is different, so it is worth being plain: we want you to fill the role.

OpenText administrators are scarce and searches run long. While one runs, your client has a business-critical platform with nobody watching it, and that pressure lands on you. Some of those roles never get filled at all.

We cover the gap while you recruit. The estate stays stable, the pressure comes off the search, and when you place the right person we hand over with full documentation, which makes them productive faster and makes your placement look good.

How it usually works

Referral, and a standing arrangement for roles that are proving hard to fill.

Partner type 03

Scope

A clear division of labour.

Our scope is deliberately narrow, and it is written into every agreement.

What we look after

The ongoing operation of estates that are already live. The OpenText platform, the database underneath it, and the business-administration layer.

What stays with you

Implementation, migration, custom development, licences, and the advisory work that comes with them.

If it is a project, it is yours. If it is the ongoing operation, that is where we can help.

How a referral works

Four steps, and you stay as involved as you want to be.

You introduce us.

An email, a call, or a name and some context. Whatever suits the relationship.

We check the fit, and you see it in writing first.

A short call to understand the account, then a written brief back to you within a week, before anything goes to your customer. If we are not the right answer, you hear that from us before anyone else does.

We contract directly.

Fixed monthly fee, our SLA, our delivery risk. Nothing lands on your paper unless you want it to.

You are paid.

A referral fee or an agreed share of first-year contract value, confirmed in writing before any introduction is made.

Some partners stay in the conversation throughout. Others prefer to hand over and hear how it went. Both work.

What we actually cover

So you know exactly what you are introducing.

The OpenText platform: Content Server, OTDS, Archive Server, Directory Services, Records Management, Extended ECM, and xECM connectors for SAP, Salesforce, SuccessFactors and Microsoft 365. Monitoring, patching, upgrades, performance, incident response and change control.
The database underneath: Oracle and Microsoft SQL Server running OpenText workloads. Backup and recovery, high availability, performance and capacity planning.
The business-administration layer: Users, permissions, categories, workflows and records-management policy, delivered with our specialist partners.
Where it runs: On-premise and private cloud, on OpenShift and Kubernetes, VMware and bare metal.
Cover: 24×7×365 response to critical incidents at every tier, not only the premium one.

Full scope, out-of-scope list and the three service depths

Something to give your customers

A conversation starter that costs you nothing.

Fifteen Things That Take OpenText Estates Down is a self-check written to be run without us. No form, no gate, nothing attached.

Take it and put your own conversation around it. If your customer works through it and finds things they cannot answer, that is a useful conversation for you to be having, whether or not it ever involves us.

Check your own estate

Let's talk

If you have customers running OpenText, we should talk.

An informal first conversation, to see whether we complement what you already do and where that might lead. The detail can wait.

Become a referral partner Send an introduction