How Freelancers Can Get Paid Without Chasing Clients

How to Get Paid as a Freelancer Without Awkward Follow-Ups

Nobody starts freelancing because they enjoy writing "just checking in on this invoice" for the third time. But most freelancers end up doing exactly that, not because clients are dishonest, but because payment was never really built into the process - it was left to sort itself out after the work was done.

The fix isn't to become pushy or add legal-sounding clauses to every email. It's to treat payment as part of the job, the same way you'd treat a deadline or a scope document: agree it up front, put it in writing, ask for a deposit where it makes sense, and make the actual act of paying as easy as clicking a link. None of this means every client pays 100% upfront, or that you stop trusting people. Some projects genuinely need milestones. Some corporate clients only run payment cycles on a Thursday. The goal is to stop leaving payment as an afterthought.

This isn't just freelancer folklore, either. GlobeNewswire reported a survey in which 74% of freelance respondents said they weren't being paid on time, and the UK freelancer body, IPSE, has found that more than half of freelancers have dealt with a late-paying client at some point in their careers. If you're tired of chasing money you've already earned, the problem usually isn't you - it's the process.

This guide covers what to change, with real examples for graphic designers, web designers, photographers, tutors and coaches, and creators - plus how PaymentLink.io handles the "make it easy actually to pay" part for all of them.

The short version

If you only take five things from this guide:

1. Agree on scope, fee, payment dates and handover conditions before the work begins - not while it's underway.
2. Ask for a deposit, booking fee or prepaid block wherever it's reasonable to do so.
3. Send a payment request that's itemised, has a due date, and links directly to a payment method.
4. Tie the final files, launch access or the next stage of work to payment actually landing - not to a promise that it's coming.
5. Reminder messages should follow a schedule you've already set, not the mood you're in on a given Tuesday.

The "make it easy to pay" part is where a tool like PaymentLink.io earns its keep. You can send a branded payment link by email, WhatsApp, SMS, or messenger, or set up a dedicated payment page so a client always has one place to return to. It's built on Stripe, so clients can pay by card, Apple Pay, or Google Pay wherever Stripe is supported.

Why freelancers end up chasing payment in the first place

Late payment rarely starts on the due date. It starts earlier - usually the moment both sides quietly assume the payment side of things will work itself out.

The client agreed to the work, not to a payment process. Someone can say yes to a website, a logo, a content package or a consultation without ever thinking through who signs off the invoice, whether a purchase order is required, or whether their bookkeeper only processes payments on Fridays. If you don't ask, you tend to find out the hard way - after you've delivered.

