TWITTER_ARTICLE

Simon Berens said that within 1 year of quitting his job to start Brighter, the…

2026-02-01 · 20:22 UTC ·sberens ·3 min read

Brief

Brighter founder Simon Berens reflects on his first year building a hardware startup after leaving software, using the shipment of more than 500 lamp units as a case study in how different hardware execution is from software development. His main lesson is that hardware requires heavier upfront planning, tighter accounting, and more conservative timelines because mistakes in tooling, sourcing, or production can set a company back by months instead of days. He emphasizes that operations depend on overcommunication with suppliers, detailed specifications, and relentless follow-up, including daily factory calls near shipment deadlines. Berens also notes that hardware testing is inherently noisier than software QA, so confidence in metrics such as thermals, lumens, and power comes only from sampling multiple units in varied environments. Finally, he highlights external constraints that software founders may underestimate, particularly tariff risk, country-of-manufacture decisions, debt-financed growth, and the value of visiting suppliers in China early to reduce miscommunication and improve execution.

Why it matters

Simon Berens said that within 1 year of quitting his job to start Brighter, the hardware startup had delivered more than 500 units, highlighting a much longer and less forgiving product cycle than software.

Key details

  • Berens argues hardware planning must be far more detailed than software planning: tooling mistakes, incorrect mass production runs, and missed inventory forecasts can delay timelines by months, so he now uses Gantt charts, custom tools, and recommends doubling timelines for repeated part iterations.
  • He says profitable hardware companies face tighter financial constraints than software startups because gross margins are lower and growth is often debt-financed rather than equity-financed; mistimed inventory purchases or missed shipments can quickly turn cash flow negative.
  • Operationally, Brighter relies on constant follow-up and explicit specifications, including daily calls with factories as containers near shipment, because unmanaged hardware tasks and supplier ambiguity create costly delays and quality failures.
  • Berens found hardware validation to be less repeatable than software testing, requiring repeated measurements of metrics like thermals, lumens, and power across multiple units and environments, and he also warns that tariffs and manufacturing-country choices can materially affect financial models.
Cleaned source text

title: @sberens: 1 year ago I quit my job to launch my hardware startup, Brighter. Today we've de...

author: sberens

content_type: twitter_article

published: 2026-02-01T20:22:53+00:00

source_url: https://x.com/sberens/status/2018057486922834416

word_count: 708

1 year ago I quit my job to launch my hardware startup, Brighter. Today we've delivered over 500 uni

1 year ago I quit my job to launch my hardware startup, Brighter. Today we've delivered over 500 units. As a software engineer, it's been a very different but rewarding experience.

Here are some lessons I learned the hard way:

1. Plan way, way more.

Coming from software, the most planning you’re exposed to is linear tickets, sprints, and setting OKRs. If you missed a deadline, it’s often because you re-prioritized, so no harm done.

In hardware, the development lifecycle of a product is many months. If you mess up tooling, or mass produce a part incorrectly, or just sub-optimally plan, you set back the timeline appreciably and there’s nothing you can do but curse yourself. I found myself reaching for more “old school” planning tools like Gantt charts, and also building my own tools. Make sure you have every step of the process accounted for. Assume you’ll go through many iterations of the same part; double your timelines.

In software, budgeting is fairly lax, especially in the VC funded startup space where all you need to know is your runway (mainly calculated from your employee salaries and cloud costs).

With [profitable] hardware businesses, your margin for error is much lower. Literally, your gross margin is lower! If you sell out because you miss a shipment or don’t forecast demand correctly, you lose revenue. If you mis-time your inventory buying, your bank account can easily go negative. Accounting is a must, and the more detailed the better. Spreadsheets are your best friend. The funding model is also much different: instead of relying heavily on equity, most growth is debt-financed. You have real liabilities!

2. Overcommunicate. Overspecify. Follow Up.

Anything that can go wrong will go wrong. Anything you don’t specify will fail to meet the implicit specification. Any project or component not actively pushed will stall. At previous (software) companies I’ve worked at, if someone followed up on a task, I took it to mean the task was off track and somebody was to blame. With a hardware product, there are a million balls in the air and you need to keep track of all of them. Though somewhat annoying, constant checkins simply math-out to be necessary. The cost of failure or delays is too high. Nowadays as a container gets closer to shipment date, I have daily calls with my factories. I found myself agreeing with a lot of Ben Kuhn’s blog post on running major projects (his blog post on lighting was also a major inspiration for the product).

3. Test everything, often, on many units

When I worked at Meta, every PR had to be accompanied with a test plan. I took that philosophy to Brighter, trying to rigorously test the outcomes we were aiming for (thermals, lumens, power, etc…), but I still encountered surprising failures. In software if you have coverage for a code path, you can feel pretty confident about it. Unfortunately hardware is almost the opposite of repeatable. Blink and you’ll get a different measurement. I’m not an expert, but at this point I’ve accepted the only way to get a semblance of confidence for my metrics is testing on multiple units in different environments.

4. Geopolitics matter

As someone who generally stays out of politics, I didn’t know much about the incoming administration’s stance towards tariffs, though I don’t think anyone could have predicted such drastic hikes. Regardless, it’s something you should be acutely aware of; take it into consideration when deciding what country to manufacture in, make sure it’s in your financial models with room to spare, etc…

5. Visit your suppliers early

I wish I had visited my suppliers much earlier, back when we were still prototyping with them. Price shouldn’t be an issue — a trip to China is going to be trivially cheap compared to buying inventory, even more so compared to messing up a manufacturing run due to miscommunication. Most suppliers don’t get international visitors often, especially Americans. Appearing in person conveys seriousness, and I found it greatly improved communication basically immediately after my first visit. Plus China is very different from the US and it’s cool to see!

Read the full blog post here: https://www.simonberens.com/p/lessons-learned-shipping-500-units

Check out the lamp: https://getbrighter.com/

Posted: 2026-02-01T20:22:53.000Z

Engagement: 447 likes, 24 retweets, 18 replies