Everything the business runs on.
Projects, field crews, procurement, customers, the books, and the analytics on top of all of it. One deployment, one database, one login. Every capability below is built and running — not a roadmap.
Configured per deployment · your currency, your tax rate, your branding
01Operations
01
Projects & sites
A project spans many physical sites, each with its own scope, status, and site code. Milestones carry deadlines and completion dates. Budgets are allocated against a purchase order and scoped to a project or a single site, tracked allocated-versus-spent.
- Site codes
- Milestones
- Budgets
- Allocated vs spent
02
Tasks & material requests
Tasks are assigned to workers, logged daily, and carry file attachments. A material request is raised against the task that needs it, so procurement can see exactly what a job is waiting on.
- Assignments
- Daily logs
- Attachments
- Requests → procurement
03
Field operations
Daily plans and end-of-day reports with custom forms per site, arrival confirmation with timestamps, photo status check-ins for low-bandwidth proof of progress, GPS positions on a live map, and HSE toolbox talks logged per site.
- Daily plan
- Photo check-in
- GPS map
- Toolbox talks
04
Sales & documents
Customer requests become quotes, approved quotes become invoices, and the whole request-to-cash lifecycle stays in one place. Documents generate as branded PDFs with logo, TIN, address, and payment instructions embedded.
- Request intake
- Quotes
- Branded PDFs
- Server-side totals
05
Procurement & materials
Every material carries a SKU, category, unit, supplier, unit cost, and stock location, with a configurable reorder level so low stock surfaces before it becomes a delay. Units of measurement are managed per business, not fixed by us.
- Material catalogue
- Reorder alerts
- Custom units
- Suppliers
06
Collaboration
Conversations and messages with attachments and read receipts live inside the platform, so project discussion is searchable later. Socket-based notifications fire on assignment and status changes, scoped to what each person is allowed to see.
- In-app chat
- Read receipts
- Live notifications
- Scoped rooms
02Accounting
Real double-entry, not income minus expenses.
A full chart of accounts and a journal-entry system where every posted entry has to balance before it is accepted. Revenue is split by service line out of the box, so telecom work and civil work never land in the same bucket.
When an invoice is finalised or paid, the entries post themselves — accounts receivable, revenue, VAT payable, and any discount — and the posting is idempotent, so running it twice never double-counts.
Finance is a first-class role
A dedicated finance user reaches the accounting suite without full admin rights — for businesses that separate the bookkeeping from running the operation.
Generated from live data, exportable as PDF
- General ledgerOn demand
- Trial balanceOn demand
- Income statementOn demand
- Balance sheetOn demand
- AR ageingOn demand
- Chart of accounts
- Journal entries
- VAT payable
- By service line
03Analytics
Six questions, in the order a business actually asks them.
Two pipelines run against your own operational data — no separate BI subscription. Retail data can come from your existing transaction records or be uploaded as an Excel file, so a shop or supplier needs no integration work to start.
01
What happened?
Daily and monthly sales, sales by weekday, top products, and a geographic breakdown.
02
Why did it happen?
Revenue-driver decomposition — which product, customer, or period moved the number, and by how much.
03
What is happening now?
Recent-window momentum and anomaly detection, so a bad week is visible in the week it happens.
04
What will happen?
Demand forecasting and customer churn prediction, each shipped with its own accuracy scorecard.
05
What should we do?
Prescriptive recommendations, ranked. Not a dashboard to interpret — a list to act on.
06
Who should we do it to?
RFM segmentation, customer clustering, cohort retention, and which products get bought together.
Every predictive model ships with a health scorecard — accuracy, ROC-AUC, precision and recall, and an explicit overfitting verdict.
You can see how much to trust a forecast before you act on it, instead of being handed a number from a black box.
04Access
Everyone sees their own part of the business.
Six built-in roles, each with a tailored dashboard. A worker sees the projects and tasks they are assigned. A customer sees their own jobs and nothing belonging to anyone else.
| Role | Operations | Field tools | Money | Analytics | Own data |
|---|---|---|---|---|---|
| Super adminThe whole picture, plus configuration | Full access | Full access | Full access | Full access | Full access |
| AdminRuns the operation day to day | Full access | Full access | Full access | Full access | Full access |
| Project managerTheir projects, sites, and crews | Scoped access | Full access | No access | Scoped access | No access |
| WorkerOnly the tasks they are assigned | Scoped access | Scoped access | No access | No access | No access |
| FinanceThe books, without the admin surface | No access | No access | Full access | Scoped access | No access |
| CustomerTheir own projects and nothing else | No access | No access | No access | No access | Full access |
05Security
Enforced on the request, not on the screen.
- Customer data isolation
- A customer can never see another customer's projects, requests, quotes, or invoices — enforced at the API and at the real-time layer, not only in the interface.
- Encrypted at rest
- Sensitive fields are encrypted with AES-256-GCM. Not reversible obfuscation, not base64 with extra steps.
- Full audit logging
- Important admin actions are logged, so you can show a client or a regulator who did what, and when.
- Rate-limited authentication
- Login and registration endpoints are rate-limited against brute force, alongside general API rate limiting.
Role checks sit on every protected action, so permissions cannot be bypassed by calling the API directly — hiding a button is not a security model.
Single-tenant. Your database, not a shared one.
Each client gets a dedicated deployment: its own database, its own backend, its own branded frontend, and its own logo, colours, and company details on every document and every email.