The terms sound fine, but don't actually mean anything. "Payment due on completion" feels reasonable until you realise nobody agreed what "completion" means. The first draft? The final one? After sign-off, or after their manager also has a look? Vague terms don't need to be replaced with legal jargon - they need one specific sentence, such as "50% is due before work starts, the final 50% before final files are released", or "Retainer is due on the 1st of each month; work for that month starts once payment clears." (For anything with real legal weight, that's a conversation for a qualified professional in your country, not a blog post - but the underlying point holds: vague terms are where late payment lives.)

The payment request itself is easy to ignore. A PDF buried at the bottom of a long email disappears fast. A bank transfer means the client has to copy a sort code, an account number, and a reference from somewhere. A payment mentioned mid-way through a WhatsApp thread gets pushed out of view by the next notification. Most of the time, this isn't a client dodging you - it's a client who's disorganised or simply unclear on what to do next. You're still owed the money, but it helps enormously to remove every excuse for not paying.

The freelancer hands over the finished work before being paid. This is the one that stings most. Files get sent, a site goes live, a gallery gets delivered - and only then does the freelancer find out whether the client actually intends to pay. For a trusted, repeat client, that risk might be fine. For a new client or a one-off project, it's a bet you don't need to be making. Sharing previews, drafts or a staging link during the project, then releasing the finished work after payment, removes that bet entirely.

And sometimes it's simply that asking for money feels awkward. Plenty of freelancers water down every payment message until it barely registers as a request at all - "just a gentle nudge whenever you get a chance" gives the client precisely zero reason to prioritise it. Being professional doesn't mean being apologetic. A calm, predictable payment process is usually better for the relationship, because both sides know exactly what to expect.

Ask about payment before you send the proposal.

Most freelancers are thorough about qualifying the project - scope, deadline, deliverables, budget - and far less thorough about qualifying how they'll actually get paid for it. A short set of questions before you quote saves a lot of chasing later:

• Who approves payment on your end?
• Do you need me to set up as a supplier, or is a purchase order required first?
• How do you prefer to pay - card, transfer, or something else?
• Can the deposit be paid before I start?
• What payment terms does your accounts department usually run on?
• Should the payment request go to you directly or to someone in finance?

This isn't an awkward conversation - it signals you run things properly. A small client might say, "Send me the link, I'll pay by card." A larger one might reveal something worth knowing early: "We need you set up as a supplier first", or "invoices are only paid on Thursdays." Either answer is more useful discovered now than after delivery.

Put your payment terms in plain English.

Terms don't need to sound aggressive. They need to be specific enough that nobody can misread them. At a minimum, confirm the total fee, the deposit amount, the due dates, the accepted payment methods, what's included in scope, what happens if scope changes, when final files or access are released, and what happens if payment is late.

A fixed-fee project might read: "The project fee is £1,800. A 50% deposit (£900) is due before work begins. The remaining 50% is due after final approval and before final files are released. Anything outside the agreed scope will be quoted separately before it starts."

For hourly work: "I bill in blocks of 10 prepaid hours. Once a block is used, I'll send a summary of completed work, and we'll agree on the next block before continuing."

For a retainer: "Retainer payment is due on the 1st of each month, covering the deliverables listed below. Work for the month begins once payment is received."

And for a one-off session: "Payment is due at the time of booking - your slot is confirmed once payment is received."

None of this replaces a proper contract or a statement of work where one's needed. It just means both sides understand the commercial agreement before anyone starts working.

Ask for a deposit - it's less awkward than it feels.

A lot of freelancers know they should ask for money up front and talk themselves out of it, worried the client will say no. Some will - and that's genuinely useful information about that client, not a reason to stop asking. A client who's serious about the work will usually understand the need for a deposit, particularly for creative, strategic, or time-blocked services. They might negotiate the percentage or need a purchase order first, but the request itself rarely surprises anyone running a real business. There's a side benefit too: once a client has paid something, they tend to send assets faster, show up to calls, and treat the project as real rather than provisional.

The right deposit model depends on the work:

• 50% upfront, 50% before final handover suits logo design, brand identity, website builds, copywriting packages and fixed-scope consulting.
• 30/40/30 split across milestones works better for larger web builds, campaigns or multi-stage creative projects.
• A booking fee plus a balance later applies to photographers, tutors, coaches and trainers reserving a date or session.
• Prepaid blocks of hours suit hourly work where the total hours are hard to predict up front.
• A monthly retainer paid at the start of the month is ideal for ongoing social, content, maintenance, or design support work.

A simple, direct message covers this well: "Great, I'm excited to get started. I've attached the project summary and payment terms. To reserve the slot, the 50% deposit is due before work begins. You can pay securely here: [link]. Once that's received, I'll schedule the kickoff and send next steps." It doesn't read as a favour being asked. It reads like your normal process, because it is one.

With PaymentLink.io, that deposit request is a payment link you can build in a couple of minutes - itemised, branded, and sent straight to the client by email or WhatsApp. A designer, for example, might create "Brand Identity Deposit – 50%" as a line item and send the link the moment the proposal is accepted. See the walkthrough for graphic designers getting paid online.

Make the actual payment request impossible to misread

A client should never have to reply asking how to pay you. A good payment request states the client's name, the project, what the payment covers, the amount, the due date, a working payment link, a reference number if you use one, and what happens once payment lands. Something like:

"Payment request: Website refresh deposit - Amount: £750 - Covers: 50% deposit for homepage redesign, service page redesign and mobile layout update - Due: before kickoff - Pay here: [link] - Next step: once paid, I'll send the kickoff questionnaire and book our planning call."

That's a meaningfully clearer request than "invoice attached," because there's exactly one obvious action for the client to take. A payment link helps here specifically because the call to action is unambiguous - the client clicks, checks the amount, and pays, without hunting for bank details or asking you to resend anything.

That said, a payment link doesn't have to replace an invoice for clients who need one for their own accounts. In practice, they work better together: the invoice gives the client a formal record, and the payment link is the fastest route to settling it. More on that below - but it's worth flagging early, because a lot of freelancers wrongly assume they have to pick one.

Separate "the client can look at it" from "the client has it"

This single change removes a surprising amount of chasing. It's easy to conflate "the client can review the work" with "the client now has everything," but they should be two distinct stages of delivery.

During review, the client sees whatever's appropriate for the work: watermarked designs, low-res images, a staging site, a PDF preview, a Loom walkthrough, a comment-only doc, or a demo with restricted access. Final handover - high-res files, editable source files, site migration, admin access, the finished strategy document - happens after final payment, not before it. A clean way to say this: "Once you approve the final preview, I'll send the balance payment link. Final files are released once the balance is received." It doesn't punish anyone. It just connects payment to delivery the way it should have been connected all along.

This is especially relevant for web work, where a freelancer can gather feedback and make revisions entirely on staging, and only launch or hand over access once the final payment clears.

Use milestones on bigger projects.

A single invoice at the very end of a large project means the unpaid balance keeps growing as the work does - which is exactly the wrong direction for your risk exposure. Milestones fix that by giving the client clear, understandable checkpoints instead. A web designer might split a project 40% to start, 30% after design approval, 30% before launch. A brand designer might run 50/25/25 across deposit, concept approval and final artwork. A copywriter might use a 50% deposit, 25% after the first draft, and 25% before the final handover.

The trick is anchoring milestones to moments the client actually understands - "after homepage wireframe approval" or "before final logo files are released," not something vague like "phase two payment." PaymentLink.io lets you create a separate, clearly labelled payment link for each stage, or point clients to a branded payment page if you'd rather have one permanent place for ad hoc balances and retainers.

Turn ongoing work into something with a clear payment trigger.

Ongoing freelance relationships have a specific way of quietly going wrong. The first project goes well, then a client starts sending small extra tasks. A few hours become a few more. You keep helping because the relationship's good - and by the end of the month, there's a messy pile of unbilled work and no obvious moment when payment was supposed to happen. This shows up constantly in design support, social posting, website tweaks, content edits, VA work and coaching.

The fix is to package the work rather than let it stay loose. Prepaid hours work well when the total time is genuinely hard to predict - sell a block of 5, 10 or 20 hours, and flag it as it runs low ("your 10-hour block is at 8.5 hours used - want me to send the next link so support doesn't pause?"). A monthly retainer suits anything with a defined, repeatable scope: "Monthly website maintenance retainer - £350, includes plugin updates, minor content changes and up to 2 hours of support; anything beyond that is quoted separately." And fixed-price packages - a 60-minute strategy call, a landing page audit, five social graphics, a single tutoring session - work particularly well listed on a PaymentLink.io micro e-commerce page, so a client can pick the service and pay, without you having to build a fresh request every time.

Fit the payment method to the client, not just to yourself

There isn't one best way to get paid as a freelancer - it depends on who's paying you. Bank transfer suits larger local clients with an accounts team. A card payment link is usually faster for individuals, small businesses and international clients. A marketplace client will pay through that platform's own system, whether you like it or not. The real question is: which method allows this particular client to pay me on time without creating additional risk for my business?

PaymentLink.io is strongest in that middle ground - a branded payment experience without building a checkout from scratch. You connect your own Stripe account, build a branded request or page, and send the link. Standard Stripe/payment gateway fees still apply, and it isn't accounting software, but it makes the actual payment step considerably clearer for the client. The full list of what's available is on the key features page.

Build your reminder schedule before you need it.

Reminders feel far more awkward when you're inventing them under pressure. Decide the schedule once, then reuse it every time: a friendly nudge three days before the due date, a short note on the day itself, a polite follow-up at three days overdue, a firmer message with a pause on further work at seven days, and a final reminder before escalation at fourteen. Not every client relationship needs all five stages, and some will need a tighter cadence - the point is to have a plan rather than decide the tone in the moment.

The tone that works best stays calm and short throughout, without turning into either an apology or an accusation:

Before due date: "Just a reminder that the balance for [Project] is due on [Date]. You can pay securely here: [link]. Once received, I'll prepare the final handover."

On due date: "The payment for [Project] is due today. Here's the link again for convenience: [link]. Let me know if your accounts team needs anything else from me."

Overdue, polite: "I can see payment for [Project] is now overdue - could you confirm when this will be settled? Link here: [link]."

Overdue, firmer: "This payment is now [X] days overdue. As agreed, I'll need to pause further work until the balance is settled. You can pay here: [link]."

No drama, no long explanation, no apology for asking - just a consistent, predictable process that both sides can rely on.

Make the payment link part of how you normally work, not something bolted on

The best version of this doesn't feel like a separate admin task - it feels like part of working with you. 

• Proposal accepted → deposit link sent.
• Deposit paid → kickoff booked.
• Milestone approved → next request sent.
• Final preview approved → balance link sent.
• Payment received → files released.

That rhythm trains clients to expect the payment step at each stage, which is exactly what stops it from feeling awkward on either side.

For repeat clients, a permanent branded payment page removes another layer of admin entirely. Instead of creating a new link for each small balance, they go to one page, enter the amount and reference, and pay. Useful for maintenance work, small top-ups, and the clients who periodically ask, "Where do I pay you again?"

What this looks like for different types of freelancers

Graphic designers - a £1,200 brand identity package might be split into £600 before concept work starts, £300 after concept approval, and £300 before final logo files, guidelines and source files go out. The client reviews watermarked previews at each stage; vector files are released only once the balance clears. (See: payment links for graphic designers.)

Web designers and developers: a £3,000 build might cost £1,200 to reserve the slot, £900 after design approval, £900 before launch, or transfer. Feedback and revisions are available freely on staging; admin access and file transfers are pending the final payment. (See: get paid as a web designer.)

Photographers - a booking fee reserves the date; the balance is due before the shoot or before gallery release; and separate links handle prints, albums, or extra edits. That structure avoids the classic trap of delivering a full gallery and then waiting weeks to be paid for it. (See: payment links for photographers.)

Social media managers - a monthly retainer due on the 1st, clearly described ("March retainer - 12 feed posts, 8 stories, monthly calendar and reporting"), with scheduling paused if payment doesn't land. That's firm, but fair - you're not a bank. (See: payment links for social media agencies.)

Consultants and coaches: strategy calls paid at booking; audits paid before delivery; workshop deposits to hold the date; balance due before the report or slides go out. Fixed-price offers suit a micro e-commerce page; bespoke work is better as a custom request.

Tutors, trainers, and instructors - session-based work is exactly where small, forgettable payments pile up. A link before the lesson, a package of sessions sold up front, or a QR code for in-person payment all remove that. (See: payment links for tutors and payment links for personal trainers.)

Creators and influencers - sponsored work can run on milestones tied to campaign approval and publication: 50% to book the slot, 50% before raw files or usage rights are released. State the deliverables plainly - platform, post count, usage period, revisions, and fee. (See: payment links for influencers.)

Changing your terms with an existing client

New clients are easy to set terms with. Existing ones feel trickier, especially if slow payment has quietly become normal over several months. Do it calmly, and give a bit of notice rather than springing it on the next invoice:

"I'm making a small update to my payment process from [date], to keep project scheduling and handovers more reliable. Going forward, new work requires the agreed-upon deposit to be paid before I start, and final files go out once the balance is settled. For ongoing work, payment is due at the start of each month. I've genuinely enjoyed working together, and this should help keep turnaround times consistent."

There's no need to frame it as an accusation - it's a process change, not a complaint. If a client pushes back, ask what specifically is difficult; often it's not the payment itself but the timing or their internal admin, and you can adjust the date or route the request straight to finance. But a client who refuses reasonable terms outright is telling you something worth listening to.

Payment link or invoice? Most freelancers need both.

Plenty of freelancers still need to issue proper invoices, and that's completely normal - it doesn't conflict with using payment links. The invoice gives the client their formal record; the payment link gives them the fastest route to actually paying it; the payment confirmation gives you both evidence it happened. In practice, this might be one line in your email: "I've attached the invoice for your records - you can pay securely by card here: [link]." That's usually a smoother experience than pushing every client to use a manual bank transfer, particularly for smaller or remote clients.

A payment link tends to earn its place when the price is already agreed, the amount is fixed or clearly itemised, the client's happy to pay by card, you're collecting a deposit, or the work is a session, package or small service that doesn't need a drawn-out procurement process. A £250 landing page audit rarely needs a full checkout flow - a clear request is enough. A traditional invoice still matters more when a client needs formal purchase-order matching, the work sits inside a corporate procurement process, payment terms are contractually fixed, or a specific invoice format is required for tax reasons.

The strongest setup, in most cases, is simply both proper records behind the scenes and an easy, obvious action for the client to take. Learn more about the payment link or invoice.

How PaymentLink.io actually removes the chasing

Everything above is process - the part you control, regardless of which tools you use. PaymentLink.io is built specifically to handle the one piece that's hardest to get right on your own: turning "please pay me" into a clear, branded, one-click action, every single time.

Connect your own Stripe account, and you can build an itemised payment request in a couple of minutes, send it by email, WhatsApp, SMS, messenger or social DM, and let the client pay by card, Apple Pay or Google Pay wherever Stripe supports it. Every link is branded to look like it came from you, not from a generic payment provider - which matters more than it sounds, because clients are noticeably more willing to enter card details somewhere that clearly belongs to the freelancer they're already working with.

There's a detail that solves a lot of what this guide has been about: every payment link you create on PaymentLink.io is generated as a proper invoice at the same time - itemised, with a reference number, customer details and all. Once the client pays, they can download that invoice directly, without ever having to ask you for one. You get your record. They get theirs. Nobody has to remember to build the paperwork separately, and there's no invoice-and-payment-link mismatch to worry about later.

For clients who pay you repeatedly, a dedicated payment page gives them a single permanent place to go, rather than a new link each time. For fixed-price services - a call, an audit, a single tutoring session - the micro e-commerce page lets a client pick and pay without you building a custom request from scratch. For anything collected face-to-face, QR code payment covers it. And everything shows up in one dashboard, so you can see at a glance what's been paid and what's still outstanding, rather than reconstructing it from an inbox search.

It isn't a bank, a payment processor in its own right, or accounting software - Stripe handles the actual movement of money, and PaymentLink.io is the branded layer that sits on top and makes the request itself unmistakable. But that layer is exactly where most freelancer payment problems live: not in whether the client can pay, but in whether they know precisely how to, right now, in one click.

Worth a look, depending on what's causing you the most friction today:

• Deposits and balances → Send a Payment Link
• One permanent place for repeat clients → Your Own Payment Link Page
• Fixed-price services → Micro E-commerce
• In-person payment → QR Code Payment
• Comparing plans → PaymentLink.io pricing

Mistakes that quietly keep freelancers chasing

A handful of habits cause most of the trouble here. Mentioning payment for the first time after delivery, rather than before work starts. Using "ASAP" as if it were a due date, instead of a real one. Writing invoice line items so vague ("Design work - £500") that nobody can tell what they're paying for. Not asking early who actually handles payment, since the person approving the work often isn't the person authorising the spend and letting scope creep sneak in without pausing to confirm the extra cost first. Releasing final files before payment lands, especially with a new or historically slow-paying client and changing your terms with an existing client without any explanation at all. And, more than anything, staying too embarrassed to follow up on money you've genuinely earned - you're not asking for a favour, you're asking for what was agreed.

A workflow you can copy for your next project

Before the proposal, ask who handles payment, whether a PO is needed, and whether the deposit can be paid before you start. In the proposal itself, spell out scope, deliverables, timeline, fee, deposit, milestones, revision limits, due dates and handover conditions. Once it's accepted, send a short thank-you, the project summary, the deposit link, and what happens next. During the project, keep track of what's been delivered, revisions used, any scope changes, and the next payment trigger. Before final handover, send the preview, the balance link, and a reminder that files follow payment. After payment, send the receipt, the final files or access, and a thank-you. And for repeat clients, periodically check whether they're paying on time, whether they should move to prepaid hours or a retainer, and whether invoices should go straight to their finance contact. That's the difference between payment being a workflow and payment being a recurring emotional task.

Ready-to-use templates

Deposit request - "Thanks for confirming the project. To reserve the slot and start work, the deposit of [amount] is due before we begin. You can pay securely here: [link]. Once received, I'll send kickoff details and next steps."

Milestone payment - "We've reached the [milestone] stage for [project]. The next payment of [amount] is due before we move into [next stage]. Link: [link]. Once received, I'll continue with [next deliverable]."

Final balance - "Glad the final preview is approved. The remaining balance of [amount] is now due before I release the final files. Pay here: [link]. Once received, I'll send the files and handover notes."

Friendly overdue reminder - "Just checking in on the payment for [project], due on [date]. Here's the link again for convenience: [link]. Could you confirm when this will be settled?"

Firmer overdue reminder - "The payment for [project] is now [X] days overdue. As agreed, I'll need to pause further work until it's settled. Link: [link]. Please confirm once arranged."

Accounts follow-up - "Following up on payment request [reference] for [project], sent on [date] and due [due date]. Could you confirm whether it's been approved, or whether you need anything further from me? Link: [link]."

The real point: fewer awkward conversations, not perfect clients

None of this guarantees that every client pays instantly. What it does is remove most of the loose ends - the "did you see my invoice?" emails, the bank details copied out of an old thread, the projects where the client has the finished work, and you have the anxiety. A proper payment process protects both sides: the client knows exactly what to pay and when, and you know exactly when work starts, when milestones are reached, and when handover occurs. That's what makes you look professional. More usefully, it gives you back the time and headspace freelancing was supposed to buy you in the first place.

If your current process is closer to "send invoice, hope, follow up, feel awkward, repeat," it's worth changing one thing at a time rather than all at once - start with the next deposit you ask for. Create your first payment link with PaymentLink.io and see what a client actually clicking "pay" feels like, instead of waiting on a bank transfer that may or may not show up.