Claude Basics Workshop with Ayub

What this workshop covers Most teams meet Claude as a chat box. They type a question, get an answer, and never touch the ninety percent of the tool that would actually change how they work. The gap between "I use Claude sometimes" and "Claude runs part of my week" is not talent or budget. It is knowing what the tool can do and having someone set it up with you, once, properly. This is a 1-hour hands-on session that takes PE and VC partners, principals, analysts, and IR teams from the basics of Claude to running real work inside it: documents, decks, connected apps, custom skills, and scheduled jobs. We start from zero and build up, so whether you have never opened Claude or already live in it, you leave using the parts that matter. We set everything up live on your own accounts, so nothing here is theoretical. Your team leaves with working setups, not notes about setups. Limited slots available. First come, first served. Section 1: Claude Basics What Claude actually is, how it differs from a search engine, and how to get answers you can trust. We cover the prompting habits that separate a vague reply from a partner-ready one: giving context, setting the format, asking for the reasoning, and pushing back when the first answer is not good enough. This is the foundation every later section builds on. Section 2: Claude AI and the Interface A working tour of Claude AI: projects to keep related work together, artifacts for documents and drafts you can edit in place, styles to match your house voice, and the settings that quietly make the tool better. You leave knowing where everything lives and how to organize your own workspace so it stays useful past week one. Section 3: Claude Cowork Cowork is where Claude stops answering and starts doing: reading files, running multi-step tasks, and producing finished deliverables end to end. We set it up from scratch and run a real task through it live, so you see the difference between asking Claude a question and handing Claude a job. Section 4: Root Files (the moat) The standing documents every session reads first: your thesis written as explicit rules, your house formats, your revealed preferences. Collection and code are commodities; this context is what makes your Claude yours. We show you how to build and maintain these so every output already knows your standards before you ask. Section 5: Claude for PPT and Documents Turning raw material into finished deliverables: IC memos and reports as Word documents, and pitch-ready decks in PowerPoint, built to your template and your voice. We do this live on your own content, so you see a real deck come together rather than a demo one. Section 6: Connectors and Plug-ins Wiring Claude into the tools you already use, Gmail, Google Drive, Calendar, Slack, and more, so it works from your live data instead of copy-paste. We cover what each connector unlocks, how to add them safely, and where the human stays in the loop for anything that sends or changes something. Section 7: Claude Skills How to turn a workflow you repeat into a permanent Skill your whole team invokes the same way, every time. Instead of pasting the same prompt each week, you build a capability once and everyone runs it to the identical standard. We build one live so you leave with a working example, not just the concept. Section 8: Scheduling How to put work on autopilot inside Claude, scheduling jobs to fire on their own cadence, so finished output is waiting for you each morning without anyone pressing a button. What you leave with A Claude setup you actually understand end to end: your workspace organized, connectors wired to your live tools, your root files in place, at least one working Skill, a scheduled job running, and the habits to get partner-ready output every time. All ready to use tomorrow on your own work. 30-minute Q&A with Ayub. Who this is for PE and VC partners, principals, analysts, and investor relations teams at funds managing $50M to $5B+ who want to move past treating Claude as a chat box and turn it into a working part of their team, set up correctly, once, so it earns its place in the daily workflow.