Pinned
Nov '25 •
Community Code of Integrity
What it means to be in the circle at The Quiet Upgrade Being here means we’re part of something intentional. We grow, learn, and build in community—not just side-by-side, but together. That requires safety, respect, and shared responsibility. Here’s what that looks like in practice: 1. Respect Each Other’s Privacy - No screenshots of posts, comments, or DMs without clear consent. - Don’t quote or share anyone’s words outside the circle, even anonymously, unless they’ve said it's okay. - We protect vulnerability, not amplify it for content. 2. Originality Matters - Don’t copy and paste member content, prompts, or teaching into outside platforms (even with “credit”) without permission. - Get inspired, but make it yours. 3. No Uninvited Sales or Outreach - Don’t DM members with offers, promotions, or asks unless explicitly invited. - Our DMs are for connection, not cold pitches. 4. Community Info Is Not for External Use - All names, questions, comments, and shared experiences stay in this community. - Do not use, quote, reference, or share any part of a member’s contribution—whether verbal, written, or visual—for personal projects, content, research, marketing, or training without explicit, written permission. - This includes screenshots, anonymized summaries, and even casual references. When in doubt, ask first. - If you’re a moderator, team member, or guest contributor, this is non-negotiable. You agree not to extract, export, or reuse any community content, member identity, or insight for outside use. - We take this seriously. Breaching this principle may result in immediate removal from the community and, if necessary, legal follow-up. 5. Moderation with Care - Moderators model the tone and culture of the space. - If boundaries are crossed, we respond with clarity, not shame. Liability & Responsibility By participating in this community, you agree to uphold the integrity of the space. If you violate any of these agreements—intentionally or unintentionally—you are solely responsible for the consequences. The community hosts and business owners are not liable for any outcomes or damages that result from another member’s behavior, misuse of information, or breach of conduct.
0
0
6d •
Mind the Line: a quick update
Something I've been thinking about for a while finally exists, and I want to share it here because it feels relevant to what we're all doing in this group. Coaches are getting sued, fined, and sometimes losing their licenses, because of language in their content. They used phrasing that reads as therapy under ICF guidelines, and nobody caught it before it went out. "You're not broken" in the wrong context. "Let's heal this together." Small word choices that can carry real professional risk. I kept waiting for a tool that would check for this. There wasn't one. So I built it. Mind the Line is an app that scans coaching content and flags anything that crosses into therapy territory before you publish it. You paste your post, your caption, your email, whatever. It tells you where the line is and what to change. I built it using Lovable, which is an AI app builder I've been working with. I'm not going to pretend I wrote code from scratch. I didn't, Lovable did that. But I had a clear problem, I knew what the tool needed to do, and I built the thing. Start to finish. Just by describing what I wanted it to do. I submitted it to the Women Build AI Build-A-Thon on April 30. There were 181 submissions. Mind the Line didn't place in the top 15, and I'm genuinely okay with that. I built a real thing, I put it in front of real judges, and Dr. Claire, one of my clients who is a coach, tried it and said it was exactly what she'd been looking for. That's not nothing. It's not available to the public yet. I'm still working through a couple of updates. But I wanted to share it here because I don't want people to assume software is someone else's job. It used to be, but now it's not. If you have a problem that a tool should solve, you might be closer to building that tool than you think. Here's my Build-a-Thon submission video. Happy to answer any questions if you're curious about the process. https://canva.link/8bxfh9opunr29yw
0
0
19d •
Website
When I was a practicing artist, I had a website so curators or any interested people could see what I had done. When I stopped doing art, I let my website die. Now that I want to do art again, I will again need a website to get exhibitions, residencies, etc. I don't know anything about mobile-first websites, so it makes sense to use AI to help me create a new web presence. I will begin doing that, and sharing it in the Classroom under the course "Build Your Website from Scratch". Hope it is helpful to anyone who wants to start building their own websites! I may begin to build websites for individual projects. Here's an old one from back in the day: https://martiantea.com/ Enjoy!
Apr 7 •
When your "quick cleanup" takes down your whole workspace
Saturday morning. Coffee. Notion open. I was tidying up old TikTok scripts in a Kanban board. I was powering through work and felt really productive. Except I didn't delete the scripts. I bulk-deleted tasks across my entire workspace. Every active task. Every client project. Gone. And yes, I panicked. I'm not going to pretend I was cool about it. I sat there staring at an empty workspace with a full client load and no idea how bad the damage was or how I was going to recover. So I did the one thing I've been training myself to do when something breaks: I opened Claude and started talking it through. (I call him Fred. Long story.) Fred calmed me down first, which honestly was the thing I needed most. Then we got to work. In about 15 minutes we had: - A clean backup of the 55 tasks that were still visible, exported to a markdown file I could actually work from while Notion was down - A support ticket filed with Notion with the exact restore point I needed (before noon CT Saturday) - A rule for myself: don't touch Notion again until the restore is confirmed, because any new edits would get overwritten Notion finally got back to me this morning (two days later). The restore is in progress. It's taken a lot longer than I expected, and it's cost me real work hours, but it's happening. And in the meantime, the markdown backup has been doing the job. I've been moving work forward without my "main system" even being available. I very quickly learned: Your system is only as good as your recovery plan. I had no backup routine for Notion. None. Didn't ever think I needed one! That's on me, and it's changing this week. Go AI first. It just saves time. I am actively learning to move out of my first instinct, panic and click, and into "open Claude and describe what just happened." Most of the problems you're used to just dealing with as they come up? AI can solve them, or at least get you unstuck in a fraction of the time. Lost files, broken spreadsheets, an email you don't know how to write, a process that keeps falling apart; stop white-knuckling it. Go AI first.
1
0
1-11 of 11
powered by
skool.com/the-quiet-upgrade-5680
For business owners who want to save time & boost profits. A community with simple systems & smart tools. Join The Quiet Upgrade.
Suggested communities
Powered by