The first client is the hardest, because it's the one you get before you can point to any others. Every freelancer remembers theirs. Here's how to make yours arrive sooner — and how to make sure it leads to a second.
Short answer: your first hardware client almost always comes from your network or a local community, not a marketplace. Show one real board, make the engagement feel low-risk, and deliver so cleanly that they refer you before the invoice clears.
Where the first client actually comes from
Forget the fantasy of a cold inbound lead. Early hardware work comes from a small number of predictable places:
- People who already know you can do the work. Former colleagues, classmates, people who've seen you build. This is the number-one source, every time.
- Local startup and hardware communities. Meetups, hackerspaces, university spinouts. Hardware is regional in a way software isn't — being the known "board person" in your city is worth a lot.
- Adjacent professionals. Firmware developers, industrial designers, and contract manufacturers all run into clients who need a board and no one to design it. Be the person they refer.
- Public work. A well-documented open project, a write-up of a tricky bring-up, a shared design. People hire engineers they've watched think.
Generic freelance marketplaces are last on the list on purpose. They compete on hourly price and rarely understand what a re-spin costs. You want clients who buy certainty, not the cheapest bidder.
What to show them
A client isn't buying your hours — they're buying the belief that the board will come back working. Nothing builds that belief like a board that already did.
| Weak proof | Strong proof |
|---|---|
| "I know KiCad and Altium" | A finished board, photographed, with a note on what it does |
| A list of courses | Clean schematic + layout + a complete manufacturing package |
| "I'm detail-oriented" | A short write-up of a bug you caught and how |
| A generic portfolio PDF | A shareable link to real, documented outputs |
Two or three real boards beat any credential. If you don't have client work yet, build them yourself — side projects prove exactly the same thing.
How to earn trust on the first project
Your job on a first engagement is to remove risk from the client's side of the table.
- Scope it in writing. What's included, what's not, what a revision costs. A clear scope signals a professional and protects you both.
- Start small if you can. A paid pilot — a review, a single board, one milestone — lets a cautious client say yes. Nail it and the bigger project follows.
- Over-communicate. A short status note every few days is worth more than most people realize. Silence reads as risk.
- Hand over a package, not a pile of files. Gerbers, BOM, pick-and-place, DRC/ERC status, a readable summary — the way you'd want to receive it. This is where most freelancers quietly lose the repeat business, and it's the subject of its own article: the deliverables that win repeat clients.
Make the first one lead to the second
The first client is a means to the second, third, and referrals. The engineers who compound fastest are the ones whose handoff makes the client look good to their own boss. A clean, versioned, shareable deliverable does that automatically.
A practical way to punch above your weight: put the project under version control and let something regenerate the manufacturing outputs on every change, so what you hand over is always current and never a mystery zip. That's the entire idea behind GoForFab — connect a KiCad project, and every push produces a professional package and a link you can send a client. Free forever, and it makes a first-time freelancer look established.
Land one. Deliver like it's ten. The rest takes care of itself.