Let's be honest about how most custom freelance work gets arranged in Nigeria right now. A client finds you, either through a referral, Instagram, or a WhatsApp group. You have a back-and-forth about what they need. You quote them a price. They agree. You ask for something upfront. They send half, or a third, or nothing at all depending on how much they like you. You do the work. You send it. And then you wait.

Sometimes they pay immediately. Sometimes they take a week. Sometimes they disappear entirely. And sometimes they come back with a long list of revisions they didn't mention before, and the implied message underneath all of it is: keep doing this until I decide to pay, or don't get paid.

This isn't bad luck. It's what happens when the payment system has no structure. The client holds all the leverage after delivery, and you held all the risk during the project. That's the real problem. Not bad clients. Just a broken arrangement.

Why custom projects are different from selling digital products

When you sell an ebook or a template on a platform, the transaction is simple. Customer pays, file delivers, done. There's nothing to argue about. The product exists before the sale. You made it once and it goes to whoever buys it.

Custom work is the opposite. You're making something that doesn't exist yet, specifically for this one person, based on a brief that was probably agreed in a voice note or a chat thread somewhere. The scope can drift. The client's taste can change. Their communication goes from responsive to silent to responsive again at 11pm on a Sunday. And at the end of all that, you're still waiting for the money to arrive before you can feel like it actually happened.

Custom projects are higher value, more emotionally involved, and structurally much harder to protect with a simple payment link. They need something more deliberate.

The core problem with custom work: the thing you're selling doesn't exist until you build it, which means the client can keep changing their mind until it does. Without a clear agreement locked in at the start, every revision request is really a renegotiation, and the person with the most leverage is whoever controls the money.

What escrow actually does for a custom project

Most freelancers have heard of escrow in the context of property purchases, where a neutral party holds the money while the deal completes. The same logic applies here, and it solves a very specific problem: both sides want to go first, and neither should have to.

Without escrow, you're choosing between two bad options. You work first and hope they pay, which is a bet on their character. Or you insist on full payment upfront, which is a bet on your character, and many clients won't take that bet with someone they just met online.

Escrow is neither of those things. The client pays in full before the project starts, but they don't pay you directly. The money goes into escrow, held by Kreddlo. You can see it's there. They can see where it went. Nobody has it until the work is confirmed. Then it releases to you.

The client hasn't handed money to a stranger. You haven't started working with nothing to show for it. The standoff is gone, because escrow removes the reason for it.

How a Kreddlo custom project actually runs

Here's the actual sequence, from first contact to final payment. No jargon, no theory. Just how it works.

1

You agree on scope and price

Before anything is created, you and the client settle on exactly what's being made, what the deliverables are, and what the total cost is. This is the brief. It goes into the project.

2

Client funds the escrow

The client pays the full agreed amount into Kreddlo escrow before any work begins. You receive a notification that the funds are secured. That's your green light.

3

You do the work

You work knowing you're already paid in principle. No more chasing. No more "just checking in" messages. The money exists. It's waiting for you to deliver.

4

You submit delivery

When the work is done, you submit through the platform. Files, links, notes, everything goes through the project record, so there's a documented trail of what was delivered and when.

5

Client reviews and confirms

The client has a set window to review the delivery. If they're happy, they confirm. The funds release to your Kreddlo balance immediately.

6

Dispute resolution if needed

If there's a genuine disagreement about whether the work matches the agreed scope, either party can raise a dispute. Kreddlo reviews the project record and mediates. Nobody just loses the money.

The contract layer: scope creep has nowhere to hide

One of the quieter things that kills custom freelance projects isn't non-payment. It's scope creep that wears you down until you're doing three times the original project for the same fee, because you never wrote down what the original project actually was.

Kreddlo's custom project flow requires a written scope before funding. What's included. What's not. How many revisions. What the deliverable format is. This isn't paperwork for the sake of it. It's the document that determines whether a client's request for "just one more change" is reasonable feedback or a new project.

When you have a signed project scope and escrowed funds, the conversation changes. "Can you just add a dark mode version?" becomes something you can answer honestly: "That's not in the original scope, but I can quote you for it." The scope document is your proof of what was agreed. It removes the awkwardness, because the answer isn't opinion. It's right there in writing.

Without written scope: every client request is subjective. You think you delivered. They think you didn't. Nobody has anything in writing. The dispute goes nowhere, and whoever is more stubborn wins. Usually not you.

