The Square Canisters Apollo 13 Had, and What Their Mismatch Almost Cost

When launch claims no longer match the product strategy, pause the draft and correct the strategy first. A reviewable post, email, or video can only be as truthful as the audience, promise, proof, and boundaries behind it.

In April 1970, Apollo 13 had a problem that could not be solved by pushing ahead with the equipment already in place. After the mission’s oxygen tank explosion, astronauts Jim Lovell, Jack Swigert, and Fred Haise faced rising carbon dioxide in the lunar module. The command module had square lithium hydroxide canisters; the lunar module used round fittings. NASA engineers had to make the available parts work together before the crew could safely return.

The NASA History Office documents the improvised adapter built from materials already aboard, including plastic bags, cardboard, and tape. The important part of the story is the mismatch. The crew had a working CO2 scrubber system and working canisters, yet the pieces did not fit the situation they were now in.

A Sunday-night strategy check has lower stakes. The mechanism is similar. Three individually plausible launch claims can still fail together when they no longer fit the product strategy.

Find the claims that no longer fit

At 9:47 p.m., the tempting move is to open the content generator, write around the inconsistencies, and promise yourself you will clean them up later. That creates a polished version of the problem.

Start with the claims that appear most often across launch material: who the product is for, what it helps them do, and why they should believe it. Put the current wording next to the actual product plan.

A founder might find these three conflicts:

• The homepage says the product serves “growing teams,” while the strategy names developers and solo founders as the first audience.
• A social draft promises fully hands-off marketing, while the real workflow includes approvals, product-scoped permissions, provider availability, and usage limits.
• A launch email leads with daily posting, while the stronger product value is the strategy work that makes posting relevant: ICP, positioning, Hook Audit, Marketing Audit, topics, and a governed publishing plan.

Each claim may sound reasonable on its own. Together, they send buyers toward the wrong expectation. That is how a launch earns attention from people the product is not built for, then loses trust when they reach the details.

Repair the source strategy before making content

Marketing Agent gives each product its own target market, ideal customer profile, positioning, brand voice, competitors, keywords, pricing, offers, and channel strategy. Treat that configuration as the source material for the launch, not as a form you completed before the “real” marketing began.

For this product, the foundation should stay close to the truth: Marketing Agent helps technical builders get a product market-ready, audit what may make it stick, create blogs, social content, and videos, then prepare or publish to connected channels within the controls they choose.

That wording leaves room for the capabilities that matter without turning conditions into footnotes. Unattended publishing can run on schedules, but connected destinations, provider access, plan usage, safety caps, and approvals shape what actually happens. A founder reviewing a draft should be able to see those boundaries before anything goes live.

This is also the moment to check proof. If a claim says the product will improve retention, connect it to the scored Hook Audit grounded in the configured source repository. If it says the launch is ready, connect it to the Marketing Audit’s review of customer evidence, positioning, offer, messaging, and acquisition strategy. If there is no evidence for a result, change the claim to describe the real capability.

Turn the corrected strategy into a reviewable draft

Once the strategy is coherent, content generation becomes much faster because the draft has fewer choices to guess at.

Set one primary promise for the launch. For Marketing Agent, a useful version is: builders can give a real product a consistent marketing system without becoming the person who manually researches, writes, edits, schedules, and republishes every week.

Then make the supporting claims earn their place. A blog section can explain how content starts from product strategy. A video can show authentic product screens, approved capture, and a tutorial flow. A social post can describe how a missed destination can receive an existing published piece without duplicating its social-page publication. Those are concrete, reviewable statements.

The draft should also show what a human still controls. Approval rules, channel connections, budgets, capability pauses, and audit trails matter because a solo founder needs marketing help without losing the ability to stop, inspect, or redirect it.

Keep the check small enough to repeat

The point of a 9:47 p.m. strategy check is not to reopen every decision made since the product began. It is to catch the few mismatches that would multiply across a launch.

Use a short pre-generation check:

• Does the audience in this draft match the product’s configured ICP?
• Does the promise describe a shipped capability rather than an assumed outcome?
• Can a reader see the relevant approval, provider, or usage boundary?
• Does the proof point back to a real audit, product screen, or documented workflow?

Apollo 13’s adapter did not create a new scrubber. It made the existing system fit the situation the crew was actually in. Before generating launch content, make your claims fit the product you actually have. Then review the draft with a foundation sturdy enough to publish from.