Karlis A.
Hardware Architect | Embedded Firmware | PCB | Robotics | DFM
Most hardware products don't fail at the idea โ they fail at execution. I lead architecture, embedded, and firmware work for founders building hardware that has to ship at production, not just demo. I'm Karlis, principal engineer and founder of null2.one โ a small senior studio for 0โ1 hardware product work. We work with founders, scale-ups, and engineering teams where the cost of a wrong technical decision is months and six figures. Where I'm strongest โ Hardware product architecture โ Embedded systems and firmware (STM32, ESP32, nRF, Linux) โ Power electronics, battery, USB-PD, thermal โ Sensors and closed-loop control โ Robotics and mechatronics โ DFM and industrialization (EVT โ DVT โ PVT) What I actually solve โ "Our prototype works on the bench but won't survive a factory." โ "We've burned months on the wrong architecture and need to reset before raising again." โ "We're juggling four freelancers and have no senior technical owner." โ "We need to validate the risky paths before committing to tooling and certifications." โ "Our BOM looks fine on paper and is unmanufacturable at volume." How I work โ three phases, fixed scope, fixed price 01. Product Definition & Architecture โ 4 to 8 weeks Turn product ambiguity into explicit architectural, commercial, and production decisions before execution begins. Output: a product definition that survives contact with production. 02. Prototype & Validation โ 6 to 14 weeks Architecture-first prototyping that surfaces real constraints early. EVT-grade hardware with a clear path to production. Firmware, electronics, and mechanical integrated into one validated system. 03. Production Readiness & Industrialization โ 8 to 20 weeks Design for manufacturing, supplier selection, EVT/DVT/PVT gate support, end-of-line test strategy, clean handoff to manufacturing. The work that decides whether first-run yield holds. Every engagement starts with Phase 01. No exceptions. You decide whether to continue to the next phase based on what comes out of the previous one. Indicative pricing (USD) โ Phase 01 โ Definition & Architecture: $8kโ$25k โ Phase 02 โ Prototype & Validation: $35kโ$120k โ Phase 03 โ Production Readiness: $60kโ$250k+ Background โ Principal engineer & founder, null2.one โ Senior Product Manager, Aerones โ robotics for wind-turbine inspection and maintenance โ CTO & CCO, NovaticLab โ patent-pending robotic automation โ BEng, VIA University College, Denmark โ 10+ years across robotics, embedded, IoT, wearables, ruggedized industrial hardware Why this works You stop paying for time and start paying for outcomes. Each phase has a defined deliverable and a price agreed before any engineering begins. You decide whether to continue at every gate โ no open-ended retainers, no scope drift. Everything we produce belongs to you: architecture, design files, firmware, test procedures, supplier relationships. No IP lock-in. Who I work with โ Hardware founders who need clarity and a real architecture before raising or building โ Scale-ups who need deep technical execution on a critical system โ Funded startups where the next architecture decision is worth six figures of avoided rework โ Engineering teams that need senior system-level leadership without hiring a CTO Not a fit โ Pure SaaS or web work โ "Can you just build this?" hourly task work โ Sub-$5k scopes โ Buyers shopping primarily on price โ Branding or marketing-only engagements Next step If you have a hardware product where the technical decisions are expensive to get wrong, send the job invite. I respond within one business day with an honest read on whether we're a fit. If we are, we scope a Phase 01 โ fixed price, defined deliverable, no commitment beyond that.