Before You Build
OtherShut Down

Berg

Berg was a London design studio and connected-products company behind Little Printer and Berg Cloud.

View original story

Product snapshot

What it was

Berg created Little Printer, Berg Cloud, and design-led connected-product work.

Who it was for

design-focused consumersconnected-hardware makerspublishers and content partnerscompanies exploring Internet of Things products

Problem / value

Made web-connected physical products feel approachable, playful, and carefully designed.

Core workflow

  • print personalized web updates
  • demonstrate cloud-backed connected devices
  • deliver partner content through Little Printer
  • support connected-product infrastructure

Core dependency

A repeated consumer job, willingness to pay, hardware margin, partner content, and cloud operations.

Product form

connected hardwarecloud platformdesign consultancyconsumer IoT device

Pricing model

VentureBeat reported Little Printer at $259; full Berg Cloud pricing was not disclosed in the checked public sources.

What happened

Summary

Berg shut down after failing to reach a sustainable business in connected products.

Outcome

The company’s respected design work and product attention did not translate into a sustainable connected-products business.

Demand signal

Public reporting describes a respected and charming product effort, but Berg still did not reach a sustainable business in connected products. The open question was not taste; it was repeat need, price tolerance, and operating cost.

Distribution issue

Little Printer had major partners and design attention, but those signals did not prove enough recurring consumer demand. Berg Cloud also required makers or partners who would pay for connected-device infrastructure.

Timeline

  • Berg began as a design consultancy
  • Little Printer debuted in 2011 and launched commercially later
  • VentureBeat reported a $1.3 million raise and Berg Cloud launch in 2013
  • Berg announced it was wrapping up in 2014

Before you build

Why it matters

Hardware and cloud-backed products create obligations after the sale: device support, cloud uptime, content partnerships, and service wind-down risk.

Primary check

Validate the paid, repeated job before shipping connected hardware: delight, press, and partners do not cover device cost, support, or cloud operations.

Checklist

  • Run paid preorder tests before manufacturing.
  • Measure repeated use by the same owner, not just launch interest.
  • Model cloud and support cost per active device.
  • What repeated job makes the device worth its price?
  • What is the gross margin after hardware, support, and cloud service cost?
  • What happens to customers if the cloud service shuts down?

Relevant if

  • You are building hardware, IoT, AI gadgets, or cloud-backed devices.
  • Your prototype is delightful but the recurring use case is not proven.

Less relevant if

  • Your product is purely software and has no device, cloud-service, or post-sale operating obligation.

Pre-build tests

  • Sell a small paid batch with clear support terms before scaling production.
  • Test one high-frequency content or workflow use case before adding partner integrations.

Transferable lessons

  • Validate willingness to pay before mistaking novelty for demand.
  • Model cloud-service cost for every device sold.
  • Treat partner logos and press as weaker evidence than repeated use.

If you build this today

Start with one high-frequency use case and a paid preorder or pilot. Model hardware margin, cloud service cost, support burden, partner dependency, and what happens when devices need service years later.