Claude Code in the Wild: Building Your Company OS in Notion

Guest Speaker

Meet Sofia

Ana Sofia Grass Giraldo

Product Owner, GTM Engineering & BI at Kapwork

Ana Sofia Grass Giraldo is a Systems Engineering and Data Science student at Pontificia Universidad Javeriana in Colombia, where she earned a full merit scholarship for the highest GPA in her Data Science program. She now works as Product Owner of GTM Engineering and Business Intelligence at Kapwork, where she built the company's entire GTM stack from scratch using Claude, Clay, and Notion. She also trains professionals in AI-powered GTM automation at Bootprint. Before any of this, she wrote her thesis with CERN's ATLAS experiment, building a mobile tool that registered 1,600 temperature sensors into production, a project that earned a formal letter of recognition from the ATLAS ITk coordinator. She also founded CiberAbu, a startup teaching digital literacy to senior citizens in Colombia.

Session Overview

What was covered

🧩

The Problem

Context lives inside people's heads, scattered across chats, docs, and spreadsheets. Scaling adds more people, which adds more mess.

🏗️

Three Systems in Notion

Personal command center, company operating system, and GTM engineer sandbox. All built through conversation with Claude Code.

📁

The Three-Tool Stack

Notion for shared operations, Obsidian for your personal Claude brain, GitHub for code and versioning. Each tool has a specific job.

🤖

Agents That Run Themselves

Trend spotting agents, content calendars, live CRM pipelines, and scheduled weekly reports built with Claude routines.

Live Demo

What Sofia built

Connected Claude Code to Notion via MCP

Install Claude Code, tell it to help you connect the Notion MCP, and Claude walks you through the steps. One connection gives you full access to create, edit, translate, and organize everything in your Notion workspace through conversation.

Built the Personal Command Center

A system for projects, memory, tasks, and content in one Notion space. Claude built the entire structure from a prompt, not a template.

Built the Company Operating System

An executive roadmap covering mission, vision, quarterly planning, and brand identity. A people and roles database where each person links to their tasks. An execution hub for tasks, meetings, clients, and products. A mission control dashboard where every metric calculates itself automatically.

Built the GTM Engineer Sandbox

A trend spotting agent connected via Claude routines that pulls from newsletters daily and drafts LinkedIn posts (one reached 25,000 views in four days). A content calendar with a personal brand voice baked in. A live CRM pipeline that updates from real data instead of manual entry. Scheduled weekly reports that run by themselves when Sofia is offline.

Added Obsidian as the Claude Brain Layer

Obsidian stores all of Sofia's Claude context: documents, guides, research, custom rules. Because it syncs to local files, Claude can reference it without re-reading everything fresh each session. That's what keeps token usage manageable even on a $200/month Max plan with five-plus hours of daily use.

Mental Models

How Sofia thinks about this

Notion = Ops, Obsidian = Brain, GitHub = Code

Three tools with three distinct jobs. Notion is cloud-based and shareable so the whole team can work in it. Obsidian holds your personal Claude context so you don't repeat yourself every session. GitHub handles code, versioning, and anything the engineering team needs to collaborate on.

Build the OS Before the Agents

Context first. When Claude already knows your company's mission, voice, people, and data, every prompt you write gets shorter and every output gets sharper. The OS is not setup overhead. It's the foundation that everything else runs on.

Token Economy

Every time you re-explain context from scratch, you're burning tokens and slowing yourself down. Obsidian is your persistent memory layer. Store your context once, reference it every session. On a lower plan, skills from the Claude Code skills directory can help you stretch further without re-pasting the same prompts.

Notion Wins for Teams Because It's Cloud-Based

Obsidian vaults are local. You can't connect your Obsidian vault to your boss's Obsidian vault. Notion is shareable, has relational databases, lets you build multiple views of the same data (calendar, gallery, chart), and gives the whole team live access. If more than one person needs it, Notion wins.

Example Prompts

What Sofia says to Claude

Connect Notion MCP

Help me connect Notion MCP in my computer

Build a CRM in Notion

Build me a CRM

Create a LinkedIn post from company context

Use the trend spotting, use the voice of my boss, use the information that you already have of my company, that is Capwork, and please create a post for LinkedIn so I can put it today.

Generate content from the operating system

Please use the executive roadmap, the company entity, and the voice of my boss, and create the content for him.

Build an agent connected to Notion

Create this agent for me. The information it gets, for example this weekly newsletter, should be stored in Notion.

From the Session

Questions Sofia answered

Why go through Claude instead of just using Notion AI?

Sofia has tried both. Claude Code produces better results. Notion AI works, but Claude is a stronger LLM right now. For agent creation and complex operations, she always goes with Claude Code.

Are you using Notion agents, or external agents connected through Claude Code?

External agents built with Claude Code. She tells Claude "create this agent for me and connect it with Notion" rather than using Notion's native AI. Claude is the builder. Notion is the storage layer.

Does running all this context through MCP burn through your Claude usage limits fast?

The OS approach actually saves tokens. When Claude already knows your context, you're not re-explaining it every session. Sofia is on the $200/month Max plan because she uses Claude five-plus hours every day. For anyone on a lower plan, Obsidian and Claude Code skills from the skills directory help you stretch further.

If you could only keep one integration between Claude Code and Notion, which one would you keep?

The company operating system. It creates the most compounding value. A solid OS is what lets companies scale fast. Sofia has seen it help companies go from $0 to $12 million and from $3.5 million to $30 million because it gives everyone clarity and consistency.

Why still use Obsidian if Notion already does so much?

Obsidian stores your personal Claude brain: context, guides, research, rules. It's local, which is exactly why it's not used for team ops. Notion is cloud-based, shareable, and has relational databases. Obsidian is your persistent memory store; Notion is your team's operating layer. One can't do both jobs well.

How do you avoid burning too many tokens when Claude has to dig through all that context?

Obsidian is the first tool. Store your context there and reference it so you're not re-pasting it from scratch. Also, look for skills in the Claude Code skills directory. Download a skill, paste it into Claude Code, and it handles the heavy lifting without repeating itself. That was her advice when she was on the $20/month plan.

Tools