You know the work. We make it run.
We build a workflow with you around how your customers already work. You sell it inside your product, and every business that runs it gets a place on the Graph of Work as it opens.
Co-build: we build one workflow with you around how your customers already work.
A workflow we build together and you sell to your customers inside your product.
Software platforms and service firms whose customers repeat the same piece of work.
You keep the customer relationship and Decidr runs the workflow, so your customers get AI inside a product they already trust.
The partners
Four partners already sell workflows built with Decidr.
Enterprise operations, leadership development, SAP finance and hiring. Each partner has a workflow in market today, built and run with Decidr.
How an enterprise really works
Sugarwork turns what an enterprise’s people know into a cited operating model, the starting point for every workflow.
AI Mentors, built with leadership authors
On-demand advice from the leadership authors Growth Faculty members already follow, sold as a subscription.
Decidr AP for SAP S/4HANA
Six agents take a supplier invoice from the inbox to posted, with one exception queue inside SAP.
Hiring products and Banjo, the AI talent agent
Co-built hiring products sold to CareerOne’s employers, now in the third year of the partnership.
The embedded model
One build reaches a whole network.
Most AI is sold one business at a time. A partnership reaches all of your customers at once. We build the workflow with you, and every customer can use it the day it launches.
Your domain, the workflow your customers repeat, and your brand.
Capture, the standard task names, the build, and the people to run it.
A workflow designed around how it already works.
The workflows
Every partner workflow is built and run the same way.
Each task gets a standard name and goes to rules, a model or a person, and every run is logged. Your customers see only your product, and Decidr runs the same operating layer underneath for every partner.
The Graph of Work
Your customers join the Graph of Work.
A business that runs a partner workflow gets a place on the Graph of Work with its tasks already named. As the Graph opens, it moves through five stages, and the businesses it buys from and sells to can join after it.
- SeededPre-boarded by its partner or from public sources, before anyone signs up.
- ClaimedThe owner claims the business and starts running workflows.
- ConnectedThe software it already uses feeds its operating model.
- RunningIts workflows run, each one scored against the goal it serves.
- TradingIt finds vendors and buyers on the Graph, and each match runs as a workflow.
Example business. The Graph of Work opens in stages alongside BusinessOS.
Expand
Customers who start with one workflow add more.
A business that arrives through one partner can take more from that partner, use workflows other partners built, or build its own and, as the Graph opens, sell it to other businesses. That makes each partner’s customers a market for the others.
Illustrative paths. Each one runs on the same operating layer and Graph.
Partner with Decidr
What we look for in a partner.
We choose a small number of partnerships where one build reaches a large customer network. These are the five things we look at first.
What you get
Questions
Most frequent questions.
What partners ask before they start.
Who owns the customer relationship?
The partner. Customers buy from the partner, inside the partner’s product, and the partner supports them. Decidr runs the workflow underneath.
Who builds and maintains the workflow?
Decidr builds it with the partner and runs the models, rules, updates and decision log. The partner brings the domain knowledge and the customers.
How is revenue shared?
Each partnership runs on a revenue share agreed with the partner and paid on the workflows its customers buy. The CareerOne partnership
What happens to customer data?
The vocabulary on the Graph is shared. Each business’s operations stay private. Decidr AP, for example, is SOC 2 Type II certified, keeps invoice data in the customer’s chosen AWS region and does not use it to train a shared model.
Does a customer need a Decidr account?
No. It uses the workflow inside the partner’s product. If it wants to claim its business on the Graph and add more workflows, it can.
How long does a build take?
The first build depends on the workflow. Once it exists, adding a customer is configuration. Decidr AP goes live for a new SAP customer in four to six weeks. The ICON partnership
