# Launch a landing page (/use-cases/rd-product/landing-pages)



Copy this prompt to start your first task:

<Prompt>
  Build a landing page for our new product and publish it as an Artifact.
</Prompt>

<LivePreview component="NewThread" scenario="{ draft: &#x22;Build a landing page for our new product and publish it as an Artifact.&#x22; }" />

## What is this workflow? [#what-is-this-workflow]

Turning a pitch into a published page, an AI teammate confirms the pitch first, drafts the copy, then publishes it as an Artifact — a link you can keep editing without it ever changing.

<Callout type="warn">
  Artifacts are visible to your **organization**, not the public internet, and this flow doesn't wire up analytics or conversion tracking. It's the right tool for something the team reviews, demos, or shares internally, and the wrong tool for a public marketing page you need real traffic data on. That's a different job for a Software Engineer teammate, built and deployed as real code.
</Callout>

## How to use this workflow [#how-to-use-this-workflow]

### Step 1: Hire a teammate for the job [#step-1-hire-a-teammate-for-the-job]

1. Open **AI Teammates** in the sidebar
2. Click **Hire AI Teammate**
3. Pick the **Content Writer** template
4. On the Profile step, replace the default bio so the job is pitch-first, not page-first
5. Confirm the name and click **Create teammate**

<Prompt>
  You publish pages as Artifacts. Before building anything, confirm the pitch: target audience, the actual differentiator, and what the call to action should do. If any of those is missing or vague, ask, don't guess. Draft the copy first and get my sign-off before you build the page. Artifacts are org-visible, not public, so never imply this is a live marketing page with real traffic.
</Prompt>

<LivePreview component="CreateAssistantPage" scenario="{ focus: &#x22;profile&#x22;, initialState: { start: &#x22;template&#x22;, templateRef: &#x22;@helio/content-writer&#x22;, name: &#x22;Content Writer&#x22;, bio: &#x22;You publish pages as Artifacts. Before building anything, confirm the pitch: target audience, the actual differentiator, and what the call to action should do. If any of those is missing or vague, ask, don't guess. Draft the copy first and get my sign-off before you build the page. Artifacts are org-visible, not public, so never imply this is a live marketing page with real traffic.&#x22; } }" />

[More on hiring →](/ai-teammates/hire-an-ai-teammate)

### Step 2: Confirm the pitch before it builds [#step-2-confirm-the-pitch-before-it-builds]

1. Ask for a page with no audience, differentiator, or CTA — it asks instead of guessing.
2. Give it the real pitch, and it drafts copy before building anything.
3. Confirm the draft reads right, then say so — only then does it build and publish.

<LivePreview
  component="AssistantChat"
  scenario="{ assistantName: &#x22;Content Writer&#x22;, messages: [
{ author: &#x22;user&#x22;, text: &#x22;I want a page for our new API product.&#x22; },
{ author: &#x22;assistant&#x22;, text: &#x22;Before I draft anything, I need three things I don't have yet: who's the audience (backend engineers evaluating alternatives reads very differently than a non-technical buyer), what's the actual differentiator versus whatever they're using today, and what should the call to action get someone to do (start a trial, book a call, join a waitlist). Give me those and I'll draft copy first, not a page, so you can react to the words before anything gets built.&#x22; },
] }"
/>

For example:

<Prompt>
  Audience: [who it's for]. Differentiator: [why it's better than the alternative]. CTA: [what you want them to do].
</Prompt>

<Prompt>
  Copy looks good. Build the page and publish it as an artifact.
</Prompt>

<Callout type="warn">
  Click through the actual link yourself before sharing it anywhere. A page that looks right in the builder can still have a broken CTA link or a highlight that doesn't match what you approved.
</Callout>

### Step 3: Iterate on the same link [#step-3-iterate-on-the-same-link]

<LivePreview
  component="AssistantChat"
  scenario="{ assistantName: &#x22;Content Writer&#x22;, messages: [
{ author: &#x22;user&#x22;, text: &#x22;Change the hero headline and add an image to the second highlight.&#x22; },
{ author: &#x22;assistant&#x22;, text: &#x22;Updated in place: new hero headline, image added to that highlight block. Same link, same artifact. If it doesn't look right, tell me and I can restore the version before this edit.&#x22; },
] }"
/>

Just say what to change. The teammate updates the same artifact, so the link stays the same and anyone with a tab open sees the update on refresh.

## What You Need to Know [#what-you-need-to-know]

**No engineer required:** hiring the Content Writer template is enough for this flow. You only need a Software Engineer teammate if you're moving to a real, publicly-tracked marketing page instead.

**The link never changes:** publishing and every later edit reuse the same Artifact URL, and version history lets you roll back an edit that went wrong.

**Nothing here needs your approval:** publishing and editing an Artifact stays inside Helio and can always be rolled back, so this flow runs on its own. See [Control](/ai-teammates/control) for what does pause for sign-off.

## Tips for Better Results [#tips-for-better-results]

| Tip                                     | Description                                                                                                                         |
| --------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Confirm the pitch before drafting       | Skipping audience, differentiator, or CTA gets you generic copy the teammate has to redo. Give it all three up front.               |
| Approve copy before the page gets built | Reacting to words is faster than reacting to a built page. Confirm the draft first, then say "build and publish."                   |
| Click the live link before you share it | A page can render fine in the builder and still ship with a broken CTA or a mismatched highlight. Open the artifact yourself first. |
| Name the specific change when iterating | The teammate updates the same artifact in place. Say exactly what to change and the link never breaks.                              |

## Common Questions [#common-questions]

<Accordions type="single">
  <Accordion title="Is the published page public?">
    No. Artifacts are visible to your organization, not the public internet.
  </Accordion>

  <Accordion title="Does this replace a real marketing page?">
    No — this flow doesn't wire up analytics or conversion tracking. For a public page you need real traffic data on, have a Software Engineer teammate build and deploy it as real code instead.
  </Accordion>

  <Accordion title="Does editing the page change its link?">
    No. Edits update the same Artifact, so the link stays the same, and anyone with a tab open sees the change on refresh.
  </Accordion>

  <Accordion title="Can I undo a bad edit?">
    Yes. Artifacts keep version history you can roll back to.
  </Accordion>

  <Accordion title="Which teammate can do this?">
    Any teammate. It's a writing and structuring task, not code. The Content Writer template is the default starting point.
  </Accordion>
</Accordions>

<Cards>
  <Card title="R&D & Product" href="/use-cases/rd-product" description="Back to the R&D & Product use case overview." />
</Cards>