AI is the new operating system for work and business. As a member of Business Systems & AI skool, you’re not just trying to be “informed” - you’re moving with conviction and becoming dangerous with your next steps. Most people are starting to “learn AI”… but without a plan or practical application they consume content, test tools, and save prompts that never turn into systems they can actually use. This targeted private session covers: ✅ your direction and goals for 2026 ✅ tools + workflows that fit your world ✅ 30 Day Custom Roadmap Next Step: Schedule your Systems & AI Roadmap Session Book Here: https://calendly.com/freestyle-consulting/bsa-skool-roadmap-session Make your next moves with intention.

Came across Jensen Huang’s “5-layer cake” framework for AI, and found it to be a clean way to see what’s actually required to build and deploy AI in the real world. So I made a simple visual to help it click faster (dropping it below). The idea is basically: AI isn’t one product or one model, but rather it’s a full stack. You’ve got foundational layers (compute/infrastructure + the software tooling), then the “middle” layers where models get trained and tuned, and then the top layers where it turns into real applications and business outcomes. If the lower layers are weak or too expensive, everything above it gets fragile. If the upper layers are unclear, you end up with powerful tech that doesn’t translate into value. Curious what you think: over the next 12–24 months, which layer(s) do you expect to cause the biggest hiccups/bottlenecks (cost, reliability, regulation, data, talent, etc.)… and which layer(s) do you think are about to take off the fastest? 👇

We recently worked with a company doing over $20M a year. From the outside, they looked like a large, established operation. But once we stepped inside, it became clear they were still running the business the same way they did in the early days — through back of napkin systems, scattered notes, memory, long lost threads, and whatever someone happened to remember that day. As we analyzed how work actually flowed, the pattern was obvious: revenue had scaled, but their internal systems hadn’t. Nothing was consistent, repeatable, or easy for the team to follow. The business looked strong, but it functioned like a small shop that had never updated how it operated. The biggest takeaway was simple: growth will expose whatever systems you didn’t build. And if everything still relies on people remembering things, the business ends up operating with stress, confusion, and unnecessary inefficiency. Case Study Question: When transforming back-of-napkin style businesses, what are the main systems you think every business should have in place before scaling? Extra questions: Have you seen this before? Maybe in your own company or someone you know?How often do you think big businesses are still running on small-business systems behind the scenes?

Hey all, Happy Monday - lets post some wins either from today, this past week, or what you hope to win this week! What's something, big or small, that you got the win on - could be as simple as you made an outreach attempt to a new prospect, or as big as you put together your landing pages for your new marketing campaign. This is a perfect thread to get some support and build your momentum! Let’s go 👊

When you think about it — every system that's been engineered, no matter how well-designed, still depends on coordination, accountability, and sequencing to actually work. That’s project management. So is PM just a support function that organizes the work… or is it actually part of the system itself — the mechanism that turns design into operational flow? Curious how others see it: where does system design end and project management begin?