Why Xelium One
Your business is connected. Your software should be too.
Winning a client, filling a requirement, onboarding a person, approving their hours and invoicing the work are one story. Xelium One keeps it on one set of records, so every team works from the same truth.
The problem
Most organisations don't lack software. They lack connection.
Every hand-off is a re-type
The client is entered in one tool, the requirement in another, the joiner in a third and the invoice in a fourth. Each copy drifts.
Nobody can trace a number
When revenue lives in a spreadsheet built from exports, nobody can say which hours, rates or placements produced it.
Approvals live in inboxes
Offers, timesheets and leave wait in email and chat, so nobody knows what is stuck or with whom.
Two approaches
The traditional approach, and the Xelium approach
Traditional approach
The usual answer is a separate tool for each team, then integrations and spreadsheets to join them.
- A CRM, an applicant-tracking system, an HR system, a timesheet tool and an invoicing tool — each with its own users and its own copy of the person.
- Integrations that must be built, paid for and repaired whenever one side changes.
- Reports assembled by hand from exports, a few days late and rarely in agreement.
The Xelium approach
Xelium One is one platform with modules, not a bundle of products. Every module shares the same sign-in, People record, roles and history.
- A record is created once and carried forward: lead to client, requirement to placement, placement to timesheet, timesheet to invoice.
- Numbers are derived, not typed: revenue comes from approved hours and agreed rates.
- Start with the modules you need; add the next one without a new system or a migration.
Key capabilities
What it does
Each capability shows whether it is available today or coming soon.
One sign-in, one People record, one set of roles
AvailableOne sign-in, one navigation and one record for each person, shared by every module.
Access checked on the server for every request
AvailableRoles and module access are checked on the server for every request — not just hidden in menus.
Change history on records
AvailableChanges are recorded. Corrections never overwrite the original.
Role-aware Home showing what needs your attention
AvailableEach person's Home shows the work waiting for them, by role.
One inbox for everything waiting on you
Coming soonEverything waiting on you — offers, timesheets, requests — in one list.
Configurable approvals, automation and service levels
Coming soonYour own approval steps, automations and response times, set up without code.
Module details:Xelium One CorePeopleAnalytics & Reports
Connected advantage
What connection changes
Because the records are shared, a change in one place is true everywhere it matters.
- Lead
- Client
- Requirement
- Placement
- Timesheet
- Invoice
- Revenue
- An accepted offer becomes exactly one placement — the record timesheets, revenue and invoices use.
- Attendance, timesheets and billable hours are kept apart on purpose, so presence never becomes an invoice by accident.
- Role and module access follow the person everywhere, including into reports and the assistant.
One business graph
Every step below is a record in Xelium One, linked to the one before it — so you can follow any number back to where it started.
- Lead
- Client
- Requirement
- Candidate
- Assessment
- Submission
- Interview
- Offer
- Placement
- Onboarding
- Workforce
- Attendance
- Timesheet
- Billing
- Revenue
- Analytics
What flows between the stages
Choose a stage to see what it does and what it hands to the next.
- 01
CRM
Leads become client accounts with contacts and opportunities.
Flows to Talent: The client account and its contacts — every requirement is linked to the client it is for.
- 02
Talent
Requirements, candidates, submissions, interviews and offers.
Flows to GyaniX: The candidate and the requirement they are being considered for.
Skills assessments from an independent platform, with results summarised for the recruiter.
Flows to Onboarding: An assessment result summary — evidence for people to weigh, never an automatic decision.
An accepted offer becomes exactly one placement and starts joining.
Flows to Workforce: A joined person with their placement, rates and dates.
Assignments with dates, work mode and utilisation.
Flows to Pulse: The person's People record and reporting manager.
- 06
Pulse
Check-in, attendance, leave and corrections.
Flows to Timesheets: Who is working and when — kept separate from billable hours on purpose.
Hours recorded against the placement, submitted and approved.
Flows to Finance: Approved hours, which nobody can edit after approval.
- 08
Finance
Approved hours × placement rates become revenue, margin, invoices and incentives.
Flows to Analytics: Revenue, margin, invoices and payments, each traceable to the hours behind it.
Reports read the same records your teams work in.
Where it all lands: Answers leadership can trace back to the work.
Why it works better, area by area
- Recruiting & ATSRecruiting that doesn't stop at the offer.Read why
- CRMA CRM that knows what you delivered.Read why
- HRMSPeople, presence and requests — on the record every module uses.Read why
- WorkforceFrom accepted offer to approved hours, without re-keying.Read why
- PulseKnow who is working, where and when — and approve requests in one place.Read why
- VendorComing soonWork with partner vendors on the same requirements — coming soon.Read why
- FinanceRevenue you can trace back to the hours behind it.Read why
- AnalyticsReports from the work itself, not from exports.Read why
- GyaniXComing soonUnderstand capability, not just claims.Read why
AI advantage
AI with a job to do
AI in Xelium One has a job to do and an answer you can question. It reads only what you may see, and a person decides.
- Illustration · example dataComing soon
What needs my attention today?
Two offers waiting for your approval, one timesheet returned for correction, and a leave request from your team for next week.
How it answers: Built from the work queues on your Home — the same lists you can open yourself.
- Illustration · example dataComing soon
Why is this month's margin lower than last month's?
Fewer approved hours on two placements, and one placement's pay rate changed mid-month.
How it answers: Each reason links to the timesheets and placement changes behind it.
Analytics advantage
Answers from the same records
Reports read the records your teams already keep, filtered by role — no exports to reconcile.
- Hiring funnel, attendance and placement-to-billing reports across the modules you use.Available
- Build your own reports with pivots, formulas and charts.Coming soon
- Ask questions about your numbers in plain language.Coming soon
- Available
- Works in Xelium One today.
- Coming soon
- Not live for customers yet — being built, or not built yet.
- Simulated in demo
- Shown in the sales demo with fictional sample data. Nothing real happens.
See the connected platform for yourself.
Book a demo with the Xelium team, or explore every module first.