Home / Work / Product Launch Docs

Documentation Suite for a New Product Feature

Creating a complete set of help articles for a SaaS feature launch — from cross-functional planning and content architecture through writing, review, and AI-ready structuring.

Article Writing AI-Ready Content Launch Planning Cross-Functional

The Challenge

A SaaS platform is launching Automations — a major new feature that lets users build custom workflows with triggers, conditions, and actions. There's no existing documentation. The content team needs to go from zero to a complete, published article suite before launch day, coordinating across Product, Engineering, and Support teams under a tight timeline. The help center also runs an AI agent, so every article needs to be structured for accurate AI retrieval from day one.

Deliverable: Launch Content Plan & Status Tracker

Before writing a single word, I map out every article needed for the launch — organized by topic, assigned a priority, and tracked through production. This gives all stakeholders a clear view of progress and prevents gaps from slipping through.

automations-launch-content-tracker.csv
Article Category Priority Status Audience Reviewer
What Are Automations? Getting Started 🔴 P0 Published All Users Product
Creating Your First Automation Getting Started 🔴 P0 Published All Users Product
Automations Pricing & Plan Limits Getting Started 🔴 P0 Review Ready All Users Product + Legal
Available Triggers and Actions Configuration 🔴 P0 Published All Users Engineering
Using Conditions and Filters Configuration 🟡 P1 Published All Users Product
Connecting Third-Party Apps Integrations 🟡 P1 Content Drafted All Users Engineering
Testing and Debugging Automations Configuration 🟡 P1 Content Drafted All Users Engineering
Managing Team Permissions for Automations Admin 🟡 P1 In Progress Admins Product
Automation Run History & Logs Configuration 🟢 P2 Content Drafted All Users Engineering
Automations API Reference Developer Docs 🟢 P2 In Progress Developers Engineering
Common Automation Errors Troubleshooting 🟡 P1 Review Ready All Users Support + Eng
Automation Rate Limits & Quotas Troubleshooting 🟢 P2 Content Drafted All Users Engineering

Deliverable: Sample Help Article

Here's an example of how I write help center articles — clear headings, scannable structure, specific details, and a tone that respects the reader's time. This article is structured to be AI-ready: each section answers a distinct question so AI agents can surface precise answers.

Help Center Article

Creating Your First Automation

Last updated: March 2026 · Audience: All Users

Automations let you connect triggers, conditions, and actions to automate repetitive tasks in your workspace. This guide walks you through building your first automation from scratch.

Before You Start

To create automations, you need:

  • A Pro plan or higher (automations are not available on Free plans)
  • Editor or Admin permissions in your workspace
  • At least one active project or data source connected

Step 1: Open the Automation Builder

Navigate to Settings → Automations from your workspace sidebar. Click New Automation to open the builder.

Step 2: Choose a Trigger

A trigger is the event that starts your automation. Select one from the trigger menu:

  • Record created — Runs when a new record is added to a project
  • Field updated — Runs when a specific field value changes
  • Status changed — Runs when a record moves to a new status
  • Scheduled — Runs at a set time (daily, weekly, or custom)

Step 3: Add Conditions (Optional)

Conditions filter which records the automation applies to. For example, you can set the automation to run only when the "Priority" field equals "High." Click Add Condition to set up filters.

Tip: Start simple. Build your first automation with just a trigger and one action. You can add conditions and additional steps later once you've confirmed it works.

Step 4: Define an Action

An action is what happens when the automation runs. Common actions include:

  1. Send a notification — Email or in-app alert to a user or channel
  2. Update a field — Automatically change a value on the record
  3. Create a task — Generate a follow-up task in a specified project
  4. Send a webhook — Push data to an external service via HTTP

Step 5: Name and Activate

Give your automation a descriptive name (e.g., "Notify team when high-priority task is created"). Toggle the automation to Active. The automation will begin running the next time the trigger fires.

What Happens Next

Once active, your automation runs in the background. You can view run history, check for errors, and adjust settings at any time from the Automations dashboard.

Deliverable: AI-Ready Content Structure

Modern help centers are increasingly powered by AI agents (like Intercom's Fin or Zendesk AI). These tools work best when articles follow specific structural patterns. Here's how I structure content so AI can surface accurate, relevant answers — not hallucinate them.

ai-content-guidelines.md
Principle What It Means Example
One topic per article Each article answers one clear question or covers one workflow "Creating Your First Automation" is separate from "Automation Pricing"
Descriptive headings H2/H3 headings state the answer topic, not just labels "Step 2: Choose a Trigger" not "Triggers"
Front-load key facts Put the most important information in the first sentence of each section "A trigger is the event that starts your automation" before listing trigger types
Structured data patterns Use lists, tables, and consistent formatting that AI can parse Trigger types in a list with bold labels, not buried in a paragraph
No ambiguous pronouns Repeat the noun instead of using "it," "this," "that" "The automation runs when…" not "It runs when…"
Audience-appropriate language Match vocabulary to the reader's expertise level End-user articles say "connect your app"; developer docs say "configure the OAuth flow"

Deliverable: Cross-Functional Collaboration Workflow

Product launch documentation doesn't happen in isolation. Here's the workflow I use to coordinate with Product, Engineering, and Support teams — especially under tight timelines.

launch-docs-workflow.md
Phase Activities Teams Involved Output
1. Discovery Review PRDs and specs, attend feature demos, interview PMs and engineers on edge cases Content + Product + Eng Article list, content plan, audience mapping
2. Drafting Write first drafts, capture screenshots from staging, create step-by-step flows Content (lead) Draft articles in CMS
3. Review Route drafts to PMs for accuracy, Engineering for technical correctness, Support for common questions Content + Product + Eng + Support Reviewed and approved articles
4. Polish Final edit pass, add media, set audience visibility, optimize structure for AI agents Content (lead) Publish-ready articles
5. Launch Publish articles, add to help center collections, enable for AI agent, notify Support team Content + Support Live documentation suite
6. Post-Launch Monitor search queries, track ticket deflection, iterate on gaps from real user behavior Content + Support + Data Updated articles, gap analysis

Approach

Launching documentation alongside a product feature requires speed without sacrificing quality. Here's what drives the process:

  • Start before the feature is final — Begin drafting from PRDs and early demos; iterate as the product evolves
  • Prioritize ruthlessly — P0 articles ("What is it?" + "How do I start?") ship before launch; P2 articles follow
  • Structure for AI from day one — Every article follows AI-ready patterns so it works with AI agents on launch day
  • Build the tracker first — The content plan is the project management tool; stakeholders always know where things stand
  • One review cycle, not three — Combine PM + Engineering + Support review into a single structured pass to save time
  • Plan for post-launch — Gaps will emerge from real usage; the content plan has room for iteration based on support data

Launching a New Feature?

I can build your documentation suite from scratch — on time, on strategy, and AI-ready from day one.

Start a Conversation