Skip to content

Frequently Asked Questions

We do offer and require a feasibility study on every project. This study will help both of us judge whether or not expectations about the project are real. Sort of like an independent point of view on your project. The study will be tailor made to meet your needs. This study will  give us an overview of the product, competition, patent research, possible insight on problems, block diagrams on your device, preliminary schematics, etc.

Now some projects are simply beyond our knowledge, or perhaps a little to big. We ask that you please do not submit projects of the following nature to IMRC TECH:

  • Bombs
  • New personal computer designs (there are just too many of these already!)
  • Aviation systems
  • Life support equipment (we can design the hardware and software but we are not going to be the responsible party to the end user)

Simple projects have less risk than complex  projects. Let's be real, there is a law called Murphy's law. Murphy's law is a popular adage in Western culture that most likely originated at Edwards Air Force Base in 1948. The Law broadly states that things will go wrong in any given situation, if you give them a chance. "If there's more than one way to do a job and one of those ways will result in disaster, then somebody will do it that way." It is most often cited as "Whatever can go wrong will go wrong" or alternately, "Whatever can go wrong will go wrong and at the worst possible time.

We try to minimize risks as much as possible. We do this by following internal procedures and utilizing software such as Microsoft project. Even with all that we can do, we have no control of part makers or suppliers. They can stop making parts even when they say were going to make this part forever. We do not guarantee that a part will exist. We can and will, in most cases, be able to substitute or design in another part. Development is a set of hurtles we must overcome. Sometimes life throws in other hurtles. We are used to this and simply jump over them or steer around them. Planning, perseverance, and commitment are other methods of reducing risk. Unfortunately these risks sometime cost time and money. So if you are not willing to take some risk do not start a project.

Simple projects might be things like an interval timer that turns something on and off, a low-end amplifier or a solar-powered illuminated house address. 

Mid-level complexity type projects are things like calculators, remote controls or anything with a microcontroller.  These types of projects take more time to finish. For mid-level projects it's best if the end product will be mass-produced or perform some truly critical function. Development time will probably range from one to six months.

High-level complexity type projects would include computer add-on cards or peripherals, measuring instruments, anything with an FPGA, 32bit processor or robots (very serious).  Multiple prototypes would likely be produced and then fine-tuned. Costs for projects like this will range from the price of a high-end car to that of a luxury house.

A mid-level or  high-level complexity type projects allows us to focus more creative ability on the design which makes for a better outcome.

Every project is different. Costs will be estimated on a per project basis. Let's take for example a mid-level development project. Costs for projects like this will range from the price of a high-end car to that of a luxury house. When we do larger projects we suggest that you have some sort of financing in place. This financing  will give you a method to amortize the cost of a project over a longer period of time. It will also help you with maintaining your cash flow during complicated long development cycles. This method is similar to a construction loan. We can use it to develop a series of benchmark (payments). This method also helps minimize your risks.

Simple projects  can often be turned out in a few months or less.  Mid-level development project time will probably range from one to six months. High-level complexity type projects require months or years of development time and a great deal of information exchange and funding.

A Non-Disclosure Agreement (NDA), also called a Confidential Disclosure Agreement (CDA), Confidentiality Agreement or Secrecy Agreement, is a legal contract between at least two parties which outlines confidential materials or knowledge the parties wish to share with one another for certain purposes, but wish to restrict from generalized use. In other words, it is a contract through which the parties agree not to disclose information covered by the agreement. An NDA creates a confidential relationship between the parties to protect any type of trade secret. As such, an NDA can protect non-public business information.

An NDA is commonly signed when two companies or individuals are considering doing business together and need to understand the processes used in one another's businesses solely for the purpose of evaluating the potential business relationship. An NDA can be "mutual", meaning both parties are restricted in their use of the materials provided, or they can only restrict a single party.

It is also possible for an employee to sign an NDA or NDA-like agreement with a company at the time of hiring, in fact some employment agreements will include a clause restricting "confidential information" in general.

To license or grant a license is to give permission. A licence (British Spelling) or license (American Spelling) is the document demonstrating that permission. A license may be granted by a party ("licensor") to another party ("licensee") as an element of an agreement between those parties. A shorthand definition of a license is "a promise (by the licensor) not to sue (the licensee)."  In some instances we will require you  to purchase a license for intellectual property we have already created. It is best to accept this procedure other than reinvent the wheel. If you have some intellectual property you want us to substitute please advise us up front. These types of things must be handled by a formal letter notifying us of such.

No, we do not manufacture at our location, we work with outside contractors to manufacture devices in quantity. We build some prototype and mid level designs on site. All of the design work is done on sight. Each design utilizes best practices available at the time.

We like to choose fairly new parts and Integrated circuits. Mostly all designs are going to surface mount or BGA type Integrated circuits. We do however have a great flexibility of parts and parts types available and would be happy to advise you on these issues. We use mostly surface mount parts. We also can use thru hole parts. We can utilize parts you may already have, but we must know up front if they are to be used.

Design specifications are like a set of detailed plans on what we are to build. We have a general questionnaire that helps with specifications. We can also offer you assistance in developing these specifications. There are costs associated with specifications. These costs vary on the complexity of the project.

Simply yes, we need design specifications to know exactly what you want built. Could you build a house without plans? We want to serve you to the best of our ability. It is required that a detailed design specification is done before the development starts.

Whenever a project is being developed, it is expected and embraced that the client will want to make changes. We expect these changes and want to comply with your needs for customization of your product. It is possible to change anything in the design whenever you would like. Any change must be proposed to IMRC TECH in writing and all changes will be considered by IMRC TECH and may result in extra work. If IMRC TECH deems it extra work, the additional cost will be calculated and approved by the customer before any changes are made. All changes will bill out at standard hourly rates. These changes will add time to the project (sometimes significantly), but it is usually worth the extra effort because you get exactly what you want out of the development.

Yes, there needs to be a development agreement in order to protect you, our dear customers, and to protect ourselves. IMRC TECH has in place a standard development agreement. We will prepare this agreement for you when you decide to have us develop your project. This agreement  is very complete and will save you time and money on attorneys. All the boiler plate legal stuff is in there already. We simply fill in the blanks of what you want built, deliverables, and an estimated time to completion.  All terms and payments to be made to IMRC TECH are included in this agreement.

No. It is a standard industry practice to make new devices in steps. These steps take the name of board revisions. All projects have revisions and changes. Some revisions reflect design creativity. It is the same thing as writing an important letter; you may rip it up and do it again. Even NASA has revisions.

Currently we have 2 full time people. We also have associates that work with us to get your job done. These associates range from parts suppliers to contract manufactures. 

We are small enough to provide very personalized services and smart enough to delegate projects to a top notch team of outside “go to” vendors and subcontractors.

We use a Design and Manage Strategy theory in our projects and designs.

Scroll To Top