mmitech
Hero illustration for the Stage Payment And Retention Ledger solution

£40k extension, eighteen-month wedding, 5% retention on the May commercial job - one ledger, three cashflows

Sent the strip-out invoice four weeks ago. By plastering she’s shocked at the next one. The May commercial job has £8k of retention I won’t see until next October. I’m running three different cashflows in my head and none of them on paper.

Customer thinks the deposit is the deposit. The strip-out invoice goes in, she queries it. By plastering she’s shocked. The May commercial job has a 5% retention you won’t see until next October, and the second half not until the twelve-month defects-liability ends. The wedding venue’s running a 50% deposit / 25% at six months / 25% fourteen days before ladder and the family-side balance pull at eight weeks out is where the angry email lands. The £3,400 dental implant plan went to Antalya on Saturday because the receptionist forgot to send the finance link on Wednesday.

Three industries; same shape - staged payments tracked against milestones, with the right customer-facing wording at the right moment, the photo evidence behind each trigger, and the release-chase to the QS thirty days before each retention milestone. This is the build that runs underneath the Quote & Chase Ladder - the chase ladder hands the deposit to this engine the moment the quote is accepted, and from there the stages run through the project with the cashflow visible to the operator and the customer-side feel handled in your voice without you typing it. The shape is sealed against HC Electrical - live commercial retention ledger running on the commercial fit-out side with the first-half / second-half release tracked and the QS-chase cadence firing thirty days ahead of each release.


What gets lost between deposit landed and retention released

The mid-build silence is where the cashflow gets eaten. A few moments - pick the ones that sound like your year:

These aren’t problems for a generic invoicing tool. They’re the bit between deposit landed and retention released - which is where the structural cashflow on every high-ticket build actually lives.

The strip-out invoice firing the moment the foreman taps complete, with the photo set attached

What solved looks like

1. Every stage is a first-class milestone - agreed amount, trigger condition, customer-facing wording

The “she didn’t know that was a stage” moment: the customer signed off on a £40k total at contract. She thinks the deposit is the deposit and the rest is at the end. The strip-out invoice lands four weeks in, she queries it. By plastering she’s shocked. The cashflow ladder lives in your head and on a Wickes receipt; the customer’s expectations don’t match yours and you’re the one having the awkward conversation.

Solved looks like: every stage carries the agreed amount, the trigger condition (the foreman’s first-fix-complete photo set, the QS’s practical-completion certificate, the venue’s six-months-out date, the dental fit appointment), the expected date, the actual date, the customer-facing wording, the payment method, and the late-payment posture. Per project the stages are configured against the contract - extension on a deposit / strip-out / first-fix / second-fix / completion ladder; wet-room on deposit / supply / install / snagging-release; commercial JCT or NEC on interim / practical-completion / first-half-retention / second-half-retention; wedding venue on the 50 / 25 / 25 ladder; dental treatment plan on consultation / treatment-plan-accepted / fit / final-review. The schedule lives on the contract from day one and the customer sees it at signature, not as a surprise mid-build.

2. Trigger-and-fire - the foreman taps complete, the invoice fires with the photo evidence attached

The “I’ll do the invoices Friday” moment: strip-out finished Tuesday. Friday admin doesn’t get to the invoice until Saturday morning. Cleared into Monday by the time she sees it, by then she’s already mentally moved on to the what’s next and the stage payment lands as a surprise, not as the closure of the stage she just lived through.

Solved looks like: when the foreman taps strip-out complete on his phone with the photo set, the next stage invoice fires the same hour with the photos attached and the customer-facing wording explaining what’s been done. “Hi Sarah - strip-out’s complete (photos attached). Next stage is first-fix electrics + plumbing, starting Monday week 6. As agreed in the contract, the strip-out stage payment of £6,200 is now due - tap below to pay, or reply with any queries before Friday.” - fires in your voice, signed off once and re-used. Same trigger as the Booking & Review Loop done-event; same voice as the Trainable Inbound AI Agent - your past emails, your covering letters, the way you describe what you do.

3. Retention as a tracked object on commercial work - chased thirty days before each release

The “I’d forgotten about the May retention” moment: the £160k commercial job from May has £8k of retention split half on practical completion and half twelve months after. October arrives. The QS is meant to release the first half. He doesn’t, because he hasn’t been chased. You don’t chase, because the original drawings are in a folder somewhere and you haven’t got time to dig them out on a Wednesday afternoon. By the time you remember, the QS has moved firms and the new one wants the as-built record before he’ll release.

