From idea to product: how it really works
Most products that come to us start with one sentence: "I want a device that does X". That sentence is a great starting point. The way from it to a product you can hold in your hand goes through several stages, and it is worth knowing them in advance.
1. Specification call
In the first meeting, free and with no obligation, we understand what the product should do, who will use it and in what environment. Already at this stage the big decisions become visible: does it need a battery, does it connect to a phone, and what is the biggest technical risk.
2. Technical specification
We turn the idea into a list of requirements and an architecture: which processor, which communication, which sensors. At the end of the stage you know what is being built, what the risks are, and how much each stage will cost and take.
3. Prototype
This is where the electronic board is built and the code is written. The result is a working prototype you can show to investors, partners and first users. It usually takes 2–4 months from the end of the specification.
4. From prototype to product
Once the prototype has proven itself, come the pilot, the enclosure, preparation for production and sometimes certification. This stage usually comes after fundraising or first sales.
How much does it cost?
This is the first question every entrepreneur asks, and rightly so. The answer depends on the product, but it is important to come with the right expectations: developing a working electronic prototype, including specification, board design, the first boards and the firmware, usually costs around ILS 20,000–30,000. A product with an app, a server or several boards will cost more, and a very simple product can cost less.
Splitting the work into stages helps here. The specification stage is relatively small, and at its end you get an accurate estimate for the rest of the way, before committing to full development.
Why a small company is usually right for entrepreneurs
An entrepreneur's budget is limited and every month counts. In a small company you talk directly to the engineer who designs the board and writes the code, so questions are answered the same day and nobody bills you for layers of management. When something doesn't work, the person who designed it also fixes it.
What to prepare for the meeting
- A short description of what the product does and who it is for
- Similar products on the market, if any
- How many units you expect to sell in the first year
- A timeline, for example an exhibition or a fundraising round
- If you already discussed the product with an AI assistant, bring that summary too
FAQ
Do I need to come with drawings or a specification?
No. It is enough to know what the product should do and who it is for. We build the technical specification together.
Who owns the product at the end?
You do. All files and source code are handed over to you.
Do you help with the enclosure design too?
Yes, through long-term partners for mechanical and industrial design, under our coordination.
I already planned the product with ChatGPT. Is that useful?
Very. Bring it to the intro call. It saves time, and we will tell you which parts are realistic, which are risky, and what is missing.