You can absolutely develop a new product while holding a full-time job — most first products in the United States are built exactly that way. What kills nights-and-weekends projects is almost never a lack of talent or money; it is an unresolved employer agreement, milestones sized for a full-time team, and momentum that dies during the first busy quarter at work. Handle those three things deliberately and a day job becomes an advantage rather than an obstacle.

Your scarce resource is hours, not dollars

A salaried inventor typically has money and no time, which is the opposite of a funded founder. That inverts how you should spend. Every hour you burn learning a CAD package, hand-soldering a board, or chasing a vendor who never answers is an hour stolen from the one thing nobody can do for you: deciding what the product must be and whether anyone wants it.

So buy time wherever the price is reasonable. Paying a machine shop, a print service, or an engineering partner for work you could theoretically teach yourself is usually the correct call, because the alternative is a project that stretches across years and quietly expires. Reserve your own hours for customer conversations, requirements, and decisions.

Be honest about the arithmetic too. Ten focused hours a week is a real budget; two hours on a Sunday when you are already exhausted is not. Block the time on a calendar the way you would a work meeting, and treat a missed block as a scheduling problem to fix rather than a personal failure.

Settle the employer question first

This is the step people skip, and the only one that can cost you the product outright. Before you spend a dollar, read what you signed when you were hired: an employment agreement, an invention assignment or "proprietary information" agreement, a confidentiality agreement, and any moonlighting or outside-activity policy in the handbook.

Typical clauses assign to the employer inventions that relate to its business or that were made using its time, equipment, or confidential information. Several states limit how far such assignments can reach — California's Labor Code section 2870 is the best-known example, and a handful of other states have comparable provisions — but the limits are narrow and fact-specific, and they never cure the practical problem of an angry employer.

Practical hygiene that keeps the line clean:

  • Work only on personal equipment, a personal email address, and a personal cloud account. Never a company laptop, company Wi-Fi, or company software license.
  • Work only outside working hours, and keep dated records of when the work happened.
  • Keep the subject matter away from your employer's products and roadmap. Overlap is where disputes start.
  • If the field is even adjacent, ask for a written release or carve-out before you invest. A quiet no is much cheaper than a surprise ownership claim.

Because these documents vary enormously, treat this section as general education, not legal advice; Projects House is an engineering firm, and an attorney should review your specific agreement. Our overview of who owns an invention made at work covers the ownership question in more depth, and forming a separate entity early — see LLC vs sole proprietorship for inventors — helps keep the two worlds visibly separate.

Cut the project into milestones you can actually close

A part-time project needs shorter stages than a funded one. Instead of "build the product," define outcomes small enough to finish inside a few weeks of evening work, each of which produces a decision:

  1. Problem confirmation — twenty conversations with people who have the problem. Costs nothing but time and kills bad ideas early.
  2. Prior-art check — find out whether the concept already exists before spending on engineering.
  3. Proof of principle — the one risky function working on a bench, ugly and wired, nothing else.
  4. Requirements document — what the product must do, for whom, at what target cost.
  5. Presentable prototype — something you can put in a stranger's hands.

The reason to work this way is not tidiness. It is that each closed milestone gives you a legitimate reason to stop, and a part-time project that ends after stage two because the market is not there has saved you a year, not wasted a month. Start with validating the idea and, if you have several concepts competing for the same evenings, decide deliberately which idea to pursue first.

Money: a salary is the best funding a first product can have

Self-funding from wages costs no equity, requires no pitch, and answers to nobody. It is also finite, so decide in advance what portion of monthly income the project gets and hold that line. Early stages — conversations, searches, a bench proof of principle — run in the low four figures for many products. A presentable prototype commonly lands in the mid four to low five figures, and tooling for volume production is a different order of magnitude entirely.

Sequencing matters more than the totals. Spend on the cheapest test that can still kill the idea, and only then on the next one. Our guide to bootstrapping a hardware product goes through the same logic from the funding side, and if you would rather run the engineering with a partner than build a team, compare outsourcing versus in-house development.

When to leave the job

Not when the prototype works — that is the moment it feels most tempting and proves least. Reasonable triggers are external and verifiable: signed purchase orders or preorders you cannot fill part time, a grant or investment that replaces salary for a defined runway, or a manufacturing ramp whose day-to-day decisions genuinely cannot wait for evenings. Until one of those is true, the day job is not slowing the product down; it is paying for it.

Working with an engineering partner on evenings and weekends

An outside team changes the constraint. Engineering moves during business hours whether or not you are available, and your job narrows to reviews, decisions, and approvals — work that fits an evening. What makes that succeed is written requirements, defined deliverables per phase, and a fixed review rhythm so nothing waits on a spontaneous phone call.

Projects House works with employed inventors on exactly this pattern: scoped phases, documented decisions, and progress that does not depend on your calendar. Tell us what you are building and how much time you have, and we will map a realistic phase plan around it — send us the details through the contact form and we will come back with concrete next steps.