Command note: a build is not finished when the builder reports success. It is finished when the account says the same thing. Shipped today: Verify stopped trusting the build's own report and now reads the sub-account back. Every object the plan asked for — pipelines, stages, custom fields, tags, calendars, forms, workflows, templates — gets looked up in the account and reported found or missing, one line each. What changed under that: • "Not checked" now counts as a defect, not a pass • A read that fails is reported as unreadable, never as fine • One marked test lead goes through the real form, gets watched in, and the test contact is deleted — and it tells you before it does that • Workflows arrive as drafts, so nothing fires at a client before a person has read it The report also went from 46 printed pages to 8. A verification nobody reads is not a verification. Steal the method even if you never touch our tool: 1) Write down what you said you would build, by name, before you build it. 2) After the build, open the account and find each item yourself. 3) Anything you could not check is unknown — never mark it done. 4) Push one test record through the real entry point, then delete it. 5) Sign off only on what you actually saw in the account. Every builder reports success. Only the account can confirm it.

Morning, everyone. I spent most of last week putting real screenshots into a member area I'm building. The thing that took longest wasn't the screenshots. It was a video player sitting on 64 pages with nothing behind it. Looked finished. Click it and nothing happened. I replaced all 64 with one sentence: "Video coming for this lesson." Felt like a downgrade for about ten minutes. It wasn't. A player that doesn't play tells someone the thing is broken. A line that says it's coming tells them it's on the way. Same amount of actual content, completely different read. Every client account I've built has a version of this. The portal tab with nothing in it. The resources link that 404s. The pipeline stage nobody has ever moved a card into. None of it is broken enough to get reported; it just quietly makes the whole build feel unfinished. So here's my focus this week: - Walk one account the way a client would, not the way I built it - Every dead end gets fixed, removed, or labeled honestly - Nothing that looks clickable stays unclickable What are you building or cleaning up this week? Drop it below 👇 I want to see what the room's working on.

Command note: every account you inherit has more people in it than the client remembers. Access is the one audit nobody schedules. Old staff, a former agency, a contractor from a project that ended two years ago — they keep working logins until somebody looks. The command I run on every sub-account: "List every user on this sub-account with their role and permissions. Then show me which of them are assigned to contacts, opportunities or calendars, and which appear in any workflow's internal notification step." What usually comes back: • Users nobody has thought about in a year • Admins who only ever needed read access • Notifications routed to someone who left • A calendar owned by a person who no longer takes calls Do it now: 1) Pull the user list and read it with the client, name by name 2) Ask one question per person: does this person still need to be in here today? 3) Reassign before you remove — contacts, opportunities and calendars follow the user 4) Fix every workflow notification pointing at anyone who is leaving 5) Note the date in the account and repeat it quarterly Removing a user takes five minutes. Explaining to a client why a stranger still had admin on their CRM is a very different conversation. An account is only as private as its longest-forgotten login.

Command note: every account needs a short list of moments that stay human. Automation usually gets built by asking what we can automate. The more useful question is what we won't — and writing that down before someone is tempted at 9pm on a deadline. Moments that usually stay human: • A refund, a discount, or any pricing exception • A complaint, or a reply to a bad review • A cancellation, or a save attempt on a leaving client • Anything involving illness, loss, or bad news • The first message after a deal is signed The list is short. It is also the part of the account clients remember. Do this today, on one account: 1) List every outbound moment — messages, notifications, status changes. 2) Mark each one automated, drafted-then-approved, or human-only. 3) Write the human-only list where the team reads it, not in your head. 4) For each human-only item, name who handles it and how fast. 5) Check that no published workflow currently sends one of them. This is not a limit on automation. It is what makes the rest of it safe to run at volume — you stop auditing everything because you already know which moments were never in scope. An automation that handles a complaint on your behalf is not saving time. It is spending trust you did not budget. Decide what stays human while it is still cheap to decide.

I noticed that you are using examples of clinics. Is your system HIPAA compliant? I have not done anything with any client with patients involved because I am not sure about this. My understanding is that even collecting information from patient leads could be affected by HIPAA compliance. I know it is possible. I just don't know how to do it, so I thought I'd ask you how you were ensuring compliance.