Where should download vs schedule fork?

A download is still a campaign. After Use this Campaign it’s activated and opens in the campaign builder with its campaign chat, same as today, with one component set (also used for MCP Apps). The thread has no separate download card. The builder always opens on Content. Downloaders only need Content (preview, ask the campaign chat, edit, download). Schedulers continue to Automation › Audience › Review. While partners search for a campaign, they’re only looking for relevant content, so nobody is asked about download vs schedule there. Open question: where the fork goes.

Switch any timeA partner can change path at any point.

Download = all stepsA download counts only when every step is downloaded, not one asset.

One goalRun a campaign, done via download or done via schedule.

Edits live in the builderEditing a step happens in the builder / asset canvas, not the thread.

SignalsPast downloads vs past schedules. A connected marketing tool is not a signal (integrations only send single emails).

proposed new UI, not in the product todayPrimary primary actionSecondary secondary actiondashed hidden or collapsed stepEverything is a grey-box wireframe. Names and labels are placeholders.

	A · Ask at Use this Campaign	B · Fork after Content	C · Inferred default + switch	D · Content first, inferred finish (main lean)
Question asked?	Always, before they see the content	Never	Only with no history (most new partners)	Never
Builder when it opens	Collapsed or expanded, from the answer	Collapsed for everyone	Collapsed or expanded, from history	Content only (downloaded before, or no history); all four steps visible, on Content, for partners who scheduled before
Clicks to download, after Use this Campaign	2 (answer, Download)	1	1 if the guess is right, else 2	1 (a secondary button for partners who scheduled before)
Scheduler sees the full process up front	Yes	No, it expands after Content	Yes, if history says so	Yes, if history says so
New partner (no history), the onboarding case	Has to decide before seeing the content	Sees content, decides at the end	Falls back to A’s question	Sees content, both finish actions equal
Cost of a wrong guess	n/a (they chose)	n/a	Wrong builder shape until they switch	Only which steps show first and which button is primary
New UI	Question block, collapsed stepper	Collapsed stepper, two finish actions	Collapsed stepper, switch link, question fallback	Collapsed stepper, finish actions with a default

Main lean · built in the main prototype

D: everyone starts on Content, and past behavior sets the default. This is B’s placement with C’s inferred default, but no question, ever. Open the main prototype →

No question before the content. Content is the step both personas need, and partners can’t judge “download or schedule?” until they’ve seen and edited it. A and C’s fallback ask at the most exciting moment, and most onboarding partners have no history, so C would mostly become A.
A wrong guess is cheap. In D it only changes which steps show first and which finish button is primary. The other action is always right next to it.
No surprise for schedulers. Partners who schedule get the stepper already expanded (as if they had picked Schedule from the start). New partners get the short version, with Continue to schedule one click away.
Small build. It reuses today’s header slot where the builder already has a download icon and a next-step button. The only new parts are the collapsed stepper and the finish-default rule.
Watch: for no-history partners, show both finish actions with equal weight, with “Download” labelled so it’s clearly all steps. Measure the split per tenant before tuning the default.

Prototype. Low-fidelity wireframes for comparing options. All names, labels and states are placeholders. Nothing is sent or downloaded.