From kickoff notes to a two-sided plan

A shared path to the first result.

A customer onboarding plan connects an agreed first outcome to each side’s responsibilities, required inputs and evidence of success.

Make this with my agent

Bring your notes. Review a draft before sharing.

Explore the method

01
Start with what is pending.
Mira’s campaign and field definitions unlock Theo’s draft.
02
Keep timing conditional.
Review is proposed within five working days after confirmed inputs; no date is booked.
03
A sample is not first value.
The demonstration does not replace Jules’s review and recorded next action.

THE REAL HTML · FICTIONAL EXAMPLEView on its own

A worked example, not a customer result. September 2026 dates are sample facts.

Now make it about your work

Their outcome. Your agent. A shared next step.

Bring the agreed result and confirmed owners on both sides. Show which customer input unlocks the next vendor action.

Start with three things

The agreed first useful outcome and phase boundaries.
Customer and vendor owners, inputs and dependencies.
Evidence of success, conditional timing and the help route.

Make this with my agent

You review the facts and access. Nothing is published without your approval.

The method behind the planFrom setup activities to a shared first result

How do I create a customer onboarding plan with an AI agent?

Give your agent the agreed customer outcome, kickoff notes, prerequisites, and confirmed owners on both sides. Ask for a customer-facing plan that leads with the first useful result and the next action—not a tour of every feature. Review the draft, then share a readable page while keeping task updates and approvals in your existing tools.

What to give your agent

The customer outcome actually agreed in the sales handoff or kickoff, with proposed goals clearly separated.
The first use case, its scope and exclusions, and the evidence the customer will review to recognize success.
Confirmed customer and vendor owners, their required inputs, dependencies, and approved help channel.
Supplied timing and its conditions; unresolved dates must stay unresolved.
Audience-safe resource links, the authoritative task record, and the plan owner and review date.

Agree on one first useful result
Start with what the customer bought the service to accomplish. 'Attend training' is an activity; 'review one report and choose a next action' describes a useful result. Use the customer's agreed definition and evidence. If they have not agreed one, make that the next question rather than inventing a success target.
Show what each side needs to do
Separate customer inputs from vendor work. Attach each prerequisite to the work it unlocks and name the confirmed owner. A vague request to 'finish setup' hides whether the customer needs to supply information or the vendor needs to prepare something. Keep credentials and sensitive source material out of the page.
Make the sequence honest
Show a few milestones with the input, output, and reviewer for each. Preserve dependency-based timing: five days after inputs arrive is not the same as a booked date. Label blocked, proposed, and unconfirmed work in words. A sample demonstration can help while waiting, but it is not evidence the customer's actual outcome has been achieved.
Lead with the next action, not the whole backlog
Put the immediate request near the top, followed by responsibilities, milestones, and supporting resources. Explain what is excluded from this first phase so a pilot does not look like a full rollout. Include the confirmed route for questions without inventing a response-time promise.
Review the plan with the customer in mind
Check that a customer can tell what they need to provide and what you will do next. Verify the audience, links, evidence and dates before sharing. Show a snapshot date and plan owner. Record progress, changing commitments, and customer confirmation in the agreed project workflow; update the reading page after review.

Keep creating and revising in the agent you already use. Start with a saved artifact style and learn how to update HTML without changing its link.

Use the full promptReady for your agent and your notes

Use the conversation where you already did the work. Only attach material you are allowed to share.

Get the ready-to-copy creation request →

Using only materials I provide or have authorized you to access, create a customer onboarding plan for [customer] and [service]. Ask only for missing essentials: the agreed first useful outcome, scope and exclusions, customer and vendor owners, prerequisites, evidence of success, timing conditions, and the approved help and tracking channels. Separate agreed goals from proposed goals. Lead with the customer's next action and show what vendor work it unlocks. For each milestone state the prerequisite, output, confirmed owner, and reviewer. Preserve unresolved inputs and dependency-based timing; do not invent calendar dates, commitments, permissions, provisioning steps, completed tasks, or evidence that first value has been achieved. A sample demonstration is not proof of customer success. Keep credentials and private source material out of the page and include only audience-safe details and approved links. Create readable static HTML with no scripts or forms. Use my saved artifact style if available. Include the supplied snapshot date and plan owner, and keep authoritative progress and approvals in our existing project workflow. Show me the draft and unresolved questions for review. Do not publish or change access without separate explicit approval.

Check before you shareAccuracy, clarity, and permission

