The most patient lender in town is you
Finish a job for a service business and something strange happens to the money: it stops moving. The work was fast — same-day, sometimes same-hour. The payment is not. It's "in the mail." It's "on the counter, I'll get to it." It's a check that will clear, eventually, after a stamp and a mailbox and a bank hold. And in the gap between work delivered and money received, the business is doing something it never agreed to: extending its customers an interest-free loan.
That gap has a name and a number. It's days-to-payment, and for a service business running on paper invoices and check promises, it's often measured in weeks. Meanwhile the payroll runs on Friday whether the check arrived or not. The supplier wants their money on their terms, not the customer's. Cash — not profit, cash — is what keeps the doors open, and slow collection is a cash problem wearing a paperwork costume.
As of July 2026, the fix is well understood and unglamorous: shorten the distance between finishing the job and getting paid. This guide is about that distance. It treats days-to-payment as the cash-flow metric it actually is, explains why payment links collect faster than mailed invoices and "I'll send a check," covers collecting on site and by text across three payment providers, and gets honest about chargeback defense — because getting paid fast only matters if the money stays paid. This is deliberately not a guide about bookkeeping; how those payments then flow into your accounting is a separate discipline covered in the companion piece on QuickBooks sync. Here, the single subject is speed of collection.
Days-to-payment: the metric hiding in plain sight
Most owners track revenue and, if they're diligent, profit. Far fewer track the one number that determines whether they can make payroll this week: how long their money spends in someone else's pocket after the work is done.
Days-to-payment is the average lag between job completion and cleared funds. It's simple to reason about and brutal in aggregate. If you finish $40,000 of work a month and your average days-to-payment is 21, then at any given moment you have roughly three weeks of billings — a substantial sum — floating out in the world as unpaid promises. That float is money you earned but can't use. It's why a profitable business can still feel broke, and why "we're doing great, why is the account always empty?" is one of the most common and most demoralizing questions in the trades.
The insight that changes behavior is this: shrinking days-to-payment is functionally the same as a cash injection, and it costs nothing. Cut your average from 21 days to 2 and you've pulled nearly three weeks of billings forward into your account, permanently, without landing a single new job or raising a single price. No financing, no new marketing spend — just closing the gap you were tolerating. Few growth levers are that cheap.
Every step in the traditional collection process adds days to the number:
- The invoice has to be created — often later, at the shop, from notes.
- It has to be delivered — printed and mailed, or emailed into an inbox that treats it like the rest of the inbox.
- It has to be noticed by a customer whose motivation to pay drops a little every day the job recedes into the past.
- It has to be acted on — a check written, an envelope found, a stamp, a mailbox.
- It has to clear.
Each of those is a place where days accumulate and where some invoices quietly fall out of the pipe entirely and become write-offs. The entire premise of faster collection is to delete as many of those steps as possible — ideally, to collect while the customer is still standing in the driveway.
Why "I'll mail a check" is the enemy of cash flow
The mailed check isn't just slow; it's slow in the specific ways that hurt most.
It collects at the moment of lowest motivation. The willingness to pay for a service peaks at completion — the relief of a working AC unit, an opened door, a fixed leak is visceral and immediate. Every day after, that feeling fades and the bill competes with everything else in the customer's life. A collection method that introduces a multi-day delay is deliberately waiting for the customer's enthusiasm to cool. Payment links do the opposite: they present the ask at the exact peak.
It creates follow-up labor. Unpaid mailed invoices don't collect themselves; someone has to notice the aging, send the reminder, make the awkward call. That's payroll spent chasing money you already earned — a pure-loss activity that a same-day collection largely eliminates.
It leaks. Some percentage of mailed invoices are never paid at all — forgotten, lost, disputed into oblivion, or simply outlasted by the customer's attention. Every collection step you remove removes a place for revenue to leak out.
It's a worse experience for the customer, too. This is the part owners underestimate. Modern customers, especially anyone under fifty, largely expect to tap and be done. The Pew Research Center documents just how completely the smartphone has become the default way people transact; a business that insists on paper is imposing friction the customer didn't want and won't thank them for. Convenient payment isn't a concession to the customer — it's better for both sides at once, which is why it's rare that faster-for-you and easier-for-them line up so cleanly.
Collecting on site and by text
If days-to-payment is the metric, on-site and same-day collection is the method. There are two dominant patterns, and a good stack does both.
Tap-to-pay on site
The tech finishes, builds the invoice in the POS from the same job and customer already in the system, and the customer pays right there — card tapped, done. Funds are captured before the tech leaves. Days-to-payment for that job: zero. This is the gold standard, and it's available on any job where the decision-maker is present at completion. Because the invoice is built from the existing CRM record rather than re-created from scratch, there's no friction between "done" and "paid" — which is the same integrated-record logic that makes multi-tech dispatch work.
The texted payment link
Not every job ends with the payer standing there. The homeowner is at work, the property manager approves remotely, the decision-maker is a spouse who'll "handle the bill." For all of these, the payment link is the tool: a link to the specific invoice, texted to the customer's phone, that opens to a clean pay screen they can complete in seconds from wherever they are.
The link's power is context. Sent from the business the customer just dealt with, tied to the job they're expecting to pay for, showing the amount they anticipated, it arrives as a welcome convenience rather than an interruption. That context is also the trust mechanism — customers complete links that obviously belong to a transaction they're part of, and hesitate only when a link feels unexpected or generic. The practice, then, is to send it in the moment: right after the work, while the job is fresh, ideally before the tech has pulled away.
This pairs naturally with the same texting muscle behind missed-call text-back and appointment reminders — the customer is already receiving useful texts from the business, so the payment link lands in an established, trusted thread rather than out of nowhere.
Run with Jarvis handles both patterns through the IntelliDrive invoicing and payment-links layer, and it does so across three payment providers — which matters for a practical reason.
Three payment providers, and why the choice is yours
Payment processing is not one-size-fits-all. Businesses land on different processors for real reasons: the rate they were quoted, the provider their bank plays nicely with, an existing account they don't want to abandon, the deposit timing that fits their cash cycle, or simply what they already trust. A payments layer that locks you to a single processor forces a compromise on all of that.
Supporting three payment providers means the collection tooling adapts to your processing setup rather than dictating it. The payment link, the on-site tap, the invoice — all the same from your side and the customer's — while the money settles through the provider that fits your business. One important honesty note: the per-transaction processing fees are set by whichever provider you choose, not by Run with Jarvis. The platform gives you the fast collection mechanism and the choice of rail; the rail's rates are between you and the processor. What you're not paying is a separate "payments module" fee — collection, across all three providers, is included from the Core plan at $500/month.
The deeper benefit of provider choice is that it removes a common excuse to not modernize collection. Owners frequently stay on slow, paper-based billing because switching payment tools felt like it meant switching processors — renegotiating rates, moving an account, retraining the office. When the collection layer sits on top of the processor you already use, that barrier disappears: you keep your rail and your rates, and only the speed of collection changes. The customer taps a link; the money lands in the same account it always did, just weeks sooner. Nothing about your banking relationship has to move for your days-to-payment to fall, which is precisely why the choice being yours matters more than which specific providers are on the list.
Paper invoice vs. payment link: the collection comparison
The two approaches diverge on every dimension that touches cash flow. This is the comparison that matters for the money in your account.
| Dimension | Paper invoice / "mail a check" | Payment link (on site or by text) |
|---|---|---|
| Typical days-to-payment | Two to four weeks | Same visit to same day |
| Moment of collection | Days later, motivation fading | At completion, satisfaction peak |
| Follow-up labor | Reminders, aging, awkward calls | Little to none — paid at the ask |
| Customer effort | Find checkbook, stamp, mailbox | Tap a link on their phone |
| Leakage / write-off risk | Meaningful — invoices get lost | Low — collected before the job cools |
| Customer experience | Friction the customer didn't want | The convenience they already expect |
| Works when payer is remote | Poorly — slower still | Yes — the texted link's core use case |
The row that quietly matters most is moment of collection. Everything else follows from it. Collect at the satisfaction peak and the follow-up labor, the leakage, and the multi-week lag all shrink together, because you removed the interval in which they all accumulate.
Getting paid fast is only half the job: chargeback defense
Speed of collection is worth little if the money doesn't stay collected. Card payments — the very thing that makes fast collection possible — come with a specific risk: the chargeback. A customer disputes a charge with their bank, and the funds can be pulled back out of your account, sometimes for work you genuinely and completely performed.
Some chargebacks are legitimate fraud protection. Others are what the industry bluntly calls "friendly fraud" — a customer who forgot the charge, had buyer's remorse, or realized a dispute is an easy way to try to get the work for free. Either way, the business that can't produce documentation loses by default. The bank sides with its cardholder unless you give it a reason not to.
Chargeback defense is the discipline of capturing that reason at the time of payment, so a dispute becomes a case you can win rather than an automatic loss. The materials that win disputes are concrete: proof the service was authorized, proof it was delivered, the job details, the payment record, and — where captured — a signed authorization tying the cardholder to the charge. A business that gathers these systematically, as part of how it collects, turns chargebacks from a silent drain into a defensible line item.
Run with Jarvis builds chargeback defense into the same IntelliDrive layer that generates the payment links, which is the right place for it: the moment you collect is the moment to capture the proof, and having both in one system means the defense record assembles itself from the transaction rather than being reconstructed after a dispute lands. This isn't a promise that you'll win every dispute — no one can honestly promise that, and card-network rules ultimately govern the outcome; consumer protection around payments is overseen federally by the FTC (ftc.gov). It's that you'll walk into each dispute with evidence instead of empty hands. Fast collection gets the money in; chargeback defense keeps it there. You want both, from the same system, or the first one is only half a win.
Putting it together: a collection system, not a collection habit
The reason collection stays slow in so many businesses isn't that owners don't know mailed checks are slow. They know. It stays slow because faster collection depends on things upstream being connected — and when they're disconnected, the fast path is too much friction to sustain job after job.
Think about what has to be true to text a payment link before the tech leaves the driveway. The customer has to already exist as a record. The invoice has to be buildable on the spot from the job that was just booked and completed. The link has to send from the business's own number. The payment has to attach back to the right invoice. Do all of that with four disconnected tools and it's a chore no crew will keep up. Do it in one connected system and it's a single tap at the end of every job — which is exactly the all-in-one versus point-solution argument, viewed from the cash-flow angle.
That's the shift worth internalizing: getting paid faster is not a willpower problem or a reminder-to-send-invoices problem. It's a system-design problem. Build the collection into the flow of the job — booked, done, paid, defended, all on one thread — and days-to-payment falls not because anyone tried harder, but because the slow path stopped being the default. And once the money is collected and defended, feeding it cleanly into your books is the natural next link in the chain, which is where the QuickBooks sync workflow picks up.
The bottom line
Every service business is, without meaning to be, a lender. The only question is the term of the loan. "I'll mail a check" writes a three-week note in the customer's favor, unpaid interest, renewed every single job. A payment link tears the note up and collects at the moment the customer is happiest to pay.
Days-to-payment is the number that tells you which business you're running. Drive it toward zero — collect on site, text the link in the moment, offer the provider that fits, and capture the proof that keeps the money yours — and you free up weeks of your own billings without earning a dollar of new work. The job was always fast. It's time the payment was, too.
Related reading: Read the companion guide on QuickBooks bidirectional sync for where the money goes after you collect it, see what AI operations actually cost in 2026, and learn why connected platforms beat point solutions. When you're ready to shorten your own days-to-payment, get in touch or compare plans on the pricing page.
