How I Doubled My Freelance Income by Pitching the "Wrong" People
CTOs are the worst people to pitch if you want to make actual money.
For 18 months, I thought I was doing everything right. I built a slick personal website, spent hours polishing my GitHub repositories, and sent 317 hyper-personalized outreach emails to CTOs, Tech Leads, and VPs of Engineering.
The result? A grueling average of $3,210 a month, working 57 hours a week, fighting over every line item on my invoices. I was constantly asked to complete 4-stage technical interviews, do take-home assignments, and justify why my hourly rate was higher than an overseas dev shop.
Then I made one radical shift: I completely stopped pitching technical leaders. Instead, I started targeting non-technical executives—specifically VPs of Product, Heads of Growth, and Operations Directors.
Within 87 days, my monthly freelance revenue shot up from $3,210 to $14,830. I didn't write better code. I didn't get any new certifications. I didn't work more hours. I simply changed who sat on the other side of the call.
The CTO Trap: Why Technical Leads Are Bad Buyers
Here is a controversial truth that took me far too long to accept: CTOs and Engineering Managers don't want to hire high-ticket freelancers because doing so threatens their team's perceived capability.
When you pitch a CTO, you are reaching out to someone whose bonus, title, and career progression rely on building an in-house engineering team. They view external contractors as an expensive temporary cost center, or worse, proof that their internal team can't handle the workload.
When you quote a flat fee of $18,450 for a project, a technical leader immediately breaks it down into hours and compares it to the base salary of an internal senior developer. They judge you on how you build rather than what your build accomplishes. You get dragged into architecture debates, framework preferences, and endless bike-shedding about state management libraries.
You end up competing against every cheap bidding site on the internet, stuck in a race to the bottom.
The Shift: Moving to Economic Buyers
Product, Growth, and Operations executives think completely differently.
A VP of Product doesn't care whether you write TypeScript, Go, or vanilla JavaScript. They don't care about your test coverage percentages or whether your Git commit history is clean.
They care that their onboarding funnel is dropping 43% of new signups on mobile, costing them an estimated $62,000 in lost subscription revenue every single quarter.
As a freelancer, I used to introduce myself like this:
"I'm a full-stack developer with 7 years of experience in React, Node, and PostgreSQL."
That sentence earned me a miserable 2.1% reply rate and dozens of rejections.
When I stopped selling my technical implementation and started selling business fixes, I shifted my positioning entirely:
"I fix mobile checkout drop-offs for mid-sized e-commerce platforms."
Same skill set. Completely different buyer. Completely different dynamic.
The "Metric-First" Approach That Changed My Revenue
When you pitch non-technical decision-makers, you aren't competing with other engineers. You are competing with the status quo—the cost of them doing nothing.
Here is the exact 3-step breakdown I used to transition away from low-paying engineering jobs toward high-value project contracts.
Step 1: Identify the "Pain Owner"
Before sending a single email, ask yourself: Who gets fired if this metric misses its target?
- If page speed is slow, the CTO isn't getting fired. But the Head of Growth is missing their conversion target.
- If internal admin tools are clunky, the Dev Lead doesn't care. But the Director of Operations is watching team efficiency plummet by 31%.
- If a new feature is delayed by 14 weeks, the VP of Product is the one who has to explain the missed roadmap to the board.
Find the person whose quarterly performance review relies on fixing the specific problem you know how to build for.
Step 2: Write Outreach That Focuses on Bottlenecks
I completely stopped attaching my portfolio or linking to my GitHub in initial messages. Non-technical buyers don't know how to evaluate a code repository anyway.
Instead, I used a short, observation-based outreach template. Here is an exact message that led to a $18,450 contract with a 31% response rate across 142 sends:
Subject: Quick observation on [Company]'s onboarding flow
Hi [Name],
Noticed that during the step 3 registration on mobile Safari, the form field auto-fill triggers a layout shift that hides the 'Continue' button on smaller screens. Looks like it's adding about 14 seconds of delay for mobile users.
I recently fixed a similar mobile drop-off for an analytics client, which recovered roughly 12% in completed signups over 30 days.
Would it make sense to send over a 2-minute video showing where the layout breaks?
Notice what isn't in this email:
- No mention of frameworks.
- No mention of my rates.
- No link to a resume.
- No request for a "30-minute introductory call."
It highlights a clear, observable metric issue and offers a zero-friction video walk-through.
Step 3: Ditch Hourly Rates and Quote on Business Risk
When you get on a call with an Economic Buyer, skip the technical discovery questions. Don't ask them what database they prefer or how they deploy code. Ask questions that quantify financial impact:
- "How long has this onboarding bug been sitting in the backlog?"
- "If this feature isn't live by next month, how does that impact your Q3 goals?"
- "What is the estimated revenue loss every month this stays broken?"
If the client tells you that a broken onboarding flow is costing them $45,000 every month in leaked revenue, quoting a fixed price of $14,800 to fix it within 21 days is a no-brainer. They aren't paying for your hours—they are paying to recover $45,000 a month as fast as humanly possible.
How to Find Non-Technical Prospects
Finding non-technical leaders who actually hold discretionary budget takes a bit of deliberate prospecting. You can't just browse job boards, because job listings for "React Developer" are almost always written by engineering recruiters who will force you back into the standard hiring pipeline.
Look for company announcements, funding rounds, or product launches, then trace who holds the KPI for that launch.
If you're looking for leads, this email list has been helpful: The Solo Pro Email List — it shares curated opportunities and insights on reaching buyers who have direct budget authority without getting tangled up in procurement delays.
The Practical Summary
Moving upmarket as a freelancer isn't about learning a new framework or putting another badge on your LinkedIn profile. It's about changing who you pitch and how you quantify your value.
- Stop pitching CTOs and Engineering Managers. They evaluate you on technical implementation and compare you to internal salary costs.
- Target VPs of Product, Growth Leaders, and Operations Directors. They evaluate you on speed to market, revenue recovery, and metric improvements.
- Sell the outcome, not the implementation. Never open a conversation with your stack. Open with an observable bottleneck in their business.
- Anchor your prices against business cost, not hourly rate. A $15,000 project fee is cheap to someone losing $50,000 every month.
Making this transition felt uncomfortable at first. I felt like an imposter stepping outside the safety of technical discussions to talk about revenue targets and conversion drop-offs. But looking back, it was the single decision that transformed my freelance work from an exhausting sprint into an actual, sustainable business.
I'm curious—what has been your experience pitching outside of engineering departments? Have you noticed a difference in budget authority when talking to product managers versus engineering managers?
Top comments (0)