Solved looks like: the 5% retention sits as a tracked obligation on the project record - first 2.5% release at practical completion (chase the QS thirty days ahead, with the as-built record, the snag-list sign-off, and the photo evidence already assembled), second 2.5% release at the twelve-month defects-liability end (chase the QS thirty days ahead, with the defects record clean). The cashflow forecast carries the retention-release dates so you know when the £8k from the May job is genuinely going to land - and the QS-chase fires automatically at the thirty-day mark, structured, with all the evidence the QS will ask for already in the email. The retention release becomes a known event on a known date instead of a thing you might remember in October.

4. Customer-facing wording per stage - in your voice, signed off once

The “is this email actually from us” moment: the templated invoice email arrives in her inbox in corporate English with a smiley face. She didn’t recognise the tone, so she rang to check it was you. Multiply by every stage on every project.

Solved looks like: the customer-facing wording per stage is drafted in your voice and signed off once at contract - what gets said at deposit-received, at strip-out-complete, at first-fix-complete, at second-fix-complete, at practical-completion, at retention-release-due. After the first ten stages on the first project, the engine has enough voice training to draft the wording for new contract shapes; you keep the send-or-edit slot for the edge cases (a customer’s flagged a payment concern, the build’s run over schedule, the variation’s pushed the next stage up by 20%). Same voice training as Trainable Inbound AI Agent; same channel routing per customer; same opt-out posture.

5. The cashflow forecast that ends the Sunday-night anxiety

The “I don’t know what’s coming in next month” moment: five projects on the books, each with three to five stages outstanding, plus the May retention you’ve half-forgotten about. Sunday evening. You’d model the forecast on a spreadsheet but you’d need an hour and a glass of wine, and the wine doesn’t help the arithmetic.

Solved looks like: every project’s stages roll up into a monthly cashflow projection - stages due to invoice next month, stages invoiced and awaiting payment, retention releases due, the variation-log running balance. The bank-feed reconciles against the projection; the Sunday-night anxiety becomes a Sunday-night two-minute glance. The May retention release shows on the October row with the QS-chase already in the queue; the £40k extension shows the next stage on the week 13 row with the trigger condition (first-fix photo) configured.

6. Finance routing built into the customer side - at the right ticket, on the right channel

The “she went to Antalya because we didn’t send the link” moment: the £3,400 implant plan got accepted at consultation but the patient didn’t sign the finance agreement because the receptionist forgot to send the link until Friday afternoon. By Saturday she’d booked Antalya. £3,400 lost to admin friction on a £25 task.

Solved looks like: finance routing per vertical and per ticket-size - V12 / Novuna / Kanda for trade-side high-ticket consumer finance, Klarna / PayPal Credit for retail-adjacent splits, Tabeo / Medenta for dental and clinical, the payment provider you’re already on for deposit / interim flows, bank-transfer with the right reference for the commercial side. The finance link fires in the customer’s channel of choice the same hour the stage trigger fires; the Saturday-morning fallback for customers who haven’t tapped by Friday catches the would-be-Antalya cases before they happen.


Sunday-evening glance at the cashflow forecast - stages, retention releases, variations all on one page

How the stage ladder runs, by default

The default trade-shape domestic-extension cadence (£25-80k rear extension on a deposit / strip-out / first-fix / second-fix / completion ladder) runs:

Per-vertical tuning lives on top of the default - a wet-room runs on a four-stage deposit / supply / install / snagging-release ladder with the supplier-lead-time risk captured against the install date; a JCT / NEC commercial contract runs the interim valuations on the agreed schedule with the QS-chase cadence; a wedding venue runs the 50 / 25 / 25 ladder with the six-months-out and fourteen-days-out triggers paced to the wedding-planning calendar; a dental treatment plan runs on consultation / treatment-plan-accepted / fit / final-review with the finance link firing at acceptance and the Saturday-morning fallback for the would-be-Antalya cases.


Who this is for

The shape repeats anywhere the ticket’s high enough that one number at the end won’t work - and the customer needs to feel the build progressing as the cashflow does.

