The Stark Playbook

Last issue we met a founder who spent ten patient years building one company on one product. Here's the twist we didn't tell you: the same founder turned around and built a second company at a dead sprint — and took it from zero to a roughly $500 million valuation in about a year. Same person, opposite philosophy. Stark is the bet that in this market, speed itself is the moat, and that the patient get out-run before they get good.

The business behind the hardware. Not what they build — how they built it.

Issue 05 was the case for doing less, slowly. This is its mirror: do a lot, immediately. Stark was founded in 2024 and within roughly a year had stacked top-tier investors, stood up production on two sides of a border, and planted offices across the continent. Whether patience or speed is "right" may depend on the moment — but the speed play has its own discipline, and it's worth taking apart. Here are the six moves.

Stark's co-founder list includes the same operator who spent a decade building the patient company in our last issue, alongside an experienced venture investor and a veteran technologist. That matters more than any single product decision. A second-time founder doesn't start at zero — they start with a filled Rolodex, a known name to investors, scar tissue about what wastes a year, and a team that will follow them out the door on day one.

That's why Stark could move at a speed a first-timer structurally can't. The patient company was the apprenticeship; the fast company is the master work. The credibility, the supplier relationships, the recruiting magnetism — all of it was pre-paid by the first company and spent immediately on the second.

Takeaway: The fastest company is usually someone's second. If you've already built once, your real starting line is years ahead of zero — run from there, don't reset.

Stark went from founding to roughly $100 million raised and a ~$500 million valuation in about a year, anchored by a top-tier venture lead. That's the inverse of last issue's revenue-first discipline, and it's a deliberate choice, not a contradiction. In a market moving this fast, the scarce resource isn't capital — it's time, and capital buys time.

Raising big and early lets you compress the calendar: hire ahead of revenue, build capacity ahead of orders, and be the obvious name when the market turns. The risk is real — you're spending against a promise — but the bet is that in a land-grab moment, the company that's already built wins the share that the careful company is still qualifying for. Momentum, here, is a strategy.

Takeaway: When the constraint is time, not money, raise to buy speed. Early capital is permission to build ahead of demand — pay for the calendar you can't otherwise get.

Within its first year Stark stood up production capacity measured in the tens of thousands of square meters — and split it across two countries rather than one. Most young companies treat manufacturing as a problem for later, after product-market fit. Stark treated capacity as the product-market fit. In a market where buyers ask "how many, how fast," the company that already has the floor space wins the order the careful company has to go raise for.

Building capacity early is expensive and risky if demand doesn't show. But it converts a hardware company's slowest variable — physical scale — into something you've already solved when the call comes. You can't pour concrete on a deadline.

Takeaway: In hardware, capacity is a lead time you can't compress later — so buy it early. The company with the floor space already poured wins the orders that reward speed.

Rather than perfect one home market first, Stark stood up operations across several countries early — production on two sides of a border, offices in several more. The logic echoes a theme from earlier issues: when your customers are governments, physical presence inside their borders is part of the product. Local capacity means local jobs, local sovereignty, and a shorter line to the buyer.

Going multinational early is operationally painful — more legal entities, more complexity, more overhead before there's revenue to carry it. The speed play accepts that cost on purpose, because being "local" in five places when the orders land beats being efficient in one place and foreign everywhere else.

Takeaway: If your buyer is a nation, be native in more than one of them, early. Multinational footprint is overhead until the moment it's the only reason you win the contract.

Stark reportedly puts well over 45% of its spend into R&D — an enormous share for any company, let alone a young one. In a fast market the moat isn't a defensible position you hold; it's the rate at which you ship a better product than the last one. Out-engineering, relentlessly, is the entire game when the technology and the requirements are both moving every quarter.

That spending profile is only rational if you believe speed compounds — that shipping faster this year buys you a lead that's expensive to close next year. It's the opposite of harvesting a mature product. It's pouring the company's fuel into staying ahead of a moving line.

Takeaway: In a fast-moving category, treat R&D rate as the moat. The lead doesn't come from defending a position; it comes from out-shipping everyone toward the next one.

Stark deliberately serves a tightly defined set of allied government customers rather than chasing every possible buyer. Counterintuitively, a narrow, clearly-stated customer boundary is an accelerant, not a limit. It tells your engineers exactly whose requirements to build against, tells investors exactly what market you're addressing, and tells buyers they're dealing with a company that has chosen a side and a standard. Ambiguity is slow; a clear boundary is fast.

This is the speed play's version of focus. The patient company focused its product. The fast company focuses its customer — same discipline, different axis. Both refuse to be everything to everyone; both move faster because of the refusal.

Takeaway: A narrow, explicit customer definition is a speed advantage, not a ceiling. Decide exactly whom you're for, and every downstream decision gets faster.

Issue 07. We've now covered the air and the sea, the patient and the fast. So here's the layer nobody puts on a magazine cover: the dirt. Next issue is a company betting that the least glamorous part of defense — the robots that crawl along the ground, not the ones that fly — is where the real operating story is, and that the unsexy layer is exactly why the opportunity is open. We'll name it next issue: the case for the unglamorous.

Commander is the business behind the hardware. Not what they build — how they built it.

New transmission every two weeks. If it earned its place in your inbox, forward it to one operator who’s building something — that’s how Commander spreads.

COMMANDER · ISSUE 06 · commander.media · Istanbul