Questions we are often asked

After the discovery call, once we have understood the full requirement. Two projects that sound alike can differ a lot in scope: how many units, which certifications, whether the hardware exists yet, how much of the cloud side you already have. We would rather ask those questions first than give a number that changes later.

You talk to an engineer for about 30 minutes about what you are building, where it stands and what is blocking it. We ask about the environment the product will live in, the volumes you expect and what "done" means for you. After the call we send a short written follow-up and share our project history, so you can see the kind of work we have done.

Nothing formal. A few lines on the product, photos of an existing prototype or machine if you have one, and any spec or tender document. If something is confidential, keep it back until an NDA is in place.

An engineer replies within 48 hours to set up the call. If it is urgent, call or message us on WhatsApp.

Yes, and it is a common way for work to start with us. We begin with a review of the schematics, layout files and firmware you already have, and tell you what we would keep, what we would change, and why. Sometimes the answer is that only a few fixes are needed.

Both. We build proof-of-concept units (more than 300 so far), then take designs through the changes production needs: test points and test jigs, a production BoM with second sources, firmware with over-the-air updates, and the handover pack your manufacturer works from. More than 500,000 production units have been built on our designs.

Yes. We work with clients across the world, mostly remotely, with visits when a project needs them. Calls can be scheduled across time zones.

It is agreed project by project and written into the contract before work starts. We will go through the options with you on the call, so you know exactly what you receive at handover.

Yes to both. We can prepare files to your manufacturer's rules and support the first build, or suggest manufacturers in India that suit your volumes and the type of board.

Yes. Training is a large part of what we do, for companies and for colleges, with more than 1,000 engineers and students trained so far. If we build something for you, we can run sessions for your team on the hardware, the firmware and the tools, so they can maintain it themselves.

That is fine. Many projects use us for one layer: a board design, firmware for an existing board, a cloud backend for devices that already work, or a dashboard. We will tell you on the call if we think another layer will cause problems later.