Skip to content
Leapforge

Leapforge Automations

Watch them run, start to finish.

Four automations, each recorded in one take. The businesses are made up for the recording and say so in their names; the runs are real — real AI calls, real emails, real timings. Two are built on n8n, two in custom code.

n8n69 seconds

Website enquiry → CRM → a personal reply, in seconds

Northbridge Properties (demo estate agency)

A buyer fills in the enquiry form. Before anyone at the agency has seen it, the lead is in the CRM and a reply that answers their actual question is in their inbox.

  1. Enquiry form submitted on the website
  2. Contact and deal created in the CRM
  3. AI writes a reply to what they asked, offering two real viewing slots
  4. Reply emailed to the buyer; the team is told in chat

In this recording

  • — Reply in the buyer's inbox 12.8 seconds after they pressed send
Custom code90 seconds

Supplier invoices → read, checked, paid — exceptions to a person

Kestrel Kitchens (demo)

Five supplier invoices arrive by email, one of them a scan. Each is read, checked against the purchase order and its own maths, and either approved or sent to a person with the reason.

  1. Invoices arrive by email as PDFs, including a scanned one
  2. AI reads each invoice; code re-checks every figure
  3. Matched against the purchase order; duplicates stopped
  4. Exceptions go to a person in chat with approve / correct buttons
  5. Approved invoices go into the payment run

In this recording

  • — About 5 seconds per invoice
  • — £2,208 duplicate invoice stopped
  • — A subtotal £236 higher than its lines and a £56 charge over the PO, both sent to a person
  • — £6,682.56 payment run prepared
n8n108 seconds

Order → invoice → bank matched → late payers chased

Brightwater Coffee Roasters (demo)

A café places a trade order and has the invoice before the page finishes loading. Each morning the bank feed is matched to open invoices, and every late payer gets a reminder in the right tone.

  1. Trade order placed on the ordering page
  2. Invoice created and emailed to the café
  3. Morning run: AI matches bank lines to invoices; code checks every match
  4. Reminders written by how late each invoice is
  5. A payment it could not prove is flagged to a person, not guessed

In this recording

  • — Invoice emailed 1.5 seconds after the order
  • — Whole cash run in 10.4 seconds
  • — £875 matched and marked paid
  • — 4 reminders in 3 different tones
Custom code91 seconds

Shop orders → stock forecast → purchase orders approved in chat

Fernhill Home (demo online shop)

Orders come into the online shop. Every product's stock is forecast against its supplier's lead time, and purchase orders are drafted, approved in one click and emailed to suppliers.

  1. New orders read from the shop
  2. Each product forecast: recent sales against supplier lead time
  3. Purchase orders drafted per supplier and posted to the team chat
  4. Approved with one click; suppliers emailed the order

In this recording

  • — Forecast in 4 seconds
  • — 2 purchase orders, £3,165, approved in chat
  • — A product selling 57% faster spotted
  • — £646 of slow-moving stock flagged

Want one of these on your process?

Tell us which process costs you the most hours. We count what it costs first, then build it inside the systems you already run.

Book a process audit