FAQs
Questions that come up in the room. Short answers. If a product screen has moved, believe the screen.
We focus on Claude. This hub doesn't teach other assistants.
Chat, Cowork, and the folder
What's the difference between Chat and Cowork?
They're one experience. No folder selected, and it's plain chat. A folder selected, and it's Cowork. You don't pick a different product.
Under the chat box, the control is Project or folder. Select yours and set it as the default. The example is 00-Ollie's-Claude. Leave it on for most things, even a basic question. Claude then knows why you're asking.
If a draft ignored your tone, no folder was selected, or the wrong one was. about-me.md lives in your personal folder.
If your app still has Chat and Cowork as two tabs, you haven't updated. Use the Cowork tab, select the folder, and leave it selected. What is Cowork?.
Does it replace my existing tools?
No. It works inside them. You still use Excel, PowerPoint, and the rest. Claude works within those files, instead of in a separate paste box.
What if it makes a mistake?
You stay in control. It checks in. You review before anything goes out. Read the email, the number, and the slide before they leave the building.
How much setup is enough? Where should the folder live?
Enough to do real work: about-me.md, about-business.md, a few lines in claude.md, and the folder selected as the default. Tone of voice is the next pass, on Opus, when you have an hour. Budget 45 to 90 minutes, not 20.
Keep the personal folder in your own OneDrive or Google Drive, so it backs up. Put shared company files in a separate folder, with one owner for About Company. SharePoint often syncs badly. If it fights you, work in OneDrive and copy finished files across. Your folder and context files.
Which tool should I start with?
Claude, then Granola, then Wispr Flow. Those three cover the session. The three tools.
Plans, models, and limits
Which plan do we need?
Pro for one person. Team for a company (from 2 seats, up to 150). Enterprise if you need the admin controls that come with it. Working in a folder is on those paid plans. It isn't a separate product from chat. You do not need Max. Max is more usage.
Free will not get you through the work. Check the current price at claude.com/pricing. The public page we checked was in dollars, with no pound figure.
Which model, and why am I hitting limits?
Sonnet for everyday work. Opus for a one-off high-value job. Fable only when it's critical, because it uses your limit fast. Leave effort on Medium. Use High for that one-off. Ignore Max.
You hit limits because each message re-reads the whole chat. Don't switch model mid-chat. Start a fresh chat from a 10-line summary. Models, effort and limits.
How long until this is useful?
You'll save time on the first day if the task is real. It feels reliable after a few weeks of using the folder, not after a bigger stack of tools. Use email and calendar for four to six weeks before you build a library of skills.
Connectors and safety
Which connectors, and who approves them?
Start with three: email, calendar, and Slack or Teams. On Team, an admin adds the connector, then you connect your own login. If it isn't in the list, it hasn't been approved, you're on the wrong account, or Microsoft's admin (Azure, groups) is blocking it. Sign-in also expires. Connectors and permissions.
Is it safe? Does it train on my data?
On Free, Pro, and Max, training is on until you turn it off. On Team and Enterprise, it's off by default. Confirm that in your admin settings.
Don't use thumbs up or thumbs down. Rating a chat can send it for review. Never put passwords, bank details, or government contract material in. Security, privacy and compliance.
Can it delete things?
Not if you set delete to never, and you don't choose Always allow. Read can be allow. Anything that sends or edits should ask. You still read the result before it goes to a client.
Can my company see what I'm doing?
On a personal account, not unless you share it. On a Team account, assume an owner can see chats. Don't use a personal login for company files to hide them. That's the worse option.
Skills, tasks, and projects
Skill, scheduled task, or project?
A skill is a method. You ask in plain English, and Claude uses it when the request matches the skill's description. /name forces one if you need to. A scheduled task is a skill or a prompt on a timer. A project is a workstream with its own files. Most people need a skill first. They need a task when they're tired of remembering to run it. They need a project when one area of work has its own pile of context. Skills.
Why hasn't my scheduled task run? Where do I see it?
Open the Scheduled section and run it once by hand so you know where the result appears. If it was set to this computer, the laptop has to be on. Some tasks can run in the cloud. Check which one you chose. Then check the connector is still signed in, and that you didn't hit a limit. Tasks don't appear on someone else's computer. Scheduled tasks.
Can we share skills? Can I take my setup with me?
Skills can be published on Team and Enterprise, or sent as a file. Read a skill before you install it. Tasks don't share across machines.
If you leave the job, your personal folder is the setup, if it lives in your own Drive. Copy it. A company Team account is the company's. Export may be admin-only. Don't rely on walking out with the org library. The context files you wrote are the part worth keeping.
Meetings and voice
Can we record meetings?
Only if policy allows, and you've told people. A transcript can be personal data. Someone can ask for a copy. If they say no, don't record. Check how long your Granola or Wispr Flow plan keeps history before you promise a year of search. Granola.
Is Wispr Flow worth it, and how do I make it spell our names?
Yes. The reason is the prompt, not the email. Speaking lets you put far more detail in, and the output is better. Ollie mostly uses it in Claude. It can take meeting transcripts if you only want one subscription, but Granola's app is a lot better for meetings. Add company names and people's names to the dictionary the first time it gets one wrong. Wispr Flow.
Results
Why isn't the output any good?
The prompt was vague, you accepted the first draft, or the folder wasn't selected. Add specifics. Ask it to plan before it edits. Then fix the file it got wrong, not just the one email. Prompting.
Should I be uneasy about using it for writing?
Use it for the first draft. You do the last pass. With a tone file and a read-through, it's a normal editorial process. Without those, people can tell, because the specifics only you know aren't there.
Anything public, with your name on it, deserves more of you than a private email does. Don't outsource the voice you want to be known for.
Is it accurate?
It's useful for structure, drafts, and pulling a transcript into shape. It is not a source of facts. Check figures, dates, and citations. Open the link. Treat it like a sharp intern who needs a manager.
The team
How do I get my team using it?
Don't mandate a pile of tools. Team plan, one owner for About Company, four to six weeks on email and calendar, a show-and-tell every fortnight. Rolling it out to your team.
Where do I go after the session?
- Finish the folder. 45 to 90 minutes, not the same evening as a dinner.
- Use it on real email and calendar this week.
- Come back to Keep going when you want a prompt for your role.
Questions: ollie@aytonlabs.io