DEV Community

Cover image for I Priced My First Security Job in the Wrong Currency. Here's What I Learned.
Imamsab Mulla
Imamsab Mulla

Posted on

I Priced My First Security Job in the Wrong Currency. Here's What I Learned.

From my book Freelance Fortune, on going from a first client to $999 an hour.

If you are a developer or security engineer thinking about freelancing, this is the mistake I would stop you from making on day one.

I had ten years of hacking experience when I placed my first serious bid on a freelancing platform. The job was a hacked WordPress site that several freelancers had already failed to clean up. I won it, fixed it in under four hours, and the same client sent me a $2,000 project next.

The hourly rate on my profile was one I had set years earlier, when I signed up, thinking the box was in rupees. It was in dollars. The client paid it without a second thought, because the market rate for incident cleanup was higher still.

Here is what I would tell my younger self, and you.

1. Price against the global market, not your local salary

Your client is comparing you with every other freelancer worldwide who can solve the problem, not with salaries in your city. Before you set a rate, look at what people with your skill charge on the same platform, in the same niche. Security, incident response and performance work are paid for the outcome, not the hours.

2. Pick the job other people failed at

A post saying "I already tried several people" is not a warning sign for a specialist. It is a filter. The generalists have left, the client is motivated, and your skill is suddenly rare.

3. Timing is a technical advantage

That post was 39 minutes old with zero bids when I found it. Evening in India is morning in the US, when clients post work. For years I slept during the day and worked US hours so I could be first. The first serious reply gets read properly. The fortieth gets skimmed.

4. Explain the fix in plain words

On the call, I walked the client through what was wrong with his site and what I would do, without jargon. Non-technical clients don't buy expertise they can't see. They buy the feeling that you understand their problem better than they do.

5. Offer a guarantee only when you can back it

I said: don't fund the milestone, pay only if I fix it. That worked because I knew I could. A guarantee without the skill behind it is just working for free.

6. Raise your rate in steps, and expect some clients to leave

I moved up to $100 so the maths was easy, then to $200, $500 and finally $999 an hour, the platform's maximum. Clients walked away at every step. Many came back.

7. Protect yourself from chargebacks

One of the worst scams I have seen: a client pays, receives the work, then tells their card company the work was never delivered. Use the platform's milestone and escrow system, keep written scope and delivery records, and be wary of clients with a bad history. I turn those down. They are not worth the headache.


I wrote all of this down, from that first bid to $999 an hour, in my book Freelance Fortune: Untold Secrets of Freelancing in the AI Era. If you build or secure things for a living and want to freelance, it was written for you.

freelancefortune.com

Top comments (0)