What we set up in our two days, and how to keep it running.
Natasha and team,
It was such a pleasure to spend two days with you, setting your Claude up for success. In your words, you went from a "Frankenstein" of fourteen tools and a lot of manual digging to a connected Claude account that drafts in Natasha's voice, triages your inboxes, checks for failed payments while you sleep, and builds a revenue dashboard in minutes.
You should be very proud of yourselves - I've sat with teams who took a full day just to get their connectors working, and you did it before lunch!
This is your reference library for everything we covered. Thank you for being such a brilliant group to work with. Keep me updated on your successes with Claude!
Love, Chantelle x
First, who's here?
Pick your name and I'll take you to your part. It remembers you for next time.
Log out of Claude, log back in, try again. The age-old fix - it sorted several things on our two days too.
A connector has dropped off
Go to Customise, then Connectors, click Connect on the dropped tool and sign in again. Five minutes, and it's rare. Guide 02 has the full steps.
I can't see the team projects or connectors
Check the workspace switcher in the bottom left corner - you're probably in your personal workspace. Switch to the team one. This catches everyone at least once.
Content doesn't sound like Natasha
Check you started the chat inside the brand project - a chat outside it can't see the voice training. If you are inside it, tell Claude what's off and add the correction to the project instructions so it sticks for everyone. Guide 03 covers it.
A scheduled task ran strangely
Open the task, read its last run, and tell Claude in that task's chat what was wrong - it can usually fix its own instructions. Guide 05 has more.
Prompts worth stealing
Step at a timeI have ADHD. Please take me through this one step at a time, and ask me to confirm when I've done each step before giving me the next one.
You don't need ADHD for it to work.
Explain it simplyCan you explain how to do this using Claude, as simply as possible?
Ask Claude before you ask anyone else.
When it sounds like AIBe less wanky.
Chantelle's favourite prompt of all time.
Check firstBefore you do this, tell me your plan and wait for my go-ahead.
For anything that matters.
Stuck? Ask Chantelle
Email hello@choicewordsbychantelle.com with any question, however small. You'll get an answer, a quick fix or a Loom. WhatsApp works too.
Support runs to early December, with grace beyond it. If it's six or eight weeks down the line and you think "I should have asked about this", ask anyway.
If Zapier plays up, we'll jump on a Zoom and sort it together.
Where everything lives
The two brand content projects are in your team workspace under Projects.
Voice training sets, voice skills and the AI telltale glossary are in the shared Google Drive folder.
Dashboards are shared links - whoever built one updates it, everyone else just opens it.
The Zapier solutions doc is in the shared folder, and guide 07 covers it step by step.
Your map of everything. Each guide stands on its own, so when you think "how do I do that thing again?", grab the one with the right name and follow the steps.
You have Chantelle on email support until early December at hello@choicewordsbychantelle.com - any question, however small. She's also on WhatsApp if that's easier.
There's grace on that. If it's six or eight weeks down the line and you think "I should have asked about this", ask anyway.
When you get stuck, ask Claude itself first. Claude knows how it works.
Can you explain how to do this as simply as possible?
Where everything lives
The two brand content projects (Natasha Bray and School of Healing Mastery) are in your team workspace under Projects - everyone on the team can use them.
The voice training sets, voice skills and the AI telltale glossary are in the shared Google Drive folder, and the voice sets are also loaded into their projects.
The dashboards are shared links - whoever built one updates it; everyone else just opens the link.
The Zapier solutions doc is in the shared folder too, and guide 07 covers the same ground step by step.
The record of your two VIP training days (Monday 2 and Tuesday 3 November 2026), so anyone on the team can see at a glance what's now in place.
Day 1 - Monday 2 November
Morning - foundations and connectors
We started with what success looks like for you: a business that's easier to run, an AI system that searches your inboxes, Drive and Slack instead of you digging by hand, and reporting that pulls itself together.
We mapped your full tool stack and agreed Claude's job is to pull your existing tools together rather than replace them.
We worked through privacy and access: every connector is personal to the person who connects it. Natasha enabling a connector for the team grants permission to use that type of connector - it never shares her logins, email or calendar with anyone.
We restructured the accounts: the admin seats run on the support and School of Healing Mastery logins, so shared information stays with the business.
Everyone connected their tools: Google Drive, Docs, Sheets, Slides, Gmail, Calendar, Canva, Kajabi, Slack, Asana, Stripe (read-only), PayPal, Dropbox, Zoom, Descript and Zapier.
We built the "Natasha Bray brand content" project with the voice training set and AI telltale glossary, and tested it with a real post.
Afternoon - skills, scheduled tasks and dashboards
Skills: your living SOPs inside Claude, with human review points built in.
A scheduled workflow that checks Stripe for failed payments and prepares the standard follow-up.
Daily inbox triage: Claude summarises what's come in and drafts replies for you to approve.
The in-app browser for research, and how artifact sharing works - only the person who builds a dashboard needs the connectors; everyone else just opens the link.
The finance dashboard, built live across both businesses in minutes.
Day 2 - Tuesday 3 November
Morning - answers, Zapier and the lead tracker
Security and GDPR answered in full (guide 10 has it in writing).
The Zapier route for the tools without native connectors: Dubsado, Keap, ThriveCart, AddEvent and extra inboxes. Kirsty connected Keap herself from the guide.
Keap product tags set up, so every offer-link click now tags the contact and logs to the email click leads tab automatically. The log starts from 3 November - historical clicks can't be pulled in.
The lead tracker built from your Dream 1000 sheet: both brands, priority order by most recent activity and touch points, click any lead for their full picture, and follow-up tracking so nobody contacts the same person twice.
The lead sheet tidied into one source of truth, with the new Top 100 client lists and a "lead for" column per tab.
Afternoon - design systems
The Natasha Bray design system built in Claude, with your brand files and Natasha's voice baked in - so slides, carousels, sales pages and graphics come out on-brand and in her voice.
A full demo of what it produces: slide deck first drafts in under five minutes, carousels in three to four, sales pages, video captions, and export to Canva, PowerPoint, PDF or images.
Both Natasha and Amy taught to create new design systems from scratch, ready for the School of Healing Mastery system after its rebrand.
A settings fix so Claude can pull files straight from Canva.
Connectors are what let Claude reach your tools - your Drive, inbox, Canva, Kajabi and so on.
The one thing to understand first
Your Claude account has two workspaces: your personal one and the team one. You can switch between them from your name/workspace menu in the bottom-left corner.
Work in the team workspace - that's where the shared projects and team connectors live. Your personal workspace is for your own private use.
Every connector you set up is yours alone. Connecting Gmail means Claude can read your inbox when you ask it to - nobody else on the team can see your emails, your Drive or anything else you've connected.
ImportantWhen Natasha (as team owner) enables a connector, she's allowing the team to connect that type of tool. She is never sharing her own logins.
Add a connector
Open Claude and check you're in the team workspace.
Click Customise in the left-hand menu.
Click Connectors.
Find the tool you want and click Connect.
Sign in to that tool when it asks you.
Done - the connector stays signed in from now on. You won't need to log in each time.
Request a connector that isn't available
If a tool shows a Request button instead of Connect, Natasha hasn't enabled it for the team yet.
Click Request next to the tool.
The request goes to Natasha for approval.
Once she approves it, go back to Connectors and click Connect as above.
Reconnect one that's dropped off
Occasionally a connector disconnects itself - usually because that tool had a big update. Claude will tell you when this happens.
Go to Customise, then Connectors.
Find the tool showing as disconnected.
Click Connect and sign in again.
That's it - it's the same five-minute job as the first time, and it's rare.
For Natasha - owner controls
Go to Customise, then Connectors, while in the team workspace.
Click on any connector to see its team settings.
From there, you can control what the team is allowed to do with that connector type - for example, keeping Stripe read-only, which is how we left it.
Connector requests from the team arrive here for you to approve.
If something looks wrong
Nine times out of ten, the fix is: check which workspace you're in (bottom left), and if in doubt, log out of Claude and log back in. If a connector still misbehaves after reconnecting, email Chantelle.
For posts, emails and community content in Natasha's voice, for either brand.
What you have
Two team projects, one per brand:
Natasha Bray brand content - for the personal brand
School of Healing Mastery brand content - for the school
Each project holds a voice training set (the instruction manual that teaches Claude how Natasha sounds for that brand), the AI telltale glossary (the list of AI-isms Claude must avoid), and the project instructions (its job description and rules).
If you need the voice training sets, they're here:
Open the project for the brand you're writing for.
Start a new chat inside that project.
Tell Claude what you want (there's an example below).
Read the draft and ask for changes in plain English: "warmer", "shorter", "that second line doesn't sound like her".
Write a Facebook post announcing the next Millions Frequency cohort, focusing on the doors closing Friday.
AlwaysStart the chat inside the project. A chat outside the project can't see the voice training set, and the content will sound like standard AI.
Treat every output as a strong draft
The voice training set gets Claude much closer to Natasha than standard AI ever would, and it still wants a human read before anything goes out. Check it says what you'd say, tweak anything that doesn't sound right, then post. The more you correct it, the better you'll get at prompting it.
Make it better as you go
If you keep seeing the same mistake, add a rule so it stops happening for everyone:
Open the project.
Click into the project instructions.
Add the rule in plain English - for example: "Never open a post with a question."
Save. The rule now applies to every chat in that project, for the whole team.
You can also add examples to the project knowledge - a favourite email, a post that performed well - and Claude will use them as a frame of reference. Two or three excellent examples beat twenty average ones.
Your own projects
Anyone can create their own project for their own work - click Projects, then the new project button, and choose private (just you) or shared with the team. A project loaded with your past course content, for instance, becomes a head start every time you build something new.
For using the voice skills, or turning one of your standard processes into a skill of its own.
What a skill is
A skill is a living SOP that Claude follows. Where a Google Doc SOP sits in a folder waiting to be read, a skill does the work with you: Claude follows the steps, pauses at the points where a human needs to check or approve, and carries on. Anything you do the same way every time is a candidate.
The two voice skills
You have a skill for each brand voice - natasha-bray-brand-voice and school-of-healing-mastery-voice. If you need the skill files again, they're in the voice training sets:
They carry the same voice training as the projects, which means Natasha's voice can travel outside the projects: in any chat, mention the brand and ask Claude to use the skill, and your drafts will sound like her. For everyday content work, the projects are still the easiest home.
See your skills
Open Claude in the team workspace.
Click Customise in the left-hand menu.
Click Skills.
You'll see your own skills and ones shared with the team.
Turn an SOP into a skill
The easy way is to let Claude do the converting:
Start a new chat.
Attach your SOP document, or tell Claude where it lives in your Drive.
Give it the prompt below.
Review what Claude produces - make sure the steps match how you actually do the job.
Ask Claude to save it as a skill, then check it appears under Customise, then Skills.
Turn this SOP into a Claude skill. Keep every step, and add a check-with-me point anywhere a human should approve before continuing.
Start with one process you do weekly, get it working well, then do the next. One good skill beats five half-finished ones.
Browse ready-made ones
Next to Skills you'll find Plugins - bundles of skills other people have built, across dozens of categories (marketing, finance, assistants and more). Before building something from scratch, have a look - you can often take one that exists and customise it to how you work.
Turn a successful chat into a skill
If you've had a chat where you achieved an outcome you want to make repeatable, just say so and Claude will do it for you.
Turn this into a skill.
A scheduled task is a job Claude runs on a timer - daily, weekly, whenever you choose - without anyone pressing a button.
What you have running
Daily inbox triage - Claude reads what's come into the connected inbox, summarises what needs a human, and drafts replies for approval. Nothing sends itself: you stay the final check while the voice beds in.
Failed payment check - Claude checks Stripe for failed payments and prepares the standard follow-up, ready for review. A job that took half an hour or more on a busy day now takes the time it takes to read the result.
Each task runs under the account of the person who created it, using their connectors. That's why the inbox tasks live on the support and School of Healing Mastery logins.
Check or change a task
Open Claude on the account the task belongs to.
Find your tasks in the left-hand menu (they sit alongside your chats and projects).
Click the task to see its recent runs and results.
To change what it does or when it runs, open its settings from the same place - or simply tell Claude in the task's chat what you want changed.
Create a new one
Start a new chat on the account that has the right connectors.
Describe the job and the schedule in plain English (example below).
Claude will set it up as a scheduled task and confirm the schedule.
Check the first run's result and refine from there - "shorter", "add PayPal", "flag anything over £500".
Every Friday at 4pm, pull this week's sales from Stripe and Kajabi and give me a summary with anything unusual flagged.
Two tips
Write the task description as if briefing a new team member on their first day: name the tools, the steps and what "done" looks like.
Keep a human approval step on anything that sends, posts or changes things. Reading and reporting can run freely; actions should wait for a yes.
For using the finance dashboard or the lead tracker, updating one, or logging a follow-up on a lead.
How dashboards work
A dashboard is a shared link. The person who built it needs the connectors behind it; everyone else just opens the link and reads. So "can I see the numbers?" never means "do I need to connect Stripe?" - you only need connectors if you're the one building or updating.
The finance dashboard - Cam
Shows revenue across both businesses - the Stripe accounts and Kajabi together, split by business and combined. Open it from the shared link. To change what it shows, ask the person who built it, or ask Claude in the chat where it was built: "add PayPal", "show this quarter by month".
Cam - if you have any questions about customising this, Talia or Chantelle can support.
The lead tracker - Talia
Built from your Dream 1000 sheet. It shows every lead across both brands in follow-up priority order, so anyone can open it and know who to contact at a glance.
Talia took the lead on the build for this one based on Natasha's specs, so it's in her hands - any questions, just ask Chantelle.
Building future dashboards
Building new interactive dashboards is fairly easy, and the output should be even better now you have your brand kits set up, as they'll look on-brand. The key is getting as specific and clear as possible about what you want them to do.
A good little hack from Chantelle's husband: describe what you want to achieve, then ask Claude this.
If you were to give yourself the mother of all prompts to achieve the above with most efficiency and best chance of success and the least revisions, what would it be?
Zapier is the bridge to tools with no connector of their own. You connect the tool to Zapier once, and Claude reaches it through the Zapier connector you all added on Day 1.
The one process (repeat it for each tool)
Open Claude in the team workspace, on the account that should have access.
Click Customise, then Connectors.
Find Zapier and click Configure - this opens Zapier's actions page.
Click to add an action, and search for the tool (for example, Keap).
Connect the tool's account when Zapier asks - sign in once, and it stays connected.
Tick the actions you want Claude to be able to use.
Back in Claude, start a new chat and test it with the prompt below.
Using Zapier, find the Keap contact record for [a client you know].
One person sets each tool up once on their account; after that, those actions are available whenever that person (or that login) asks Claude.
What each tool gives you
Dubsado - triggers when a form is completed, an invoice is paid, or a project status changes. Dubsado's own internal automations carry on exactly as they are; this sits on top so those events can reach the rest of your tools.
Keap - the full works: find, create and tag contacts, look up purchase history, work with campaigns. This is also what powers the offer-link click tags feeding the lead tracker.
ThriveCart - reading sales, products and customer data, which is exactly what reporting needs.
AddEvent - creating events, adding attendees and pulling RSVP lists.
Extra inboxes
Claude's own Gmail connector links one inbox per Claude account. For a second or third inbox:
Follow the same process above, choosing Gmail as the tool in Zapier.
Sign in with the extra inbox's address when Zapier asks.
Tick the actions you need - search emails, read email, create draft.
Name the connection after the inbox (for example "SHM inbox") so Claude knows which is which.
Once that's done, one person's daily triage can sweep every inbox they've connected and deliver a single summary.
If it sticks
Zapier setup is the fiddliest thing in this pack, and it's a one-off. If you hit a wall, email Chantelle and you'll jump on a Zoom and sort it together.
For on-brand slides, carousels, graphics, sales pages or social content - or when you're ready to build the School of Healing Mastery design system.
What a design system is
A design system is your brand loaded into Claude: fonts, colours, logos, banners, photos and - because we added them - Natasha's voice documents. Once it exists, anything you design comes out on-brand and in her voice as a first draft, usually in minutes.
Create something with the Natasha Bray design system
Open Claude in the team workspace.
Click Artifacts in the left-hand menu, then Design.
Select the Natasha Bray design system from the design system picker.
Describe what you want (example below).
Wait while it builds - a design usually takes under five minutes; bigger pieces take longer.
Review it and ask for changes.
Create a first draft slide deck for a 60-minute masterclass on [topic], pulling relevant content from my Google Drive.
Edit what it makes
Two ways, both easy:
Tell it in the chat: "Slide 4 is too busy - cut it right back", "make the headline bigger", "swap that photo".
Click directly on the part you want changed and comment on it.
It understands loose instructions ("something about this isn't quite right", "make it more editorial") as well as precise ones.
Export and share
With the design open, go to export.
Choose your format: Canva, PowerPoint, PDF or images.
Or share the design itself with the team the same way you share anything in Claude, and present slides directly from Claude if you want to.
A design you love can be duplicated and used as a template: duplicate it, then say "keep this layout, change the text to..." - your own template library, inside your brand.
Build the School of Healing Mastery design system (after the rebrand)
You both know how to do this - here's the reminder:
Gather the SHM brand files into one folder on your computer or Drive: fonts, hex codes, logos, banners, brand photos, brand guidelines.
In Claude, go to Artifacts, then Design, then manage design systems.
Create a new design system and upload the brand folder.
Let it build - it takes a while with a lot of files, and that's normal. It will tell you what it found and ask about anything missing.
Test it: "Create me an Instagram graphic announcing [something]" and judge the result against the brand.
Give it feedback in the same chat until it's right, then Natasha can set it for the team.
The other route: duplicate the Natasha Bray system and tell it what to change for the school. Either works - a fresh build suits a full rebrand better.
One note on the brand files
The Natasha Bray system is built on the brand files we could gather on the day. It works now, and it gets sharper the moment the full brand kit (complete hex codes, confirmed fonts, brand photos) is added - just upload the new files to the design system when they arrive.
For when you want Claude to look at live websites for you, or you're wondering which model to pick for a job.
The in-app browser
Claude has a built-in browser, which means it can go and look at real web pages - including ones behind a login, because you're signed in. Good uses:
Research - "Go through [a Facebook group] and summarise what people are asking about [topic]."
Competitor research - "Look at [competitor]'s current offer page and summarise their positioning and pricing."
Engagement audits - "Go through my last 20 Instagram posts and build me a table of likes, comments and shares."
How to use it
Start a new chat.
Ask for what you want and name the site - Claude will open the browser itself.
The first time on a site, approve the access when it asks.
Let it work - you can watch it browse.
Use it for reading and research. Posting to social media stays a human job - and the voice projects make the writing part fast.
Models
Claude offers more than one model - think of them as different gears.
The default model is right for almost everything you do day to day: content, inbox work, dashboards, design.
The most powerful model is worth switching to for big, complex jobs - long strategy documents, heavy analysis, anything where you'd say "take your time and think hard".
The model picker is in the chat box. If you never touch it, the default serves you well.
The practical ruleStart with the default, and if a result feels shallow on a big job, switch up a gear and run it again.
For when anyone - a team member, a client, your accountant - asks where your data goes. This is the written version of what we covered on Day 2.
The short answer
Claude Team holds the same tier of security certifications as Google and Slack. Your data is protected to the same standard as the tools you already trust with the business.
The detail
Certifications: SOC 2 (Type I and Type II) and ISO 27001 - the same audit standards Google Workspace and Slack are certified against - plus ISO 42001, a dedicated AI governance standard.
Your team's data is never used to train Anthropic's models.
A GDPR Data Processing Agreement is built into the Claude Team commercial terms - it applies automatically, with no separate signature needed.
Compliance documentation lives on Anthropic's Trust Centre at trust.anthropic.com, with the certifications listed at support.claude.com (search "certifications") - that's where to point anyone who asks for paperwork.
The house rules we agreed
Deep therapeutic client records stay out of Claude. The risk is low, and you are protected, but special-category data deserves extra caution under GDPR wherever it goes - so the rule is simple: it doesn't go in.
If part of a document is useful and part is sensitive, redact: delete the sensitive section and share the rest with Claude.
Financial connectors stay read-only (that's how Stripe is set) unless you deliberately decide otherwise.
Nobody can see anyone else's connected accounts. The only way anyone could reach your inbox through Claude is with your Claude login and password - so treat those like any other password.
For when you're stuck, when something misbehaves, or when a draft sounds too much like AI.
Prompts worth keeping
The step-at-a-time prompt - for anything fiddly or overwhelming
I have ADHD. Please take me through this one step at a time, and ask me to confirm when I've done each step before giving me the next one.
You don't need ADHD for it to work - it turns any techy job into a guided walk-through, and Claude waits for you at every step.
The explain-it-simply prompt - when you don't know how to do something in Claude
Can you explain how to do this using Claude, as simply as possible?
Claude knows how it works. Ask it before you ask anyone else - it will usually walk you straight through.
The de-AI prompt - when a draft sounds like a robot wrote it
Be less wanky.
Chantelle's favourite prompt of all time, and it works remarkably well. Follow it with specifics if needed: "cut the clichés, shorter sentences, say it like a human."
The check-first habit - for anything that matters
Before you do this, tell me your plan and wait for my go-ahead.
One cautionAI is the ultimate people pleaser. It would rather try something than say "I can't do that", which means it can overreach. If a result seems off, say "that's wrong - stop and tell me what you actually did", and it will come clean.
Quick fixes
Something's not responding or looks odd
Log out of Claude.
Log back in.
Try again. The age-old fix - it sorted several things on our two days too.
A connector has dropped off
Go to Customise, then Connectors.
Click Connect on the dropped tool and sign in again. Guide 02 has the full steps.
You can't see the team projects or connectors
Check the workspace switcher in the bottom left.
Switch to the team workspace. Personal and team are separate - this catches everyone at least once.
A scheduled task didn't run or gave a strange result
Open the task and read its last run.
Tell Claude in that task's chat what was wrong - it can usually fix its own instructions.
Content doesn't sound like Natasha
Check you're chatting inside the brand project (guide 03).
If you are, tell it what's off and add the correction to the project instructions so it sticks.