What should a Head of Product demand from a wearable development partner at each project milestone?

A wearable development partner should deliver clear, verifiable outputs at every project milestone: from a technically grounded feasibility assessment at discovery, through functional prototypes with documented performance data, to a production-ready design package with certification evidence. The specific demands shift at each phase, but the underlying standard stays the same — no assumptions, no black boxes, and no surprises when the budget is already committed. This article works through the six milestone questions every Head of Product should be asking before signing off on the next phase.

What should a wearable development partner deliver at the discovery phase?

At the discovery phase, a wearable development partner should deliver a structured feasibility assessment that identifies which technologies are viable for your application, flags the risks that could derail the project later, and gives you a realistic picture of cost and timeline before any significant budget is committed. This is not a sales pitch dressed up as analysis — it is a technical document with a clear recommendation.

Discovery is where the most expensive mistakes in custom wearable product development are made, and almost all of them stem from the same cause: moving into prototyping before the technical foundations have been stress-tested. A credible partner will challenge your assumptions about components, materials, and form factor at this stage — not validate them uncritically.

What a strong discovery deliverable looks like in practice:

• A written assessment of which sensing, actuation, or integration techniques are appropriate for your specific use case
• An honest evaluation of whether off-the-shelf components can meet your requirements or whether custom development is unavoidable
• A preliminary view on certification implications — particularly if you are developing in the medical or defence space, where MDR compliance or military standards will shape hardware decisions from day one
• A phased cost estimate with explicit assumptions, so you know exactly what would change that number
• A clear go/no-go recommendation with the reasoning behind it

A feasibility check that runs one to four weeks and surfaces a genuine technical risk is worth far more than a fast-tracked entry into prototyping that collapses six months later. If a partner cannot produce this level of rigour at discovery, that is the signal to stop before the real money starts moving.

How should a development partner demonstrate progress during prototyping?

During prototyping, a wearable development partner should demonstrate progress through working hardware at defined intervals, not status updates and slide decks. Each prototype iteration should be accompanied by documented performance data, a clear list of what was tested, what passed, what failed, and what the next iteration will address.

Wearable prototyping is inherently iterative — the first functional sample will not be the last, and that is expected. What separates a reliable partner from a risky one is whether the iteration is disciplined or chaotic. A structured approach to wearable prototyping typically moves through two distinct stages before reaching final prototypes.

Pilot samples: exploring the design space

Early pilot samples (typically two to ten units) are built to test specific hypotheses about form factor, sensor placement, actuator behaviour, or material compatibility. They are not meant to look finished — they are meant to answer specific questions quickly. A good partner will tell you exactly which questions each build is designed to answer, and will not move to the next iteration until those questions have a documented answer.

Final prototypes: validating the complete system

Final prototypes, usually five to thirty units, should carry all required features in the intended form factor and be suitable for uncontrolled user testing. At this stage, the partner should be able to show you performance data under realistic conditions — not just bench tests. For biometric wearable product development in particular, this means sensor data collected on moving users, not mannequins or static rigs.

Throughout prototyping, a partner working with an Agile development methodology will give you sprint-level visibility into what was built, what was learned, and what the next sprint prioritises. If you cannot get that level of transparency, you are carrying more project risk than you should.

What does good user testing support look like from a wearable partner?

Good user testing support from a wearable development partner means the partner actively contributes to test design, helps recruit or structure the right user cohort, and translates raw user feedback into specific engineering actions — not just a report that lands on your desk. The partner should treat user testing as a technical milestone, not a box to tick.

This is where many wearable projects lose momentum. A prototype that performs well in the lab fails in user testing because nobody asked the right questions about comfort, donning time, sweat resistance, or how the device behaves during the actual movements a real user makes. A partner with genuine experience in wearable product development services will have encountered these failure modes before and will design the test protocol to surface them early.

Specifically, look for a partner who can:

• Define measurable acceptance criteria for the user test before it starts, not after
• Identify which failure modes are most likely given the device type and user population
• Instrument the prototypes to capture objective data alongside subjective user feedback
• Separate comfort and usability issues from technical issues — these require different fixes
• Produce a prioritised list of design changes with a rationale for each, ready to feed directly into the next development phase

For medical wearables in particular, user testing is not just a product quality exercise — it is part of the clinical evidence required for regulatory submission. A partner who understands MDR requirements will structure user testing with that downstream obligation in mind from the start.

Which certifications should a development partner own versus guide?

A wearable development partner should own the technical preparation for certification — hardware design choices, documentation, testing protocols, and risk management files — while the legal responsibility for placing a product on the market remains with the manufacturer of record, which is typically the client. The partner’s job is to make sure the product is certifiable, not to absorb your regulatory liability.

The practical distinction matters enormously in sectors like medical devices, defence, and hazardous environments. CE marking under the EU Medical Device Regulation (MDR) for a Class II wearable requires a technical file that reflects design decisions made throughout development — not a document assembled at the end. If your development partner is not thinking about MDR compliance during hardware selection and firmware architecture, you will pay for that oversight later in redesign costs and delays.

What a capable partner should be able to demonstrate:

