Freelancing in Tech Is a Business, Not a Service
I started freelancing thinking skills were enough. They weren't. The lessons I wish someone had handed me on day one — visibility, systems, communication, and saying no.

Freelancing changed my life. It also almost broke me first.
When I started, I had a simple model in my head: get good at the craft, and clients will follow. I was wrong in a specific, expensive way. Skills get you the first client. They do not get you the next twenty.
Here's what I wish someone had told me on day one.
1. Freelancing is a business, not a service
The work you sell is software. The thing you actually run is a business — with sales, delivery, finance, support, and ops. If you only care about the code, the rest will collapse around you within a year.
Treat the business side with the same respect you give the codebase. Track your hours. Track your revenue per project. Know which type of client makes you money and which type costs you money once you account for everything.
2. Choose the right skills, not all the skills
Early on I learned everything. Every framework. Every database. Every cloud provider. It felt productive. It was actually a way of avoiding a real decision.
What works better: pick one stack, pick one type of client, and become the obvious choice for that combination. Depth sells. Breadth confuses.
3. Communication is the multiplier
The best engineer I know loses to mediocre engineers who communicate well. Repeatedly. It's not fair, but it's true.
Three habits that compound:
- Reply within a working day, even if it's just "I've seen this, will respond properly tomorrow."
- Send a short weekly update on every project. Status, blockers, next steps. No client has ever complained about being too informed.
- Tell the truth when something slips. Early. Bad news travels well when it travels fast.
4. Systems beat hustle
The first time you take a holiday and your business collapses because everything was in your head, you'll understand why systems matter. Until then, build them anyway.
Templates for proposals. A CRM, even if it's just a Notion table. Standard contracts. A repeatable onboarding flow. None of this is glamorous. All of it is the difference between freelancing for two years and freelancing for ten.
5. Visibility is underrated
I used to think good work would speak for itself. It doesn't. Good work plus visible work speaks for itself.
That doesn't mean becoming an influencer. It means making sure the people who would hire you know you exist and know what you do. A simple portfolio. A LinkedIn presence with three thoughtful posts a month. A few case studies that explain the outcome, not the tech.
If your work is invisible, you're competing on price. If it's visible, you're competing on fit.
6. Learn to say no
The single most profitable word in freelancing is "no."
No to the project that doesn't fit. No to the client who haggles before you've started. No to the discount you'll resent in week three. Every wrong-fit yes blocks the right-fit yes that was about to walk through the door.
The honest summary
Freelancing isn't a side hustle dressed up in nicer language. It's a business you can run from anywhere, on your own terms, if you treat it seriously. If you don't, it'll grind you into a slightly better-paid version of the job you left.
Pick the harder, more boring path. Build the systems. Charge properly. Say no more often. The rest takes care of itself.
Written by
Oben Desmond Ashu
Full-Stack Engineer · Social Finance UK
Imposter Syndrome at the Next Level
Joining Social Finance and moving to the UK gave me imposter syndrome like never before. Here's how I've come to think about that feeling — not as a warning, but as a signal.
This landed at the right moment. We're three months into a build we never validated. Bookmarking the prototype checklist.
The 'consistency over intensity' line is one I've been trying to articulate to my team for months. Stealing this.
Curious how you decide which prototype format to use — landing page vs Figma vs Notion. Is it gut feel or a checklist?