Onit Apptitude is the low-code application platform underneath Onit’s enterprise legal management products, used to build and deploy the workflow Apps that a legal department runs day to day. Legal service request intake, contract approval routing, matter opening, settlement authority, outside counsel engagement, and legal hold all sit on the same underlying engine. Understanding Apptitude matters because it is the layer where a legal department’s own processes get encoded, and therefore the layer that determines how well the platform fits the business.
What is Apptitude used for?
Apptitude builds the workflow Apps that carry a legal department’s repeatable processes. Each App combines a form, a set of business rules, a routing path, and a data model, and each is configured to one specific process.
Common Apps in an enterprise deployment include the following.
- Legal service request. Structured intake so business users reach the right legal team with the right information attached.
- Contract request and approval. Routing by value, region, contract type, and risk category.
- Matter opening. Consistent matter creation with the correct metadata captured at the start.
- Authority requests. Settlement authority, litigation authority, and similar approvals that need a documented decision trail.
- Legal hold. Issuing, tracking, and releasing holds with an auditable record.
Scale here is a function of process count. Onit’s case study on Archer Daniels Midland notes that ADM has built hundreds of purpose-built workflows on the platform since adopting Onit in 2015, expanding steadily as its legal function evolved.
What does low-code mean in practice on Apptitude?
Low-code means the platform is configured through its own tooling, which shortens the distance between defining a process and running it. The practical effect is speed of iteration. A change to an approval threshold or a routing rule is a configuration change, so processes can evolve as the business does.
Onit has demonstrated that build speed publicly. In its Hack the House competition, corporate legal teams from organizations including Colgate-Palmolive, Corteva Agriscience, and McDonald’s built working Apps in three weeks, with the winning team automating the trademark renewal process.
Low-code changes where the effort sits. Less of it goes into building software. More of it goes into deciding precisely how a process should behave, which is where implementation experience earns its value.
What results have organizations achieved with Apptitude?
Published customer outcomes give two useful reference points for what a mature Apptitude deployment delivers.
Archer Daniels Midland. ADM’s legal, regulatory and compliance function runs a global portfolio across litigation, regulatory, compliance, and commercial matters. Onit reports that following automation, half of ADM’s US NDAs are executed within hours or a day and are fully automated, with structured workflows accelerating loss contingency assessment, settlement authority requests, and authority to file a lawsuit. ADM’s broader legal operations program also reduced outside legal spend by more than one third, recognized at the Transatlantic Legal Awards and by the Association of Corporate Counsel.
Corteva Agriscience. Onit reports that Corteva’s legal transformation program saved close to a million hours between 2021 and 2025 through automated digital workflows and multilingual AI assistants, and that the program won Overall Winner at the 2024 Buying Legal Counsel Awards.
Both figures describe multi-year programs across many Apps. They indicate what the ceiling looks like over time. The sensible way to read them is that returns accumulate as more processes move onto the platform.
What does an Apptitude implementation involve?
The work divides into process definition, configuration, data modeling, and testing, and the first of those consumes more time than most plans allow. An App can only automate a process that has been decided, so ambiguity in the process surfaces as delay in the build.
Delivery on an Apptitude program runs through four stages.
1. Process definition. Mapping the current path, agreeing the target path, and resolving the exceptions. Exceptions are where the detail lives.
2. Configuration. Building the form, the conditional logic, the routing, and the notifications.
3. Data modeling. Deciding what each App captures, how it relates to matters and vendors, and what reporting depends on it.
4. Testing. Proving every configured path behaves correctly for every user profile.
Configuration volume grows quickly at enterprise scale. On one program, Basla configured more than fifty custom business rules, including compound conditional actions where several conditions resolve together before the platform acts. The reasoning behind that approach is set out in why workflow automation fails without conditional logic.
Intake design deserves particular attention, since the request form is where business users meet the platform. On a legal service request implementation, Basla built eight separate intake front doors covering language and country variations within a single deployment, an approach described further in conditional UI architecture for legal intake at scale.
How is Apptitude configuration tested?
Through scenario coverage of every configured path, for every user profile that will touch the App. The platform itself arrives working, so what has to be proven is the configuration built on top of it.
That produces a larger test surface than teams expect. Every intake variation, approval branch, business rule, and permission combination is a scenario. On a contract lifecycle management rollout, Basla created and executed over a thousand test records to cover the configured paths.
Two categories carry the most risk when skipped. Role-based testing exposes permission gaps that administrator-level testing hides, covered in why skipping role-based security testing breaks go-lives. Deployment testing confirms that configuration validated in a sandbox behaves the same in production, covered in the hidden dangers of packaging workflows for production.
What happens after an Apptitude App goes live?
Adoption decides the return, and the first weeks determine adoption. Business users meeting a new intake form generate questions at a predictable volume, and planning for that keeps the configuration team free to resolve genuine defects.
On one Onit rollout, Basla’s delivery team handled roughly two hundred tickets in the first week after go-live. Around sixty percent were users asking how to complete a task, and the balance were genuine defects requiring a developer. The hypercare window ran for eight weeks with every report triaged before anything reached the configuration team. That model is described in why launches fail without a hypercare triage desk.
Documentation matters more on a low-code platform than on a conventional build, because the configurability that makes Apptitude fast also makes undocumented decisions hard to reconstruct later. A rule written to handle a specific regional exception is obvious during the workshop and opaque eighteen months on, a pattern covered in why undocumented configuration becomes technical debt.
How does Apptitude relate to the wider Onit platform?
Apptitude is the workflow layer that sits alongside Onit’s matter management, eBilling, and contract capabilities, and Onit continues to consolidate these onto its Unity architecture. For the wider platform picture, Swiftwater’s practitioner guide to Onit Apptitude is a useful reference, and the program-level view is set out in what an Onit ELM implementation actually involves.
Conclusion
Onit Apptitude is the layer where a legal department’s own processes get encoded, which makes it the layer that determines how well the platform fits the business. The low-code model removes the software engineering problem and leaves the harder one in place: deciding precisely how each process should behave, including the exceptions nobody wrote down.
That is where implementation effort concentrates. Published customer outcomes show what accumulates when an organization keeps moving processes onto Apptitude over several years. What those outcomes share is a disciplined build, with processes defined before configuration starts, every path tested against every user profile, and configuration decisions documented while the reasoning is still fresh.
How Basla can help
Basla provides the delivery capability behind Onit workflow implementations, covering business analysis, process definition, App configuration support, documentation, testing coordination, and post-go-live support. Basla has delivered legal technology across more than a hundred jurisdictions, with hands-on experience supporting Onit legal service request, matter management, eBilling, and contract workflows.
Frequently asked questions
What is Onit Apptitude?
Onit Apptitude is the low-code application platform underneath Onit’s enterprise legal management products. It is used to build and deploy the workflow Apps a legal department runs day to day, including legal service request intake, contract approval routing, matter opening, authority requests, and legal hold.
What is the difference between Apptitude and Onit ELM?
Onit ELM is the enterprise legal management platform covering matter management, eBilling, and contract capability. Apptitude is the workflow layer that sits alongside those modules and controls how work is created, routed, and completed. ELM holds the data. Apptitude governs the process.
What can you build with Onit Apptitude?
Any repeatable legal process that involves a form, a set of rules, and a routing path. Common examples include legal service request intake, contract request and approval, matter opening, settlement and litigation authority requests, legal hold, and outside counsel engagement.
Does Onit Apptitude require developers?
Less than a conventional build, since Apps are configured through the platform’s own tooling. Enterprise deployments still benefit from delivery expertise, because the difficulty sits in process definition, conditional logic design, data modeling, and testing.
How long does an Apptitude App take to build?
It depends on how well the underlying process is defined. Onit’s Hack the House competition showed corporate legal teams building working Apps in three weeks. Enterprise deployments with multiple jurisdictions, languages, and approval variations take considerably longer, and most of that time goes into process definition.
How is Apptitude configuration tested?
Through scenario coverage of every configured path for every user profile that will touch the App. Every intake variation, approval branch, business rule, and permission combination is a test scenario, which produces a larger test surface than most teams plan for.
*This article is provided for general information only and does not constitute legal advice. Basla Solutions provides legal technology implementation and support services and does not practice law.*