Is the customer's agreed first useful result clear, with evidence rather than a generic completion percentage?
Can each side identify its next action, owner, and dependency?
Are dates and commitments agreed, proposed, or unresolved exactly as the sources state?
Is a sample demonstration clearly different from the customer's actual result?
Are sensitive inputs, credentials, and internal-only notes excluded?
Does the page name its snapshot owner and explain where updates and questions belong?

When HTML fits

A customer-ready reading page assembled from your authorized kickoff notes, outcome agreement and task records. Use it to make the shared plan understandable without requiring the customer to learn another editor just to read it.

When another format fits better

Use an onboarding or project platform when customers need to submit inputs, update tasks, receive automated reminders, or track live progress. Keep provisioning, credentials, approvals, and authoritative completion records in their existing systems. This page explains the plan; it does not execute it.

What we started withThe same facts, as an email

Fictional project email

Cedar Studio × Signal Desk — next steps after kickoff

Hi Mira and Jules,

Here is our September 7, 2026 snapshot. Our agreed first useful result is to review one weekly campaign summary, identify one change and record one next action in the existing project thread. We have not achieved that yet.

The pilot covers one campaign, supplied synthetic data, a draft and a guided review. Live account connections, historical imports and company-wide rollout are excluded. Mira, please confirm the campaign and the meanings of its supplied fields in the project thread. Those inputs are pending.

I will prepare the draft after those inputs are confirmed, using only the supplied source. Drafting has not started. Jules will then check totals against that source, identify a change and record the next action in the thread. The review has not happened; none of the milestones is complete.

At kickoff we proposed review within five working days after input confirmation. No date or booking is confirmed, and this is not a service commitment. While waiting I can demonstrate the format using a synthetic sample, but no demonstration is recorded as complete, and a demonstration would not count as customer first value.

Please send questions and confirmations in the same thread; no response time is promised. I will update this snapshot after review. It is not live tracking and contains no credentials, private customer information or working system links.

Theo, plan owner

Inspect the HTMLOne self-contained file

The example is sanitized and isolated from this site. No scripts, forms, or live data.

