Software built by an operating company
We build the inspection, document, reporting and AI systems that audited operations run on, because our own facilities, consultancy and training work runs into the same problems.
01Today
Scores on a printed sheet, photographs on a phone, and the visit rebuilt from memory that evening.
Printed checklist, photos on a phone02The record
Each finding carries its photograph, its asset, and an action with an owner and a due date.
The finding- Raised
- Action assigned
- Closed with evidence
03The screen
Four taps per finding, in the order of the walk, and capture carries on with no signal.
On site, on a phone- Photograph
- Severity
- Note
- Asset
04The approval
The reviewer sees every photograph beside its finding and approves the report before it reaches a client.
Named reviewerApproves the reportName and time logged05The output
The report, the findings register and the action list come from the same records, with no retyping.
Audit and inspection apps- Inspection report
- Findings register
- Action list
01Today
Invoices and delivery notes arrive as phone photographs, and a clerk retypes every field.
Invoice photographed on a van seat02The record
Supplier, VAT number, date, each line and the VAT total, every field carrying a confidence level.
The invoice- Read
- In the queue
- Verified
- In the import file
03The screen
The field highlighted on the document, the value read beside it, and one action to confirm or correct.
At a desk- Document image
- Value read
- Confirm
- Correct
04The approval
Handwritten and low-confidence fields wait for the clerk, who still approves every payment.
Accounts clerkConfirms uncertain fieldsName and time logged05The output
Verified invoices leave as an import file your accounting system accepts. Nothing posts on its own.
Data extraction- Import file
- Correction log
01Today
A request arrives by email and waits in an inbox until somebody remembers to chase it.
A request in somebody's inbox02The record
The email becomes a record with an owner and a due date, and the next step lands on a named person.
The request- Received
- Assigned
- Awaiting approval
- Decided
03The screen
One short form at a desk. The person who asked is told where the request stands.
At a desk- Request
- Owner
- Due date
- Status
04The approval
Routed, timed and logged. The decision itself stays with the approver.
Named approverMakes the decisionName and time logged05The output
If it waits, it climbs from the owner to their manager to the overdue register.
Workflow automation- Overdue register
- Escalation ladder
01Today
At month end a coordinator builds the report from WhatsApp photos, a ticket export and a spreadsheet.
WhatsApp photos, a ticket export, a spreadsheet02The record
Waiting needs a reason. Without one, a job held for a client decision looks like one nobody started.
The work order- Raised
- Assigned
- In progress
- Waiting
- Done
- Verified
03The screen
Site observations go on a short form when they happen, not written from memory at month end.
On site, on a phone- Site
- Date
- Observation
04The approval
The report waits for the contract manager, and the approval is logged with it.
Contract managerApproves the reportName and time logged05The output
Each section assembles from its records. A section with no source is marked as manually written.
Dashboards and reporting- Monthly report
- Source map
- Definitions sheet
Step 5 of 5 · The output
ITF Digital · the instrument
System topology
Nothing here replaces what you already run. The sources stay. What gets built is the layer between them and the document, so the document assembles itself from the record instead of being typed at month end.
- 01SourcesWhat you already run
- 02Agent layerNormalise, check, assemble
- 03OutputsAssembled, not typed
- 04The traceSource to document
Documents every engagement leaves behind
Whatever the service, each of these exists before the step after it starts, and each one is yours whether the project continues or not.
The current-state process map
From the one-week systems audit. Every step, handoff, wait and owner, drawn from the work as it runs today. Useful to any supplier you show it to.
The written specification
What gets built, what stays manual, what it connects to and the acceptance tests. Its out-of-scope list settles most arguments before they start.
The data model document
Every record, field, state, permission and relationship, updated to the day of handover and written for the next developer.
The test record
Each test traced to a line of the specification, with who ran it and the result, including a full data export and a restored backup.
The cutover record
What moved and when, the fallback, and the date the old process was retired rather than left running beside the new one.
The handover pack and runbook
Administrator training, the credential register, the operations manual and numbered procedures for whoever is on call.
The source code
In your repository from the first commit, with hosting, domains and subscriptions held in your company's name.
Fourteen services, in five groups
Each one can be bought on its own, and most projects touch two. Every card opens on the symptom that usually brings a buyer to it and names what the first week produces. Security readiness work sits with ITF Cyber, linked last.
Internal tools and portals
A spreadsheet became the system nobody dares change. The first week produces a data profile of it.
Read moreBuildMobile apps for field work
Crews on remote sites still hand in paper job cards. We rebuild the job card as one record before any screen.
Read moreBuildAudit and inspection apps
Inspection photos stay on phones and never reach the report. Week one reorders your checklist to match the walk.
Read moreBuildDocument control systems
Nobody can prove which revision of a form was in use. We start with a register of what you actually hold.
Read moreBuildWebsites and web apps
Your site is a template, English only, or years old. Arabic and English pages come from a content model you own.
Read moreAIAI agents for back-office work
Someone spends days assembling prequalification packs. The agent starts by matching the buyer's index against what you hold.
Read moreAIAssistants over your own documents
Staff ask the same procedure question every week. Before any assistant, we list which of your procedures contradict each other.
Read moreAIData extraction
Delivery notes and supplier invoices get retyped by hand. Twenty of your real documents become the field specification.
Read moreAIDocument and report generation
Quotations and letters are rebuilt from the last one sent. Your template set comes back with its variable fields marked.
Read moreAutomate and reportWorkflow automation
Permits, calibrations and medicals lapse without warning. An obligation register puts an owner on every line.
Read moreAutomate and reportDashboards and reporting
The monthly client report takes two days to write. A source map traces each of its sections to a record.
Read moreConnect and runSystems integration
Three systems know one customer by three names. The identifier map is written before any code.
Read moreConnect and runNetwork management
Scanners drop out in the warehouse aisles. The work opens with a coverage survey and a topology drawing that matches the building.
Read moreAdvisoryAI readiness
Management wants an AI plan by next quarter. You receive a ranked register of tasks where AI earns its place.
Read moreITF CyberSecurity readiness
Control registers, security policies and incident response planning are delivered by ITF Cyber.
Read moreWhat the software hands to a person
Every AI system we build has the same shape, written into the scope before anything is built. The agent reads, extracts, checks against your rules, chases an owner and drafts the output. Then it hands the draft to the person the scope names, who approves anything that leaves the building or changes a record of consequence. The run log is what you show an auditor who asks how a document was produced.
- Agents do the repeated reading, checking, chasing and drafting that eats a person's week
- Conformity calls, payments and decisions a regulation assigns to a competent person go to that person, with the evidence laid out
- Every run is logged with its inputs, its output and the name of whoever approved it
The build cycle
Eight steps, and you can see working software at step 4. Nothing here is a black box for three months.
- 01
Enquiry
The process that is hurting and what it costs you.
You receiveA scoping call.
- 02
Systems audit
We map the current workflow, the handoffs and where the data actually lives.
You receiveA current-state process map.
- 03
Specification
What gets built, what stays manual, what it connects to.
You receiveA written specification and scope.
- 04
Build
Built in visible increments you can look at, not a black box for three months.
You receiveA working increment you can use.
- 05
Pilot
Run live on real work with one team before anyone else touches it.
You receiveA pilot report with fixes applied.
- 06
Deploy
Rolled out, with the old process retired deliberately rather than left running.
You receiveThe live system and a cutover record.
- 07
Handover
Your people trained, the documentation written for them rather than for us.
You receiveAn operations manual and admin training.
- 08
Support
A named owner, a response window and a change log.
You receiveA support agreement and a change log.
Asked before the first call
Who owns the code and the data?
You do. The code sits in your repository from the first commit, and a full data export is built and tested in the first release, not written the week you ask to leave. Hosting, domains and subscriptions are opened in your company's name.
Will AI make decisions in our business?
Agents read, check, chase and draft. Approvals, conformity calls, money and anything regulated go to a named person, and that hand-off is part of the signed scope rather than a setting somebody can switch off.
How long before we see something working?
One week for the systems audit, a few days for the specification, then two to five weeks to the first increment you can use on real work. If a supplier promises a finished system inside that window, ask to see it run on your data.
What does a typical first engagement look like?
A facilities contractor's coordinator spends the last two days of every month building client reports from WhatsApp photos, a ticket export and a spreadsheet. The systems audit traces each report section to its source and finds one, site observations, written from memory. The build assembles the report from records and adds a short capture form for observations, with the first client's report produced from real data in week three. The coordinator now approves the report instead of writing it.
Can you work with the systems we already have?
Usually, and it is the first thing we check. Many products have workflow and reporting features nobody switched on. Where a connection is needed, the identifier map is written before any code.
Where do you work, and which sectors do you know?
Most of the work runs remotely, for clients anywhere, and we come on site across Saudi Arabia when the job needs it. We write for manufacturing, food facilities, warehousing and logistics, industrial contractors, facilities and property operators, and healthcare facilities, each on its own sector page.
Part of one system
Every division keeps records to the same standard, so the second one you need works the way the first one did.
Start with the systems audit
One week inside your workflow, and a current-state process map you keep whether or not anything gets built afterwards.