Testimonial - Collect and embed testimonials in minutes

Mike Signorini

I had not used Claude or Cowork, but after moving to Google Workspace in APril, did that Academy and it was EXACTLY what I needed to set up. I was frustrated with continually repeating prompts to Gemini and not impressed with ability to positively influence my work flow. I needed help. I bought the full Academy and for the first 7 modules thought I had made a mistake. Then I got started. I am four days in and making insane progress. I am learning from explaining my context, but this system is learning with me and teaching me. I have built skills, workstations, projects, scheduled tasks. I understand what it all means from the Academy, but I feel more like I am onboarding a new team member: and they get it!! I am impressed. I still have many things to figure out, but I am less concerned now than I was 5 days ago, as I feel like I am engaged in way that is healthy to my workflow, my professional life and my larger team. Thank you Jeff! I am a frugal man, and this is worth every penny.

Aug 25, 2026

Greg

The biggest impact was the setup of the system itself: CLAUDE.md, MEMORY.md, ARCHIVE.md, and so on. Sample prompts definitely helped provide the right instructions to get started. As you expected, I quickly began to build on the foundation you provided. However, for some reason, Codex was better at understanding what I needed, while Cowork required precise guidance to the point where its "intelligence" – artificial, but still intelligence, right? – started to diminish for me. At some point, the progressive reading of CLAUDE.md (root → Workspace) stopped working. That's on Anthropic. But if someone will watch your video where you describe the setup, they will likely be frustrated when they will try to setup it themselves. Ultimately, you provided what I couldn't find from other sources: simplicity and clarity. There are too many sources and too many systems – every author uses their own, sometimes needlessly sophisticated systems. To those who just starting with your setup process I would say to start slowly, adapt details to your own needs and style of working, but lean to Jeff's simple structure, always keep it in mind. If you ever feel system becomes complex – step back, return to Jeff's basics and reduce complexity: use file pointers, progressive disclosure. AI can bloat instructions up very fast if left unchecked. But very soon you'll get to the point where you'll accelerate to the point of being unstoppable.

Jun 18, 2026

Tjark Reinecke

The biggest impact has been the inbox-to-bookkeeping pipeline. Raw scans land in one folder, get triaged once with a naming convention and status marker, then ride a single rail: tracker entry, payment-run XML per company, banking-app import, a trigger phrase flips them to paid, and the same trigger bundles them into a weekly handoff package for the bookkeeper. The same receipt stopped getting touched seven times. Day-to-day: I run weekly payment runs across eight entities by typing one phrase. Edge cases hold cleanly too — when an account needs topping up first, the XML waits, the tracker stays in "in export", and a doubled reminder (scheduled task + calendar) sits there until I act. For someone on the fence: the value isn't the folder structure, it's that short trigger phrases fan out into deterministic steps you'd otherwise do by hand. Two things make the setup worth it specifically — workflow rules live in one file and Cowork keeps every running scheduled task in sync with them, and the routing table means new files know their own home, so you stop naming folders. My recommendation: commit to the inbox + tracker loop first and ignore the rest. Once that one loop saves you an hour a week, everything else clicks into place on its own.

May 8, 2026