PLANS
Same product.
Different amount of it.
Every plan opens the same UBoss. What a plan decides is how many of its modules a company can see, how many people it seats, and whether a monthly AI allowance is included.
- 4Plans, from a pilot to a negotiated rollout
- 5 to 14Modules, depending on the plan
- 1 to 40Seats, or a number agreed with you
Plans
Four plans. The difference is what opens.
Every plan is the same product. What changes is how much of it a company can see, how many people it seats, and whether AI work is included.
Pilot
See the product with your own company in it, before you buy anything.
1seat5modulesNoneAI allowance- The whole workspace, with a worked example already in it
- One seat — yours. A Pilot is for seeing the product, not for running a team on it
- No AI allowance, so it costs nothing and nothing runs
Starter
One team running its work through UBoss, with AI included.
10seats6modulesIncludedAI allowance- A monthly AI allowance in UBoss Tokens, included
- UBoss Profile Search for checking somebody’s history before you hire
- Ten seats
Most companies start here
Growth
The whole product: agents you build, work they run, people who approve it.
40seats12modulesIncludedAI allowance- Agent Builder, and the Engine Agents you build with it
- The Executor Agent, which watches execution and raises exceptions
- Approvals, so work stops where a person has to decide
- Reports, and the access screens to run the company
- Forty seats and a larger monthly allowance
Enterprise
Everything, with the seats, allowance and controls agreed with you.
Agreedseats14modulesIncludedAI allowance- Custom roles — permission sets you write yourself, inside your own ceiling
- Performance and badges across the company
- Seats and allowance negotiated rather than fixed
What a plan costs is agreed with you. Seats, the monthly allowance and the plan itself are set per company, and an invoice follows what was agreed rather than a number on a web page. Tell us the work you want to put through UBoss and you will get the figure for that, not for a tier.
| Module | Pilot | Starter | Growth | Enterprise |
|---|---|---|---|---|
| Objectives | ||||
| To-do List | ||||
| Org chart and reporting lines | ||||
| Agent Builder | ||||
| Engine Agents | ||||
| Executor Agent | ||||
| Approvals | ||||
| Reports | ||||
| Users and access | ||||
| Custom roles | ||||
| Performance and badges | ||||
| UBoss Profile Search | ||||
| Seats | 1 | 10 | 40 | Agreed |
| Monthly AI allowance | None | Included | Included | Included |
Before you
get started.
How agents work, where people decide
and what to expect from a demo.
01What is the difference between an agent and a skill?
An agent is configured to carry out a particular job. A skill is an approved, versioned definition of how a type of work should be done. UBOSS brings skills, permitted connections and objective context together in an agent.
02Where do people stay involved?
People own the objective, do the human work and make the required approval decisions. UBOSS coordinates the workflow and routes exceptions; an animation or an agent does not replace a person’s authority.
03Can we use our own processes and skills?
Company-custom skills are part of the UBOSS model. In your demo, we’ll explore your process, the output it needs and the rules it must follow before defining the implementation scope.
04How is pricing calculated?
We scope your requirements first: teams, workflows, agents, skills and expected AI usage. Your quote defines the included usage and any additional charges. Published flat rates and self-service subscriptions are not currently offered on this website.
05What should we bring to a demo?
Bring one real, repeatable objective, an example of the inputs and the output you need. Include the process owner and, where relevant, someone responsible for governance. Use non-sensitive examples for the initial conversation.
06Can agents take actions without approval?
Actions are bounded by the configured skill, permissions and company policy. Steps that require approval wait for a person. The workflow also records decisions and exceptions so the team can see what happened.