What This Meeting Is For

The first conversation with an engineer is not a pitch and it is not a sales call. It is a scoping session. By the end of it, both sides should be able to say what the product has to do, which parts of it are unknown, and roughly what the first phase of work would cost and take. An hour spent well here saves weeks of a project pointed in the wrong direction.

Inventors usually prepare for the wrong meeting. They rehearse why the market is huge and arrive with no dimensions, no user, and no failure mode. The engineer, meanwhile, is trying to find the constraint that decides everything: the power budget, the price point, the size limit, the regulatory class. Give them that and the meeting becomes productive in ten minutes.

What to Bring

None of this needs to be professional. It needs to exist.

  • One sentence describing the problem, phrased about the user and not about your solution. "Warehouse pickers lose 40 minutes a shift walking back to a scanner station" is useful. "An innovative platform for logistics efficiency" is not.
  • A sketch, however rough. Napkin drawings, a photo of a cardboard mock-up, or an annotated photo of an existing product with arrows. If drawing feels impossible, sketching a product idea with no technical skills covers the minimum that communicates.
  • Numbers you already know. Approximate size, weight, how much force or flow or run time it needs, how many units a year, target retail price. Guesses labeled as guesses are fine.
  • Two or three closest existing products, with links and prices, plus one line on why each one is not good enough.
  • Your constraints. Budget for the first phase, the date something has to exist by and why, and anything non-negotiable such as a battery that must last a week or a shape a retailer requires.
  • Any prior work. Patent filings, a prior prototype that failed, an earlier quote, CAD from a previous contractor. Especially the failures, which are the most informative thing in the room.

Writing the whole thing up beforehand is worth an hour of your time; the structure in writing an idea brief works as a meeting agenda even if you send nothing in advance.

How to Actually Present It

Lead with the user and the moment of use, not the mechanism. Describe someone picking the product up, what they do with it, what happens, and what they do next. Engineers build requirements out of use cases, and a two-minute story about a real person generates more design constraints than twenty minutes of feature list.

Then say plainly which part of the idea is the hard part. Every product has one thing that will decide whether it works: the sensor accuracy, the seal, the battery, the folding mechanism, the cost target. If you know what it is, say so. If you do not, say that too, and let the engineer find it.

Separate the requirements from the preferences. "It has to fit in a standard pocket" is a requirement. "I pictured it in brushed aluminum" is a preference. Engineers will hold both, but they optimize hard against requirements and quietly discard preferences when they conflict. Mislabeling a preference as a requirement is how projects get expensive.

Finally, do not oversell. An engineer who tells you a feature is impractical is doing the job you are paying for. Arguing them out of it in the first meeting means you will hear about it later, at the tooling stage, for real money.

What Is Happening on the Other Side of the Table

The engineer is running a private checklist while you talk. Expect these questions and have a position, even a rough one.

Is this mechanical, electronic, or both, and does it need software? Many ideas that sound electronic are better solved mechanically, a fork examined in does your idea need electronics. What is the target unit cost at volume, because a product that must land at $29 retail cannot carry a $14 bill of materials. What volume, since 500 units a year and 50,000 units a year are completely different products. Does it touch a regulated space such as medical, children, food contact, or wireless. Who is the buyer and who is the user, because they are frequently not the same person. And what already exists, since a two-minute patent or catalog search often surfaces something close.

You will also be evaluated as a client. Engineers look for whether you have a decision process, whether the budget is real, and whether you can distinguish what you know from what you assume. Saying "I do not know, I would need to test that" raises your credibility rather than lowering it.

Confidentiality: What Is Realistic

Ask for an NDA before the meeting and most established firms will sign a mutual one without argument. Understand what it does and does not do: it protects a specific disclosure, not a general concept, and it does not stop independent development of similar ideas. The practical boundaries are in NDAs for inventors.

The more consequential document is the development agreement, because it determines who owns the CAD, the firmware, and any inventions made during the work. Default terms vary widely, and the questions to settle before signing anything are laid out in who owns the IP when a company develops your product. Raise it in the first meeting; a firm that gets uncomfortable when you ask is telling you something.

What You Should Leave With

A first meeting is not free consulting and no one will hand you a design. But you should walk out with the engineer's read on technical feasibility, a named list of the biggest unknowns, a rough order of magnitude on cost and schedule for a first phase, and a clear next step with a date. If the firm proposes a paid definition phase before quoting the whole project, that is normal and usually the right sequence; see what a product definition phase costs. What should worry you is a full fixed price for a complete product quoted in the first hour, with no questions asked about volume, cost target, or regulation.

Bring the Idea, We Will Bring the Questions

Projects House runs first sessions as structured scoping conversations: we work through the use case, the constraints, and the unknowns, then come back with a written read on feasibility and a phased plan. Send a sketch and a few lines about the problem through our contact form.