Space hardware · 2026 · 4 MIN READ
A space hardware startup that asked for a way out of stealth – and, a few years later, needed every public surface to tell one true story while its products kept changing.
The shape of the problem before we touched it.
A space hardware startup's chief executive introduced us to the colleague leading the company's next step: bringing it out of stealth and in front of buyers. It was a young manufacturer with flight hardware on the way and almost nothing public to say about it.
The brief named two deliverables. The problem underneath was a product line that would keep changing faster than any single document could keep up with, which made every public surface a place where an out-of-date fact could live.
How we mapped it before we moved.
Messaging came before anything was built to carry it. A positioning workshop at the company's facility produced a first draft within a month, and four more versions followed over the next seven weeks, with the chief executive and the business-development lead commenting on each. The first website went live about two weeks after its first target, while product content was still arriving. It was the first sign of a pattern that outlasted that site: here, what a launch waits on is rarely code.
From there the work widened as the company did: a retainer, press materials for partner milestones, a product naming system, then social, datasheets and a public relations program.
Record how settled a fact is, not just what it says.
What got made – and where it had to hold up.
Then the threads crossed. With the company's own developer building a new site and the launch already running late, its head of sales and marketing asked us to lead the work with the developer. We ran the layer around the build – a tracker of more than a hundred items, content, decisions and coordination – while development stayed with the company's developer. The launch target moved three times in a month, mostly waiting on product content and reviews rather than code, and the site went live at the end of the month. A customer case study came off the site before launch because the customer hadn't given permission to publish it.
The press program had its own rule for proof. When an independent research partner published test results on the company's hardware, the release went out on the wire nearly as the partner wrote it. The client's brief was to lean the company first, so we moved two paragraphs to put its voice ahead of the partner's and changed none of the partner's words. The research stayed the partner's, which is what made it worth publishing.
The day after the site launched, we audited it against the facts we had locked the week before and found it already disagreeing with them. That changed how we keep the company's facts. Every figure, name and claim we use now carries a state – settled, verify before use, contested, or never for publication – and the state travels with the work, so a number checked one month isn't quietly trusted two months later.
What changed – and what didn't.
What changed. The company came out of stealth with a first website and then a brand site. Its test results are on the record in a release that carries the research partner's name rather than the company's own claims. And a cold pitch we sent to trade and local outlets became a feature in an industry trade magazine.
What didn't. That feature was the first real test of the fact states, and we routed it the wrong way. Our corrections to the reporter's draft waited on the client's review, and the review ran past the print deadline. The print edition went out as drafted. The online version took the client's own changes, which caught some of what we had flagged; our correction list itself was never sent. The facts were right in our file and not on the page, and that routing failure is ours. We also can't yet say what the new site is bringing in, with no traffic or lead read to report, and we haven't found a story from any of the other outlets pitched at the same time.
What we'd keep. What we'd watch.
We'd keep a record of how settled each fact is, attached to the work rather than to someone's memory, for any company whose products move this fast. And we'd keep a light hand on third-party proof: an angle turns someone else's evidence into your claim.
We'd watch where corrections go. A factual correction to a reporter goes to the reporter, on our clock, while the client's review runs in parallel – that review is for positioning, and it should be. And we'd watch what counts as done. The live site is the record, not the email saying something on it was fixed.
Yours in the work.
Filed 2026