<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><title>Cedar Studio · First useful report</title><style>
*{box-sizing:border-box}html{color-scheme:light}body{margin:0;background:#f6f8f5;color:#20352f;font:17px/1.65 system-ui,sans-serif}main{max-width:960px;margin:auto;padding:clamp(20px,5vw,64px)}h1,h2,h3,p{margin:0 0 18px}h1{font:500 clamp(32px,5vw,58px)/1.12 Georgia,serif;letter-spacing:-.025em;overflow-wrap:anywhere}h2{font:500 29px/1.25 Georgia,serif}h3{font-size:19px;line-height:1.4}.label{font:700 12px/1.5 system-ui,sans-serif;letter-spacing:.1em;text-transform:uppercase}.intro{font-size:20px}.action{background:#174b40;color:#fff;padding:26px;margin:28px 0}.action p:last-child{margin:0}.grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(min(100%,235px),1fr));gap:20px;margin:24px 0}.card{background:#fff;border:1px solid #bfcec4;padding:24px}section{margin:36px 0}ul,ol{padding-left:23px}li{margin-bottom:14px}.note{color:#455e53;font-size:14px}.pending{border-left:5px solid #92651d;padding-left:20px}footer{border-top:1px solid #bfcec4;padding-top:24px;margin-top:40px;font-size:14px}@media print{body{background:white}.card,.action{break-inside:avoid}}
</style></head><body><main>
<header><p class="label">Cedar Studio + Signal Desk / Fictional example</p><h1>Your first useful report. One clear next step.</h1><p class="intro">Review one weekly campaign summary, identify one change, and document one next action in the existing project thread.</p><p class="note">Agreed at kickoff · First value is not yet achieved.<br>Reviewed snapshot: September 7, 2026 · Plan owner: Theo</p></header>
<aside class="action"><p class="label">Customer action / Inputs pending</p><h2>Mira, confirm the campaign and field meanings.</h2><p>Use the existing project thread. Those inputs unlock Theo’s report draft. Draft work has not started.</p></aside>
<section><h2>A responsibility on each side</h2><div class="grid"><article class="card"><p class="label">Customer / Mira</p><h3>Confirm the inputs</h3><p>Choose the campaign and confirm the meanings of its supplied fields in the project thread.</p><p class="note">Status: required inputs pending.</p></article><article class="card"><p class="label">Vendor / Theo</p><h3>Prepare the report draft</h3><p>Start after required inputs are confirmed. Use only the supplied source, with no live account access.</p><p class="note">Status: not started.</p></article><article class="card"><p class="label">Customer / Jules</p><h3>Review and record the action</h3><p>Check totals against the supplied source, identify one change, and record one next action in the existing project thread.</p><p class="note">Status: review not yet performed.</p></article></div></section>
<section><h2>The path to the first result</h2><ol><li><strong>Inputs confirmed.</strong> Mira supplies the campaign and field meanings before draft work begins.</li><li><strong>Draft prepared.</strong> Theo turns the confirmed inputs into a report for Jules to review.</li><li><strong>Customer review recorded.</strong> Jules checks the totals and records the observation and next action in the project thread.</li></ol><p class="note">No milestone is marked complete in this snapshot.</p></section>
<section class="pending"><p class="label">Timing / Proposed, not booked</p><h2>The clock depends on confirmed inputs.</h2><p>Review is proposed within five working days after required inputs are confirmed. No calendar date or booking is confirmed. This interval is not a service commitment.</p></section>
<section><h2>What this first phase includes</h2><div class="grid"><article class="card"><h3>In the pilot</h3><ul><li>One campaign.</li><li>Supplied synthetic data.</li><li>A report draft.</li><li>A guided customer review.</li></ul></article><article class="card"><h3>Outside this phase</h3><ul><li>Live account connections.</li><li>Historical imports.</li><li>Company-wide rollout.</li></ul></article></div></section>
<section><h2>A demonstration can help. It is not the result.</h2><p>While inputs are pending, Theo can show the format with a synthetic sample. That demonstration does not count as customer first value. No demonstration is recorded as complete.</p><p>The evidence we need is Jules’s review of the report totals, an identified change, and a next action recorded in the project thread. That review has not happened yet.</p></section>
<section class="card"><h2>Questions and changes belong in the project thread.</h2><p>Ask Theo there if an input or instruction is unclear. No response-time promise is supplied. Record task changes and customer confirmation there; Theo updates this page after review.</p><p class="note">This is a reviewed snapshot, not live progress tracking. It does not collect inputs or provision access.</p></section>
<footer>Fictional worked example by share/artifacts. Organizations, names and dates are invented for demonstration. Source: the fictional kickoff notes accompanying this example. No private customer data, credentials or working system links are included.</footer>
</main></body></html>

The original worked scenarioThe source scenario, step by step

A first report, with responsibilities on both sides

A fictional customer and reporting service. These supplied kickoff facts become a shared path, not a claim that onboarding is complete.

The original notes

Cedar Studio and Signal Desk agreed the first useful result: review one weekly campaign summary, identify one change, and record one next action. Mira must confirm the campaign and supplied field meanings; pending. Theo prepares the draft only after those inputs. Jules checks totals against the supplied source and records the action in the existing project thread. Review is proposed within five working days after required inputs are confirmed; no date booked. A synthetic sample can demonstrate the format while waiting, but it does not count as customer first value. Live connections and wider rollout are excluded. First value is not yet achieved.

First useful result

Review one weekly campaign summary, identify one change, and record one next action. First value is not yet achieved.

Customer next step

Mira confirms the campaign and supplied field meanings. These inputs are pending.

Vendor next step

Theo prepares the draft after required inputs are confirmed. A synthetic sample may demonstrate the format but does not count as customer first value.

Evidence

Jules checks totals against the supplied source and records the action in the existing project thread.

Timing and limits

Review proposed within five working days after required inputs are confirmed; no date booked. Live connections and wider rollout are excluded.

The customer sees what they can unblock, what the vendor will deliver, and how both sides will recognize progress.

Questions, adaptations & sourcesGo deeper when you need to

How is this different from a new-hire onboarding guide?

A new-hire guide helps an employee do their first tasks and find internal policies. A customer onboarding plan coordinates two organizations around a purchased service: agreed value, customer prerequisites, vendor work, and evidence that the first outcome has been reached.

What if the customer has not supplied the inputs yet?

Name the missing inputs, the confirmed owner, and the work waiting on them. Keep any dependent date conditional. You can offer a clearly labeled sample if appropriate, but do not mark the customer's outcome achieved because a demonstration worked.

Can the customer check off tasks on this page?

No. It is a static reading page, not a live checklist. Direct the customer to the agreed project workflow for updates and questions, then revise this snapshot after reviewing those changes.