Landing Copy Cta

Landing Copy: CTA / Close

This is the ask. Every other section builds toward this moment; this section's only job is to make the ask itself, matched to the urgency the token system already specified. It is not a place to introduce new argument, new proof, or new mechanism — if the case isn't made by the time this section runs, that's an upstream section's gap, not something to patch here with more copy.

What this section answers

One thing: what does the reader do right now? Not why (that's every section before this one), not what happens after (a line of reassurance is allowed, but this section doesn't re-argue the case) — the specific action, named as an action.

The algorithm

Per landing-copywriter's paragraph algorithm, a CTA-only section gets 0 paragraphs — 1 line, rendered as a > blockquote per the output format. Where landing-sequencer assigns the CTA to a section that also carries a beat (a closing section with both a payoff paragraph and the ask), the CTA line still stays separate from the paragraph — never merged into the last sentence of prose.

The line itself, in order:

1. Verb first, plain and specific. "Start your free trial," not "Get started" if there's a more specific verb available — "Get started" is correct only when it's genuinely the most specific true description of the action.
2. Match the token system's urgency. If landing-systems marked the CTA high-urgency, the verb mode carries that (imperative, immediate: "Start now"). If low-pressure, the verb mode matches (invitational, unhurried: "See how it works"). A CTA whose verb mode contradicts the token system's stated intent is a mismatch to fix here, not something landing-builder should silently soften or sharpen later.
3. No stacked qualifiers. One clear verb phrase — "Start your free 14-day trial, no credit card required" crams a second claim into the CTA line itself; if that reassurance is load-bearing, it's a fragment of copy just below the button, not inside the CTA text.

Writing standard (scoped to this section)

• Apply landing-copywriter's full writing standard.
• No stock closers. Never end the page on "the future looks bright" or "join us on this journey" — the CTA is the specific action, not a sentiment.
• No urgency manufactured with punctuation or caps. Urgency comes from verb mode and the token system's specified intent, never from an exclamation point or all-caps standing in for an actual persuasive reason.
• No hedge in the ask. "You might want to consider starting a trial" fails here completely — the ask is direct or it isn't an ask.

Self-test

• The line is a specific action verb, not a vague "Learn more" where a more specific true verb was available.
• Verb mode matches the token system's stated CTA urgency (high-pressure vs. low-pressure) — checked explicitly, not assumed.
• The line stands alone as a > blockquote, not merged into the preceding paragraph's last sentence.
• No new argument, proof, or mechanism claim appears in this section — if the case isn't made by now, that's flagged upstream, not patched here.

Constraints

• Never introduce new persuasive content in the CTA section — its job is the ask, not one more argument.
• Never let the CTA's verb mode drift from what the token system specified for this build — a mismatch here is a defect, not a stylistic choice.
• Never stack a second claim or qualifier into the CTA line itself — supporting reassurance is separate copy, not part of the action verb phrase.