10 Questions to Ask When Choosing an Electronics Design Company
What to ask to find the best designers.
Choosing the right electronics and embedded design company is one of the most important decisions you will make when developing a new electronic and embedded product. The right partner can help reduce technical risk, accelerate development and bring valuable engineering expertise to your project. Whether you are considering a specialist electronics consultancy, a contract manufacturer with design capabilities, or a freelance engineer, there is rarely a single "right" choice.
The right choice will depend on your priorities, your product's complexity, budget, timescales and internal resources. These ten questions will help you evaluate the available options and identify the partner best suited to your project.
Before you start looking at suppliers, ask yourself and your team 2 questions. These questions will help you narrow down who to search for and contact.
1) What are the priorities and goals for your design project?
Before comparing electronics design companies, take a step back and ask what success looks like for your project.
Are your priorities to:
Reach the market as quickly as possible?
Minimise development costs?
Access specialist engineering skills?
Reduce technical risk?
Prepare for large-scale manufacture?
Different development partners may be better suited to different priorities, so aligning your team on what matters most will make the selection process much easier. While we would all like the best possible quality at the lowest price delivered yesterday, the reality is that there are trade-offs between development speed, risk, and cost. Identifying your priorities and setting clear goals simplify the search process.
2) What skills, experience and resources does your project require?
Modern products rarely involve electronics alone. Depending on the application, you may need expertise in embedded software, IoT, cloud connectivity, compliance or manufacturing support.
Consider which skills already exist within your team and which will need to come from an external partner. You should also think about whether experience in your industry or application area is important to the project's success.
3) What relevant experience do they have?
Electronic products vary widely in terms of complexity, technology and application, from simple monitoring devices to connected industrial systems. While no development company will have designed every type of product, relevant experience can help reduce project risk and improve development efficiency.
Relevant experience may include:
Similar products or applications
Similar technologies, such as embedded software, wireless communications or high-speed digital design
Connected devices, cloud platforms and IoT systems
Compliance with industry-specific regulations
Experience in your target market or industry
Modern products often require a combination of electronics, embedded software, cloud services and user interfaces. A development partner with experience across the technologies required by your project may be able to identify potential issues earlier and provide a more integrated solution.
When assessing experience, focus not only on what products they have developed, but also on the engineering challenges they have solved and the outcomes they have delivered.
4) Do they have the resources to support your project?
The skills required to develop a modern electronic product often extend well beyond electronics design. Depending on the application, a project may require embedded software, cloud connectivity, IoT infrastructure, user interfaces, compliance testing or manufacturing support.
Before selecting a development partner, consider whether they can provide the resources needed to support your project throughout its lifecycle. A single engineer may be perfectly suited to some projects, while others may benefit from access to a broader range of specialist skills.
Consider:
Who will be carrying out the work?
Does the company offer both electronics and software development?
If the product is connected, can they support cloud services, dashboards or mobile applications?
Are additional resources available if the project expands?
What happens if a key team member becomes unavailable?
The right answer will depend on the needs of your project. Some developments require only a small amount of specialist expertise, while others benefit from a multidisciplinary team working together. A clear understanding of the resources available can help ensure the development partner can support your project from concept through to deployment.
5) How do they approach product development?
Every development company has its own approach to delivering projects. While a structured development process is important, not every project requires the same level of planning, documentation and review.
A good development partner will typically have a defined process that can be tailored to suit the size, complexity and risk of the project. Too much process can create unnecessary overhead, while too little can increase the risk of misunderstandings, missed requirements and costly rework.
Consider:
How are requirements captured and agreed?
How are assumptions and gaps in the requirements identified?
What reviews are carried out during development?
How are changes to requirements managed?
How is functional testing handled?
Understanding a company's development process can provide useful insight into how they manage quality, risk and project delivery.
6) How will the project be communicated and managed?
Communication is one of the most important factors when choosing a development partner. In our experience, projects are far more likely to run into difficulties because of misunderstandings, unclear requirements or poor communication than because of the engineering itself.
At an industry event we attended recently, engineers and MDs from several design companies discussed the most important role in a development team. Most participants agreed that the project manager (PM) is the single most important team member. While this may not apply to every project, it reflects the reality that communication, coordination and decision-making are often just as important as technical expertise.
When evaluating a potential development partner, consider:
How will progress be communicated?
Who will be your primary point of contact?
Will you have direct access to the engineers carrying out the work?
How is project information recorded and shared?
Can meetings be held in person when needed?
Location may also be a consideration. While remote working is now common, face-to-face meetings can still be valuable when defining requirements, reviewing designs or discussing complex technical issues.
Good communication works both ways. The clearer you can be about your objectives, requirements and priorities, the easier it will be for your development partner to deliver the right solution.
7) How will risks be identified and managed?
Every development project involves risk. These risks may relate to technology, requirements, costs, timescales, component availability, compliance, or key personnel.
A good development partner will actively identify and manage risks throughout the project rather than simply reacting to problems as they arise. The earlier a risk is identified, the easier and less costly it is usually to address.
Risk can be reduced in many ways, including good requirements capture, regular reviews, prototyping, testing and effective project management. It can also be reduced by building on proven software, electronics and development platforms rather than starting every aspect of a project from scratch.
When evaluating a potential development partner, consider:
How are risks identified and monitored?
How are risks communicated and managed?
What steps are taken to reduce technical and commercial uncertainty?
Can existing technology, software or proven platforms be leveraged to reduce risk?
No project is ever risk-free, but a structured approach to risk management can significantly improve the likelihood of a successful outcome.
8) What is your approach to intellectual property?
Different development companies take different approaches to intellectual property, so it is important to understand what rights you will have once the project is complete and, more importantly, what matters to your business. This comes back to the priorities and goals identified at the start of the selection process.
In practice, new products are not developed from scratch. Almost all products make use of existing technologies, software libraries, development tools, silicon vendor IP, communication stacks or hardware platforms. Some of this intellectual property may belong to the development partner, while other elements belong to component manufacturers or third-party suppliers.
The key consideration is not necessarily who owns every piece of intellectual property, but understanding what you will own and receive at the end of the project. This includes whether you will own the resulting design and receive the associated source code, design files and documentation, what rights you will have to use, maintain and further develop the product, and whether any ongoing dependencies could affect its future development.
There is rarely a single right answer. Some organisations prioritise more IP ownership and control, while others are happy to build on proven technologies and development platforms if it reduces cost, technical risk and development timescales.
When evaluating a potential development partner, consider:
Is complete ownership of all possible IP important to your business?
Would building on proven technology help reduce cost, risk or development timescales?
What rights will you have to manufacture, maintain and further develop the product in the future?
How will intellectual property and confidential information be protected?
Understanding how intellectual property and confidentiality will be managed will help ensure the chosen approach aligns with your technical, commercial and long-term business objectives.
9) What will the project cost and how will it be billed?
In the UK, custom electronics and software development projects are most commonly done on a time and materials basis due to the unknowns of development. Consequently, the total cost will vary depending on the engineering rate and the effort needed to complete the work.
Experienced contract engineers typically charge between £60 and £100 per hour, depending on skill set and experience, with development companies often charging somewhat more.
It may be tempting to choose the cheapest supplier you can find, but this can be a false economy. A more experienced engineer or development team may save money in the long run by completing the work more efficiently and avoiding costly mistakes. Problems identified after the design is complete often cost far more than any savings made by selecting a lower-cost supplier.
You should also consider the resources available to the development company. Experienced staff, test equipment, premium CAD software, project management systems and proven technologies all come at a cost, but they can also improve quality, reduce risk and shorten development timescales.
A development partner should be able to provide a realistic estimate together with a breakdown of the expected costs and assumptions.
When comparing estimates, it is important to understand exactly what is included. Differences in engineering effort, project management, testing, documentation, support and project scope all have a significant impact on the final cost. A lower estimate is not always the most cost-effective option if important activities have been excluded.
Understanding how different suppliers arrived at their estimates will help you make a more informed comparison and assess whether the proposed approach aligns with the needs of your project.
10) What are the deliverables?
It is important to understand exactly what will be delivered and what is included within the scope of the estimate. Hopefully, the estimate will have a clear section outlining both scope and deliverables.
Commonly, different companies may understand your brief differently, and not all may be estimating for the same project and deliverables. This is where your communication and design brief must be clear from the outset. Make sure you are comparing apples to apples and ask if you are not sure about something.
Deliverables may include prototypes, source code, design files, documentation, manufacturing data, test reports, compliance support or production assistance. It is also important to understand what rights you will have to use, maintain and develop the resulting product in the future.
Understanding exactly what will be delivered will help you make a fair comparison between suppliers and choose the partner that best aligns with your project's objectives.
Conclusion
Choosing the right electronics and software development partner is one of the most important decisions you will make. The right partner can help reduce risk, provide access to valuable engineering expertise and improve the likelihood of a successful outcome.
There is rarely a single "right" choice. The most suitable development partner will depend on your project, your organisation's priorities and the skills and resources you already have available. By understanding your own requirements and asking the right questions, you will be better placed to evaluate potential suppliers and select a company that is a good fit for your project.
Taking the time to consider topics such as experience, resources, risk management, communication, intellectual property, project costs and deliverables can help avoid misunderstandings and improve the chances of a successful development programme.
We hope these questions provide a useful framework for evaluating potential development partners and selecting the company best suited to your next product development project.
If you think Ripcord Design could be a good fit for your next electronics development project, please contact us.