Review
Access Review
IT, Cybersecurity & Service Management
APPROVED SKILL EXAMPLE 01Chief Agent
powered by UBoss AI
You set
the objective.
It builds the team.
Business intent becomes a working system of agents, governed skills and people — each with a role it was given, a boundary it cannot cross, and an owner who signs the work off.
- 400Governed Skills in the catalogue
- 2,800IF-THEN rules those Skills carry
- 24Industries with a pack of their own
What it runs on
- Objectives
- Agent Builder
- Governed Skills
- Human approval
- Audit trail
INSIDE THE UBOSS WORKSPACEA field-service workflow, from request to sign-off.
Plan the work.
Track the result.
An objective becomes a plan.
Start with the result you need. See the work, the people and the approval points that get you there.
THE OBJECTIVE
RETURN EVERY REPAIR WITHIN 5 WORKING DAYS
Workflow designed
Log equipment conditionHuman task
Complete repair and record partsHuman task
Draft the service recordAI task
Review and sign offApproval
PRODUCT ILLUSTRATION · NOT LIVE CUSTOMER DATA
THE UBOSS SKILL CATALOGGive every agent
Give every agent
a defined way to work.
Select the skill the job requires. Each one defines the work, the required output and the rules the agent must follow.
01
UBOSS Verified
Platform-governed skills for work across departments.
02
Industry Packs
Industry-specific processes, checks and required outputs.
03
Company Custom
Skills authored for your company and kept within its scope.
6 sample skills found
Operations
Accounts Payable Control
Finance & Accounting
APPROVED SKILL EXAMPLE 02Analysis
Accounts Receivable Collections
Finance & Accounting
APPROVED SKILL EXAMPLE 03Analysis
Anti Bribery Due Diligence
Regulatory, Legal & Compliance
APPROVED SKILL EXAMPLE 04Analysis
Asset Lifecycle Planner
Maintenance, Assets & Utilities
APPROVED SKILL EXAMPLE 05Operations
AI Use Case Classification
Data, Analytics & AI
APPROVED SKILL EXAMPLE 06A selection from the UBOSS catalog8 skill categories Built around real business work
WORKFLOWS BY DEPARTMENTReal work.
Real work.
Mapped to the right team.
WORKFLOW / 01
Close the service loop.
Coordinate field service from the first condition record to the final sign-off.
Explore your use caseThe input
A repair request and equipment record
AI prepares
Prepare a service record from submitted evidence
People decide
Complete the repair and approve the record
The outcome
A reviewed service record and clear ownership
Illustrative workflows. We’ll define the exact skills, connections and scope with your team.
AUTHORITY STAYS WITH YOUR PEOPLEPeople approve.
Explore governance & security
People approve.
UBOSS keeps the record.
Define who can act, what they can access and which steps need approval. Follow the decision from request to outcome.
People approve
Consequential steps wait for the right decision.
Access has limits
Roles and scope define who can do what.
Decisions leave a record
Versions, approvals and exceptions stay traceable.
Connect it
It fits what you already run.
Your directory decides who exists. Your identity provider decides how they sign in. And anything the screens can do, your own systems can do — as the person who authorised it, never as more.
Connect it to what you already run
Everything the screens do, your systems can do. The reference is generated from the product itself, so what it lists is what answers.
- A browsable API reference, kept in step because it is built from the code
- Objectives, tasks, approvals and reports, reachable as data
- Versioned with the product rather than beside it
A program cannot do more than the person behind it
There are no API keys to leak and no service account with a key to the building. An integration acts as somebody, with exactly the access that somebody holds.
- The same roles and permissions that govern the interface
- Refused with a reason when the grant is missing
- Revoking a person revokes everything built on them
People stay in step with your directory
Joiners appear, movers change, leavers lose access — without anybody remembering to do it in a second place.
- SCIM 2.0, so your identity platform stays in charge
- Users and groups, synced on your schedule
- Every change recorded, like any other change
Your sign-on, not another password
Connect the identity provider your company already uses. UBoss never becomes another place where credentials live.
- SAML 2.0 and OpenID Connect
- Set up by your company, for your company
- A secret you give it is never shown back to anyone
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 |
COMMON QUESTIONSBefore you
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.
SEE CHIEF AGENT WITH YOUR OWN USE CASEYour workflow.
Your workflow.
Inside Chief Agent.
Bring a recurring report, a review process or an operational task. We’ll walk through its people, agents, skills and approvals.
Book a Workflow Demo