Your idea, running on real hardware in eight weeks.

Board, firmware, on-device AI, cloud and app — built by one team, on one contract, in China. You leave with working units you can put in an investor's hands.

5 unitsAssembled, cased, demo-ready
Source includedFirmware, backend, app
Costed BOMAt 1k, 10k and 100k
Fixed pricePublished before you email us

What lands on your desk

Not a render and not a deck. Hardware someone can pick up, switch on, and form an opinion about.

Bench, week six. The enclosure is still printed and the cable management is a disgrace, but it boots, it listens, and it answers.

Most of this job is finding out what does not work.The schedule holds because we fail early and in public — a demo every Friday, on the actual hardware, including the weeks when it barely runs.

Eight weeks, week by week

The clock starts when the spec is locked, not when you first email us. That is why Sprint 0 comes first.

Weeks 1–2

Lock the spec

Chip selection, the on-device versus cloud split, a bill of materials with real quotes, and the certification path.

Weeks 3–4

Bring up the board

First assembly back from the line. Power rails and peripherals verified, firmware skeleton talking to all of it.

Weeks 5–6

Make it think

Model quantised and running on target. Wake word, latency and power budget tuned. Cloud and app wired in.

Week 7

Give it a body

Printed or machined enclosure, full integration, and the rough edges filed down until it survives being handled.

Week 8

Hand it over

Five units in a case, a demo that holds up on stage, and an honest account of what breaks at volume.

Five disciplines, one invoice

Most AI hardware stalls in the gaps between vendors. The firmware house blames the ODM, the ODM blames the model team, and the launch slips two quarters.

Embedded

ESP32 through RK3588. Bring-up, drivers, RTOS and Linux, power budgets.

On-device AI

Quantisation, NPU deployment, wake word, streaming speech, latency work.

Cloud

Device management, OTA, model orchestration, cost control, data residency.

Hardware

Schematic, layout, mechanical, enclosure, EVT-ready design files.

Mobile

Pairing, provisioning, and the app your beta users will actually judge you on.

Eight weeks is not us working faster. It is nobody waiting on a handover. Chip selection and model selection happen in the same meeting — and on a device with a fifteen-dollar bill of materials, that is the meeting that decides whether the product can exist at all.

Prices published, before you ask

Every stage credits into the next. You will know the number before you write the first email.

Stage one

Sprint 0

$Explore
Two weeks
  • Architecture and chip comparison
  • Bill of materials with quoted parts
  • On-device versus cloud cost model
  • Certification and compliance path
  • A fixed quote for stage two
Start here
Stage two

Proof build

$Scope
Eight weeks
  • Everything on the deliverables list
  • A weekly demo on real hardware
  • Sprint 0 credited in full
  • Your engineers in our repository from week one
Scope a build
Stage three

To production

Quoted
By programme
  • EVT, DVT and PVT
  • CE, FCC, UL, battery transport
  • Factory selection and transfer
  • Or a per-device firmware licence if you build elsewhere
Talk it through

Sprint 0 is paid work, and worth doing even if you then hire someone else. Two weeks of honest costing is cheaper than eight months of discovering the product cannot be built at your price.

Tell us what you are trying to build.

A paragraph is enough. You will hear back from an engineer within one business day — either to book a scoping call, or to say plainly that this is not a good fit for us.

Send the brief