PROFESSIONAL SERVICES · SYSTEM
IN SHORT
Collect, read and check onboarding documents automatically, prepare the risk assessment against your own policy, and put a drafted engagement letter in front of a partner — with the AML decision staying firmly with your responsible person.
The problem
Onboarding is the first thing a client experiences and it is usually the worst. Documents are requested by email, arrive in pieces, get checked by whoever has time, and the engagement letter waits on a partner who has not been told the file is ready. Two weeks pass on work that involves perhaps ninety minutes of actual judgement, and the client — who was ready to instruct on day one — spends that fortnight wondering whether they picked the right firm.
How it works
A structured request goes out and what comes back is read: identity documents, proof of address, incorporation details, beneficial ownership, source of funds narrative. Each is checked for validity, expiry and consistency against the rest of the file, and anything missing or poor quality is chased automatically without a person noticing it was missing. Screening results and the collected evidence are assembled into a risk assessment laid out against your own policy, and an engagement letter is drafted from your precedent with the scope and fee basis populated. The responsible person then reviews a complete file rather than assembling one.
Where the money is
Partly hours — onboarding is expensive time spent on clerical work — but mainly conversion and speed. Work-in-hand that is stuck in onboarding is not billable and is at risk of going elsewhere. Firms that shorten this from two weeks to two days feel it in realised fees within a quarter.
What stays with your people
The AML decision, the risk rating, the scope, the fee and the decision to act. Every one of those carries regulatory and professional consequence and stays with the responsible person. The system prepares the file; it never accepts a client.
What you get
- Structured document collection with automatic chasing of gaps
- Documents read and checked for validity, expiry and consistency
- Risk assessment prepared against your own written policy
- Engagement letter drafted from your precedent, scope populated
- Complete evidence pack and audit trail for the file from day one
Questions we get asked
- Does it make the AML decision?
- No, and it should not. It collects, reads, checks, screens and assembles the evidence into your own policy format. Accepting the client and setting the risk rating stays with your responsible person, and the audit trail records who decided what and on what evidence.
- Will it work with our existing verification provider?
- In most cases yes, through their API or export. The automation sits around the provider — collection, chasing, assembly, drafting — rather than replacing the checks you already trust.
- How long does it take to build?
- Typically four to six weeks for a first version covering 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.
