The Transition Nobody Prepares You For

Shipping your first 500 units feels like crossing a finish line. You actually built something physical, got it manufactured, and put it in customers' hands. The dopamine is real. The customer photos are real. The revenue hitting your Stripe account is very, very real.

And then you realize you've crossed a different kind of line—one that triggers a whole category of legal obligations that didn't apply when you were a person with a prototype. You're now a company with a product in the market. The rules are different here.

This isn't about paranoia or worst-case scenarios. It's about understanding what the landscape actually looks like once you're selling at scale, so you can make informed decisions about risk rather than discovering problems through lawsuits.

Product Liability Is No Longer Theoretical

When you sold 50 units to friends and early adopters who knew they were buying from a bootstrapped startup, product liability was technically possible but practically unlikely. Those customers understood what they were getting. They probably wouldn't sue you if something went wrong.

At 500 units and growing, you're reaching normal consumers who expect normal products. They don't know you're three people in a garage. They just know they bought something, and if it hurts them or their property, they'll look for someone to hold responsible. That someone is you.

The Insurance Question

If you're selling physical products and you don't have product liability insurance, you're betting your company—and potentially your personal assets—on nothing ever going wrong. That's not a reasonable bet.

Product liability insurance for hardware startups typically costs $2,000-5,000 annually for early-stage coverage. The exact number depends on your product category, volume, and risk profile. That's not nothing for a bootstrapped company, but it's survivable. What's not survivable is a lawsuit without coverage.

The process: find a broker who works with hardware startups (there are several who specialize in this), describe your product honestly, get quotes. Don't try to minimize the risk profile in your application—if you have a claim later and the insurer discovers you misrepresented the product, they'll deny coverage.

Regulatory Compliance Gets Real

Most hardware startups do some minimum viable compliance to launch—FCC certification for anything with wireless, basic safety testing, maybe CE marking for Europe. But compliance isn't binary. It's a spectrum, and the questions regulators ask get harder as you scale.

What You Might Be Missing

Consumer Product Safety Commission (CPSC) requirements kick in for consumer products in the US. If your product is subject to any specific safety standards—and there are thousands of them—you need to be testing against those standards and maintaining documentation.

California's Proposition 65 requires warnings for products containing chemicals on a very long list. If you're selling to California consumers and haven't done a Prop 65 analysis, you're exposed to lawsuits from bounty hunters (yes, this is a real thing—lawyers who specialize in Prop 65 claims against companies who don't comply).

Battery regulations are increasingly complex. If your product has a lithium battery, there are shipping regulations, labeling requirements, and safety testing standards that apply. These have gotten stricter following high-profile battery fires.

The move here isn't necessarily to achieve perfect compliance immediately. It's to understand what you're not compliant with, assess the risk, and make deliberate decisions. Some gaps are urgent; others can be addressed as you scale.

Contract Infrastructure

At 500 units, you need actual contracts governing your relationships with customers, suppliers, and anyone else touching your business. Not template terms copied from the internet—contracts that actually reflect your business and protect your interests.

Terms of Sale

Your terms of sale should address what happens when things go wrong: what are you liable for, what's excluded, how are disputes resolved, what are return and refund policies. The defaults that apply if you don't specify are usually not what you want.

Limitation of liability clauses matter here. You want to limit your exposure to direct damages, exclude consequential damages where legally permitted, and cap total liability at something you can survive (often the purchase price or some multiple of it). These clauses aren't bulletproof, but they're better than nothing.

Supplier Agreements

If your manufacturer ships you defective products that you then ship to customers, who's responsible? Without a clear agreement, you might eat the cost and the liability.

Good manufacturing agreements include quality standards, testing requirements, what happens when products don't meet spec, and indemnification provisions where the manufacturer shares liability for defects. Getting these terms takes negotiation—manufacturers don't love giving them—but they matter.

Intellectual Property

At this stage, you should have at least a basic IP strategy. That means: have you done a freedom to operate analysis to confirm you're not infringing someone's patents? Are you protecting your own innovations with patents, trade secrets, or both? Is your brand trademark protected?

The worst time to discover you're infringing someone's patent is when you're scaling. The second worst time is after a competitor starts copying your innovations because you never protected them.

The Warranty Liability Stack

Every product you sell comes with implied warranties under the law—the implied warranty of merchantability (the product does what products of this type should do) and the implied warranty of fitness for a particular purpose (if you know why the customer is buying it, the product should work for that purpose).

You can modify these warranties with your terms of sale, but there are limits, especially for consumer products. And you can add explicit warranties on top—one-year warranty, lifetime warranty, whatever fits your strategy.

The key is understanding what you're actually promising. Every warranty is a potential future cost. If you offer a one-year warranty and your product has a 15% failure rate, you need to reserve for the cost of honoring that warranty. If you haven't thought this through, your margins might be worse than you think.

Setting Up the Right Structure

If you haven't already, this is the time to make sure your corporate structure actually protects you. The basic idea: your company should be a separate legal entity (LLC or corporation) that holds the product liability and business risks, so your personal assets aren't on the line if something goes catastrophically wrong.

But this protection only works if you actually treat the company as separate from yourself. That means: separate bank accounts, clear capitalization, proper documentation of major decisions, not using the company as a personal piggy bank. If you blur the lines too much, plaintiffs can "pierce the corporate veil" and come after you personally.

What to Do Now

This is a lot. Here's how to prioritize:

Immediate: Get product liability insurance. This is non-negotiable at your volume. The risk of operating without it exceeds the cost.

Next 30 days: Audit your terms of sale and make sure they actually address limitation of liability, warranties, and dispute resolution. If you're using templates, have a lawyer review them.

Next 90 days: Review your regulatory compliance status and identify gaps. Prioritize by risk level and market access requirements. If you're selling in Europe, GDPR and CE marking compliance should be high priority.

Ongoing: Build relationships with a lawyer who understands hardware startups. You don't need them on retainer, but you need someone you can call when questions come up. The cost of good legal advice is almost always less than the cost of discovering you should have gotten advice earlier.

You built something real. Now build the infrastructure to protect it.