If you are a developer who would rather ship code than write pitches, the shortest path to clients is a small agency owner with more projects than developers. Write to ten of them, offer to take one fixed-scope piece off their plate, and let the work do the selling. After that, non-technical founders and word of mouth tend to fill in the rest.
This isn't a growth-hacking plan. It's a way to turn what you already do well into a short, repeatable routine that takes a few hours a week. Below: why businesses pay for outside developers, where to find them, how to scope the first job so you don't get burned, and the emails to send.
Why a business hires a freelance developer
Rarely because they love code. Usually because something is stuck. An agency sold a project that includes custom work and its one developer is booked for six weeks. A founder with no technical cofounder needs an integration built before a demo. An operations manager has a spreadsheet process that breaks every month and wants it turned into a small tool. In all three cases, the buyer isn't evaluating your stack. They're asking whether you'll finish and whether you'll make them look foolish.
That tells you what to show: finished things, clear communication, a plain explanation of what you'll do and when. You can leave out the architecture talk.
Agencies with overflow, and founders without a CTO
Two groups hire freelancers repeatedly. Small web, design and marketing agencies (3 to 25 people) that subcontract anything their in-house team can't absorb. And non-technical founders who need a build but can't judge a developer.
Agencies are the better first target. They already know what a developer costs, they don't need you to explain the work, and they tend to send more projects once the first goes well. Arjun, a freelance developer in Atlanta, built a list of agencies by looking at the "Work" pages of local design shops and marketing firms. He picked those whose portfolio included web apps or e-commerce but whose team page showed no engineers. He found 26 in an afternoon, and for each wrote down the owner or head of delivery.
If you'd rather not find the names by hand, Rocketship can search agencies by size, location and role, and you can see the first 25 names before any credit is spent. The thing to check, wherever the list comes from, is that the person you write to decides who builds the project.
The offer: a fixed-scope first project with a handoff
Hourly quotes are risky for both sides. The client doesn't know the total, and you're stuck defending every hour. For a first job, propose a fixed scope with a price, a delivery date, and a handoff.
Arjun's template: "A Stripe checkout integration for your client's online store, $2,400, delivered in 8 business days. Includes: working code in your repo, a short README, and a 30-minute walkthrough for your team. One round of fixes within 14 days. Anything outside this list gets a separate quote." The scope has five items, the price is a number, and what happens at the end is written down.
Run the math. If it takes him 24 hours, that's $100 an hour. If an agency sends him one such project a month, that's $2,400 a month on top of whatever else he has. Four agencies at that pace is $9,600 a month, which is full time. You don't need many of them, and agencies come back when the first one went smoothly.
Write the scope as a list of things that will be true when you're done, not a list of tasks. "Users can check out with a card and receive a receipt by email" is a good line. "Implement payments" is not.
A first email to an agency owner
Keep it under 100 words, include a specific example of what you can take, and ask a small question:
Subject: Overflow dev help for Brightwave Studio
Hi Tom, I saw Brightwave's recent work for the Peachtree Market redesign. I'm a freelance developer in Atlanta (Node, React, Stripe, Shopify), and I take overflow work from a couple of local agencies: integrations, custom checkout, small admin tools. I price by fixed scope with a handoff doc, so your team knows what it's getting. If you ever have a build you can't staff, I'd be glad to quote one. Is that something that comes up? Arjun Rao, Rao Dev, 15 Marietta St, Atlanta GA. Reply "no thanks" and I won't write again.
That email contains no code, no stack list longer than a line, and no hype. It asks if the problem exists. If you dislike pitching, this is a good format because it's closer to a question than a sales message. The mindset is covered in doing outbound when it feels like begging, which is worth reading if the discomfort is what stops you from sending.
Why quoting hourly with no scope costs you
When you say "$90 an hour" to a founder who can't judge how long things take, you invite one of two outcomes. They assume it will be cheap and are shocked at the invoice, or they micromanage each hour. Either way, you end up arguing about time instead of results.
If a client insists on hourly, cap it: "$90 an hour, estimated 20 to 28 hours, I'll tell you at 20 whether I'll go over." That keeps the conversation honest without a fixed price. For solo technical founders who also want to learn to sell their own product, you'd rather be building, so build the thing that sells makes a related case.
Follow up after three days with your open capacity
Developers often assume that silence means no. Usually it means busy. Send a second email after three days, shorter than the first: "Tom, in case this got buried, I take about two projects a month and have room in November." A third a week later can share something useful, like a one-page checklist for handing off a custom checkout. Then wait two months and try again.
If you'd prefer the follow-ups happen while you're heads-down in a build, Rocketship's AI worker sends them from your own Gmail and reads replies, so someone saying "actually, we do have something" gets an answer the same day. See the AI workers page.
Booking the scoping call and arriving prepared
When an agency or founder replies, offer two 30-minute slots. Before the call, read their site and the brief they've sent. Prepare five questions: what does done look like, who uses it, what does it connect to, what is the deadline, and who approves. During the call, take notes, repeat back the scope in one paragraph, and say you'll send a written fixed-scope quote within 24 hours.
Engineers often say too much on these calls. Say less, ask more, and let them describe the problem. Running a sales call when you debug for a living goes into this in detail, including how to treat an unclear answer as a question to ask next, not a bug to fix.
Send the quote, then follow up in two days. The first project is the hard one to land, and the second one usually arrives without any outreach. If you also write for a living, how to get clients as a copywriter uses teardown-first outreach that translates well to code reviews and small fixes.
If you build websites as well as software, cold email templates for web designers and freelancers has a teardown-style email you can adapt.
A freelance pipeline is a short list of agencies, a fixed-scope offer and a follow-up habit. Rocketship finds the buyers, emails them from your own Gmail, follows up, and books the meeting on its own. Plans that get you customers start at $24.99 a month (Launch), and every monthly plan starts with a 7-day free trial, card required.