Skip to content

Customer Experience Blueprint

Safety checked

Onboard a new agency client in Hive from a project template

1HiveNovember 2026

Avoid a client’s first week starting with unowned tasks or a missing kickoff. The setup shifts template dates, flags weekend deadlines and open owners, then verifies approved updates in Hive before handing over a week-one list and welcome-note draft.

Install Prompt

Copy this prompt and paste it into your AI agent to install.

What problem does this solve?

Each new client needs the same start. Someone makes the project, copies the standard tasks, sets a kickoff, and gives week one an owner and a date. Teams do this by hand, and steps get missed. A task has no owner. A date is left over from an old job. The kickoff is not on the board. The client's first week then starts with a gap.

This Blueprint does the set-up from one brief. It then checks the result against what Hive holds, and tells you what is still open.

Start here when the client has signed and you know the team.

How does it work?

This Blueprint takes a short brief and sets up a new client project in Hive from one of your templates. It adds a kickoff card, sets owners and dates for week one, and reads the result back. You approve each write. It drafts the client welcome note in chat and does not send it.

Status: built and run. Last run on Nov 19, 2026, in Claude with the Hive connector, on a live Hive workspace.

  1. Give the brief. You tell Claude the client, the project name, the start date, the kickoff date, who is on the team, and any special need for week one.
  2. Pick the template. Claude lists the project templates in the workspace. You choose one. If there is none, Claude says so and stops. It does not make templates.
  3. Create the project. Claude shows the plan. After your yes, it creates the project from the template and adds the teammates you named. It moves the copied dates so that the earliest one lands on your start date. Owners from the template are not copied unless you ask.
  4. Read what the template made. Claude lists the cards with dates and owners, sorted by deadline. It names the cards with no owner. Copied dates can land on a weekend. Claude lists every card with a start date or a due date on a Saturday or a Sunday and asks you if it must move.
  5. Add the kickoff and set week one. Claude shows a table: the kickoff card with an agenda, and an owner and a date for each card. After your yes, it writes them to Hive. It reads them back to check.
  6. Hand over. You get the week-one list, what is still open, and a draft welcome note for the client. If you ask, Claude posts a status update on the project.

Example from our run: a template with 7 cards and a first date of Dec 1 was used for a project starting Mon Jan 11, 2027. Every date moved by 41 calendar days. Two cards then fell on a Sunday. Claude showed this, and after a yes it moved them to Monday. The kickoff card was added for Tue Jan 12, and 6 of 8 cards got an owner. In a later test, a new Claude session that had only the skill file used a template with no dates and a sub-card. It created the project, kept the sub-card under its parent, added the kickoff card, and proposed week-one dates for approval.

What's the biggest win?

Every client starts the same way. No card keeps a date from an old job. The team opens the board and sees who does what in week one. The template stays as it was: after our copies, it still had its 7 cards and its dates.

What's required to run this?

  • A Hive workspace and permission to create projects. Hive's Free plan limits the number of projects.
  • At least one template in the workspace. This is a project saved as a template.
  • The Hive connector added in Claude. Set-up steps: https://hive.com/integrations/claude?utm_source=g2&utm_medium=blueprint&utm_campaign=agency-client-onboarding
  • The skill file from this Blueprint, added to Claude as a skill or pasted as the first message.
  • Optional: a free-hours check for the team in week one, if your workspace has Team resourcing. Hive lists Team resourcing as an add-on to the Teams plan (+ $5 for each user each month on hive.com/pricing).

What are the constraints?

  • Claude does not build templates. Make the template in Hive first.
  • It adds only the teammates you name to the project. It does not add the client. It never invites a person. If you need an invite, you do it in Hive. We tested it in a workspace with one member.
  • Hive notifies each person who becomes the owner of a card. It does not notify people when Claude adds them to the project.
  • The welcome note is a draft in chat. Claude does not send it.
  • It does not send a calendar invite for the kickoff. It makes a card with the date. Send the invite yourself.
  • Copied dates move by calendar days, not working days. The weekday of a card can change, so a copied date can land on a weekend. Claude lists those cards and asks you if each must move. Public holidays and leave are not checked.
  • If a template card has no date, the copy has no date. Claude proposes dates for you to approve. Sub-cards are copied with their parent card.
  • Owners from the template are copied only if you ask. In our test, the one owned template card kept its owner.
  • It does not set budgets, rate cards, or billing defaults.
  • It does not link the project to a CRM account.
  • Every write needs your yes.
  • It runs when you start it. We tested it in Claude.

Tools in this Blueprint

Hive logo
4.6(692 reviews)
Claude logo
4.6(513 reviews)

About This Blueprint

Industry
Advertising & Marketing
2 Skills
Product & DesignSafety checked

Send Weekly Product Defect Reports

Catch product defects before scattered support tickets obscure a rising trend. Weekly reports group faults by product and type, compare them with the prior four weeks, and include customer photos and quotes for faster quality investigations.

Yuma AIYuma AIClaudeClaudeShopifyShopify

Urska Blagojevic

GTM Lead at Yuma AI (YC W23)

2 Skills
Customer ExperienceSafety checked

Fix Wrong AI Agent Answers Before They Recur

Stop the same support mistake from frustrating customers again: trace incorrect Yuma replies to the Handbook, missing order data, failed actions, or bugs, then test a proposed fix before publishing it. A weekly report highlights recurring causes and the next tickets to investigate.

Yuma AIYuma AIShopifyShopifyClaudeClaude

Urska Blagojevic

GTM Lead at Yuma AI (YC W23)

1 File
ProductivitySafety checked

Find the date a project runs out of budget, and the cards that used the most time

Catch a budget overrun before month-end by seeing when logged hours or project costs will run out at the current pace. The breakdown shows the arithmetic, flags the cards consuming the most time, and waits for your approval before posting to Hive.

HiveHiveClaudeClaude