PROFESSIONAL SERVICES · SYSTEM
IN SHORT
Onboarding is slow because documents are requested piecemeal, checked by whoever has time, and the engagement letter waits on a partner nobody told. Automating collection, checking and drafting leaves the partner reviewing a complete file — usually within a day.
What actually goes wrong
A prospect says yes. Someone emails a list of documents. Two arrive, one is a photograph of a passport at an angle, the proof of address is out of date. Nobody notices for four days because nobody owns the file yet. Checks are eventually run, a risk assessment is written, and the engagement letter sits in a partner's drafts over a weekend. The client, who was ready to instruct on day one, spends a fortnight wondering whether they chose the right firm.
What it costs
Work in hand that is stuck in onboarding is not billable and is not safe. Prospects do lose momentum, and some of them talk to your competitor while they wait. The internal cost — expensive people doing clerical chasing — is real but secondary to the conversion cost, which almost no firm measures.
How the fix works
A structured request goes out and everything returned is read and checked for validity, expiry and consistency. Gaps and poor-quality documents are chased automatically, immediately, describing precisely what is wrong. Screening results and collected evidence are assembled into a risk assessment laid out against your own policy, and an engagement letter is drafted from your precedent with scope and fee basis populated. The responsible person reviews a complete file instead of assembling one.
What stays with your people
The AML decision, the risk rating, the scope, the fee and the decision to act. All of those carry regulatory and professional consequence, and none of them are automated. The system prepares the file; it never accepts a client.
What you get
- Structured collection with immediate, specific chasing of gaps
- Documents checked for validity, expiry and internal consistency
- Risk assessment prepared against your own written policy
- Engagement letter drafted from your own precedent
- A complete, evidenced file for the partner on day one
Questions we get asked
- Does this weaken our AML position?
- It should strengthen it. The checks are the same or better, the evidence is assembled consistently rather than by whoever was free, and the audit trail records exactly what was collected, when, and who accepted it. What changes is the waiting, not the rigour.
- Will it work with our existing verification provider?
- In most cases yes, through their API or export. The automation sits around the provider rather than replacing checks you already trust.
- How quickly can it be running?
- Typically four to six weeks for your most common client type, then extended to trusts, complex structures and overseas clients once the routine path is proven.
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.
