Learning in Action · 05

Freelancing Lesson: Clarity, Quality, and Trust

If you are not clear about what you do, others will define you incorrectly. Here is how I priced work and built trust without bargaining.

On this page3 sections
Photo of a small team in a coworking space — one person sketching a system architecture diagram on a whiteboard while others work at multi-monitor desks and one shakes hands with a visitor.

One thing I understood early in freelancing: if you are not clear about what you do, others will define you incorrectly.

I was never trying to be "just" a web designer or digital marketer. My core identity was always a freelance web developer — someone who builds functional systems and real solutions. Websites and basic digital marketing were only entry points, not the destination.

As work moved from websites to software and applications, responsibility expanded to deployment, performance, reliability, and maintenance. That's how my focus naturally grew into DevOps and infrastructure — not as a title change, but as a continuation of building things properly. From writing code, to running it, to maintaining it, everything became one workflow.

Getting Clear Before Getting Clients

Before freelancing worked, three things had to be clear: what I'm building, how it benefits the client, and how far the solution can realistically go. Only then could I communicate it clearly.

My approach was simple. I didn't force anyone. I didn't manipulate conversations. I didn't oversell. I focused on making sure people knew that I'm doing this, what kind of work I can handle, and how it helps their business. If they needed it, they came. If they didn't, that was fine.

Pricing, Kept Intentionally Simple

I started with one clear package — a website — with a few complementary essentials. No complicated tiers, no confusing plans.

As work evolved from basic sites to custom development to dynamic platforms to software and infrastructure, pricing evolved with the value of the work. Each project depended on scope, complexity, responsibility, and long-term impact. I always explained why the price, what they'll get, and how it solves their problem. That clarity reduced bargaining.

Sometimes I said honestly:

"You may find cheaper options — this is what they usually offer. My approach is different, and this is the value I bring."

That honesty built trust.

Mutual Benefit, Not Manipulation

One belief I strongly hold: freelancing and business are about mutual benefit, not manipulation. If one side wins by the other losing, it won't last. That's how repeated work happens.

Instead of chasing many small projects, I chose to take fewer projects, focus on quality, and build things properly.

Quality compounds. Trust compounds faster.

Over time, that matters more than quantity ever will.

Next in this series: the mistakes I made early, underpricing myself, the benefits of teamwork, and what I'd do differently starting today.

Tagsfreelancingpricingtrustcareerlearning-in-action

Originally published on LinkedIn.

Muhammed Nasvih V

Muhammed Nasvih V

Lead DevOps & Cloud Engineer · Jeddah, Saudi Arabia

Writes The Stack Notes — field notes on infrastructure, AI, money and work. Cloud infrastructure, CI/CD, security and automation at Code7 Information Technology.

This is the log of how the career was actually built — the current version of it is the DevOps and IT lead role at Code7. See the experience.

Back to The Stack Notes