• Hands-on experience preparing technical documentation for the certification classes relevant to your product (MDR Class I/II, CE marking, ATEX for hazardous environments, or military certification standards)
• A clear understanding of which design decisions are certification-critical and why
• Relationships with notified bodies or test laboratories, so they can advise on realistic timelines and costs
• A risk management process that runs in parallel with development, not as a retrospective exercise

ATEX and military certification add substantial cost and documentation burden. A partner who has not navigated these before will underestimate both. Ask for specific examples of products they have taken through certification, and ask what went wrong — the answer will tell you more than a list of credentials.

What should a partner prove before production handoff?

Before handing off to production, a wearable development partner should prove that the design is manufacturable at your target volume, that the bill of materials is stable, that the product meets its performance specification under real-world conditions, and that all documentation required for external production is complete. A first series of thirty to fifty units produced in-house is the standard mechanism for proving this.

This is the stage where the gap between a capable development partner and a capable manufacturer becomes visible. Many organisations that can build a working prototype cannot produce a first series that an external manufacturer can replicate reliably. The difference lies in design-for-manufacture decisions, component sourcing discipline, and the quality of production documentation.

Before signing off on production handoff, demand evidence of the following:

1. Validated performance data from the first series — not from lab prototypes, but from units built using the same processes an external manufacturer will use
2. A stable and sourced bill of materials — with confirmed lead times and identified alternatives for components at supply risk
3. Complete production documentation — assembly instructions, test procedures, quality control criteria, and firmware flashing protocols
4. Yield data from the first series run — what percentage of units passed first-time quality checks, and what the failure modes were
5. A clear handoff protocol — including who owns what during the transition, and what the partner’s role is if defects emerge post-handoff

Tooling costs for wearable production can reach hundreds of thousands of euros. The purpose of a disciplined first series is to validate that those costs are justified before they are committed. A partner who pushes to skip this stage is transferring risk to you.

How do you evaluate whether a wearable development partner is the right long-term fit?

A wearable development partner is the right long-term fit if they have demonstrated the ability to move with you across multiple development phases, can absorb increasing technical complexity as your product matures, and treat your product roadmap as a shared responsibility rather than a series of discrete contracts. The clearest signal is whether they surface problems early or manage them quietly until they become your problem.

Long-term fit in wearable prototyping and production services is not primarily about cultural alignment or communication style — though both matter. It is about whether the partner’s technical depth matches the complexity your product will accumulate over time. A team that is excellent at proof-of-concept work but lacks certification experience, or is strong on hardware but thin on firmware, will become a bottleneck as your product matures.

Evaluate long-term fit against these criteria:

• Disciplinary coverage: Does the partner have genuine in-house expertise across hardware, firmware, textile integration, and human factors — or do they subcontract critical disciplines to parties you have no visibility into?
• Sector depth: Have they developed products in your specific domain — medical, defence, sports, or industrial safety — and can they speak to the regulatory and user environment you operate in?
• Transparency under pressure: Ask them to describe a project that went wrong and how they handled it. A partner who cannot answer this question honestly is not a partner you want managing your production handoff.
• Roadmap thinking: Are they asking about your product roadmap beyond the current phase, or are they scoping only the immediate deliverable? A genuine development partner thinks in product lifecycles, not project sprints.
• IP and commercial terms: Understand who owns the intellectual property in the result and under what conditions. Default arrangements vary — make sure the terms match your commercialisation plans before the project starts.

The partners most likely to become genuine long-term collaborators are those who tell you what you need to hear at discovery, not what you want to hear. That honesty at the start of the relationship is the best predictor of reliability when the project gets difficult.

How Elitac Wearables supports every milestone in your development journey

Elitac Wearables is built specifically for the kind of technically complex, multi-phase wearable development that this article describes. As a Head of Product, you need a partner who can hold the full picture — from feasibility through to a certified, manufacturable product — without handing off critical disciplines to parties outside your line of sight. That is exactly how Elitac operates.

Here is what working with Elitac looks like in practice:

• Discovery and feasibility: A structured feasibility check that surfaces real technical risks and gives you a cost estimate grounded in actual development assumptions — not a sales number
• Prototyping with full discipline coverage: Hardware, firmware, textile integration, biosignal sensing, haptics, and human factors all managed in-house, using the proprietary TacOS firmware platform to reduce iteration time and cost
• User testing support: Test design, instrumentation, and engineering translation of user feedback — structured with downstream certification requirements in mind for medical and regulated applications
• Certification preparation: Hands-on experience with MDR (Class I and II), CE marking, ATEX, and military certification standards, built into the development process from the first phase
• First series and production handoff: In-house production of thirty to fifty units to validate manufacturability, followed by complete documentation for external scale-up
• Long-term partnership: Elitac works as an extension of your team across the full product lifecycle, with the cross-sector experience — medical, defence, sports, industrial safety — to match your roadmap as it grows

If you are at any stage of a wearable development project and need a partner with the technical depth to take it forward, contact Elitac Wearables to discuss your requirements directly with the team.

Related Articles

• What hardware components power haptic feedback in wearables?
• How do you build a wearable product business case that gets board-level buy-in?
• How do you choose the right hardware for a wearable device?
• How long does wearable product development take?
• What are the biggest challenges in wearable product development?