Site event
Record what happened while it is still fresh.
SubconFlow.OS · Built for UK subcontractors
Commercial control from site event to payment.
SubconFlow.OS keeps site diaries, original evidence, variations, payment applications, invoices and payments connected to the right client, project and commercial record.
Private evidence storageRole-based accessAudit historySubscription billing
SUBCONFLOW.OS COMMERCIAL TRAIL
- 01Site event
- 02Evidence
- 03Variation
- 04Application
The factual record stays connected as the commercial position develops.
One commercial record across the full subcontract workflow.
Site diariesEvidenceVariationsApplicationsInvoicesPayments
One connected workflow
Stop rebuilding the story from WhatsApp, photos and spreadsheets.
SubconFlow.OS is built around preserving what happened, what proves it, what changed commercially and what eventually got paid.
Evidence
Attach the original photo, document or supporting record.
Variation
Identify the commercial impact and price the extra work.
Application
Carry the value into the relevant payment application.
Invoice
Issue the commercial record against the right project and client.
Payment
Track what was paid, what remains outstanding and why.
Built around the commercial record
The evidence does not disappear when the conversation moves on.
Record site facts quickly
Capture labour, delays, instructions, extra work and affected time while the details are still reliable.
Preserve original evidence
Keep supporting files private and link them to the event, variation or action they actually support.
Control the money trail
Carry commercial value through variations, applications, invoices and payments without losing the source record.
Export an organised record
Prepare structured evidence packs and notice drafts for review instead of reconstructing the chronology later.
Built for real subcontract structures
One customer can have many sites. Every site keeps its own commercial trail.
Store the client once, then keep contacts, projects, variations, applications, invoices and evidence correctly separated underneath it.
<30 sectarget for a quick site record
1 trailfrom site event to payment
4 rolesOwner, Admin, QS and Site access
Simple monthly plans
Start with the size of your business now, then grow the workspace later.
Every plan uses the same core commercial workflow. Limits control active projects and workspace users.
Starter
£49/month
For a small subcontractor getting site and commercial records under control.
- Up to 3 active projects
- Up to 3 workspace users
- Core records and evidence
Pro
£99/month
For growing subcontractors running several live projects and commercial workflows.
- Up to 15 active projects
- Up to 10 workspace users
- Full commercial workflow
Business
£199/month
For larger teams needing wider project and user capacity.
- Up to 100 active projects
- Up to 50 workspace users
- Wider operational capacity
Subscription availability and trial length are confirmed during checkout.
FAQ
Questions subcontractors usually ask first.
Who is SubconFlow.OS for?
SubconFlow.OS is built for UK construction subcontractors that need a reliable commercial record across multiple clients and sites.
Is it project-management software?
Not in the generic sense. The product is focused on site facts, evidence, variations, payment applications, invoices, payments and the commercial trail connecting them.
Can one client have multiple sites?
Yes. A client company can have multiple projects or sites, each with its own diaries, evidence, variations, applications, invoices and payment history.
Can site staff and commercial staff have different access?
Yes. Workspace roles separate Owner, Admin, Commercial/QS and Foreman/Site access so commercial information can be restricted appropriately.
Does SubconFlow.OS decide whether money is legally due?
No. It preserves the records and figures your team enters. Contractual entitlement, notice requirements, tax treatment and legal advice still require human review.
Can I export my records?
Yes. The platform includes structured exports and evidence-pack workflows so the underlying record can be taken out of the system when needed.
Keep the record before you need the argument