On your own server
Self-hosted, in your office or your hosting account. Your staff records and payroll data never leave your control.
Our Workflow Automation services
Everything Your Company Runs On, in One System.
Attendance in a register, leave over WhatsApp, payroll in a spreadsheet and project files on somebody's laptop. Each part works; nothing joins up, and every month end is a reconciliation. This is one system where all of it connects - and it is finished, so you are deploying it, not commissioning it.
2020Founded in Lahore
2Offices, Lahore and Dubai
4Teams under one roof
Post-launchSupport included
What defines this service
Priced per company
One system for everyone who works there. Adding the twentieth or the hundredth person costs nothing extra.
Everything is attributable
Roles decide who sees what, and an audit trail records who changed which figure and when. Financial and audit records are never hard-deleted.
Ongoing Support
We stay on after launch for fixes and small changes.
Issue and solution
How many of these happen in your company?
Read the left column first. Most owners we sit down with recognise five or six of them straight away - and the right column is what each one looks like a month after the system goes in.
| Issue | Solution with the system |
|---|---|
| Someone asks for leave on WhatsApp, and at month end nobody agrees how many days they have left | The request routes to the right approver, and the balance updates itself the moment it is approved. |
| Every month somebody re-types the attendance register into a spreadsheet | Clock-in and clock-out feed payroll directly. Nobody re-types anything. |
| You cannot say what last month's late arrivals actually cost you | Lateness accumulates against your own rule and reaches payroll with the working shown. |
| An advance was approved somewhere in a chat thread, and now nobody can find it | Requested, decided and dated in one place, with the approver named and findable a year later. |
| To find out where a job has reached, you have to ring the person doing it | Every job sits at a named stage with a named owner, visible to anyone allowed to look. |
| You do not know what a finished job cost, because the numbers sit in three different files | Hours, expenses and advances are filed against the job as they happen. |
| The latest version of a file is on somebody's laptop, and they are on leave | One library, with folders created automatically for every job and every client. |
| When someone resigns, the way they did things walks out with them | Stages, checklists and approvals are recorded rather than remembered. |
| You are paying for four systems by the user, and half of what they do overlaps | One system, priced per company. Hiring does not change what you pay. |
| Two departments report the same month differently, so you end up rebuilding the figures yourself | One set of figures, exportable, with an audit trail behind every change. |
If you ticked more than a couple of those, one system usually pays for itself inside a quarter. Book a 20-minute look at it.
Why choose ITS Global
Why put all of this in one system?
Because the cost is never in any single tool. It is in the joins between them: the hours spent reconciling a register against a payroll sheet, the approval nobody can find, the report that has to be rebuilt by hand because no two departments count the same way.
What You Can Hold Us To
A written scope before any priceYou see what is included and what it costs before work starts.
The people who quote it build itNo handover from a sales team to a delivery team.
You own the code and the accountsRepository, hosting and ad accounts in your name from day one.
Problems reach you from us firstIf something is off track you hear it before you find it.
The real problem
A system that already exists, configured to how you work.
Most internal software is quoted as a bespoke project: months of discovery, a build, and a first usable version somewhere near the end. This is the other way round. The system is complete and in daily use - it runs ITS Global's own office - so the work is configuration rather than construction: your departments, your roles, your leave policy, your approval chains, your staff imported and your first month reconciled against how you do it today.
The half of the system that handles a company - people, attendance, leave, payroll, advances, expenses, approvals, messaging, files, reporting and the audit trail underneath all of it - is the same whether you run a clinic, a workshop or a studio. The half that handles your trade is the part we shape: the stages work moves through, who owns each one, what gets checked before a job is called finished, and what kind of files each job produces.
- One place where attendance, approvals and payroll already agree
- Every approval recorded and findable months later
- A live answer to "where is that job", without asking anyone
- No per-seat licence rising every time you hire
- Your data on your own server, exportable whenever you want it
Getting It Wrong Costs Later
Attendance and payroll never agreeApprovals live in chatNobody can see where work isPer-seat software grows with headcount
Built the Right Way
On your own serverPriced per companyEverything is attributableOngoing Support
Our solution
One system, the whole working day.
Each part is connected to the others, which is the point. A late arrival reaches payroll on its own; an approved expense lands against the project it belongs to.
Attendance and leaveClock-in and clock-out, lateness accumulated against the policy you set, leave balances, holidays and a leave calendar the whole team can see.
People and teamsEmployee records, departments, teams, roles and permissions, documents against each person, and a joining-to-leaving history.
ApprovalsLeave, advances, expenses and anything else that needs a yes: requested, routed to the right approver, decided and recorded where it can be found again.
Your Workflow Automation Platform
Runs on your own serverYour data, exportableRoles and permissions built inReports you can export
Payroll, advances and expensesSalaries with the month's attendance and leave already applied, advances tracked against the person, and expenses filed against the job that caused them.
Projects and workflowEvery job moves through your own stages, with an owner per stage, tasks, deadlines and a status anyone can read without asking.
Files and assetsProject and client files in a structured library with folders created automatically, so the current version is never on one person's laptop.
Technology we work with
Our process
How a deployment runs.
Two weeks from a signed scope to your team using it, because the building is already done.
- 01 Walkthrough We sit with the people who do the work and write down how attendance, leave, approvals and jobs are handled today.
- 02 Install The system goes onto your server or ours, with backups scheduled and access restricted before anyone logs in.
- 03 Configure Departments, roles, permissions, your leave and lateness policy, your approval chains and your workflow stages.
- 04 Import Staff records, leave balances and open jobs brought in from whatever you keep them in now, then checked against your own figures.
- 05 Train One session per group - staff, managers, administrators - recorded so anyone who joins later gets the same walkthrough.
- 06 Run a real month The first payroll cycle runs in parallel with your existing method and the two are reconciled line by line before you retire the old one.
Fit
The parts we shape around your trade
A garage and a clinic both have staff who arrive late and invoices that need approving. What differs is the work itself, and those are settings rather than code.
The stages a job moves throughA workshop books estimate, parts, work, road test, invoice. A studio books script, voiceover, visuals, editing, review. You name your own, and who owns each one.
What gets checked before a job is doneYour checklists, filled in as data rather than written into the software, so they change when your standards change.
The files each job producesThe folders every job and every client gets, and what an uploaded file is filed as.
Your attendance rulesShift times, grace periods, how accumulated lateness converts to leave, and how that reaches payroll - configured, not hard-coded.
Who is allowed to see whatSalaries visible to finance and not to team leads, client files visible to the team on that client. Set per role, changeable later.
What you call thingsThe words on the screen are yours - clients or patients, jobs or cases, channels or sites.
Where it is used
Which businesses this fits
The company half is the same everywhere - staff, attendance, leave, payroll, approvals and files. What changes is what a job is called, the stages it moves through, and whether the trade needs a part building on top. The middle column is running today; the third is quoted with your deployment.
| Industry | What it runs from day one | Added for that trade |
|---|---|---|
| Construction and contracting | Attendance across several sites, labour advances and payroll, and every contract tracked as a job with its own stages, drawings and sign-offs. | Site check-in from a phone, and materials booked against the contract. |
| Manufacturing and workshops | Shift attendance and overtime, job cards moving through your own stages, and a checklist filled in before anything is called finished. | Raw material stock and consumption booked against each job card. |
| Facilities, cleaning and security | Large rosters across client sites, leave and replacement cover, and payroll that already knows who actually turned up. | Check-in at the client site, and a monthly report per contract. |
| Logistics, freight and clearing | Every consignment is a job with a named owner at each stage and all of its documents in one folder, with the staff side running behind it. | Invoicing per consignment, and a portal where the client tracks their own. |
| Creative, marketing and software agencies | Client work as jobs with review and approval before delivery, versioned files, and the hours and costs recorded against each one. | Quotations and invoicing, and a client login for approvals. |
| Content and video production studios | Runs as it ships: script, voiceover, visuals, editing, QA, thumbnail and publishing, with the asset library already built around it. | Nothing. This is the trade the system was first built for. |
| Law, accounting and consulting firms | Matters as jobs, documents versioned against each of them, approvals on record, and the whole staff, leave and payroll side underneath. | Time recorded against a matter, then billed from it. |
| Architecture and engineering | Every drawing package as a job with revisions, authority approvals attached, and sign-off recorded before anything is issued. | Stage invoicing against the fee proposal. |
| Schools, colleges and training institutes | Staff attendance and leave, payroll and advances, purchase approvals, and a file library per department. | Student records and fee collection, where you want them in one place. |
| Auto workshops and service centres | Every vehicle in for work as a job: estimate, parts, work, road test, with the technicians' attendance and payroll behind it. | Parts stock, and the estimate turned into an invoice at handover. |
| Clinics, laboratories and medical centres | Staff rosters, leave, payroll and documents against each employee, with approvals that leave a record. | Appointments, a doctor and room calendar, and patient records. |
| Hospitals | Departmental staff, rosters across shifts, leave and cover, payroll and advances, purchase approvals, and documents held against every employee. | Patient records, appointments and theatre scheduling, and procurement across departments. |
| Trading and distribution | Head-office staff, attendance, payroll, and approvals for expenses and advances, with every order tracked as a job. | Stock, purchase orders, and invoicing against the order. |
| Retail chains and showrooms | Staff across branches, shift attendance, leave cover and payroll, with one set of figures for every branch. | Stock per branch, and the till connected to it. |
| Restaurants and hospitality | Staff across shifts and outlets, attendance and overtime, leave cover and payroll, with purchase and expense approvals per outlet. | Rota scheduling, the till connected to stock, and kitchen inventory. |
The middle column is running today. The third is built onto it for your trade and quoted with your deployment, so you always know which is which. Ask where your business fits.
What you get out of it
What You Get
at the End of It.
- One place where attendance, approvals and payroll already agree
- Every approval recorded and findable months later
- A live answer to "where is that job", without asking anyone
- No per-seat licence rising every time you hire
- Your data on your own server, exportable whenever you want it
- Rules you can change yourself as the company changes
Who This Is For
- Companies of roughly 15 to 150 staff running people operations on paper, chat and spreadsheets
- Owners who cannot get a straight answer on attendance, leave balances or job status
- Businesses paying for several overlapping subscriptions priced per user
- Organisations that need staff and payroll records to stay on their own infrastructure
Tell us what
you are trying to build Get a Free Consultation
you are trying to build Get a Free Consultation
Frequently asked questions
Workflow Automation FAQs
A product, deployed and configured for you. The system is complete and in daily use in our own office, so what you are paying for is installation, configuration to your policies, data import, training and support - not months of development. Where your trade needs screens the system does not have yet, we quote that separately and say so before you commit.
On your server, or on hosting in your name that we set up and manage for you. It is a self-hosted system, so staff records, salaries and client files stay under your control, and you can export everything at any time. There is no version of this where your payroll sits on somebody else's platform unless you choose it.
Per company, not per user, as a one-off deployment plus an optional monthly plan for hosting, backups, updates and support. Adding staff does not change the price. Exact figures depend on which parts you switch on and how much existing data has to be migrated, and you get them in writing after a short call.
Yes, and it is usually the sensible route. Attendance, leave and approvals for a single department is enough to prove the system against your own policy in a couple of weeks, and the rest is switched on afterwards without rebuilding anything.
It keeps running until you are satisfied. The first payroll cycle is run in parallel and reconciled line by line against your existing method, and only then do you retire the old one. Historic records are imported wherever the source system will give them up.
Yes. It is a browser-based system that works on desktop, tablet and phone, so staff can clock in, request leave and see approvals from a phone without installing anything.
Stages, approval chains, checklists, leave rules and permissions are administration settings, changed by your own administrator without calling us. Anything structural enough to need us is quoted as a change, and the audit trail keeps the history of what the rules used to be.
Ready to get started?
Let’s Get Your Company on One System.
Tell us what you are working on. Someone from the team in Lahore or Dubai replies within one working day.
Get a Free Consultation
A person replies within one working day.
