Cleaning the install base.
Productized utility modules for OpenText™ Content Server admins. We only build what OpenText Customer Success asks us to build. Then we ship it as a subscription instead of a one-off SI engagement.
Customer-pull, never engineering-push.
Every module on this site exists because a real OpenText customer asked for it through the Customer Success group. We don't speculate about what admins might want. We build the items that already have a named buyer and a documented use case.
The result is a roadmap with a track record before it ships.
-
01OpenText Customer Success surfaces the requestAn admin tells their CS contact what's slowing them down. The CS group routes it to us with the customer's environment context.
-
02We scope it against the install baseIf three or more customers carry the same friction, the module is greenlit. If not, it goes back as a one-off SI engagement.
-
03Demo in three weeks. MVP in three months.One Subject Matter Expert plus one ex-OpenText engineer. Built on Content Server, deployed inside the customer's existing OT footprint.
-
04Ships as ARR, not as services revenueSubscription priced inside the OpenText commercial relationship. Renewals attach to the OT renewal, not a separate vendor contract.
The four modules customers ask for first.
You already have an OpenText contract. Add what's missing.
Procurement runs through the OpenText SolEx program. The buying decision is an incremental add to a contract you already hold — not a net-new vendor onboarding.
Ten utility modules. One install base.
Every module attaches to OpenText™ Content Server inside an existing customer footprint. Click into any one for capabilities, provenance, and the customer who asked for it first.
Module Name
Short description.
Subscription priced inside your existing OpenText commercial relationship. Final pricing set at the time the OpenText Customer Success group greenlights the module against your installed footprint.
Who asked for this.
Routed through the OpenText Customer Success group. Greenlit against the documented friction; not built on speculation.
Buy ModulOT on OpenText paper.
We're a Vendor of Record–approved OpenText SolEx Partner. That means procurement does not start a new vendor file. The line item attaches to the OpenText commercial agreement you already hold, and renewal lands on the OpenText renewal cycle.
Your team requests a module
Through your OpenText account team or directly through Customer Success. We respond with a scoped quote inside two business days.
OpenText SolEx writes the order
The line item lands on OpenText paper. No new MSA. No new vendor onboarding. No new tax or banking record. No new InfoSec questionnaire.
You activate inside your existing CS environment
Module deploys into your Content Server footprint. Subscription term aligns to your OT renewal so accounts payable sees one invoice, not two.
The vendor onboarding tax. Removed.
Procurement clears in days, not quarters, because every gate that normally meets a new vendor was already cleared the day you signed your OpenText agreement.
Where the dollars and the contract actually move.
Customer payment lands at OpenText under your existing agreement. OpenText retains its 30% partner share and routes the remainder to ModulOT for module delivery, support, and ongoing maintenance. Your AP, legal, and InfoSec teams interact with one entity — OpenText.
Ready to scope a module against your environment?
Waterloo, Ontario.
We sit inside Canada's enterprise-software corridor, beside the partner ecosystem we build for. Reach us in Eastern Time.
Waterloo, Ontario, Canada