Working with Nira

Virtual assistant pay in South Africa: how rates get set

There are no figures on this page, and the reason is stated below. What is here is the part you can actually act on: what moves a rate, how one gets agreed, and what changes when you work through an agency rather than direct.

A hand resting on an open blank notebook on an oak desk, with a calculator, a mug of coffee and a sunlit curtained window behind.

There are no numbers anywhere on this page, and that is worth explaining before anything else, because the absence is doing work rather than avoiding it. Nira publishes what clients pay for talent — an entry rate is stated plainly elsewhere on this site. If this page then published what talent is paid, anyone reading both pages would be reading Nira’s own commercials, which is not something any agency should hand over for free. There is also, separately, no properly sourced South African salary data for this kind of work that this site could cite honestly, and the editorial line here is that an unsourced figure does not get published just because a reader would find it convenient. So this page does the other useful thing instead: what actually moves a rate, how one gets agreed in practice, and what changes when the arrangement runs through an agency rather than straight to a client.

What actually moves a rate

Scope moves it more than anything else. A calendar and an inbox is a different job from a calendar, an inbox, a CRM you are expected to keep clean, and a customer-facing queue you answer alone — and the difference is not cosmetic, it is what the role can be trusted with. Seniority moves it too, in the specific sense of how much judgement the work carries: whether you are told what to do or trusted to notice what needs doing, which is the same distinction the how to become a virtual assistant guide makes about what clients are actually assessing when they hire.

The systems you can already operate matter, and matter more the more specific they are — a named platform you have used in production is worth more than a general claim of being comfortable with software. Sector matters too, and regulated sectors in particular pay for the ability to be handed records — financial, medical, legal — and trusted not to mishandle them; that trust is expensive to establish and worth something once it exists. Hours matter, particularly how unsociable they are: a role that asks you to be available at the edge of a client’s working day, rather than comfortably inside your own, is asking for more than the same tasks performed at a convenient hour. How long you have been doing this specific kind of work matters, separately from how long you have been employed generally. And underneath all of it is a simple distinction: whether the client is buying a person for a fixed set of hours, or buying a service they can rely on regardless of who is doing it at any given moment — those are priced differently because they carry different risk for the client.

How a rate actually gets agreed

The order matters more than most people realise, and getting it backwards is the single most common mistake. Scope comes first: what the role actually covers, in enough detail that both sides could describe it the same way to a third person. Hours come second, once the scope is clear enough that hours can be estimated honestly rather than guessed. A rate comes last, because a rate is a function of the first two things, not an input to them.

Quoting a number before any of that exists is the mistake, and it is an understandable one — a client asks early, and silence feels like it costs you the conversation. But a number given without scope is a number you will regret in one direction or the other. Too low, and you are locked into work that grows without the rate growing with it. Too high, and you have priced yourself out of a role that might have suited you well at a fair number for what it actually involved. Ask about the work before you name a figure. It is not evasive; it is the only way to give an answer that holds up once the work starts.

Two open laptops facing each other across a shared oak desk.

Agency or direct

An agency pays you less than the client pays the agency. That is the arrangement, not a secret, and it is worth saying plainly rather than leaving it implied. What you get in exchange is real: the agency finds the client and vets them before you are ever introduced, agrees the scope on your behalf, handles the contract, does the invoicing and chases it when it is late, arranges cover if you are unwell, and carries the risk of a client who simply stops paying. None of that is free to provide, and the difference between what the client pays and what you are paid is where the cost of providing it sits.

What you give up is control. You have less say over which client you end up with, less direct influence over the relationship once it exists, and a rate that was not entirely yours to set alone. A direct client, by contrast, pays the whole rate straight to you — and requires you to do everything above yourself: find them, vet them as much as you are able to, negotiate and write the contract, invoice, chase the invoice, and absorb the loss if they stop paying. Neither arrangement is straightforwardly better. It is a genuine trade, and this site’s position is that a reader deciding between them deserves the case against Nira’s own model stated as clearly as the case for it.

What raises a rate inside a role

Rates rarely move because someone asked for more money in the abstract. They move because the work changed, and the change is provable. Writing down what you actually do — the processes you run, the decisions you are trusted to make without checking first — turns invisible competence into something a client can see and therefore something they can justify paying more for. Taking on work nobody explicitly asked you to take on, and doing it well enough that it stops being noticed as an addition, is the clearest signal there is. Over enough time, becoming the person who actually knows how a part of the business runs — the one who would be missed for reasons beyond hours worked — is what moves a role from being priced as a set of tasks to being priced as trust.

Two people talking across a small table in a bright room, notebooks open.

Negotiating without a number in your first message

Get scope in writing before you get anything else in writing, because every later disagreement about a rate is really a disagreement about what was included in it. Get hours in writing too, specifically enough that both sides would describe them the same way — “roughly full-time” is not an hours agreement, it is a disagreement waiting for a slow month. And ask, early and without apology, what happens when the work grows: whether hours are revisited, on what basis, and how often. A client who has already thought about that answer is telling you something about how they intend to work with you. One who has not is telling you something too, and it is worth knowing before you start rather than after. For a sense of where the international roles that make these questions worth asking actually sit, where the international roles actually are is the place to look next.

Questions

Follow-ups.

  • Should I quote an hourly rate or a monthly one?

    Quote whichever matches how the work will actually be measured, not whichever sounds more impressive. Ongoing, open-ended support where a client is watching your calendar is usually costed by the hour, because the hours themselves are the variable. A fixed, defined scope — a project with a clear end, or a role with a set weekly commitment — is often cleaner as a period rate, because it removes both the temptation to work slowly and the anxiety of being timed. Neither is the wrong answer in itself; the wrong answer is the one that stops matching the work in month four. Ask what the client already uses for its other contractors, and match it.

  • Should I quote in rand or in the client's currency?

    Quote in the client's currency once you are talking to a client abroad, because that is the number they are budgeting against and the one that will appear on whatever they use to approve payment. Do the rand conversion yourself, quietly, before you propose anything — that protects you from a client doing it badly or not at all. What you should avoid is quoting in rand and leaving them to convert it, because exchange rates move, and neither of you wants a dispute later about which day's rate was meant to apply. Keep your own rand figure for your own planning; keep the number you send them in their currency.

  • What do I say when a client asks for my rate before we've agreed the scope?

    Say that you would rather understand the work before naming a number, because a rate given blind is either too low for what the role turns out to involve or too high for what turns out to be simple, and both outcomes cost you the placement. Ask what the role actually covers, how many hours a week, and which systems are involved, and offer a rate once you have answered those for yourself. A client who is serious about hiring well will not mind the question being turned around — it shows you think about scope before you think about a figure, and that is one of the things they are quietly assessing.

Keep reading

The other guides.

Or start at working with Nira — what the work is like, what is expected, and how matching runs.

If you want to be considered

Send us your application.

An open application, read by a person here. If your experience matches a role we are placing, someone will be in touch; if it does not yet, we keep it on file.