M TWELVE

Embedded engineering studio

Embedded firmware and production tooling for products that need to ship.

M TWELVE helps product teams deliver robust embedded systems across firmware, ultra-low-power design, connectivity, TouchGFX HMIs, and lean Windows tools for factory, diagnostics, flashing, and test.

Start your project brief Review selected work
  • Founder-led, senior engineering delivery
  • Built for real constraints: power, reliability, manufacturing
  • Available for new development and troubled project recovery
C/C++ESP32nRF52STM32FreeRTOSBLEWi-FiCANTouchGFXOpenCVWinAPIAWS IoT

Engineering-first partner

Technical decisions are made around reliability, bring-up speed, and long-term maintainability.

Production-ready mindset

Development includes validation and manufacturing realities, not just demo firmware.

Fast, direct communication

Concise updates, weekly demos, and clear next actions for CTOs and engineering managers.

Services

Specialized embedded engineering services

Focused support where teams usually lose time: firmware architecture, power budgets, connectivity reliability, HMI flow, and factory tooling.

Embedded firmware

New firmware and refactors for C/C++ projects on ESP32, nRF52, STM32, and FreeRTOS-based systems.

Connectivity systems

BLE, Wi-Fi, and CAN stacks with robust retries, secure pairing/provisioning, and field diagnostics.

Ultra-low-power and signal processing

Power state design, wake strategies, FFT/filtering pipelines, and sensor-driven edge logic.

TouchGFX and HMI

Production HMIs that stay readable, responsive, and stable under real device constraints.

Windows production tooling

Lean desktop apps for flashing, calibration, diagnostics, data capture, and operator workflows.

Consulting and project rescue

Takeover of troubled firmware efforts, root-cause analysis, stabilization plans, and execution support.

Selected work

Concrete embedded projects, not generic case blurbs

Representative examples of projects delivered under tight power, timing, and production constraints.

Working-hours counter beacon

Context: CR2032-powered beacon needed long life while measuring machine run-time in noisy environments.

Solution: Implemented ultra-low-power firmware on nRF52833 with vibration wake-up, magnetometer FFT processing, and BLE telemetry.

Outcome: Practical battery-constrained operation with reliable runtime measurement for maintenance planning.

Tech: C/C++, nRF52833, BLE, FFT, low-power state design

Connected piggy bank platform

Context: Consumer product requiring secure local + cloud connectivity, sensor inputs, and interactive UI behavior.

Solution: Built ESP32 firmware with encrypted BLE, Wi-Fi connectivity, IMU/LCD handling, and AWS integration patterns.

Outcome: Stable connected experience with architecture suitable for production expansion.

Tech: ESP32, BLE, Wi-Fi, AWS IoT, IMU, LCD

Lift controller TouchGFX HMI

Context: Industrial lift controller needed a robust operator interface and live parameter control over field buses.

Solution: Delivered TouchGFX HMI communicating over CAN, with clear state handling and device feedback loops.

Outcome: Improved operator usability and safer controller configuration in deployment.

Tech: TouchGFX, STM32-class MCU, CAN, embedded UI architecture

Production-line OpenCV inspection tool

Context: Manufacturing flow needed fast visual quality checks without introducing heavy, complex software.

Solution: Built a lean Windows/OpenCV app for image processing, defect detection, and operator-friendly review.

Outcome: Faster production validation with actionable defect signals during line operation.

Tech: C/C++, OpenCV, WinAPI, multithreaded processing

Custom Windows factory and diagnostics tools

Context: Product teams needed reliable internal tools for flashing, data capture, and field diagnostics.

Solution: Delivered purpose-built desktop utilities aligned with production and service workflows.

Outcome: Less manual work, clearer diagnostics, and smoother manufacturing/test operations.

Tech: WinAPI, device protocols, test workflow automation

Why M TWELVE

A technical partner built for hard delivery constraints

Firmware plus desktop tooling in one partner

Few teams cover embedded firmware and factory-facing Windows tools with equal rigor. This reduces integration friction and handoff risk.

Practical low-power and signal expertise

Power budgets and sensor logic are treated as core architecture concerns, not late optimizations.

Clean handover for internal teams

Delivery includes maintainable code paths, documentation, and predictable communication cadence.

New builds and rescue engagements

Works with both fresh product plans and inherited projects that are behind schedule or unstable.

Process

A straightforward delivery model

01

Discovery

Review hardware, firmware state, constraints, timelines, and business priorities.

02

Proposal and milestones

Define scope, delivery phases, acceptance criteria, and collaboration rhythm.

03

Build and weekly demos

Execute in short cycles with transparent progress, decisions, and risk handling.

04

Validation and handover

Verify behavior on target hardware and provide transfer-ready outputs for your team.

About

Founder-led embedded engineering studio

M TWELVE is based in the EU (Croatia, CET) and works remotely or on-site. The studio focuses on practical engineering execution for teams building connected and embedded products.

Working style

  • Direct communication with technical decision makers
  • Clear scope and visible weekly progress
  • No inflated process overhead
  • Delivery built for maintainability after handover

FAQ

Common questions before kickoff

What projects are a strong fit?

Embedded products that need reliable firmware delivery, power optimization, connectivity robustness, HMI work, or production-support tooling.

Can you work with our existing engineering team?

Yes. Engagements are often collaborative with internal firmware, hardware, QA, or manufacturing teams.

Can you take over a troubled firmware project?

Yes. Rescue work typically starts with a focused technical audit, risk map, and a stabilization plan.

Do you build production and diagnostics tools?

Yes. Windows tools for flashing, diagnostics, calibration, and data capture are a core service area.

How do engagements usually start?

Start with a concise brief. After initial review, you get a recommendation on scope and next technical steps.

Contact

Share your project brief

For faster qualification, include product type, current blockers, target timeline, and who will own technical decisions.

Useful details to include

  • Hardware platform and current firmware status
  • Top risks: power, connectivity, reliability, manufacturing, or schedule
  • Key dates: prototype freeze, pilot build, production start
  • Preferred engagement model and weekly availability

Typical response: within one business day (CET).

Project brief form

Secure Google Form intake with M TWELVE review within one business day.

Talk to an embedded engineer