A wearable becomes a real product through two linked disciplines, and pcb design and firmware development for wearables is the pairing that turns a concept sketch into hardware you can charge, strap on and ship. The printed circuit board is the physical body: the board that holds the processor, the radio, the sensors, the battery management and the antenna inside a shape a person will tolerate on their wrist, chest or ear. The firmware is the behaviour: the code that lives on that processor and decides when to sample a sensor, when to wake the radio, when to sleep and how long the battery lasts. Neither one is finished until the other proves it works.
Most founders and operators we meet have a clear picture of the finished product and a fuzzy picture of the path to it. This article walks that path in order, with the timelines, cost ranges and decision points a non-technical owner needs to budget and plan. If you want the short version: a first working wearable prototype is usually a four to seven month effort, and the money splits roughly evenly between the board and the code.
What PCB Design and Firmware Development for Wearables Really Involves
It involves designing a circuit board small enough to hide inside a comfortable enclosure, then writing embedded software that squeezes useful behaviour out of a battery the size of a coin. Everything difficult about pcb design and firmware development for wearables comes from that one constraint pair: very little space and very little power. A desktop product can be generous with both. A wearable cannot.
The Board: Where Physics Sets the Rules
A wearable board is typically four to eight copper layers stacked in a rigid or rigid-flex sandwich, often under 25mm across. Onto that you place a microcontroller, a Bluetooth Low Energy radio, an antenna, a power management chip, a charging circuit, and whatever sensors the product exists to read. Every one of those parts competes for the same square millimetres, and some of them actively interfere with each other. A switching power regulator placed too close to an analogue heart-rate sensor injects noise into the exact signal the product sells. An antenna routed too close to the battery loses range. Board layout is the discipline of arranging those conflicts so none of them wins.
The Firmware: Where the Product Actually Behaves
Firmware is the code written directly onto the microcontroller, with no operating system in the way most of the time. It handles the sensor sampling loop, the Bluetooth connection to a phone, the storage of readings when the phone is out of range, the battery gauge, the firmware update mechanism and the recovery path when something goes wrong in a customer’s hands. On a wearable, the single biggest firmware job is power discipline. The processor spends more than 99% of its life asleep, and the skill is in waking it as briefly as possible. A competent power-aware firmware build routinely gets three to ten times the battery life of a naive one on identical hardware, which is why we treat pcb design and firmware development for wearables as one engagement rather than two suppliers.
Stage One: Requirements Before Anyone Opens a CAD Tool
The first stage produces a written specification, not a drawing. It sounds like a formality and it is the cheapest place in the whole project to make expensive decisions. Two to four weeks of structured requirements work regularly saves a board respin worth CAD 15,000 and six weeks of schedule.
The questions that determine everything downstream are blunt and business-led:
- How long must it run between charges? Seven days and ninety days are different products with different chips, not the same product tuned differently.
- What does it sense, and how accurately? Medical-grade accuracy and wellness-grade accuracy differ by an order of magnitude in component cost and in regulatory burden.
- How many units in year one? Five hundred units and fifty thousand units justify completely different manufacturing choices.
- Where does the data go? A phone app, a web dashboard, a hospital system or all three. This decides the radio, the storage size and the security model.
- Who certifies it, and where? A radio sold in Canada, the United States and the European Union faces three approval regimes.
Sound requirements work also settles the build-versus-buy line. Using a pre-certified Bluetooth module instead of a bare radio chip adds around CAD 4 to CAD 9 per unit and removes roughly CAD 30,000 and three months of radio certification from the programme. At low volumes that trade is almost always correct. Our product engineering services team makes that call with you before it becomes irreversible.
Stage Two: Schematic Capture, Layout and the First Real Boards
Stage two turns the specification into manufacturable files and a small batch of physical boards. It usually takes six to ten weeks and breaks into three steps that happen in order.
Schematic and Component Selection
The schematic is the electrical logic of the product, drawn as connections rather than positions. Component selection happens alongside it, and this is where supply chain reality bites. We check lifecycle status and real lead times on every critical part before committing, because a chip with a 46 week lead time is not a design choice, it is a delay. Expect the schematic phase to run two to three weeks for a typical sensor wearable.
Layout, Antenna Placement and the Stack-Up
Layout is where the board physically becomes a wearable. The engineer assigns every component a position and every connection a copper path, following spacing and reliability rules such as those published by IPC, the electronics industry standards body. Antenna placement is the part most likely to go wrong on a first attempt: human tissue absorbs 2.4GHz energy, so an antenna that measures perfectly on a bench can lose half its range once the device sits against skin. Good practice is to keep the antenna at the edge of the board, keep copper and battery away from it, and budget one tuning iteration.
Fabrication and Assembly of the First Batch
Ten to twenty prototype boards, fabricated and assembled, typically cost CAD 1,500 to CAD 6,000 and take ten to twenty business days depending on layer count and how exotic the parts are. Order enough that the firmware team, the mechanical team and the test bench each get their own. Boards are cheap at this stage. Waiting is not.
Stage Three: Bring-Up, Where the Code Meets the Copper
Bring-up is the first week the two halves of the project meet, and it is the single most informative week of the programme. The boards arrive, and the firmware team powers them up one subsystem at a time: first the power rails, then the processor, then the clock, then each sensor, then the radio. Nothing is assumed to work until it has been measured.
Why PCB Design and Firmware Development for Wearables Cannot Be Split Across Vendors
Because the failures do not respect the boundary. A sensor reading that drifts could be a layout problem, a firmware timing problem, or a component running outside its rated conditions. When one team owns both sides, that question is answered in an afternoon with an oscilloscope. When a board house and a software contractor own different halves, it becomes a three week argument, and we have been called in to clean up several of those. Keeping pcb design and firmware development for wearables under one roof is a scheduling decision as much as a technical one.
Firmware then builds outward from working silicon. The sensor drivers come first, then the sampling and filtering logic, then the Bluetooth service definitions that follow the profiles maintained by the Bluetooth SIG specification library, then data buffering, then over-the-air update support. Over-the-air update is not optional. It is the mechanism that lets you fix a field problem without a recall, and retrofitting it after launch is painful. Full firmware for a first-generation wearable typically runs eight to sixteen weeks, overlapping with board revisions rather than following them, which is the normal rhythm of pcb design and firmware development for wearables.
Where AI Belongs in a Wearable, and Where It Does Not
AI belongs wherever raw sensor data has to become a human-readable conclusion, and it usually belongs off the device. A wrist sensor produces a stream of numbers. The customer wants a statement: you slept poorly, your posture slipped, this machine is vibrating abnormally. Turning the first into the second is a model problem, not a firmware problem.
The practical split we recommend to most clients:
- On the device: lightweight signal processing and simple event detection, such as recognising a step or a fall, where latency matters and the maths is small enough to run in a few kilobytes.
- On the phone or in the cloud: anything involving a trained model, personalisation, trend analysis or natural language summaries, where you can retrain and improve without touching the firmware on thousands of shipped units.
That second layer is where our AI integration services connect to the hardware, and it is also where the companion experience lives. The dashboard, the account system and the mobile app that your customers actually see come from web and app development work running in parallel with the board, not after it.
Realistic Timelines and Budgets for PCB Design and Firmware Development for Wearables
A first working, demonstrable wearable prototype usually costs CAD 60,000 to CAD 180,000 and takes four to seven months. The spread depends mostly on sensor complexity and certification scope. The table below reflects typical ranges for a single-sensor Bluetooth wearable at low volume.
| Stage | Typical duration | Typical cost range (CAD) | What you hold at the end |
|---|---|---|---|
| Requirements and architecture | 2 to 4 weeks | $6,000 to $15,000 | Written spec, component shortlist, costed bill of materials |
| Schematic and board layout | 6 to 10 weeks | $12,000 to $35,000 | Manufacturing files and a reviewed design |
| Prototype fabrication and assembly | 2 to 4 weeks | $1,500 to $6,000 | 10 to 20 populated boards |
| Bring-up and firmware | 8 to 16 weeks | $25,000 to $90,000 | Working device, update mechanism, test tooling |
| Enclosure and mechanical integration | 4 to 8 weeks | $8,000 to $30,000 | Wearable housing, printed or soft-tooled |
| Radio and safety certification | 6 to 12 weeks | $8,000 to $60,000 | Legal permission to sell |
Two budget lines catch people out. The first is board revisions: plan for two, because a wearable that works perfectly on its first layout is luck rather than method, and a revision costs roughly 20% to 40% of the original layout fee. The second is certification. A design built around a pre-certified radio module sits at the bottom of that range, while a custom radio design sits at the top, and that gap is decided in week two of the project. Budgeting honestly for pcb design and firmware development for wearables means funding both revisions and certification from the start rather than discovering them at month five.
Certification and Getting to Manufacturing
Certification is legal permission to sell, and it is gated on frozen hardware and firmware. Any wearable with a radio is a regulated transmitter. In Canada that means meeting the radio standards specifications administered by Innovation, Science and Economic Development Canada, with the United States and European Union each running parallel regimes. Battery shipping rules and, for anything touching skin, biocompatibility testing come on top.
Manufacturing readiness is a separate exercise from prototyping and deserves its own budget. It covers a design-for-manufacture review, a functional test fixture so the factory can verify every unit in under thirty seconds, firmware programming and serial number provisioning on the line, and a pilot run of 100 to 500 units to find the problems that only appear at volume. Expect eight to sixteen weeks and CAD 25,000 to CAD 90,000 for that transition on a straightforward product.
How to Choose a Technical Partner
Choose a partner who will own the whole loop from schematic to shipped firmware, and who says no to things. Four questions separate a real engineering partner from a supplier who will hand you a folder of files:
- Who owns bring-up? If the answer is not a specific named engineer on their team, the project has a gap exactly where failures live.
- What is the revision plan? A partner who quotes one board spin either has not built a wearable or is not telling you the truth about the budget.
- Who owns the design files and the firmware source? You should, in writing, from day one. Ask for the escrow or repository arrangement in the contract.
- How will you prove battery life? The answer should involve measured current draw on real hardware, not a spreadsheet estimate.
At Prototype Toronto we run pcb design and firmware development for wearables as a single engagement with one engineering lead accountable for both halves, alongside the AI and digitalisation work that turns the device data into something your customers and your operations team can use. Our product engineering and prototyping service line covers the full path from a written requirement to a certified, manufacturable device.
If you are weighing a wearable concept and want a grounded view of what it will cost, how long it will take and which decisions to make first, book a free consultation with our engineering team. Bring your battery life target, your sensor list and your year-one volume, and we will give you a costed plan for pcb design and firmware development for wearables before you commit to a build.
Frequently Asked Questions
What does pcb design and firmware development for wearables actually involve?
It covers two linked jobs. The PCB design lays out the board and selects the processor, radio, sensors, battery management and the shape that fits inside the product. The firmware is the code running on that board, handling sensor readings, power states and the wireless connection. Both are specified together, because most firmware limits trace back to a hardware choice.
How long does it take to get from a schematic to a prototype that works?
Expect three to six months for a first working unit once requirements are settled. Roughly four to six weeks goes to schematic and layout, two to three weeks to board fabrication and assembly, then several weeks of bring-up and firmware work. Custom antennas, unusual sensors or a mid-project scope change extend that timeline.
What should we budget before manufacturing starts?
Engineering for pcb design and firmware development for wearables commonly lands between $40,000 and $150,000 CAD, driven by sensor count, radio choice and how much software the device needs. Add roughly $2,000 to $8,000 per board revision for small-batch fabrication and assembly. Most products go through two or three revisions before the design settles.
Why does battery life depend on the firmware and not just the battery size?
A wearable spends most of its life asleep. The board sets how little power the components can draw while idle, and the firmware sets how often the device wakes, samples and transmits. Changing a Bluetooth update from every second to every thirty seconds can multiply runtime with no hardware change at all.
Do we need wireless certification, and is there a way to reduce it?
Any product with Bluetooth or Wi-Fi needs radio certification before sale, ISED in Canada and FCC in the United States. Using a pre-certified radio module instead of a bare chip removes most radio testing and usually cuts certification to a few thousand dollars and a few weeks. The tradeoff is a slightly higher unit cost.
Many redesigns start with early choices on fit, battery and enclosure. Read about avoiding costly redesigns in wearable device development.
