These are operator-built systems demonstrated with synthetic Northstar data. Each example states who it is for, the operational outcome and the evidence in the film. They are not a catalogue of products for sale and they are not external client case studies.
Frontline capture
SiteLog
Tradespeople and administrators
Outcome
Weekly site records that first fed existing cost-control and payment processes.
Evidence shown
A tradesperson records work against a selected project and location for the current week. The entry appears in the weekly summary and a weekly invoice is generated. An administrator then exports the selected week and reviews the project and user-management controls.
A later extension connecting SiteLog records, managers’ cost allocation and existing accounting software.
Evidence shown
A site manager allocates weekly labour costs to project budget locations and checks remaining value. A quantity surveyor creates a controlled variation, builds a client quote and reviews an overspend request. Accounts then generates a payment workbook with detailed records and a Sage-compatible nominal and cost-code export.
One controlled route from application through certification, payment and retention.
Evidence shown
A commercial user opens live contracts, works in a ledger that keeps applications, certificates, payments and retention together, and uses role dashboards for due actions, variances and forecast hygiene.
A portfolio of live, completed and pipeline projects is shown with identity and contract value. Opening a live project reveals codes, contract terms and a hand-off into Applications Ledger.
A consistent pipeline of likely future work, including a new probable record.
Evidence shown
The pipeline lists likely future work with value, margin, status, owner and division. A new probable is captured through a consistent form, including year-by-year value and retention, and joins the same list.
A connection to accounts software, a controlled extraction and reusable workbook outputs.
Evidence shown
The operator tests a connection to accounts software, queues the period datasets, runs the extraction and reviews evidence counts before opening the resulting workbooks.
Short-term daily cash, project schedules and a longer forecast from connected sources.
Evidence shown
The commercial finance console opens short-term and long-term cashflow. A daily workbook, a project cost-value schedule and a longer forecast with facility checks are reviewed in turn.
This connected workflow began as independent bespoke systems, built one at a time with a long-term approach that allowed them to form one fully integrated system.
SiteLog first fed existing cost-control and payment processes. BudgetFlow later extended the connection: a weekly scheduled API extraction transfers SiteLog records; managers allocate costs; a BudgetFlow export is produced at a set point each week for import into existing accounting software.
Finance extraction and reporting use deterministic local processing. AI does not process company accounting data. Verified inputs and accounts data feed the checked processing that produces Cashflow and Management Accounts.