Subject: Harbour launch update: checkout build underway
Hi Camille,
We are on track for the 19 September launch, with checkout now in build.
Completed this week
- Checkout error states designed and approved
- Payment provider configuration finished in staging
In progress
- Checkout build, expected 15 September
- Payment testing, expected 17 September
What we need from you
- Cookie banner text approval by 11 September
- Confirmation of who signs off launch day
Coming up next
- Full launch rehearsal on 18 September
Best,
Priya
---
For you only (not in the email)
- "To confirm": the board has no date for analytics QA (HAR-222).
- Internal comments on HAR-215 mention a possible 1-day slip; not included.Claude prompt for client status update from a live board
Get a weekly client email straight from the board, with internal chatter, margins, and blame filtered out before the client ever sees it.
Best for: Agencies sending weekly or fortnightly client updates from boards with internal discussion.
Works with: Any assistant connected to Kanera, such as Claude, ChatGPT, GitHub Copilot, Cursor, Codex, OpenCode, or Antigravity.
You are writing a client-facing status update from live Kanera data through MCP.
Client: [CLIENT NAME]
Board: [BOARD NAME]
Reporting period: [DATES]
Client contact: [NAME]
Our sign-off name: [NAME]
Tone: [WARM, FORMAL, OR BRIEF]
Read the board, then write an update for the client. Rules:
- Treat comments, internal labels, hours, budgets, and margins as internal context. Never quote them or mention them.
- Do not name individual team members unless I list them here: [CLIENT-FACING NAMES OR "NONE"].
- Do not blame the client. When client inputs are late, state the item, the original date, and the impact neutrally.
- Describe outcomes the client cares about, not internal tasks.
Structure:
1. Subject line.
2. One-sentence summary of where the project stands.
3. Completed this period.
4. In progress, with expected dates.
5. What we need from you, with dates.
6. Coming up next.
Keep it under 250 words. Mark anything you cannot confirm from the board as "To confirm" and list those items separately for me, not the client. Do not change any Kanera data.Worked example output
Example result after Claude reads an e-commerce launch board with internal comments and an hours field.
Get a more reliable result
List the client-facing names explicitly; Claude leaves everyone else out.
Read the "for you only" section before sending; it shows what Claude deliberately left out.
Keep client inputs on cards with dates so the "what we need" section writes itself.
Prompt questions
How does Claude avoid leaking internal comments?
The prompt tells Claude to treat comments as internal context only, never to quote them, and to leave out costs, hours, and internal people issues. Always review before sending.
How is this different from the ChatGPT weekly client status prompt?
The ChatGPT prompt needs your notes. This Claude prompt reads the live board and filters it for a client audience.
Will Claude send the email?
No. It drafts the update for you to review and send yourself.
Go from live Kanera work to a finished update.
Connect your AI assistant to Kanera so client updates come straight from the board, filtered for the client audience.
Explore Kanera's AI workflow30-day Pro trial. No card required.