Product Creation Studio vs Very: full comparison for 2026
Quick verdict
Product Creation Studio (4.5/5) edges ahead of Very (4.2/5) overall. Product Creation Studio is the better choice for hardware startups needing industrial design and firmware together. Very is the stronger option for distributed-delivery IoT programs needing firmware plus data and ML. The right choice depends on your project size, budget, and required tech stack.
Product Creation Studio vs Very: head-to-head summary
| Criterion | Product Creation Studio | Very |
|---|---|---|
| Founded | 1999 | 2011 |
| HQ | Seattle, Washington, USA | Bozeman, Montana, USA (fully distributed team) |
| Team size | 43 | 51–200 |
| Rating | 4.5 / 5 | 4.2 / 5 |
| Primary differentiator | Combines industrial design and mechanical engineering with firmware under one roof, rather than firmware alone | Fully distributed IoT team combining firmware delivery with machine-learning-driven data solutions |
| Pricing model | Full product development engagements | IoT product development engagements from concept through deployment |
| Min. engagement | Not published | Not published |
| Primary tech stack | Embedded C/C++, ARM Cortex-M, CAD and mechanical design tools | Embedded C/C++, IoT connectivity stacks, Machine learning data pipelines |
| Industries served | Consumer products, Medical devices, Industrial equipment | Industrial IoT, Consumer IoT, Smart infrastructure |
Product Creation Studio vs Very: overview
Product Creation Studio
Product Creation Studio was founded in 1999 by Cameron Smith and Scott Thielman and is based in Seattle, Washington, with a team of roughly 43 people. The firm's model combines strategic industrial design and mechanical engineering with firmware and electrical development in one team, aimed at hardware companies that need a product built end to end rather than a firmware-only vendor. Client work spans consumer, medical, and industrial products, and the studio has operated under the same structure for more than two decades.
Very
Very, formerly known by a different name, was founded in 2011 and is headquartered in Bozeman, Montana, operating as a fully distributed team of 51 to 200 people working from numerous countries rather than from central offices. The firm builds connected ecosystems spanning IoT hardware, firmware, and software infrastructure, plus interface design and machine-learning-driven data solutions built on top of device data. Very has appeared on the Inc. 5000 list of fastest-growing private US companies multiple times, a verifiable third-party growth signal distinct from marketing claims.
Services and capabilities: Product Creation Studio vs Very
| Capability | Product Creation Studio | Very |
|---|---|---|
| RTOS firmware development | ✓ | ✓ |
| Bare-metal & driver development | ✗ | ✗ |
| Secure boot / OTA firmware updates | ✗ | ✗ |
| MCU & platform migration | ✗ | ✗ |
| Connectivity & IoT protocols | ✗ | ✓ |
| Functional safety / MISRA compliance | ✗ | ✗ |
| Embedded AI / on-device inference | ✗ | ✓ |
| Firmware GUI development | ✓ | ✗ |
| Staff augmentation | ✗ | ✗ |
Tech stack comparison: Product Creation Studio vs Very
| Framework / platform | Product Creation Studio | Very |
|---|---|---|
| FreeRTOS | N/A | N/A |
| Zephyr | N/A | N/A |
| STM32 | N/A | N/A |
| ARM Cortex-M | ✓ | N/A |
| BLE | N/A | N/A |
| Embedded Linux | N/A | N/A |
| Secure OTA | N/A | N/A |
| PCB | N/A | N/A |
| AWS IoT | N/A | N/A |
| RISC-V | N/A | N/A |
Pricing comparison: Product Creation Studio vs Very
| Criterion | Product Creation Studio | Very |
|---|---|---|
| Minimum engagement | Not published | Not published |
| Engagement models | Fixed project | Fixed project, Dedicated team |
| Rate transparency | Not public | Not public |
| Price tier | Mid-market | Mid-market |
Target audience comparison: Product Creation Studio vs Very
| Dimension | Product Creation Studio | Very |
|---|---|---|
| Best company size | Startup to mid-market | Startup to mid-market |
| Best industries | Consumer products, Medical devices, Industrial equipment | Industrial IoT, Consumer IoT, Smart infrastructure |
| Best use cases | New hardware product needing industrial design and firmware developed together, Medical device concept requiring mechanical and firmware co-design | IoT program needing firmware paired with machine-learning-driven data analysis, Smart infrastructure product requiring both device firmware and interface design |
| Typical project type | Fixed project | Fixed project |
Product Creation Studio vs Very: pros and cons
| Product Creation Studio | |
|---|---|
| + | Combines industrial design, mechanical engineering, and firmware for a hardware product that needs all three from one vendor |
| + | Over two decades of continuous operation since 1999 gives a long reference base |
| + | Founder-led studio structure keeps senior staff involved through the full product cycle |
| - | Firmware is one part of a broader industrial-design practice rather than the sole focus |
| - | A firmware-only engagement may end up paying for design capability it doesn't need |
| Very | |
|---|---|
| + | Repeat appearances on the Inc. 5000 list provide a verifiable third-party growth signal |
| + | Fully distributed team structure can draw specialist talent regardless of location |
| + | Combines firmware delivery with data solutions and machine learning on top of device telemetry |
| - | Fully distributed structure means no central office for in-person collaboration during an engagement |
| - | Montana headquarters is a smaller regional base than most firms' US locations on this list |
Who should choose Product Creation Studio?
A typical fit: new hardware product needing industrial design and firmware developed together.
Combines industrial design and mechanical engineering with firmware under one roof, rather than firmware alone. Minimum engagement is not publicly disclosed. Works best with clients in Consumer products, Medical devices, Industrial equipment.
Who should choose Very?
A typical fit: IoT program needing firmware paired with machine-learning-driven data analysis.
Fully distributed IoT team combining firmware delivery with machine-learning-driven data solutions. Minimum engagement is not publicly disclosed. Works best with clients in Industrial IoT, Consumer IoT, Smart infrastructure.
Decision matrix: Product Creation Studio vs Very
| Your situation | Recommended choice |
|---|---|
| You need full-ownership delivery on a defined project scope | Product Creation Studio |
| You need a large dedicated team for an ongoing programme | Very |
| Your budget is at the lower end | Compare: Product Creation Studio (Not published) vs Very (Not published) |
| You need specialist depth in a specific vertical | Product Creation Studio |
| You need staff augmentation or team extension | Neither; consider alternatives that offer staff aug |
| You need consulting before committing to a build | Both may offer discovery engagements |
Use case fit: Product Creation Studio vs Very
| Use case | Product Creation Studio fit | Very fit | Winner |
|---|---|---|---|
| New hardware product needing industrial design and firmware developed together | Strong | Limited | Product Creation Studio |
| Medical device concept requiring mechanical and firmware co-design | Strong | Limited | Product Creation Studio |
| IoT program needing firmware paired with machine-learning-driven data analysis | Limited | Strong | Very |
| Smart infrastructure product requiring both device firmware and interface design | Limited | Strong | Very |
| Fixed-price build | Limited | Limited | Both equally |
| Staff augmentation | Limited | Limited | Both equally |
Verdict: Product Creation Studio vs Very
Product Creation Studio (4.5/5) is the stronger overall choice for most Firmware Development projects. Combines industrial design and mechanical engineering with firmware under one roof, rather than firmware alone.
Very (4.2/5) is worth a look if you need smart infrastructure product requiring both device firmware and interface design. If your situation matches that, Very is a competitive option.
Related comparisons
Product Creation Studio vs Very FAQ
Is Product Creation Studio better than Very?
Product Creation Studio (4.5/5) scores higher overall, but "better" depends on your use case. Product Creation Studio's strongest advantage: combines industrial design, mechanical engineering, and firmware for a hardware product that needs all three from one vendor. Very's strongest advantage: repeat appearances on the Inc. 5000 list provide a verifiable third-party growth signal.
How do Product Creation Studio and Very differ in pricing?
Product Creation Studio uses full product development engagements pricing. Very uses iot product development engagements from concept through deployment pricing. Neither firm publishes a full rate card; a discovery call is required for project-specific quotes.
Which is better for enterprise: Product Creation Studio or Very?
Very is the larger team and typically the better enterprise-scale choice. For very large programmes, verify team size and compliance coverage directly with each company before shortlisting.
What are the main differences between Product Creation Studio and Very?
Product Creation Studio's primary differentiator is: combines industrial design and mechanical engineering with firmware under one roof, rather than firmware alone. Very's primary differentiator is: fully distributed IoT team combining firmware delivery with machine-learning-driven data solutions. They also differ in team size (43 vs 51–200), minimum engagement (Not published vs Not published), and primary industries served (Consumer products, Medical devices vs Industrial IoT, Consumer IoT).
Verify all details directly with each company before making a decision.