Activity
Mon
Wed
Fri
Sun
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
What is this?
Less
More

Owned by Piotr

How to start, grow and maintain family business without ruining your personal life. Strategies and tactics for small businesses and families.

Memberships

Agentic Foundations

8.1k members • Free

AI Video Creators Community

5k members • $9/month

AI Automation Society Plus

3.6k members • $99/month

AI Automation Society

355.5k members • Free

Max Business School™

264.9k members • Free

Skoolers

191.5k members • Free

2 contributions to AI Automation Society
I scaled multiple businesses to 8 figures!! now I'm rebuilding everything in Claude. Help me not screw it up.
EYYYYY I'm an entrepreneur based in Miami. Over the years I've scaled multiple projects to 8 figures and built communities with several million followers combined. I mention this only to give context about the scale I'm operating at day-to-day. Right now I'm migrating my ENTIRE operation to Claude. Not just isolated tasks — I'm designing a global architecture from scratch that includes: - A "mother project" that orchestrates my whole life and businesses - Subprojects for each company/client I collaborate with - A daily personal assistant that reviews my goals, routines, and decisions - Reusable global skills (proposals, meeting notes, content, etc.) - Local skills only when the project context justifies it - Automated workflows for the tasks I do repeatedly The philosophy I'm building on: a minimal root CLAUDE.md (more of a "map" than a container), dense context at lower levels, skills with lazy loading so I'm not burning tokens unnecessarily, and a clear separation between tools (scripts), workflows (procedures), and skills (packaged expertise). My question for the community: What architectural decisions did you make that you later wished you'd done differently? I'm especially interested in hearing from those of you who have already been running Claude Code at real scale for months — not the YouTube tutorials, but the painful lessons that only come from daily use. A few things I'm specifically debating: 1. Global skills by default and local by exception, or the other way around? 2. How do you balance automating everything vs keeping manual control on critical decisions? 3. Which daily workflows gave you the biggest ROI from day one? 4. Any expensive early mistake you can help me avoid? I'm planning to document the entire process and I'm happy to share the learnings with the community as I go. The idea is for this to also serve as a case study for other entrepreneurs who want to do the same. Thanks in advance to anyone who takes the time to reply. Comments are worth gold at this stage 🙏
1 like • 29d
Try "crawl before you walk apprach", start from non ai automations and then move to more demanding tasks. And document your business context and SOPs so that cladue code have sth to work on.
🚀New Video: Google’s New Tool Just 10x’d Claude Code
Google just released an open source CLI that lets you control your entire Google Workspace from the command line. In this video, I connect it to Claude Code and show you how it can manage your Docs, Sheets, Gmail, Calendar, and Slides without ever leaving Claude Code. If you use Claude Code, this changes everything.
2 likes • Mar 10
​Has anyone tried it with a Google Service Account credentials? The logging out @Nate Herk mentioned others experience is caused by the test mode of the PC app (seven-day expiration time). A GSA gives permanent access to many selectable resources and relies on resource sharing, but I don't have a paid GWS account to verify this. You should also add payment method to the project to avoid running out of free api calls.
1-2 of 2
Piotr Grall
1
2points to level up
@piotr-grall-9938
on a spring-break, full-time father and entrepreneur.

Active 1h ago
Joined Nov 4, 2025
ISFJ
Kębłowo
Powered by