A half-finished product description exposes the three facts a credible marketing draft still needs: who the product serves, what problem it solves, and what changes after using it. Complete those blanks before asking anyone, human or AI, to write the page.
In April 1970, Apollo 13’s crew faced rising carbon dioxide inside the lunar module. The command module carried square lithium hydroxide canisters. The lunar module used round openings. Both parts worked, but they did not fit together.
In Houston, NASA engineer Ed Smylie and his team had to build an adapter using materials available aboard the spacecraft. The procedure they developed used items including plastic, cardboard and duct tape. The astronauts followed the instructions, connected the canisters and brought the carbon dioxide level down.
The episode is documented in Jim Lovell and Jeffrey Kluger’s book Lost Moon. It remains memorable because the missing connection was small, specific and consequential. “We have a canister” was true. “We have an opening” was true. Neither statement described a working system.
A half-finished product description creates the same kind of gap.
Find the missing connection before polishing the sentence
Consider this description:
“An AI platform that creates and publishes marketing content.”
It names a category and two capabilities. It still leaves the reader to supply the important parts.
Who needs it? A solo developer promoting one product has different constraints from an agency managing twelve client brands.
What problem has become painful enough to solve? The founder may have no positioning, an empty editorial calendar, three disconnected channel accounts and four hours a week available for marketing.
What outcome should the product create? “More content” is weak. A clearer result might be a product strategy that guides blog posts, videos and social publishing across connected channels while the founder keeps control of approvals.
Treat the incomplete description as a diagnostic tool. Add three visible blanks:
“For [specific audience] who struggle with [specific problem], this product helps them [specific outcome].”
Do not rush to make it elegant. Awkward but complete beats polished but hollow. The purpose of this pass is to expose missing decisions.
Make the audience narrow enough to change the draft
“Founders” rarely gives a writer enough direction. A bootstrapped developer preparing a first launch does not evaluate marketing software the same way as a growth team replacing several tools.
A useful audience definition changes what the copy emphasizes.
For a solo developer, the description might focus on turning product context into a working strategy, then creating and publishing content without repeating the same setup for every channel. Control matters because unattended publishing may feel risky. Time matters because promotion competes directly with building.
For an agency, product-scoped permissions, approval rules, budgets and audit trails carry more weight. The underlying product may be the same, but the credible description changes because the buyer’s job changes.
If selecting one audience feels uncomfortable, start with the person most likely to recognize the problem today. The description can later support additional paths. Trying to fit every possible buyer into the opening sentence usually removes the details that help any buyer recognize themselves.
The same issue appears when a launch has channels but no clear buyer. [The Missing Buyer in a Quiet Launch](\/blog\/the-missing-buyer-in-a-quiet-launch-and-what-it-costs-across-every-channel-cc610d9b\/) shows how that omission spreads through every draft.
Describe the problem as a situation, not a category
“Marketing is hard” says little. Name the work waiting on the founder’s desk.
The product has shipped, but the target market remains broad. Positioning lives in scattered notes. The blog has not been updated in six weeks. A LinkedIn post needs rewriting for Reddit, and the next video still needs a script. Nobody has checked whether the offer has credible evidence behind it.
That situation gives the description something solid to resolve.
Marketing Agent can define the product’s audience, positioning, voice, competitors, keywords, pricing and channel strategy. It can score marketing readiness and retention mechanics, generate evidence-linked content angles, create localized articles and videos, and publish to connected destinations when provider access and approval settings permit.
Those capabilities become persuasive only after they connect to the founder’s actual problem. Otherwise, they read as an inventory.
State the outcome without promising fiction
The outcome should describe a changed working state the product can genuinely produce.
“Grow faster” cannot carry that burden. Neither can “transform your marketing.”
A defensible outcome is more concrete: one product strategy guides audits, an editorial calendar, blog articles, social posts and videos; approved work reaches connected channels; supported performance data informs future angles. The founder spends less time reconstructing context and more time deciding what deserves attention.
Keep limits in view. Provider availability still applies. Unattended work is opt-in and governed by product-specific schedules, safety caps, permissions and approval rules. Honest boundaries make the promised outcome easier to trust.
Before drafting a landing page or launch post, write the description with the three blanks still visible. If one remains vague, stop there. The Apollo 13 team could not solve its problem by describing the canister more enthusiastically. It needed the missing interface.
Your draft needs the same thing: a named audience, a lived problem and an outcome the product can actually deliver.
Comments
No comments yet.