---
title: "Quickstart: From Adding Kite to Your First Shipped Work"
description: Add Kite to a channel, take it up on its first offer, review the draft in the thread, and publish. A short walkthrough of the first conversation.
---

# Quickstart: From Adding Kite to Your First Shipped Work

This guide follows a team through its first session with Kite, from the install to a published piece of work. The only setup step is **[adding Kite to Slack](/get-started/add-kite-to-slack)**.

:::note The example team
The examples below follow a three-person startup that sells scheduling software to clinics. They have no marketing hire yet, and their founder, a designer, and an engineer share a `#growth` channel in Slack.
:::

## 1. Kite joins and offers work

The founder invites Kite to `#growth`. Kite says hello, reads the company website, and replies with two offers: a comparison page against the competitor the site mentions most, and a rewrite of the pricing page headline. It does not recite the company's profile back at them. It offers work.

## 2. Take Kite up on an offer, or ask for something else

The founder replies in the thread: "Do the comparison page." That reply is all Kite needs. It researches the competitor, drafts the page, and builds it on the site as a draft. If the team wanted something else, they would say so in the same thread: "Skip those. Pull a list of 50 multi-location clinics in Texas with a contact at each."

## 3. Review the draft

Kite posts the result in the thread with a **Preview** button to see the draft page and a **Review** button that opens the website editor. The designer previews it and replies: "Lead with the time saved at the front desk, not the feature list." Kite revises and posts again.

## 4. Publish

The founder replies "Publish it." Kite merges the draft and deploys it to the live site, then posts the live link. (The team could also have clicked **Review** and pressed **Publish** in the editor themselves.)

## 5. Keep going

From here the team asks for work as it comes up, and Kite brings work to them:

- It posts a digest when it spots something in the team's Slack conversations that lines up with an active initiative.
- It proposes initiatives, each with an **Approve** button that tells Kite to break the initiative into tasks and start.
- Results of every task land in the thread where it was asked for.

## Tips for a strong start

- **Give Kite context early.** Reply to its first message with anything the website does not say: who your best customers are, what you are launching next, which competitor matters most.
- **Be specific when you ask for changes.** "Make the headline about saving front-desk time" gets a better revision than "make it better."
- **Keep each piece of work in its own thread.** It keeps drafts, feedback, and results easy to follow.
- **Keep an eye on credits.** Every conversation and task uses credits. See [How credits work](/pricing-credits/how-credits-work).

## What's next

- **[How Kite works](/get-started/how-kite-works)**: what Kite does on its own and what it does when asked.
- **[Approvals and autonomy](/slack/approvals)**: the propose-first default and how to change it.
- **[What Kite can do](/capabilities/)**: the kinds of work to ask for.
- **[Website Building](/website-building)**: build and edit the website Kite hosts for you.
