Enterprise software. Thoughtful delivery.
Servexa / Service and facilities operations

Every service, accounted for.

Connect the promise, the work and the commercial result. Servexa brings service contracts, scheduling, field execution, quality and job economics into one operating platform.

What it is

Follow the job beyond the completion tick.

A service starts with what the customer was promised. It passes through entitlement checks, scheduling, people, parts and field evidence before it becomes a billable record. Servexa is designed to keep that chain together, so operations and commercial teams can work from the same job history.

Build the service around your operating model.

Define services, prices, forms, checklists, approval rules and workflows inside the platform. Its scope spans residential service and commercial facilities operations, including customer and site hierarchies, assets, contracts and subcontractors. Agree the modules and deployment scope around the service lines you intend to run.

Follow the work

01

Define the promise

Check the customer, service, coverage and price.

02

Plan the work

Assign the people, time and resources the job requires.

03

Capture delivery

Record the work, evidence, time and materials at the point of service.

04

Close the loop

Verify quality and connect the job to cost, billing and follow-up.

An illustrative workflow. The sequence and controls are configured for the agreed scope.

The problem

The work Servexa helps you coordinate

The contract and the job tell different stories.

Make the scope, entitlement and commercial rules available where work is booked and delivered.

A busy day does not explain productivity.

Capture travel, work, waiting and material use in the job record to understand where time and cost go.

Closing work should complete the evidence.

Bring checklists, quality checks, consumed materials and commercial status into the closeout process.

Capabilities

What Servexa does

Customers book it themselves

A catalogue with real prices and durations, slot selection, address, payment and confirmation. Where a contract covers the work, the customer is told so before they pay. Built mobile first, because most of them arrive on a phone.

A dispatch board built for a whole shift

Unassigned queue, technician timeline, capacity against the day, SLA countdowns and live status. Drop targets validate skill, zone, parts and overtime before you release, so the rule is learned from the interaction rather than from a rejection.

A field app that works without signal

Jobs cached ahead of time, checklists with required photo and numeric evidence, parts drawn from the van, and a sync chip that is always visible so nobody wonders whether the job went through.

Configuration, versioned

A service is a versioned definition with a draft, a review and a publish date. Change the price and you see the 412 contracts and 38 bookings it touches, and whether Finance has to approve it. Attributes added here appear in the booking form, the field app and the invoice, without a release.

The commercial result, not just the completion

Contracts and entitlements, quotations and subscriptions, materials, subcontractor cost and job economics, so a finished job has a margin attached to it and not only a tick.

Quality that is evidenced

Checklists, photographs, quality scores, complaints and rework linked back to the job record and the person who did it, so a claim about service levels has something behind it.

Workflow as its own engine

Multi-stage side effects, customer notification, route recalculation, parts reservation, run on a dedicated workflow engine with its own database. The interface fires one intent and shows the progress; it orchestrates nothing itself.

Arabic and English as equals

Both languages are first class in the product, not a translation mode: true right to left, Arabic service names beside English ones in the same editor, and a missing translation raised as a blocker before publish.

See it

Inside Servexa

Screens from the product itself, with any account name or customer data replaced by neutral examples. Where a product is still in build, the screen is drawn from its design specification.

The Servexa dispatch board: an unassigned queue, a technician timeline for the day with jobs, travel, breaks and overtime, SLA countdowns, and an assignment suggestion showing the reasoning behind it.
The Servexa dispatch board
The customer booking flow: a service catalogue with prices and durations, contract cover shown before payment, and the options for the chosen service drawn from its configuration.
Booking a service in Servexa
Two technician screens: the day list with jobs cached for offline work, and a job in progress with its checklist, photo evidence and a suggested note drawn from what was captured.
The Servexa field app
A service definition in draft, with the change summary against the live version, what the change affects, and the approval it will need before publish.
The Servexa configuration studio
Modules

How Servexa is put together

Commerce and customers

Service catalogue and packages, booking, payment, customer accounts and properties, quotations, subscriptions and invoicing.

Operations

Work orders, the dispatch board, the assignment engine, capacity and shift planning, routing, SLA management and live queue health.

Field execution

The technician application on iOS and Android, offline job packs, checklists and evidence capture, van stock, timesheets and completion sign-off.

Configuration studio

Versioned service definitions, dynamic attributes, pricing rules, checklists, SLA policies, translations, effective dating and impact analysis before publish.

AI layer, provider independent

Assignment suggestions with the reasoning shown, review assistance that catches a missing translation before it ships, job notes drafted from the evidence a technician captured, and an analytics copilot over approved data. The layer is provider independent by design, so the model behind it is a configuration choice rather than a rebuild, and every answer shows where it came from.

Contracts, quality and intelligence

Maintenance agreements and entitlements, planned maintenance, quality scoring, complaints and rework, and job economics reporting from enquiry to profit and loss.

Security and deployment

Plan the fit for your organisation

Role-based access controlAudit logging
Download

Product brochure

What Servexa covers, how it is put together, and what it needs to run.

FAQs

Common questions about Servexa

Which service businesses does Servexa address?

The solution specification covers residential service operators, field service teams and commercial facilities management. Customer and site hierarchies, assets, contracts and subcontractors support the different operating models.

How much can be configured?

The specified configuration scope includes service definitions, pricing, forms, checklists, documents, roles, approvals and workflows. Implementation starts by mapping your service lines to that scope and agreeing any extensions.

How do we assess modules, AI and deployment?

Use a walkthrough built around one of your service journeys. Confirm required modules, mobile and offline behaviour, provider accounts, hosting, data handling and AI permissions before agreeing a rollout. The supplied specification describes the intended platform scope; the implementation proposal establishes what will be delivered.

What would a better working day look like?

Bring us the process you want to improve. We’ll explore the product, technology and delivery work it needs.