Five lessons, about an hour and five minutes. Everything so far has been about doing the work well. This module is about the arithmetic and paperwork that decide whether doing it well actually pays — rates, agreements, and the specific friction of getting paid across borders.
The three common ways to price support work reward genuinely different things, and picking the wrong one for a given client isn't just a preference — it can quietly cost you money for months without either side noticing why.
Hourly rewards time spent, which is fair for unpredictable workload but means getting faster at the job literally lowers your income unless you renegotiate. Retainer — a fixed monthly fee for owning the queue — rewards outcomes and efficiency, and is where the trust-ladder rung 4 role from module 1 naturally lands. Per-ticket rewards volume, which fits a high, predictable ticket count but can quietly pressure rushing through complex tickets to keep the per-ticket rate worthwhile.
Hourly: ₦2,500/hr, roughly 15 hrs/week = ₦37,500/week, but the faster Tolu gets, the less he earns for the same output. Retainer: ₦140,000/month flat for owning the whole queue — rewards Tolu for getting efficient, since the fee doesn't shrink. Per-ticket: ₦800/ticket, which works well at steady volume but tempts rushing the harder ones.
Price a made-up support role three ways — hourly, retainer, per-ticket — and note which model you'd actually choose and why.
A quoted rate that looks reasonable on paper can quietly lose money once the real costs of earning it are counted — and most beginners never count them, which is a large part of why underpricing is so common at entry.
Data and connectivity costs for the hours worked. Power — a generator or inverter running during a shift is a real cost, not a rounding error, in markets where outages are common. Unpaid time: replying to a client's messages outside billed hours, or time spent invoicing and chasing payment, which is real work that often goes uncounted. And tax, if applicable, which changes what a quoted rate actually nets.
Quoted: ₦2,500/hour. Real costs per hour worked: ~₦150 data, ~₦200 power (generator, prorated), ~30 minutes of unpaid admin per 10 billed hours. The quoted rate is still reasonable — but only once these are actually counted rather than assumed away.
List your own real costs per working hour — data, power, anything else genuinely relevant to you — and see what they actually add up to.
Most beginner support work happens with no written agreement at all — just a message thread and a handshake understanding. This works fine until it doesn't: a scope disagreement, a payment delay, a "actually I meant something different" that costs real money to sort out after the fact.
What's covered (channels, hours or ticket volume), what isn't, the rate and payment schedule, and a trial-shift or notice period on both sides. It doesn't need to be a legal document — a clear, mutually agreed message that both sides can point back to is often enough at this scale, as long as it's actually written down rather than assumed.
"Confirming our agreement: I'll cover email and WhatsApp support, roughly 15 hrs/week, at ₦2,500/hr, invoiced every two weeks. This doesn't include live chat or social DMs — happy to discuss adding those separately. Either of us can end this with 2 weeks' notice. Let me know if this matches your understanding!"
A paid trial period, clearly time-boxed, lets a founder assess fit without a long commitment, and lets you assess whether the brand and the work are actually what they seemed before agreeing to anything longer.
Write your own one-page agreement message for a made-up support role, using the worked example's shape.
A support rep working for a brand based in another country runs into a genuinely different problem than the work itself: actually receiving the money. Payment platforms, currency conversion, and intermediary fees can turn an agreed rate into a smaller and later-arriving number than either side expected, and not knowing this in advance is how good working relationships sour over a purely mechanical issue.
Which payment rails the client can actually use to pay into your country, what each one's fees and typical delivery time are, and what exchange rate you'll actually receive versus the quoted mid-market rate — platforms differ meaningfully here, and the difference is real money, not a rounding error.
Delays and fees in receiving money already earned are a genuine, common source of frustration for freelancers working across borders, and part of why some quietly stop taking international clients even when the work itself pays well. Knowing this in advance, and testing a payment route before committing to a rate, is what protects against it — rather than discovering the problem after weeks of unpaid work.
List two payment methods you could realistically receive cross-border payment through, and what you know or can find out about each one's fees and delivery time.
Time tracking and invoicing done at the last minute, from memory, is where money quietly gets lost — a shift undercounted, a rate misapplied, an invoice sent late enough that payment slips a cycle. A five-minute daily habit prevents an hour of reconstruction at month end.
Log hours or tickets the same day, not from memory a week later. Keep one running sheet, however simple, rather than scattered notes. And send the invoice on a fixed schedule — the same day every two weeks, say — rather than whenever you remember to.
Set up a simple running log — even a single spreadsheet row per shift — and log one made-up entry to see the shape of it.
Build the three pieces of paperwork that make this role a real business, end to end — not hypothetically, but with your own real numbers where possible.
Whether you can turn this role into an actual, defensible small business — not just do the support work well, but be paid for it reliably and fairly.
You should now have: a pricing model chosen with real reasoning, your real hourly cost, a one-page agreement template, a tested payment route, and a tracking habit. Module 10 turns to the last piece — actually finding your first three clients.