Contact

What helps in a first message

• What the product or system is, in a sentence or two.
• What stage it is at: concept, prototype, pre-production, or a fielded product with a problem.
• What you need from us. If it maps to one of our services, say which; if not, describe the problem.
• Constraints that matter: schedule, budget range, certification targets, existing toolchains.

If the work is confidential, say so and we will sign an NDA before details are shared.

How a project runs

1. First conversation. A call or email exchange, usually within a couple of days of your message. We ask about the product, the stage it is at, what has been tried and what the schedule looks like. No charge, no obligation.
2. Written scope. For anything beyond a short review we send a scope document: what we will deliver, what we assume about inputs from you, milestones, price basis and schedule. You mark it up until it is right. For larger or uncertain work we may propose a short paid discovery phase first so the main scope accurately captures the project complexity.
3. Agreement and NDA. A short services agreement covering IP, confidentiality and payment terms. We sign your NDA or supply ours.
4. Delivery in milestones. Work is broken into milestones with a demonstrable result at each one: a schematic review, a board bring-up, a firmware release on real hardware, a test report. You see progress on a regular cadence.
5. After delivery. A support window for questions on what was delivered is included. Ongoing support or further phases are scoped separately.

Engagement models

• Scoped projects. A defined deliverable at a fixed or capped price: a board, a firmware release, a test fixture, an architecture review.
• Ongoing development. Time-and-materials work as an extension of your team, typically in weekly or monthly blocks.
• Reviews and short assessments. A few days to look at a design, a codebase or a failure and provide a written assessment and recommended plan.