From Employee to Freelance Developer — What No One Tells You

Why I Left

At Terros, I was building great things — 4 published apps, 70,000+ users on one platform, integrations with DocuSign and Stripe. The technical growth was real. But I hit a ceiling: same stack, same clients, someone else defining the roadmap.

I wanted to own the full process. Architecture decisions, client conversations, stack choices. Freelancing meant betting on myself.

Month 1-2: Slower Than Expected

I had three years of production experience and a decent GitHub. I assumed clients would follow. They didn't.

The hard truth: your GitHub doesn't get you clients. Nobody searches GitHub for freelancers. You need to go where clients are.

What actually worked:

• Direct outreach on LinkedIn — personalized messages to CTOs and technical founders at companies whose products I understood.
• Referrals from former colleagues — my first two freelance contracts came from people I'd worked with.
• Freelancing platforms (Malt, Upwork) — slow to start but eventually a steady secondary channel.

What didn't work:

• Posting "available for work" on Twitter into the void.
• Sending generic proposals to every job posting.
• Waiting.

Pricing: The Mistake Everyone Makes

I initially priced myself too low because I was scared. A junior rate, when my work was senior-level.

Two things shifted my thinking:

1. Cheap signals risk — clients who push hardest on price are often the most difficult to work with. Higher rates filtered for better clients.

2. Calculate your real rate — as an employee, your cost to the company is 1.5-2x your salary when you factor benefits, taxes, sick days, holidays. As a freelancer, you pay all of that yourself, plus have no guaranteed income between projects. Factor that in.

My rate increased 40% in year one. I lost zero good clients because of it.

Contracts Matter More Than You Think

I lost money on my second project because of a vague scope definition. The client kept adding features and considered it "part of the original spec."

Now every contract has:

• A detailed scope document with explicit out-of-scope items
• A change request clause (new scope = new estimate + new invoice)
• Payment milestones (30% upfront, never start without it)
• A kill fee for early termination

Use a lawyer to draft your base contract once. It's worth the cost.

Managing Multiple Clients

Running 2-3 projects simultaneously sounds like it multiplies income. It does — but it also multiplies context-switching tax.

My system:

• Each client gets a dedicated Notion workspace with a daily standup doc I fill in before starting work
• Deep work blocks of 3-4 hours per project, no mixing within a day
• Weekly status emails even when nothing dramatic happened (keeps trust high)
• Hard limit: never more than 2 active projects with tight deadlines

Technical Growth Is Your Responsibility

As an employee, conference tickets, courses, and learning time are partly someone else's problem. As a freelancer, they're entirely yours — in time and money.

I budget 10% of income for learning and allocate Friday mornings to building side projects or reading docs. The market rewards skills that are 12-18 months ahead of mainstream adoption. When I started learning FastAPI in 2022, it was still niche. By the time clients started requesting it, I had production experience.

The Good Parts Nobody Talks About

• Choosing which problems to solve is deeply motivating.
• Working across industries (logistics, HR, insurance, coworking) in a short time gives you pattern recognition most developers don't build until 10+ years in.
• The autonomy is real. 11am meeting? Rescheduled because I was in a flow state at 7am and finished early.
• The income ceiling is entirely self-imposed.

Freelancing isn't for everyone. It requires discipline, tolerance for uncertainty, and active business development. But for developers who want to grow fast and own their trajectory, it's the best environment I've found.