Marketing Draft Inputs: How Four Short Blocks Turned Eli’s Launch Into One Clear Story

A useful first-session marketing draft needs four inputs: positioning, ideal customer profile, brand voice, and concrete launch details. Together, they tell Marketing Agent what the product means, who should care, how the message should sound, and what readers can act on now.

At 9:40 on Sunday night, Eli was sitting at his kitchen table in Manchester with a cold mug of tea and a launch announcement open in three tabs. He had built a deployment-monitoring tool for small engineering teams, but every draft described it differently. One called it an observability platform. Another promised simpler incident response. The third said it helped developers ship with confidence.

The launch was scheduled for Monday morning. If Eli chose the wrong message, his first readers might leave without understanding why the product existed. He had no customer quote to rescue a vague claim and no marketer arriving before breakfast.

Positioning gives the draft one job

Positioning decides which idea leads and which ideas wait.

Eli wrote a plain sentence: “For small engineering teams without a dedicated reliability specialist, this product shows which deployment caused a production problem.” That sentence narrowed the job. The launch draft no longer had to explain every monitoring feature or compete for every meaning of “observability.”

Good positioning identifies the category, the relevant alternative, and the reason someone would choose this product. It also prevents a common Sunday-night mistake: adding more claims because none of the existing ones feels strong enough.

Marketing Agent can use positioning as the shared source for blog articles, social posts, newsletters, videos, and channel strategy. That consistency matters because message drift compounds. A founder who describes the product three ways creates three different expectations, a problem explored in The Three Product Descriptions, and What Their Drift Costs a Developer.

The ICP decides what deserves explanation

“I help developers” gave Eli almost no direction. A solo developer maintaining a weekend project has different pressures from an engineering lead handling releases across a growing team.

He defined his first audience more tightly: technical founders and engineering leads at small software teams, already shipping to production, worried about tracing failures after a release, and unwilling to adopt a tool that requires days of setup.

Now the draft had useful boundaries. It could mention the anxiety of a failed deployment without explaining what a deployment was. It could address setup effort because that objection mattered. It could avoid language aimed at procurement teams because they were outside this launch.

An ICP helps Marketing Agent choose examples, pains, objections, channels, and calls to action with more discipline. The narrower input creates a more recognizable artifact. Readers should be able to think, “This sounds like my Tuesday,” rather than merely agree that the product seems useful.

Brand voice keeps the draft sounding like its builder

Eli’s first generated paragraph used the kind of inflated language he would never say aloud. The problem was not grammar. The draft had no instructions about how his product should speak.

He added three rules: write like an experienced engineer helping another engineer; prefer concrete examples over broad promises; acknowledge setup and provider limits directly. He also listed words he did not want associated with the product.

That changed the texture of the copy. Sentences became shorter. Claims became easier to defend. The draft stopped sounding borrowed.

Brand voice works best as operational guidance, not a row of adjectives. “Confident, modern, friendly” leaves too much room for interpretation. Specify what the brand explains, what it refuses to claim, how technical it can be, and which words would make the founder wince.

This is also where control matters. Marketing Agent can generate content from one product strategy, while approval rules and product-scoped permissions determine what can move from draft to publication. Unattended work remains an explicit choice, subject to connected-provider access and configured limits.

Launch details turn strategy into something usable

With positioning, ICP, and voice in place, Eli had a coherent message. He still lacked a launch draft someone could act on.

The final input supplied the missing edge: what was launching, which capability was ready, what remained limited, which channels were connected, and what action the reader should take. Launch details can include a release date, plan availability, trial terms, supported destinations, or a feature boundary. They should reflect what is true now.

For Marketing Agent itself, that distinction would mean stating that new workspaces receive a 14-day Growth trial without a card, while usage and provider availability still apply. It would mean describing direct publishing only for connected destinations where provider access permits. Specific caveats make the copy more credible because they tell the reader where the promise ends.

At 11:18, Eli had one launch article draft and three channel versions built from the same product context. The article led with the failed-deployment problem, spoke to small engineering teams, sounded like him, and described only the capability ready for Monday. He still had to review every claim. That was the point of the first-session artifact: enough structure to edit, challenge, and ship.

Before opening a blank Sunday draft, write four short blocks in plain language. State who the product is for, the position it should own, the rules governing its voice, and the facts of this launch. Then generate one artifact and inspect where it drifts. Those weak sentences will show you which input needs sharpening.