What happens when the client doesn't confirm?

This is the question everyone wants answered. You delivered the work. The client has gone quiet. What happens to the money?

First, Kreddlo sends the client reminders. Most delays aren't malicious. People get busy, get distracted, or just don't think about it. A prompt usually moves things along.

If the client still doesn't respond within the review window, the delivery is treated as accepted and the funds release. The silence can't be used as a weapon to hold your money indefinitely. Either they review and confirm, or time runs and you get paid anyway.

If they raise a dispute before the window closes, that triggers the mediation process. Both sides present their case. Kreddlo looks at the project scope, the delivery submission, and the communication record, and makes a decision. The money doesn't just disappear. It goes somewhere based on who was right.

Real scenarios: what this looks like in practice

Without escrow

You design a brand identity. Client loves it, posts it everywhere, then claims they can't pay right now. Two months later you've sent 14 follow-up messages, threatened nothing because you have no leverage, and mentally written off the income. The work is live. You have nothing.

With Kreddlo escrow

You design the same brand identity. Client funded the escrow before you started. You submit delivery. They confirm within 48 hours because the money is already moved, and they want the files officially. Funds release. Conversation over.

Without escrow

A client hires you to build a website for 150,000 naira. You ask for 50% upfront. They send 70,000 and you start. Halfway through, they expand the scope to include an e-commerce section they "forgot to mention." You deliver. They say the site "isn't quite what they imagined" and refuse the remaining balance. You have a half-finished site on their domain and 70k in hand.

With Kreddlo escrow

Same web project. The scope is written before anything starts: five pages, contact form, no e-commerce. Client funds 150,000 into escrow. When they request the e-commerce section midway, you point to the agreed scope and quote separately. You deliver exactly what was agreed. Funds release. Extra work is a new project with new payment.

Who this is actually for

Escrow-backed projects on Kreddlo work best for any freelance work where:

  • The output is custom-made (not a pre-existing product)
  • The project takes more than a day to complete
  • The fee is large enough to hurt if it doesn't arrive
  • The client is someone you haven't worked with before
  • The brief has any room for interpretation

In practice that covers most serious freelance work. Logo design. Web development. App builds. Copywriting projects. Social media management retainers. Video editing. Architecture drawings. Consulting engagements. If you're making something for a specific person for a specific fee, escrow is the right container for it.

The thing no one wants to say out loud

Here's the uncomfortable truth that sits underneath all of this: most clients who don't pay aren't bad people. They're people who were never given a reason to treat the transaction seriously.

When a client pays via bank transfer with no paper trail, no deadline, no formal agreement, there's an easy psychological off-ramp. The work wasn't "official." The project was casual. They meant to pay eventually. The freelancer will understand.

The moment funds go into escrow, the transaction becomes real in a way that informal arrangements never are. The money moved. There's a project record. There's a delivery submission with a date on it. Confirmation is a button they need to click. That's not paranoia or distrust. It's structure. And structure, not goodwill, is what gets people paid.

The thing escrow actually does for your client relationship: it removes the money conversation from the project relationship entirely. They don't have to feel chased. You don't have to feel like you're begging. The system handles it. You both just do the work.

If you're a buyer reading this

Escrow isn't just for freelancers. If you hire people for custom work, escrow protects you too. You don't have to worry about paying someone who disappears before delivering. You don't have to hand money to someone you've never worked with before and just hope. The funds are yours until the agreed work arrives. That's a much more comfortable way to commission something.

Read more about how this looks from the hiring side in our post on buyer protection and why it matters when you pay a freelancer.

Where to go from here

If you've been doing custom work the old way, with verbal agreements, informal payment arrangements, and hoping for the best, this post probably sounds a bit like a mirror. Most freelancers in this market know exactly what the problem is. They've lived it. The question is just whether they're ready to stop accepting it as normal.

Escrow doesn't make you less professional. It makes the work more official. Clients who won't agree to it are telling you something worth knowing before you start. Clients who agree immediately are telling you something valuable too.

For more on the broader non-payment picture and what to watch for before you take any project, see our guide on how escrow protects freelancers from non-payment and our deeper post on how to get paid without getting scammed. And if a client wants a formal invoice rather than a project-based escrow flow, the guide on how to invoice clients as a freelancer in Nigeria covers that process from start to finish.