A 9:07 p.m. strategy download turns the positioning decisions in a founder’s head into a product brief the marketing system can use. Before launch week begins, define the buyer, problem, promise, proof, voice, offer, competitors, keywords, channels, and approval boundaries in one place.
In April 1970, the Apollo 13 crew faced rising carbon dioxide inside the lunar module. The command module carried square lithium hydroxide canisters, while the lunar module used round ones. The crew had working filters, but they did not fit the system keeping them alive.
NASA engineer Ed Smylie and his team had to convert what engineers on the ground knew into instructions the astronauts could follow with materials already aboard the spacecraft. They built and tested an adapter, then Mission Control relayed the procedure to the crew.
NASA documents the episode in its Apollo 13 history and oral histories. The famous phrase “square peg in a round hole” describes the physical mismatch, but the deeper problem was operational: knowledge at Mission Control had no value until it became a usable specification for people working under different conditions.
A founder approaching launch week faces lower stakes, but the mechanism is familiar. The positioning may exist. The marketing system still needs an adapter.
The decisions already hiding in your head
At 9:07 p.m. on the Friday before launch week, imagine opening a blank product brief.
You know who built the product for. You can describe the painful workaround that pushed you to build it. You know which competitor customers mention, which claim you refuse to make, and why one feature matters more than the other twelve.
None of that knowledge has a stable home yet.
The homepage draft calls the buyer a “modern team.” A scheduled LinkedIn post speaks to growth leaders. The launch email targets developers. One video script promises full automation even though publishing depends on connected providers and approval settings.
Each asset sounds plausible by itself. Together, they describe several products.
Start by writing the decisions that should remain consistent everywhere:
- Name the primary buyer in language specific enough to exclude someone.
- Describe the problem as the buyer experiences it before introducing the product.
- State the outcome the product can honestly deliver.
- Record the evidence supporting each meaningful claim.
- Define words the brand uses and words it avoids.
- List the alternatives customers already consider.
- Set the offer, price, channels, and approval requirements.
Marketing Agent stores these decisions per product, including the target market, ideal customer profile, positioning, brand voice, competitors, keywords, pricing, offers, and channel strategy. That product brief then grounds audits, content, videos, distribution, and future research.
The value comes from continuity. You make the decision once, inspect it, and give each later task the same starting point.
A brief should constrain the launch
A useful strategy brief rules things out.
If the ideal customer is a developer shipping a real product without a dedicated marketer, the launch copy should respect technical judgment and limited time. It should avoid vague promises about “transforming growth.” It should explain what work gets completed, where the founder keeps control, and which outcomes depend on provider access.
If the product requires approval before publishing, record that boundary. If unattended posting is allowed only for selected channels, record that too. If a claim lacks customer evidence, mark it as unproven instead of dressing it up.
These constraints reduce the chance that each new draft reopens the positioning debate. They also expose gaps while there is still time to fix them. A scored Marketing Audit can examine readiness across customer evidence, positioning, offer, messaging, and acquisition strategy. A Hook Audit can inspect retention mechanics against the configured source repository.
The brief supplies the intended strategy. The audits test whether the product and evidence support it.
This is why seven individually polished drafts can still fail as a launch system. When drafts are missing one approved product strategy, consistency becomes manual review work, and contradictions survive because every draft looks reasonable in isolation.
Turn Friday-night clarity into Monday inputs
Keep the first download short enough to finish. Twenty imperfect fields that can be reviewed are more useful than a positioning manifesto abandoned after two pages.
Write the primary customer first. Then capture the customer problem in their language, the current alternative, the promised outcome, and the evidence available today. Add the brand boundaries and publishing rules after the core argument is clear.
Where evidence is missing, say “unknown.” Where the product supports opt-in automation, avoid implying that every action runs unattended. Where distribution depends on a connected platform, preserve that caveat in the brief rather than adding it later as fine print.
Then test the brief against three launch assets: the homepage opening, the launch post, and the first video script. A reader should encounter the same buyer, problem, and promise in each, adapted to the channel rather than reinvented for it.
If the customer problem still sounds interchangeable with every startup’s problem, work there next. The story of how Maya turned generic launch copy into a buyer’s story shows why that single field affects the rest of the message.
Build the adapter before the pressure arrives
The Apollo 13 filter adapter succeeded because Smylie’s team worked from real constraints: the incompatible hardware, the materials aboard, and a procedure the crew could execute. The instructions connected expertise on the ground to action in the spacecraft.
Your product brief serves the same practical role. It converts founder knowledge into inputs that content, audits, videos, publishing rules, and future decisions can use without guessing.
At 9:07 p.m., do not begin with a launch thread. Open the product strategy and write the customer, problem, promise, proof, and boundaries first. Monday’s drafts can move faster because they begin from decisions you have already made.
Comments
No comments yet.