Construction and commercial sub-contracting - construction, commercial-fit-out builders, commercial electricians, commercial plumbers, commercial-maintenance roofers, commercial-contract decorators, commercial-grounds landscapers. JCT / NEC stage-payment ladders, retention split (first half at practical completion, second half at twelve-month defects-liability), QS-chase thirty days before each release, FM-side write-back where the helpdesk has one. The retention column becomes a tracked object, not a thing you might remember in October.

Domestic-extension and high-ticket build - extension-specialist builders. The £25-80k rear extension as a deposit / strip-out / first-fix / second-fix / completion ladder, with photo-evidence triggers per milestone, the customer-side wording explaining what’s been done and why this invoice is now due, and the variation log running alongside.

Bathroom and wet-room fitters - bathroom-fitter plumbers. The £8-25k wet-room with the wedding-style stage-payment ladder (deposit / supply / install / snagging-release) and the supplier-lead-time risk captured against the install date so a bespoke-tray slip doesn’t push the customer-facing schedule out of date.

Boiler installs, heat pumps, and solar-PV-and-battery - boiler-installer gas engineers, heat-pump-installer gas engineers, solar-PV-and-battery MCS installers. The £6-20k install with deposit at acceptance, balance on completion, finance routing per ticket (V12 / Novuna / Kanda for consumer-finance, the payment provider you’re already on for deposit). The MCS / BUS submission pairs with Grant & Submission Handling.

Wedding venues and high-ticket event suppliers - wedding venues, wedding suppliers. The 50% deposit / 25% at six months / 25% fourteen days before stage ladder, with the eight-weeks-out pull awkwardness handled before it gets to lawyers and one-star reviews.

Dental treatment plans and clinical finance - dental clinics, aesthetic and PMI clinics. The £1,800-£5,000 treatment plan with V12 / Tabeo / Medenta finance routing, deposit at signature, completion-stage at fit, defects-liability handled by clinical protocol. The Saturday-morning fallback catches the would-be-Antalya cases.

Same engine; different stages; different triggers; different finance route.


The closest thing we’ve already built

HC Electrical - live commercial retention ledger running on the commercial-fit-out side. First-half retention released at practical completion (QS-chase fires thirty days ahead with the as-built record and snag-list sign-off assembled), second-half released at the twelve-month defects-liability end (QS-chase fires thirty days ahead with the defects record clean). The clearest reference for any commercial sub-contractor carrying retention as an open object on every project. See Hc Electrical for the build detail.

A private-hire event venue we’ve built end-to-end - the wedding-venue stage-payment ladder (50 / 25 / 25) live on the wedding-supplier side as part of the same engine. The six-months-out and fourteen-days-out triggers fire automatically; the eight-weeks-out family-payment-problem exception triggers the structured conversation cadence rather than the angry email.

mendbuddy is the multi-channel platform that runs the customer-facing wording - the “strip-out’s complete, here’s what’s next” SMS / WhatsApp / email at each stage trigger, voice-trained so it lands in your voice and on the channel the customer reads.

For high-ticket installs that come with grant or submission paperwork (OZEV, MCS / BUS, DNO notifications, manufacturer warranty registration), the stage-payment ladder pairs with Grant & Submission Handling - the submission state and the stage state run on the same project record. For the customer-side view of the project across the build, it pairs with Customer & Third Party Portal - the customer sees the project plan, the photos, the stage payments, the variation log, and the snag list as it builds.


The thirty-day-ahead QS chase - as-built record and snag-list sign-off already in the email

Tell us what your stage cycle looks like

What contract shapes you work to, what your retention exposure looks like across the year, where the cashflow gap bites worst (the deposit-to-strip-out window, the practical-completion-to-first-half-retention window, the wedding eight-weeks-out family-payment-problem), and what your worst stage-collection or retention-release experience in the last year was. Tell us the project that ate the most cashflow and we’ll come back with a sketch of what we’d build so the next one runs on rails. No demo, no calendar widget. Email reply, scoped sketch, you decide.


FAQ

Will it work with JCT / NEC contracts?

Yes for the standard forms - JCT Minor Works, JCT Standard, JCT Intermediate, NEC4 Engineering and Construction Contract. The stage structure reads from the contract form; the engine carries the right wording for the form variant in the customer-facing and QS-side communications. Custom contract forms get scoped per project.

Will it integrate with our accounting (Xero / QuickBooks / FreeAgent / Sage)?

