CONSTRUCTION · SYSTEM
IN SHORT
Deadlines slip because enquiries arrive in an inbox nobody owns, in formats nobody can sort, while the estimator is on site. Automated triage reads every pack the hour it lands, ranks it by value and deadline, and acknowledges it — so nothing good expires unopened.
What actually goes wrong
Tender packs land in a shared inbox alongside supplier invoices and site queries. Nobody has time to open each one, so the pile is triaged by whoever is nearest a laptop, usually late in the day. Big opportunities are judged on the subject line, and the ones with awkward attachments get left for tomorrow. By the time the estimator looks, half the return window is gone and the answer is a rushed price or no price at all.
What it costs
A mid-sized contractor receiving forty enquiries a month and properly answering twenty-five is not short of demand — it is short of hours. Every unpriced enquiry is a bid you did not make at zero marginal cost. Winning one extra job a quarter from work already sitting in the inbox usually dwarfs the cost of the system that finds it.
How the fix works
Every inbound email and portal notification is read, classified by trade, contract value, client and return date, and logged against a pipeline record with the documents attached. Anything under your minimum value or outside your trades is parked with a polite decline. Everything else is acknowledged within minutes and queued for the estimator with a deadline clock running. A morning digest shows what must be priced today.
What stays with your people
The bid/no-bid decision, the price, and the client relationship. The system never submits, never commits to a rate, and never declines a named client without a human looking. It removes the sorting, not the judgement.
What you get
- Every enquiry read and logged the hour it arrives, whatever the format
- Ranked by value, deadline and fit with your trades
- Automatic acknowledgement so clients know they have been heard
- A daily list of what must be priced today, in deadline order
- A record of everything declined and why, for pipeline reporting
Questions we get asked
- How quickly can this be running?
- Enquiry triage is usually the fastest workflow to put live — four to six weeks from the start of a build, because the process is already written down in people's heads and the inputs are just email.
- Will it read tender portals as well as email?
- It reads the notification emails those portals send, and where a portal offers an API or export we connect to it directly. We will confirm which of your portals are practical at audit stage.
- What if it misjudges an enquiry?
- Nothing is deleted. Low-scoring enquiries still appear in the pipeline, just further down, and a wrong call is one click to reprioritise. The classifier is tuned on your own decisions over the first few weeks.
TRUST & CREDENTIALS
How we work, and what stands behind it
This page is maintained by Forth Systems. Everything listed below describes our own team, hosting choices and the technologies we build on — it is a statement of practice, not an independent certification or an endorsement by the vendors named.
UK team & data residency
Who builds it, and where your data sits while they do.
UK-based engineers
Edinburgh-headquartered. Every system is designed, built and supported by our own UK-based engineering team — no offshore delivery pool.
UK / EU hosting by default
Applications and databases are provisioned in UK or EU regions unless you require otherwise, with encryption in transit and at rest.
Human-in-the-loop by design
Every AI system we ship keeps a manual override. Nothing irreversible happens without an operator able to review, edit or stop it.
Audit trails as standard
Automated actions are written as first-class records — who or what did it, when, against which input — so operations stay evidence-ready.
Systems we build on
The platforms our systems run on. These are the technologies we deploy and support — not sponsorships or reseller badges.
OpenAI, Anthropic & Google models
Model-agnostic delivery. We route each workload to the model that fits it on cost, latency and accuracy, and can switch without a rebuild.
Supabase & Postgres
Row-level-security Postgres as the operational spine under every platform we run.
Stripe payments
Payment capture, checkout and reconciliation wired directly into job and permit workflows.
Xero, Sage & HubSpot integrations
Production integrations into the finance and CRM systems UK operators already run, so automation lands where the business keeps its records.
Streetworks & industry credentials
Operational domains we build in daily, with the sector systems we integrate against.
DfT Street Manager integration
The permit chain we built for Kerbco creates and tracks streetworks permit applications against DfT Street Manager and local highway authority processes.
NRSWA-aligned workflows
Permit, reinstatement and traffic-management workflows built to the New Roads and Street Works Act process contractors are inspected against.
Traffic management planning
Roadplan produces signing and guarding layouts for council submission and for the crew installing them on site.
Operator-built, not consultancy-built
Our platforms are built around real operating workflows — including the permit chain we built for our client Kerbco, a Scottish drop kerb contractor.
Insurance certificates, registration numbers and security documentation are available on request — ask the team.
