The quote follows itself up, and the invoice chases itself.

The problem

You write the estimate on a Thursday evening. You email it. And that, functionally, is the end of your sales process. Nobody knows whether it was opened. Nothing in the calendar says ring them Monday. You remember it on Sunday night, feel briefly bad, and by then they have had three days to accept somebody else's. The quote that loses is rarely the one that was too expensive. It is the one nobody followed up.

At the other end, the same gap runs the other way. The job finishes Friday. The paperwork reaches the office Monday. The invoice goes out late the following week on thirty-day terms, so work done in May gets paid in July. Nobody notices any single invoice is late. What gets noticed is the quarter, by which point four of them are sixty days out and every one of those conversations is harder than it would have been on day three.

In between, the same numbers get typed four times. The price is in the quote, the dates are in the calendar, the line items are in the accounting package, the payment is in the bank. Every retype is a fresh chance for the invoice to disagree with the quote. And an invoice that disagrees with the quote does not get queried the day it arrives. It gets put to one side. That is a thirty-day delay wearing a question as a disguise.

You can buy pieces of this. Your accounting package already sends invoice reminders, and it is worth every cent of what it costs. What it does not know: whether the quote was ever answered, which jobs are waiting on a deposit, that the customer added two radiators on the Tuesday, or that the reminder it is about to fire off is going to somebody who paid by bank transfer yesterday. The pieces are cheap because each one only sees its own end. The middle is where the money is, and nobody sells the middle.

How it works

Seven things happen between the estimate leaving and the money arriving. Your accounting package already does one of them, and it is not one of the two that matter most.

1. 01The quote is built from the record, not from a blank pageIt is assembled out of what the enquiry already captured, priced off your own rate card rather than from memory, and sent as a link rather than a PDF attached to an email. The link matters for one reason: a PDF that sits unopened in a spam folder looks exactly like a PDF that was read and ignored, and those two situations need completely different follow-up.
2. 02Opened and ignored is a different event from never openedA quote that was opened twice on the day it arrived and then went quiet is a live conversation waiting for a nudge about a specific worry. A quote that was never opened is a delivery problem, and the fix is a text saying it was sent rather than a cheerful message about whether they have had a chance to think it over. The system can tell these apart, so it treats them differently.
3. 03Follow-up runs until there is an answer, including noThree touches over about ten working days, on whichever channel the customer used to reach you in the first place, each one written to say something rather than to check in. It stops the moment anybody replies. A no is captured with a reason and that reason goes on the record, because the pattern across forty declined quotes is the most useful pricing information in the business and almost nobody collects it.
4. 04A yes becomes a job rather than an emailAccepting the quote creates the job, holds the slot that was pencilled in, takes the deposit if there is one, and writes the agreed scope to the record in the words it was agreed in. The slot is held and then confirmed rather than booked outright, for the same reason it is in the inbound system: two accepted quotes will eventually reach for the same Tuesday.
5. 05The invoice is raised from what was done, not from what was quotedVariations are captured against the job while they happen, by whoever is on site, in a form that takes about twenty seconds. The invoice is then assembled from the quote plus the variations, which is the difference between an invoice that gets paid and an invoice that gets a phone call. It goes out the evening the job completes rather than on the next office day.
6. 06Payments are matched rather than reconciled by handCard payments land against the invoice automatically, and bank transfers are matched on reference and amount, including the partial ones and the ones where somebody paid three invoices in one lump. This is the step that stops the worst failure in the whole run, which is chasing somebody who has already paid. It costs a customer more goodwill than the late payment ever cost you.
7. 07Late is a sequence, and a person is at the end of itDay three is a note that it may have been missed. Day ten is firmer and carries a statement. Day twenty-one stops being automatic and arrives on a named person's list with the whole history attached, because by then the thing that recovers the money is a phone call from somebody the customer knows. Every step cancels the moment the payment lands, including mid-sequence.

What it's built from

Five pieces, and any of them swaps for the equivalent you already pay for. The shape of the pipeline is the deliverable; the logos are an implementation detail.

• HubSpot, or whatever holds the dealOne record per customer carrying the quote, its version history, the follow-up that has gone out, the job and the invoice. Pipedrive, Zoho or the CRM you already have does this equally well. What matters is that there is one place where the answer to how did this end is written down, rather than four places that each know a quarter of it.
• n8n, the part that decidesSelf-hosted on European infrastructure, and the actual product. Every follow-up cadence, escalation threshold, matching rule and stop condition lives here as something you can open and read. When the terms change from thirty days to fourteen, one person changes one number in one place rather than hunting through four tools for wherever that was configured.
• Claude, for the writing and the readingDrafts each follow-up against what is actually in the quote and what the customer said when they asked for it, so the second touch refers to the two radiators rather than to your valued business. It also reads the replies, which is how a message saying we have gone with someone else gets filed as a loss with a reason instead of sitting in the sequence for another week.
• Stripe, for the money and the matchingPayment links on the invoice, and the reconciliation feed the matching runs on. A link rather than bank details on a PDF typically moves payment forward by days, because it removes the gap between deciding to pay and being somewhere you can do it. Bank transfer stays available for the customers who will only ever pay that way.
• Twilio, for the channel that actually gets readQuote follow-up and the first late-payment note go by text as well as email, because an email to a builder arrives alongside forty others and a text arrives alone. It carries the compliance floor with it: opt-outs honoured at the point of request, quiet hours respected, nothing sent on a Sunday morning.

