FORTH SI CASE STUDY · SCOTLAND · UK-WIDE

Kerbco: a Scottish drop kerb contractor, before and after Forth SI

Short answer: Kerbco ran an eleven-step manual permit chain with no admin team. Forth's Super Intelligence layer connected quoting, payment, Street Manager, utility drawings, crew credentials and compliance into one sequence triggered by a single enquiry form — taking manual steps per job from 11 to 1, with traffic management kept in human hands.

Drop kerb & vehicle crossing permits · Owner-operated contractor · zero admin headcount

Groundworks crew installing a drop kerb vehicle crossing while a phone shows a completed permit checklist
Illustrative scene of drop kerb work — not a photo of Kerbco's crew.

£0 → £50k

NEW PIPELINE BUILT

11 → 1

MANUAL STEPS PER JOB

£16.90 → £0

MAP COST PER JOB

Minutes

ENQUIRY TO PRICED QUOTE

Before and after, step by step

AREABEFOREAFTER FORTH SI
Data entryEvery job re-keyed across quoting, permits, drawings and paperworkOne enquiry form is the entire manual data-entry burden
QuotingCrossings priced by handPriced automatically from width, footway build-up and council fee — in minutes
Permit feeChased manually from the customerCaptured on acceptance; payment arms the rest of the chain
Street ManagerOpened and tracked by hand, waiting on the council referenceRecord opened and submitted; the permit reference returns to the job automatically
Utility drawingsRequested late — risk of arriving the morning the crew turns upRequested automatically from the permit reference, during scheduling
Crew and complianceCertification and RAMS assembled by handCertified operatives assigned from a credential library; compliance pack generated
Mapping£16.90 per job on a commercial licenceIn-house mapping engine — £0 marginal cost per quote
Human controlOne person doing everything, capping growthTraffic management stays deliberately manual in Roadplan — a human draws it

How the Super Intelligence layer was applied

  1. 01

    Connect the software

    Quoting, payment, Street Manager, utility requests, credentials and documents joined into one job record.

  2. 02

    Give it company context

    Council fee rules, footway build-ups and operative ticket expiry dates held as shared knowledge the system checks against.

  3. 03

    Coordinate authorised work

    Each step triggers the next — payment arms submission, the permit reference fires drawing requests.

  4. 04

    Keep people in control

    The safety-critical traffic management plan is still drawn by the operator, not generated.

Timeline: Enquiry-to-permit chain live in 9 weeks; mapping engine replaced the paid licence at week 14.

The problem before

  • Every single enquiry triggered the same eleven-step manual chain: hand-price the crossing, chase the customer for the permit fee, open a Street Manager account, wait on the council reference, request statutory undertaker utility drawings, dig out operative certification, and assemble health and safety, RAMS and reinstatement paperwork by hand.
  • The work is unforgiving of incomplete submissions — a missing utility drawing or an out-of-date ticket sends a council application to the back of a four-to-eight week queue, and the customer blames the contractor, not the council.
  • Site mapping was bought in at £16.90 per job from a commercial licence, a cost that scaled linearly with every single quote — including the ones that never converted.
  • With no admin headcount, the whole chain competed for the same hours as the actual groundworks. Growth was capped not by demand but by how much paperwork one person could physically process.

Questions trades owners ask

What does the operator still do by hand?
Traffic management. Signage, coning and pedestrian routing are drawn manually in Roadplan, producing both the council submission plan and the crew's sign install sheet. Everything else in the eleven-step chain runs automatically.
What triggers the permit chain?
Payment of the permit application fee. Acceptance of the quote captures the fee, and that payment arms Street Manager submission, the utility drawing requests and the compliance pack — nothing waits on someone remembering to chase.
How are out-of-date operative tickets prevented from reaching a council?
Operatives are assigned from a credential library with expiry dates. An operative with a lapsed ticket cannot be attached to a submission, which is what stops applications being bounced to the back of a four-to-eight week queue.
Why build a mapping engine instead of paying the licence?
The £16.90 per-job map cost scaled with every quote, including the ones that never converted. Building mapping into Kerbco took the marginal cost of quoting to zero, which is what made a high-volume lead-magnet model viable.
Does this work outside Scotland?
Yes. Council fee structures and footway build-up rules are configurable per authority, so the same chain runs UK-wide with local pricing and submission requirements.

Running a trades business with the same paperwork problem?

Scope what Forth SI would connect in your business in six questions, or read the full technical case study.