Practice areas

Software built for the way an industry already works.

Operational software is written against a trade, not against a template. Each area below has its own stakeholders, its own record that has to survive a dispute, and its own systems that cannot be switched off. The delivery organization is more than 45 people: in-house planners, architects, designers and data analysts, with engineering contracted to scope.

Where the work is

Where the work is.

Eight practice areas, served under two engagement models, and a route for work outside them. Programs are priced per job against a program schedule. Practices are delivered as a fixed scope agreed before the build starts.

Large construction and development

The system a job is run from: scope, submittals, change orders, draws and the daily record that decides a claim two years later. Built around the schedule the program already works to, and connected to the project controls the owner and the lender already read.

Program scale · Priced per job

Infrastructure

Multi party work where an agency, a prime, several subcontractors and an engineer of record all need the same facts and different views of them. Permissions, approvals and the audit trail are designed before anything else, because they cannot be retrofitted.

Program scale · Multi party

Data centers

Open work, which vendor is on the floor, who was granted access, site conditions and the reporting cadence upward, held as software rather than as a folder of workbooks. Deployed on premises where the site requires it, with no dependence on an outside connection to keep working.

Operations · On premises capable

Inspection and professional services

The deliverable is the product, so the deliverable is what gets automated: findings captured in the field become the finished report without a retyping step. Eight hours of report production reduced to under one hour, with the report reaching the client before the inspector is back at the office.

Deliverable automation

Healthcare and clinical

Scheduling, intake, clinical note templates your clinicians control and the internal record keeping that sits around a practice management system rather than replacing it. Engagements in this area are delivered under a non disclosure agreement and are never described in identifiable terms.

Confidential · Under NDA

Industrial and commercial operations

For service businesses running crews across many sites: an account folder per building, service lines that change over the life of an account, complaints evidenced with photographs, and the instruction a supervisor sends a crew. Nothing outbound leaves without a person releasing it.

Multi site · Crew scale

Laboratory and analytical

A calculation method that has grown into a workbook only one person can safely operate, rebuilt as auditable software with the reporting generated behind it. The engine is checked value for value against the laboratory's own source workbook rather than reimplemented from a description of it.

Verified against source method

Natural health practice

Client records, protocols, intake and the follow up sequence a practitioner runs by hand today, built as one system a small team can operate. Engagements in this area are delivered under a non disclosure agreement and described by sector only.

Confidential · Under NDA

Programs outside these areas

Operational software is operational software. If the work is substantial and the process behind it is real, the engagement model is the same one used above, and the sector being new to this list changes nothing about how it is scoped or delivered.

By enquiry

Engagement models

How the two models differ.

The difference is not size of ambition. It is who has to agree, and how the scope is fixed.

Programs.

Program work is priced per job, against a schedule that already exists and parties already contracted to each other. Scoping runs as a procurement exercise: a capability statement, a security questionnaire, insurance certificates, references, a master agreement and a continuity position, settled before a schedule of work is agreed. Scope is expected to move, because the program moves, so a change is an instruction against the master agreement rather than a renegotiation.

Practices.

Practice work is a fixed scope, settled in two conversations. The first reads how the business currently runs and proposes nothing. The second is the plan and a working mockup of the real screens, in the real design, carrying every button, folder and setting the finished product will have. Changes happen at that stage, where a change costs a conversation, and once the scope is signed the build runs to completion without coming back for decisions.

Identical in both.

The irreversible decisions come first in either model: separation of one client's data from another, server side permissions, what is kept when a record changes, what may be sent and who releases it, and how the business gets all of its own data back out on any day it asks.

Name the area and the process that costs the most time, and the capability statement will come back written against it.

Programs and practices are served nationwide, United States. To start: call (252) 666-7217 or email [email protected].