Yes for all named. The ledger writes invoice events back to your accounting system per stage; retention sits as a tracked liability against the customer record so the year-end shows the right unrealised income. The bookkeeping stays where it always was; we don’t replace the ledger.

Will the customer-side wording actually sound like us?

After the first ten stages, yes - the voice training is the same shape as Trainable Inbound AI Agent. The first ten fire as send-or-edit drafts for you; after that the routine ones run unattended and you keep the send-or-edit slot for the edge cases the agent flags (a customer’s gone quiet, the build’s run over schedule, the variation pushed the next stage by 20%).

Can the eight-weeks-out wedding-balance pull be handled gracefully?

Yes - that’s why the cadence is staged earlier. The 50% at signature, 25% at six months, 25% fourteen days before is the standard shape; the “family flagged a payment problem” exception at eight weeks out triggers a structured conversation cadence rather than an angry email - the venue manager gets a one-line summary and a draft reply in their voice, the family gets a calm, structured “let’s find a way through” message instead of an aggressive chase. The lawyer’s letter at three weeks and the one-star review at six weeks after both disappear from the pattern.

What about the dental V12 / Tabeo / Medenta side - does it route to the right finance partner per treatment-plan ticket size?

Yes - the finance routing is per-vertical and per-ticket. The finance link fires in the patient’s channel of choice the same hour the treatment-plan acceptance trigger fires; the Saturday-morning fallback for patients who haven’t tapped by Friday catches the would-be-Antalya cases before they happen. Per-clinic rules sit on the configuration so a high-volume implants clinic and a single-chair private practice route to different defaults.

Will it integrate with our payment providers for the stage-payment links?

Yes - whichever provider you’re already on, for deposit and interim flows. For high-ticket consumer finance, we route to whichever partner you’ve already on-boarded with (V12 / Novuna / Kanda for trade-side, Tabeo / Medenta for dental, Klarna / PayPal Credit for retail-adjacent splits). For commercial bank-transfer, the right reference and the right invoice number land on the email automatically. We don’t bring you onto a new payment stack; we wire to whatever’s running.

How does the retention-release QS-chase actually fire - won’t the QS just ignore it?

The chase is structured - at thirty days ahead of each release, the email lands with the as-built record, the snag-list sign-off, the photo evidence, and the contract reference all pre-assembled. A QS who’s about to release on time replies “on track”; a QS who needs more goes back with the specific gap, which lands as a structured query on your dashboard. The cadence escalates at fifteen days and at the release date itself; the “chase that lifts to the partner-side at the customer’s firm” shape is the same as the Invoice & Dunning Ladder day-45 escalation. Most QS responses come back within 72 hours of the structured chase; the chronic late-releasers see the evidence pack and pay-or-explain.

What happens to a stage that gets disputed - a customer who queries the strip-out invoice?

The dispute routes to a triage queue on your dashboard with the customer’s reply, the original stage trigger, the photo evidence, and the contract wording all attached. You resolve from one screen; the resolution writes back to the customer-facing view. Disputed amounts hold while you respond; the rest of the project’s cashflow forecast adjusts to show the held line. Disputes don’t break the cadence; they reshape it for that customer until resolved.

Does this replace our diary / our job-management app / our QS software?

No. It sits on top. The stage-payment object talks to your existing diary (Tradify, ServiceM8, Powered Now, Commusoft, Google Calendar), your existing accounting (Xero, QuickBooks, FreeAgent, Sage), and your QS-side records where you maintain them. The cadence runs in the gap those tools don’t fill - between deposit landed and retention released, which is where the cashflow on every high-ticket build actually lives. If you don’t have a QS system, the project record lives in its own store and you can decide later whether to migrate it anywhere.

What does it cost?

Every build is scoped per client - depends on your contract shapes, retention exposure, accounting stack, and finance partners. We talk it through, agree the scope and the price in writing, then build. No per-stage charges, no surge billing if you have a busy quarter. See pricing for how we work.

Tell us what's slowing the business down

Send an enquiry - what you do, what's slowing you down, what you've already tried. We'll come back with a sketch of what we'd build and what it would cost. No calendar, no demo to sit through.

No calendar widgets. Email reply, scoped sketch.

Tell us what's slowing the business down

Email reply, scoped sketch, you decide. No calendar widgets, no demo to sit through.

No calendar widgets. Email reply, scoped sketch.