What it's worth

Do this with your own numbers rather than ours. It takes a minute, and it is the only version of it worth believing.

• You send 40 quotes a month and a third of them are never answered either way.13 open quotes a month with no decision attached. You are not losing those on price, because no price comparison ever happened.
• Structured follow-up gets an answer out of half of those, and a third of the answers are yes.Two extra jobs a month. At a 2,000 euro average that is around 48,000 euros a year from quotes you had already paid to produce.
• Invoices currently go out six days after the job, on thirty-day terms, and you bill 60,000 euros a month.Invoicing the same evening pulls roughly 12,000 euros of working capital permanently forward. It is not new revenue, it is money you already earned arriving six days sooner, every month, for good.
• One person spends the published European average of about ten hours a week on statements and chasing.Around 43 hours a month, most of it on invoices that would have been paid anyway. The sequence does the first two touches; the person only does the ones where a person helps.

These are illustrations using published averages and round numbers, not results we are reporting. Your quote volume, job value, win rate and terms will move all four lines, which is why the first week of the build measures them rather than assuming them.

The research behind those assumptions

Published figures rather than ours. They describe the size of the problem, which is the number worth knowing before spending anything on it.

• 60.3days is the average business-to-business payment period across the EU, against terms that are mostly thirty. EU Payment Observatory, Summary 2025
• 9.85hours a week is what companies report spending chasing late payments, on average. EU Payment Observatory, Summary 2025
• 100bneuros a year in cash flow is what EU small and mid-sized companies are owed late at any one time. EU Payment Observatory, Summary 2025
• 70%of a sales person's time goes on things that are not selling, mostly admin and preparation. Salesforce, State of Sales
• 23%of companies audited in a study of 2,241 of them never responded to an enquiry at all. Follow-up discipline is rarer than anybody assumes. The Short Life of Online Sales Leads, HBR

What it costs

This is sold as one system at the automation price on the services deck, and what moves it is how many things it has to hold together rather than how many hours it takes. The bottom of the range is one CRM, one accounting package, one payment provider and a quote that is mostly the same shape every time. It climbs when every quote is priced from scratch, when there are stage payments or retentions, when two trading entities invoice from the same pipeline, or when the accounting package is old enough that the integration is the project.

Running cost is the payment fees you already pay, messaging billed per message, and a small hosting line. No per-seat licence, which matters more than it sounds: the people who most need to see whether a quote was answered are usually the exact people nobody would buy a seat for.

Outside the build price, as ever, is somebody watching it. That is the care retainer, and on this system it earns its keep faster than on most. A follow-up sequence that quietly stopped firing in March stays invisible until about July, and by then it has cost you more than the whole engagement did.

What goes wrong, and what happens then

Every one of these is in the build because it happens, not because somebody raised it once in a workshop.

• The customer pays and the chase goes out anywayThe single worst failure in the run, and the reason matching runs before any sequence fires rather than on a nightly schedule. Partial payments stop the sequence too and move the record to a different, quieter one.
• They reply to the quote with a question rather than an answerThe reply is read, the sequence pauses, and it goes to a person with the quote attached. A follow-up that arrives after a customer has asked something and had no answer is worse than no follow-up at all.
• The job changed on site and nobody told the officeVariations are captured where the change happens, by whoever is standing there, rather than recalled on Friday. An invoice that does not match the work is the most expensive kind of late payment, because the clock restarts when it is queried.
• The quote was never openedTreated as a delivery failure rather than as a soft no. A short text saying it was sent goes out, and if it is still unopened after that the record is flagged for somebody to ring, because at that point the email address is probably wrong.
• Two accepted quotes want the same slotThe hold-then-confirm step covers it. Without it, this is the failure that eventually happens to everybody who lets a quote acceptance write straight to a calendar.
• A customer goes to twenty-one days every single timeThat is not a chasing problem, it is a terms problem, and the system says so. Repeat offenders surface in the monthly view, which is the conversation about deposits or shorter terms that nobody has because nobody has the list.
• The accounting package rate-limits, or the bank feed stallsRetries with backoff, and a failure raises an alert rather than disappearing. A reconciliation step that stopped running is something you hear about that night rather than discover when the first wrong chase goes out.
• Somebody disputes an invoiceEvery automatic sequence stops on that record immediately and it goes to a person. Automation chasing a customer who is actively unhappy is how a disagreement about 400 euros turns into a lost account.