The Decision Is Bigger Than the Idea

Most first-time inventors go looking for a partner because they have hit a wall: the idea needs electronics and they are a mechanical person, or it needs engineering and they are a salesperson. That is a real gap. The mistake is treating it as a single question with a single answer, because a co-founder, a paid contractor, and an engineering firm solve very different versions of it and cost very different things.

The wrong choice is expensive in a specific way: equity given away in month two cannot be recovered in year three, and a partner who leaves after six months usually leaves holding a claim on everything built so far.

First, Define What You Are Missing

Write down what you cannot do, concretely. Not "technical help" but "I need someone to design a BLE board, write the firmware, and take it through FCC." Then sort each gap into one of three buckets.

  • A bounded deliverable. A CAD model, a PCB layout, a mold-ready part file. This is contract work. Buy it, do not marry it.
  • A discipline you need for years. Ongoing firmware ownership, a manufacturing relationship, a sales motion into a channel you do not know. This might justify equity.
  • Capacity, not capability. You know how, you do not have hours. Hire, do not partner.

Only the middle bucket argues for a co-founder. The question of whether you truly need one, rather than a well-paid contractor, is worth working through carefully; the technical co-founder question has a different answer for a hardware product than the software-startup folklore suggests.

Where Candidates Actually Come From

Serious hardware people are rarely browsing job boards. The channels that work in practice:

  • Your own industry. The strongest partnerships come from people you have already worked alongside. A former colleague who has seen you handle a bad week is worth ten strangers with better resumes.
  • Suppliers and vendors. The applications engineer at your connector supplier, the process engineer at a machine shop, the firmware consultant a peer used. These people are pre-filtered by having shipped things.
  • Specialist communities. Field-specific forums, maker spaces with real equipment, IEEE or ASME local chapters, and university labs. A lab that already works on your problem is a partnership channel in itself, and academic collaborators often come with grant funding attached.
  • Engineering firms. The path most first-time inventors underrate. A firm brings a team, insurance, references, and a contract instead of a relationship, and the comparison is laid out in design firm versus freelance engineer.

What to Verify Before You Commit

Enthusiasm in a first meeting predicts nothing. Run a real check on anyone about to hold equity or a critical deliverable.

Shipped work, not portfolio images. Ask what they personally did on the last product that reached customers, in what role, and what broke. Someone who cannot name a failure has either not shipped or is not honest about it. Ask to see a drawing package or a schematic they produced, not a rendering; renderings prove nothing about whether the thing was manufacturable.

References from the difficult project. Ask for a reference from a project that went badly, not the showcase one. Call the reference and ask what they would do differently.

Availability arithmetic. "Nights and weekends" is 10 to 15 real hours per week. A hardware development phase that needs 800 engineering hours will take over a year at that rate. Make the person state hours per week in writing and then check whether the schedule survives it.

IP encumbrances. If the candidate is employed, their employment agreement may assign inventions made on their own time to the employer, particularly in the same field. This is not theoretical; see employee invention ownership rules. Get a written release or expect a dispute later.

A paid trial. Before any equity discussion, buy a small, bounded piece of work at market rates. Three weeks and a few thousand dollars buys more information than three months of conversation: do they hit dates, do they document, do they raise problems early or hide them.

Put It in Writing on Day One

The single most common failure is a handshake partnership that runs for a year and then splits. Whatever the split feels like at the beginning, write it down before work starts.

A founders agreement should cover the equity split, roles and decision rights, what each person is contributing in cash and hours, IP assignment to the company, and what happens when someone leaves. Vesting is the clause that saves the venture: standard is four years with a one-year cliff, and vesting schedules exist precisely because early partners sometimes disappear in month five holding 40 percent.

On the split itself, avoid the reflexive 50/50. Weight it by contribution, capital at risk, and who carries the product after launch; splitting equity between co-founders covers the frameworks. Whatever you agree, put the IP assignment in the same document. A partner who did the CAD and never signed an assignment owns that CAD.

The Alternative: Maybe You Do Not Need One

Plenty of physical products get to market with a solo owner buying services. If your gap is a bounded deliverable, paying a firm for a phase is cheaper in every dimension than giving up a quarter of the company, and you can hire a firm for one phase rather than the whole program. The trade is that you carry the coordination load and the loneliness, which is a real cost documented in solo founder realities.

A workable rule: give equity for judgment you will need repeatedly and cannot buy, pay cash for work you can specify. If you can write a statement of work for it, it is a purchase, not a partnership.

Bring Us the Gap You Cannot Fill

Projects House works with inventors who need a discipline they do not have, on a contract with defined deliverables and no equity. Tell us where your project is stuck and what you can already do yourself through our contact form, and we will tell you whether the right answer is a firm, a contractor, or a partner.