This guide is for people who help other teams use AI. You might work alone, in a small firm or inside a larger company. You might run training, build workflows or write AI policy.
AI work makes a lot of loose pieces. You have chats in ChatGPT, Claude and Gemini. You have prompts that work well, and steps you repeat for each client. Most of it lives in chat history, where it is hard to find again.
The 16 plays in this guide help you answer five questions:
Clients: Where is everything for this client?
AI chats: Which chat was that work in?
Processes: How do we do this job the same way each time?
Prompt libraries: What can my client keep and use after I leave?
Proof of work: What did we deliver, and what is still open?
You do not need to read the guide from start to end. Start with the question that matters most to you now.
How each play works
Each play starts with a familiar problem. It then shows one way to set it up in Humble, what to check and what gets easier.
These are ideas, not rules. Change them to fit the way you already work.
How every play works in Humble
A few simple ideas come up again and again:
One home per client:Keep the links, notes and tasks for a client together, so you never ask where something is.
Every chat has a home:Save each AI chat to the task, note or person it is for.
Two kinds of chat:A one-off chat goes on its task. A chat you use again and again goes on a process note.
Prompts are notes:Write each prompt you trust into a note, so you can share it and improve it.
One plan you both see:Share the project tasks with the client, so they know what you need and what comes next.
Hand over as you go:Build what the client keeps during the work, not in the last week.
Chapter 02~8 min read · four plays
Client work
Where is everything for this client?
Most AI consultants work with more than one client at a time. This section helps you give each client one home, plan the project with them in one shared view, see all your clients together and remember each person you work with.
The plays in this section
Give every client one home.
Plan the project with your client in one shared view.
See every client in one view.
Remember each person at the client.
Play 1: Give every client one home
The situation
The statement of work is in your email. The kick-off deck is in Google Slides. The best chat from the discovery call is somewhere in Claude. When the client asks a question, you open five tabs to find the answer.
One way to set this up in Humble
You can create a space for the client, such as Northwind.
Add a note called Client home: Northwind. Write the goal of the work, the dates, the main contact and what you will deliver.
Open the statement of work and use the browser extension to add it to the client home. Do the same for the kick-off deck and the client’s shared folder.
Add the AI chat with the most useful summary of the client, such as your discovery call notes in Claude.
Tag the note with the client, such as #Northwind.
Check this
A client home is most useful when it always holds:
The statement of work, or the agreed scope.
The main contact and who signs off.
The kick-off deck and the plan.
The AI chat that holds the best client summary.
The client’s shared folder or workspace.
A useful test is: Could I start a call with this client after one minute on this note?
What changes: you start each piece of client work from one note, not from five tabs.
My NotesAdd note
Recent 1
Client home: NorthwindAI support pilot · Oct to Dec · Dana PriceStatement of workKick-off deckDiscovery call summary#Northwind
The key AI chat too
A client home note in Humble, with the statement of work, kick-off deck and discovery chat linked to it.
Play 2: Plan the project with your client in one shared view
The situation
The project plan is a slide from the kick-off. The client does not know what you need from them this week, so data access and sign-offs arrive late. Every week, someone asks, “What happens next?”
One way to set this up in Humble
Make a task for each part of the project, with a date and the client tag. Start each one with a verb, such as Run discovery interviews.
Assign the tasks the client owns to the right person at the client, such as Give access to the support inbox or Sign off the pilot scope.
Put this week’s work in Now and the next two weeks in Next. Put the rest of the plan in Later. Later is your roadmap.
Share the client’s space with your contacts at the client. They see the same plan you do.
Open the plan together at the start of each weekly call. Move tasks when the plan changes.
Check this
Every task the client owns needs one named person and a date. A useful question is: Does the client know what we need from them this week?
You can assign a task to someone at the client even if they don’t have a Humble account. To see all their tasks in one place and manage them, they need a Humble account.
Before you share the space, check that everything in it is fine for the client to see.
What changes: the client sees what they owe you and what comes next, without a status email. The plan is one shared view, not a slide that goes out of date.
Northwind AI pilotSearch tasks…Filter
Now 2This week
DPGive access to the support inboxDue 7 Oct#Northwind
JRRun discovery interviewsDue 9 Oct#Northwind
Next 2Next 2 weeks
DPSign off the pilot scopeDue 16 Oct#Northwind
JRBuild the reply prompts#Northwind
Later 2Roadmap
JRTrain the support team#Northwind
DPReview the pilot results#Northwind
What the client owes you
A project plan shared with the client. Orange tasks belong to the client and purple tasks to you. Later shows the roadmap.
Play 3: See every client in one view
The situation
You have three clients this month. Each has its own calls and deadlines. While you focus on one, a task for another one slips.
One way to set this up in Humble
Give each client its own tag, such as #Northwind or #Meridian.
Tag each task and note with its client.
Connect your Google or Outlook calendars. Client calls and workshops then sit next to your tasks.
Start each day with what is due today, across every client.
Check this
Useful views might include:
Everything due this week, across all clients.
One client’s tasks only, before a call with them.
Tasks that are waiting on the client.
What changes: you can move between clients without losing track of the others.
Play 4: Remember each person at the client
The situation
The head of operations wants quick wins. The legal lead is worried about data. You learned this on two calls a month ago, and now you can’t remember who said what.
One way to set this up in Humble
Open each person’s LinkedIn profile. Use the browser extension to save them as a contact.
Add a note on what they care about and what worries them.
Tag them with the client, such as #Northwind, so the tag works as a list of people.
Before a call, open the person to see their timeline of notes, meetings, emails and tasks.
Check this
Before each call, ask: What does this person need from the work, and what did I promise them?
What changes: you start every call knowing what each person cares about.
Chapter 03~7 min read · three plays
AI chats
Which chat was that work in?
Many of your chats are one-offs. You open a chat to test an idea, check some wording or think through a problem. The chat helps, then it is lost in a long list. This section helps you give every chat a home.
The plays in this section
Save each one-off chat to its task.
Find a chat by client, not by scrolling.
Keep the chats that work well.
Play 5: Save each one-off chat to its task
The situation
You are writing an AI policy for a client. You draft it in Claude, check the risk wording in ChatGPT and compare tool terms in Gemini. A week later, the client asks why you chose one sentence. You can’t find the chat that explains it.
One way to set this up in Humble
Make a task for the work, such as Draft AI policy for Northwind, with a due date and the client tag.
Open a chat in ChatGPT, Claude or Gemini.
Click the Humble extension and pick the task. Humble saves the chat to it.
Give the chat a clear name, such as Policy first draft, so the link on the task makes sense later.
Do the same for every chat you use on this task, in any AI tool.
Check this
A useful habit: before you close a chat, save it. If it helped with a task, it belongs on that task.
If a chat does not belong to any task, ask if it should be a new task.
What changes: every chat for a piece of work is on the task, whichever AI tool you used.
Back to tasks
Draft AI policy for NorthwindJR
Oct 17NOW
First draft of the AI use policy for the support team.
Related items
LINKS
Policy first draftRisk wordingCompare tool terms
Add this page
TAGS
Northwind
Chats from any AI tool
A task in Humble with three AI chats saved to it, one each from Claude, ChatGPT and Gemini.
Play 6: Find a chat by client, not by scrolling
The situation
You have had 12 Claude chats about one client. They sit in a list with every other chat you have had this year. Search finds the word, but not the chat you meant.
One way to set this up in Humble
Open the task the chat was for. Every chat saved to it is there.
If you can’t remember the task, filter by the client tag.
If the chat was about a person, such as notes before a hard call, save it to that person. Open the person to find it again.
Check this
A useful test is: Can I find last week’s best chat for this client in under a minute?
What changes: you stop asking an AI tool the same question twice because you lost the first answer.
“The huge gap in my workflow was keeping track of all the chats I create, and what for. Having all my tasks and notes in one place across the whole web is just amazing.”
SSSunnie Southern CEO, Viable Synergy
Play 7: Keep the chats that work well
The situation
One chat gave you a great way to sort interview notes into themes. You will need it for the next client too. But it is saved on one client’s task, and next month you won’t remember where.
One way to set this up in Humble
When a chat works well, ask: Will I do this job again?
If yes, set up a chat for that job alone. In Claude this could be a project. In ChatGPT it could be a custom GPT. Give it the instructions that worked.
Save that chat to a process note for the job, not to one client’s task. Chapter 4 shows how.
Copy the prompt that worked into your prompt library. Chapter 5 shows how.
Two kinds of chat
Where each kind of chat goes
Kind of chat
What it is like
Where to save it
One-off chat
Used once, for one piece of work
The task or person it was for
Chat for a job
Set up for one job and used again and again
The process note for that job
What changes: your best chats become tools you use again, not lucky finds.
Chapter 04~7 min read · three plays
Processes and procedures
How do we do this job the same way each time?
You do some jobs for every client: discovery interviews, AI readiness checks, workshop plans, policy drafts. This section helps you write each job down once, with links to the AI chat set up for it.
The plays in this section
Write a process note that links its AI chat.
Keep one list of all your processes.
Give a process to the client’s team.
Play 8: Write a process note that links its AI chat
The situation
You run discovery interviews for each new client. Each time, you rebuild the steps from memory. You also look for the Claude project you set up to sum up each interview.
One way to set this up in Humble
Add a note called How we run discovery interviews.
Write the steps in order. Keep each step short.
At the step where AI helps, name the chat to use. For example: “Step 4: paste the notes into the Interview summary chat.”
Open that chat, such as your Claude project or custom GPT, and use the browser extension to add it to the note.
Link the other things the job needs, such as the question list in Google Docs.
Tag the note #Process.
A process note to copy
Name: How we [job].
When to use it: one sentence.
Steps: in order, one action each.
AI chat: the chat set up for this job, linked to the note.
Other links: templates, question lists, examples.
Last checked: the date you last ran it.
A useful test is: Could someone new do this job from the note alone?
What changes: each job is done the same way every time, with the right AI chat one click away.
A process note in Humble. The steps name the AI chat to use, and the chats are linked to the note.
Play 9: Keep one list of all your processes
The situation
You have written some processes down. One is in Notion, one is in a Google Doc and one is in an old email to a contractor. When you need one, you don’t know where to look.
One way to set this up in Humble
Tag every process note #Process. Open the tag to see the full list.
If a process already lives in Notion or Google Docs, you don’t need to move it. Make a short process note and link the doc.
Name each note the same way: How we [job]. The list then reads like a menu of what you do.
When you change how you do a job, change the note and the date it was last checked.
Processes many AI consultants keep
How we run discovery interviews.
How we check if a team is ready for AI.
How we plan a training workshop.
How we draft an AI use policy.
How we choose a first AI pilot.
How we close a project and hand over.
What changes: your way of working is written down in one place, and you can grow it over time.
Play 10: Give a process to the client’s team
The situation
Part of your job is to leave the client able to do the work without you. But your process lives in your head and your chat history, so the client team can’t repeat it.
One way to set this up in Humble
Make a copy of your process note for the client, such as How Northwind sorts support tickets with AI.
Change the steps to use the client’s own tools and words.
Link the chat the client’s team will use, set up in their own AI account.
Use the add person button on the note to share it with the person who will own the process.
Check this
Before the project ends, ask: Has someone at the client run this process without me?
What changes: the client keeps the way of working, not only a slide about it.
Chapter 05~6 min read · three plays
Prompt libraries
What can my client keep and use after I leave?
A good prompt is worth keeping. This section helps you build a prompt library as notes in Humble, share it with your client and keep it up to date.
The plays in this section
Build a prompt library as notes.
Share the prompt library with your client.
Keep the library up to date.
Play 11: Build a prompt library as notes
The situation
Your best prompts are in old chats, a text file and a slide from last year’s workshop. When a client asks for “the prompt you showed us”, you rewrite it from memory.
One way to set this up in Humble
Make one note for each prompt, or one note for each group of prompts, such as Prompts: customer support replies.
Paste the prompt in full. Mark the parts the reader fills in, such as [customer name].
Add a line on when to use it, and a line on what a good answer looks like.
Link an example chat where the prompt worked well.
Tag each note #Prompt and with its topic, such as #Support.
A prompt note to copy
Name: Prompt: [what it does].
Use it when: one sentence.
The prompt: in full, with [fill-in parts] marked.
A good answer: what to look for.
Example: a link to a chat where it worked.
Works best in: ChatGPT, Claude or Gemini, if it matters.
For example: Prompt: reply to an angry customer. “You are a support agent at [company]. Read the email below. Write a short, calm reply that says sorry once, explains what happens next and gives a date. Email: [paste email].”
What changes: your best prompts are in one place, ready to use and ready to share.
Play 12: Share the prompt library with your client
The situation
At the end of a workshop, you send the prompts as a PDF. A month later, you improve three of them. The client is still using the old PDF.
One way to set this up in Humble
Make a note for the client’s library, such as Prompt library: Northwind support team.
Copy in the prompts that fit their work. Change the examples to use their products and their words.
Click the add person button on the note. Type your client’s email and click Send.
Link the library to the client home, so it is part of what you deliver.
Check this
Before you share, read the library as the client would. Ask: Could someone who missed the workshop use these prompts?
Remove anything that names another client.
What changes: the client gets a library they can open and use, not an attachment that sits in an inbox.
Manage access
Prompt library: Northwind support team#Prompt#Northwind
Share with an email address
dana@northwind.comSend
People with access
JRYou
DPdana@northwind.com
Add your client
Sharing a prompt library note in Humble. Type the client’s email, click Send, and they appear in the list of people with access.
Play 13: Keep the library up to date
The situation
AI tools change often. A prompt that worked well in spring gives weaker answers in autumn. Nobody notices until a client complains.
One way to set this up in Humble
Add a Last checked date to each prompt note.
Make a task each month: Check the prompt library. Test the prompts you use most.
When you improve a prompt, update your own note first. Then update the notes you shared with clients.
If a client has a new use for AI, add a prompt for it instead of writing a new document.
Check this
Each month, ask: Which prompt did I change, and which clients use it?
What changes: your library gets better each month, and clients keep getting value after the project ends.
Chapter 06~5 min read · three plays
Proof of work
What did we deliver, and what is still open?
Clients pay for results they can see. This section helps you show what you did, end each meeting with clear next steps and keep in touch after the project.
The plays in this section
Show what you delivered.
End every client call with owned next steps.
Hand over at the end of the project.
Play 14: Show what you delivered
The situation
It is time to send an invoice or a progress report. You know you did a lot. But you have to rebuild the list from your calendar, your sent emails and your chat history.
One way to set this up in Humble
Tag every task with its client as you go.
When you finish a task, mark it done. It appears on your timeline.
Before an invoice or a review, filter the timeline by the client and the weeks it covers.
Open a task to see the chats, docs and notes behind it, if the client asks for detail.
Check this
A useful test is: Can I list what I did for this client last month in five minutes?
What changes: your report and your invoice come from work you already saved, not from memory.
Play 15: End every client call with owned next steps
The situation
A workshop ends with good ideas. Everyone agrees to “follow up”. Two weeks later, nothing has moved, and nobody is sure who said they would do what.
One way to set this up in Humble
Before the call ends, read out each next step and who owns it.
After the call, make each step a task with an owner and a date. Tag it with the client.
For a step the client owns, assign it to them on the shared plan (Play 2). Or share the task with their email, and they can open it straight away.
Link the call notes and any chat you used to the tasks they belong to.
Check this
For each next step, ask: Does it have one owner and one date?
What changes: next steps leave the room with an owner, and the client can see what is theirs.
Play 16: Hand over at the end of the project
The situation
The last week of a project is busy. You rush to write a handover document. Some of what the client needs is missing, and some is out of date already.
One way to set this up in Humble
Start the handover note in the first week, such as Handover: Northwind.
Each time you finish a process note or a prompt library for the client, link it to the handover note.
In the last week, share the handover note with the client owner.
Keep the client’s people as contacts, with a note on what you did together. Open them again when they get in touch.
A handover note usually holds
What you delivered, with links.
The process notes the client now owns.
The client’s prompt library.
What is still open, and who owns it.
Ideas for the next piece of work.
What changes: the handover is ready when the project ends, and the next project starts from what you learned.
Chapter 07~3 min read
The weekly rhythm
The plays work best as small habits. The rhythm below is a starting point. Change it to fit your week.
Every day: save as you go
You can start with a short look at:
What is due today, across every client.
Which client calls need you to prepare.
During the day, save things close to where they appear:
A useful AI chat → saved to its task.
A client email → linked to its task.
A new request → a task with an owner, a date and the client tag.
Before each client call
Open the client home.
Open each person you will meet, and read their timeline.
Open the shared plan: what the client owes you, and what comes next.
Once a week: tidy and plan
Give any chat without a home a task or a process note.
Turn a chat that worked well into a process or a prompt.
Plan next week for each client.
Once a month: check and report
Filter the timeline by client for reports and invoices.
Test the prompts you use most.
Update the process notes you used this month.
At the end of a project
Share the handover note.
Copy what you learned into your own process notes.
Keep the client’s people as contacts.
If you only build one habit, make it this one: save every AI chat to its task before you close it.
Chapter 08~4 min read
How to organise this in Humble
There is no single correct setup. The structure below is a simple place to start.
What goes where
When you have…
A useful place for it
A client
A space, a client tag and a client home note
The scope, plan and key links
Links on the client home note
The project plan and roadmap
Tasks in Now, Next and Later, in a space shared with the client
Something the client needs to do
Task assigned to your contact at the client
Something you need to do
Task with a date and the client tag
A one-off AI chat
Saved to its task, or to the person it is about
An AI chat set up for one job
Linked to the process note for that job
A job you do for every client
Process note, tagged #Process
A prompt you trust
Prompt note, tagged #Prompt and its topic
Prompts for one client
A prompt library note, shared with the client
A person at the client
Contact, with notes and a timeline
A next step the client owns
Task shared with their email
An email about the work
Linked to its task
What you hand over
Handover note, shared at the end
Spaces
One space for each client is usually enough, plus one for your own way of working. For example:
Northwind
Meridian Group
Our methods (your process notes and prompt library)
Share a client space with your team and your contacts at the client, so everyone sees the same plan. Keep your methods space to yourself, or to your own team.
Tags
Client
#Northwind#Meridian#Acme
Kind of note
#Process#Prompt#Handover
Topic, only where useful
#Support#Policy#Training
Keep client tags and topic tags apart. A prompt for support teams is #Prompt and #Support. Add a client tag only to that client’s own copy.
Naming
Client home: Client home: [client].
Process notes: How we [job], such as “How we run discovery interviews”.
AI chats: name the chat for what it did, such as “Policy first draft”.
Tasks: start with a verb, such as “Draft AI policy for Northwind”.
Handover: Handover: [client].
Chapter 09~2 min read · 30 min to do
The 30-minute setup
You can use this checklist to set up your first client in half an hour. It does not need to hold everything to be useful.
0–5 minutesInstall the browser extension. Connect Google or Outlook Calendar.You’ll have: A way to save chats and pages, and your client calls next to your tasks.
5–12 minutesCreate a space and a client home for your busiest client. Add the scope, the plan and the client tag.You’ll have: One place to start all work for that client.
12–20 minutesMake tasks for the project plan in Now, Next and Later. Assign the client’s tasks to them and share the space. Save your recent AI chats to their tasks.You’ll have: A plan the client can see, and this week’s chats where you can find them again.
20–26 minutesWrite one process note for a job you do often. Link the AI chat you use for it.You’ll have: The first page of your methods.
26–30 minutesCopy your three best prompts into prompt notes, tagged #Prompt.You’ll have: The start of a prompt library you can share.
The end state
You should be able to answer:
Where is everything for this client?
Which chat was that work in?
How do we do this job the same way each time?
What can my client keep and use after I leave?
What did we deliver, and what is still open?
You bring the judgement, the client relationships and the AI know-how. Humble keeps your chats, processes and prompts connected to the work, so you don’t have to hold it all in your head.
See how it works in Humble
The plays in this guide use features available in Humble today.
See how Humble keeps your tasks, notes, people and AI chats connected. If you would like to bring Humble to your clients, you can also join our AI consultant partner network.
This guide was written by the Humble team, based on how AI consultants can use the product in their day-to-day work.
It is a practical guide to one way of working, not the only way to run AI projects. Every client is different, so use the parts that help and change the rest.
Humble saves chats from ChatGPT, Claude and Gemini through the browser extension. Claude projects and custom GPTs are named as examples of chats set up for one job; Humble links to them like any other page. Client names in the examples, such as Northwind, are invented. The guide describes Humble as of October 2026. Some product details may change over time.
Receive new role guides as they are published. Occasional, not frequent.
We will email you a confirmation link first. Nothing is sent until you confirm, and you can unsubscribe at any time. How we use your email.
Want to try it yourself first?
No team rollout and no commitment. Use Humble with your next client and see whether having your chats, processes and prompts in one place makes the work easier to hold.
Statement of work
Kick-off deck
Discovery call summary
