COMMANDER — 100 FACEBOOK AD VARIANTS One-day in-person AI assistant training · Grant & Bill · Charleston coast · August 18 & 19, 2026 Generated 2026-08-03 · 100 ads across 10 angle families ⚠️ 10 ads are flagged NEEDS VERIFICATION — they reference a prior session or past attendees. Confirm with Grant & Bill before running, or drop them. ────────────────────────────────────────── C01 · Curiosity Principle: Specificity as credibility ⚠️ NEEDS VERIFICATION: Describes a specific past attendee. Only run if a prior session actually happened. PRIMARY TEXT Someone in the last room actually timed it. Forty-one minutes a morning, just sorting email before real work started. By lunch that day he had an assistant reading the inbox for him, flagging what mattered, drafting the replies he types anyway. He built it. Not us. He had never written a line of code in his life. Commander is one day, in person, on the Charleston coast. August 18 or August 19 — pick one. You walk out with a working assistant, not a folder of notes. Dates and details at the link. HEADLINE: He Timed It. 41 Minutes. DESCRIPTION: A one-day, in-person build session on the Charleston coast. August 18 or 19. Non-technical people welcome. BUTTON: Learn More WHY: The oddly precise number does credibility work a round number can't. ────────────────────────────────────────── C02 · Curiosity Principle: Confession opener ⚠️ NEEDS VERIFICATION: Describes watching a specific past attendee. Needs a real prior session. PRIMARY TEXT I ignored all of this for about two years. Assumed it was hype dressed up in a new font. What changed my mind wasn't a demo. It was watching a guy who sells insurance build something in an afternoon that reads his inbox, sorts it, and drafts the four replies he sends every single day. He isn't technical. He just had one day and someone sitting next to him. That's Commander. One day, in person, on the Charleston coast. August 18 or August 19. See what the day looks like at the link. HEADLINE: I Was Wrong About This DESCRIPTION: One day, in person, Charleston coast. August 18 or 19. Build your own working AI assistant, start to finish. BUTTON: Learn More WHY: Skeptics move for another skeptic, not for enthusiasm. ────────────────────────────────────────── C03 · Curiosity Principle: Reversal of expectation ⚠️ NEEDS VERIFICATION: Claims Grant & Bill have done this 'a few hundred times' and describes a recurring mid-morning pattern. PRIMARY TEXT The best twenty minutes of the day is the part where nothing works. Somewhere mid-morning, everybody's build breaks. Wrong instructions, wrong format, the thing answers a question nobody asked. Then it gets fixed, in the room, with two people who have done this a few hundred times looking over a shoulder. That's the part a video can't give anybody. Commander is one day, in person, on the Charleston coast. August 18 or August 19. You leave with the thing running. Full details at the link. HEADLINE: The Part Where Nothing Works DESCRIPTION: In-person build day on the Charleston coast, August 18 or 19. Run by Grant and Bill. You leave with it working. BUTTON: Learn More WHY: Praising the failure moment stops the scroll and sells the one thing a course can't. ────────────────────────────────────────── C04 · Curiosity Principle: Unanswerable question ⚠️ NEEDS VERIFICATION: 'Most report' implies past attendee data. Soften to Christa's own result if there's no history. PRIMARY TEXT Here's a question almost nobody in the room can answer on the first try: what happened to Tuesday? Not as a guilt thing. Most people genuinely can't reconstruct it. The hours go to email, follow-up, scheduling, looking things up, writing the same message for the ninth time. People who come to Commander build an assistant that takes that pile off the desk. Most report getting somewhere around two hours a day back. One day, in person, Charleston coast. August 18 or August 19. Details at the link. HEADLINE: What Happened To Tuesday? DESCRIPTION: One-day, in-person AI assistant build on the Charleston coast. August 18 or 19. BUTTON: Learn More WHY: An open question with no available answer creates a loop the reader carries into the click. ────────────────────────────────────────── C05 · Curiosity Principle: Mundane detail, bigger story ⚠️ NEEDS VERIFICATION: Describes a specific room from a past session. PRIMARY TEXT There's a folding table at the back of the room with a power strip and too many outlets on it. That's where people end up around three in the afternoon. Laptop open, testing the thing they just built against their own actual email. Not a sample inbox. Theirs. That's the whole point of the day. Nobody takes notes. Everybody builds a working assistant and takes it home. Commander. One day, in person, Charleston coast. August 18 or August 19. Take a look at the link. HEADLINE: The Table At The Back DESCRIPTION: A one-day, in-person build session on the Charleston coast. August 18 or 19. BUTTON: Learn More WHY: A boring physical object signals a real room and separates this from every webinar in the feed. ────────────────────────────────────────── C06 · Curiosity Principle: Overheard dialogue ⚠️ NEEDS VERIFICATION: 'The sentence we hear most' claims repeated past sessions. PRIMARY TEXT "Wait. It just did that?" That's the sentence we hear most, usually somewhere around eleven in the morning. It comes right after somebody's assistant reads a real email thread and drafts a reply that actually sounds like them. There's a pause. Then they run it again to be sure it wasn't luck. Commander is one day, in person, on the Charleston coast. August 18 or August 19 — two sessions, same day of content, pick whichever fits. Grant and Bill run it. A room this size fills. Seats at the link. HEADLINE: Wait. It Just Did That? DESCRIPTION: One-day, in-person AI assistant build on the Charleston coast. Two dates: August 18 and August 19. BUTTON: Sign Up WHY: Quoted speech reads as eavesdropping rather than advertising. ────────────────────────────────────────── C07 · Curiosity Principle: Zeigarnik open loop ⚠️ NEEDS VERIFICATION: Describes a repeated behavioural pattern across past sessions. PRIMARY TEXT Almost nobody builds the thing they came in wanting to build. They switch to something else by ten a.m. People arrive thinking they want help writing content. Then they watch the inbox walkthrough and quietly change their mind. Email triage first. Follow-up second. Content ends up third. We let them switch. It's their assistant, not ours. Commander is one day, in person, on the Charleston coast. August 18 or August 19. Non-technical is normal here — that's most of the room. See the agenda at the link. HEADLINE: Nobody Builds What They Planned DESCRIPTION: One day, in person, Charleston coast. August 18 or 19. Build the assistant you actually need. BUTTON: Learn More WHY: States an outcome without explaining it, forcing the read. ────────────────────────────────────────── C08 · Curiosity Principle: Unexpected concrete image ⚠️ NEEDS VERIFICATION: 'The last one' — explicitly claims a prior session with named details. PRIMARY TEXT Two people showed up to the last one with printed emails in a binder. Both left with an assistant running. Nobody laughed. Half the room is people who have run a business a long time and never had a reason to care about any of this until it started eating their mornings. One day, in person, on the Charleston coast. You build it. You take it home working. August 18 or August 19. Pick one. Details at the link. HEADLINE: They Brought A Binder DESCRIPTION: In-person, one-day AI assistant build on the Charleston coast. August 18 or 19. BUTTON: Learn More WHY: Gives permission to the least confident reader in the audience. ────────────────────────────────────────── C09 · Curiosity Principle: Counterintuitive claim ⚠️ NEEDS VERIFICATION: 'The first time' implies multiple past sessions observed. PRIMARY TEXT The people who do best in the room have never written a line of code. That surprised me the first time. The reason, I think: they don't try to make it clever. They describe their job out loud — this is what I do every Monday, here's how I answer this kind of email — and the assistant gets built out of that. Turns out knowing your own work in detail beats knowing software. Commander. One day, in person, Charleston coast. August 18 or August 19. See what a day looks like at the link. HEADLINE: No Code. Best Results. DESCRIPTION: One-day, in-person build day on the Charleston coast. August 18 or 19. BUTTON: Sign Up WHY: Flips the biggest objection into the qualifying advantage. ────────────────────────────────────────── C10 · Curiosity Principle: Withheld moment ⚠️ NEEDS VERIFICATION: Describes what 'happens to almost everyone' — needs prior sessions. PRIMARY TEXT There's a moment that lands around two in the afternoon, and it happens to almost everyone in the room. It's when the assistant stops feeling like a toy. Somebody hands it a real task — a messy inbox, a follow-up list, an afternoon of research — and it simply handles it. The room goes quiet for a second. That moment can't be scheduled. You can only be in the room for it. Commander. One day, in person, Charleston coast. August 18 or August 19. Details at the link. HEADLINE: The 2 P.M. Moment DESCRIPTION: One day, in person, on the Charleston coast. August 18 or 19. BUTTON: Book Now WHY: Naming a precise time for an unnamed event opens the tightest information gap in the set. ────────────────────────────────────────── O01 · Outcome Principle: Prospection simulation PRIMARY TEXT By 8:40 a.m. the inbox is already sorted, the three that matter are flagged, and the rest can wait until noon. That's an ordinary morning once you've built an assistant to do it. Commander is one day, in person, on the Charleston coast. You actually build it, with Grant and Bill in the room, and you leave with it running. Email triage, follow-up, scheduling, research. The small work that eats a morning. Roughly two hours a day back. August 18 or August 19. Pick the day that works. HEADLINE: Build Your AI Assistant in a Day DESCRIPTION: A one-day, in-person build session on the Charleston coast. August 18 or 19. BUTTON: Learn More WHY: Opens inside a specific future morning, so the reader lives the outcome before any feature. ────────────────────────────────────────── O02 · Outcome Principle: Concreteness effect PRIMARY TEXT The first thing most people hand off is email. Not all of it. Just the sorting, the drafting, the following up. That one change is worth about an hour a morning. Then you add scheduling. Then research. Then the content you kept meaning to write. Commander is one day, in person, on the Charleston coast. Grant and Bill walk you through building your own AI assistant. No coding, no tech background required. It's working before you leave the room. August 18 or August 19. Choose your day. HEADLINE: Hand Off Email First, Then More DESCRIPTION: One day, in person. You build the assistant yourself and take it home working. August 18 or 19. BUTTON: Sign Up WHY: Starts with one narrow believable task, which lowers the skepticism barrier. ────────────────────────────────────────── O03 · Outcome Principle: Peak-end recall PRIMARY TEXT Leaving the office while the light is still gold over the marsh — that's the part people mention first. Not the technology. The evening. Commander is a single day on the Charleston coast where you build your own AI assistant with Grant and Bill. Email triage, follow-up, scheduling, research, first drafts. The work that quietly keeps people at a desk until seven. Roughly two hours a day back. That's dinner. That's the drive home with the windows down. That's a Friday afternoon that feels like one. August 18 or August 19. HEADLINE: Roughly Two Hours a Day Back DESCRIPTION: Build your own AI assistant in one in-person day on the Charleston coast. August 18 or 19. BUTTON: Learn More WHY: The end of the day is what people remember, and this sells that moment rather than the tool. ────────────────────────────────────────── O04 · Outcome Principle: Subtractive framing PRIMARY TEXT A short list of things you stop doing: rewriting the same follow-up email for the fourth time. Digging through a thread for one detail. Copying notes into three places. Starting every draft from a blank page. Checking mail in bed because the day never officially ended. One day, in person, on the Charleston coast. You build your own AI assistant — you, not a vendor — and it goes home with you working. With Grant and Bill. August 18 or August 19. See what the day looks like. HEADLINE: The Work You Stop Doing DESCRIPTION: A one-day in-person build on the Charleston coast, August 18 or 19. BUTTON: Learn More WHY: A list of vanished chores is easier to picture than a benefit statement. ────────────────────────────────────────── O05 · Outcome Principle: Narrow before/after PRIMARY TEXT Before: forty-five minutes each morning sorting mail. After: four minutes reviewing what the assistant already sorted. That's one task. Now run the same before-and-after on follow-up, scheduling, research notes, and the content that keeps sliding to next week. That adds up to about two hours a day. Commander is one day, in person, on the Charleston coast. Non-technical by design. You build the assistant yourself, with Grant and Bill in the room, and it's running before you go home. August 18 or August 19. Pick one. HEADLINE: One Task, Before and After DESCRIPTION: See the arithmetic on a single morning task, then multiply it. Charleston coast, August 18 or 19. BUTTON: Sign Up WHY: One small provable contrast earns the bigger claim. ────────────────────────────────────────── O06 · Outcome Principle: Affective forecasting PRIMARY TEXT Sunday night is when a lot of us start working — mentally, on the couch, running Monday three days early. The reversal is simple. When the week's small work is already handled, Sunday goes back to being Sunday. Commander is a one-day, in-person build on the Charleston coast. You leave with your own AI assistant handling email triage, follow-up, scheduling, and research. About two hours a day back. Grant and Bill run it. August 18 or August 19. Learn more about the day. HEADLINE: Give Sunday Night Back to Sunday DESCRIPTION: One in-person day on the Charleston coast, August 18 or 19. BUTTON: Learn More WHY: Names a felt weekly moment in first-person plural, staying compliant while hitting the emotional low point. ────────────────────────────────────────── O07 · Outcome Principle: Delegation metaphor PRIMARY TEXT Hiring is slow. Training is slower. This is closer to building a capable new hire in one day — and you do the building. Commander is a single day, in person, on the Charleston coast. By evening you have an AI assistant that knows how you work: what to answer, what to flag, how you follow up, what your notes should look like. No coding. Grant and Bill teach it for people who don't think of themselves as tech people. August 18 or August 19. Two dates, one day each. HEADLINE: Delegate Without the Hiring Part DESCRIPTION: Build an assistant that learns how you work, in one in-person day. August 18 or 19. BUTTON: Book Now WHY: Solo professionals understand delegation but not AI, so the familiar frame makes the outcome legible. ────────────────────────────────────────── O08 · Outcome Principle: Capacity framing PRIMARY TEXT Same number of clients. Same standard of work. Less of you required to make it happen. That's the honest description of what an AI assistant does when you build it around your actual workflow instead of downloading someone else's. Commander is one day, in person, on the Charleston coast. Grant and Bill. You build it, you keep it, it's running when you leave. Around two hours a day back. August 18 or August 19. One day each. Learn more. HEADLINE: Same Work, Less of You in It DESCRIPTION: An assistant built around your workflow, not a generic template. Charleston coast, August 18 or 19. BUTTON: Learn More WHY: Speaks to owners who are the bottleneck in their own business without touching revenue language. ────────────────────────────────────────── O09 · Outcome Principle: Temporal discounting PRIMARY TEXT You walk in Tuesday morning. You walk out Tuesday evening with a working AI assistant you built. That's the timeline. Not a course you finish someday. Not notes to implement later. One day on the Charleston coast, and the thing exists. By the end of that week it's sorting email, drafting follow-up, handling scheduling, pulling research. August 18 is a Tuesday. August 19 is a Wednesday. Pick the one that fits your calendar. HEADLINE: Built in a Day, Working That Night DESCRIPTION: No homework, no someday. One in-person day on the Charleston coast. August 18 or 19. BUTTON: Sign Up WHY: Collapsing the distance between effort and payoff beats the biggest objection busy operators have. ────────────────────────────────────────── O10 · Outcome Principle: Vivid single image PRIMARY TEXT The 5:30 game is the benchmark around here. Whether the day ends in time to be in the folding chair for first pitch. Most of what keeps people late isn't the important work. It's triage, follow-up, scheduling, the fourth version of the same email. Commander is one day, in person, on the Charleston coast. You build your own AI assistant — no coding, no tech background — and it goes home working. Run by Grant and Bill. August 18 or August 19. HEADLINE: Make the 5:30 Game DESCRIPTION: One in-person day on the Charleston coast, August 18 or 19. BUTTON: Learn More WHY: One hyper-specific image does the emotional work in a single line, which survives Facebook truncation. ────────────────────────────────────────── J01 · Objection · I'm not technical Principle: Self-efficacy building PRIMARY TEXT Most people who sign up for Commander do not consider themselves technical. That is the room we built the day for. There is no code. There is no setup you have to do beforehand. Grant and Bill walk the room through it step by step, and you stop when you need to stop. By the end of the day you will have built a working AI assistant. Yours. Not a demo someone showed you. One day, in person, on the Charleston coast. August 18 or August 19 — pick the one that fits. HEADLINE: No Code. No Tech Background. DESCRIPTION: A one-day, in-person build day in Charleston. You leave with a working AI assistant you built yourself. BUTTON: Learn More WHY: Removes the disqualifying belief before the reader applies it to themselves, without telling them what they are. ────────────────────────────────────────── J02 · Objection · I don't have a whole day Principle: Cost-of-inaction reframe PRIMARY TEXT A full day is a real ask. We know what a Tuesday costs a working professional in Charleston. Here is the honest trade. Commander is one day, in person, start to finish. You build your own AI assistant while you are in the room. The outcome is roughly two hours a day back — email triage, follow-up, scheduling, research. We are not asking you to add a day. We are asking you to spend one to work on the days after it. August 18 or August 19. Choose the one you can actually protect. HEADLINE: One Day. Then Your Days Back. DESCRIPTION: Commander is a single in-person day in Charleston. Choose August 18 or 19. BUTTON: Learn More WHY: Validates the time objection as legitimate instead of dismissing it, which lowers resistance before the trade. ────────────────────────────────────────── J03 · Objection · AI is overhyped Principle: Inoculation framing PRIMARY TEXT Plenty of what gets said about AI is noise. If that is your read, you are reading it the same way we do. So Commander is built to skip the argument. No trend talk. No predictions about the future of work. You come in with your actual work. You spend one day building an assistant that handles a piece of it. At the end you look at the thing you built and decide for yourself whether it is useful. That is a much shorter conversation than the hype. One day on the Charleston coast. August 18 or August 19. HEADLINE: Skip The Hype. Build The Thing. DESCRIPTION: No trend talk. One in-person day in Charleston building against your real work. August 18 or 19. BUTTON: Learn More WHY: Joins the skeptic's side of the table rather than arguing, so the reader never defends a position. ────────────────────────────────────────── J04 · Objection · I tried ChatGPT, it was useless Principle: Attribution reframe PRIMARY TEXT A lot of people open ChatGPT, ask it something, get back something generic, and quietly close the tab. That is a fair reaction. A blank box does not know your clients, your process, or the way you write. Commander is the other approach. You spend the day giving an assistant your context — how you follow up, what your files look like, what you actually need drafted — and you build it around your work instead of asking it to guess. One day, in person, on the Charleston coast. August 18 or August 19. Bring the work that did not go well. HEADLINE: Generic Answers Have A Cause DESCRIPTION: Build an assistant around your real context and process. August 18 or 19. BUTTON: Learn More WHY: Reattributes a past failure to the setup rather than the reader, which preserves ego and reopens the door. ────────────────────────────────────────── J05 · Objection · It'll replace me Principle: Agency restoration PRIMARY TEXT The worry that this technology makes a professional redundant is worth saying out loud, not talking around. Here is how Commander treats it. You are not handing your judgment to anything. You are building a tool that takes the parts of the day nobody hired you for — the triage, the scheduling back-and-forth, the follow-up you keep meaning to send. The closing, the relationship, the read on a situation. That stays where it is. You build it. You decide what it does. One day on the Charleston coast. August 18 or August 19. HEADLINE: You Build It. You Direct It. DESCRIPTION: One in-person day in Charleston building an assistant for the work nobody hired you for. BUTTON: Learn More WHY: Converts a fear of displacement into a frame of ownership — the opposite emotional posture. ────────────────────────────────────────── J06 · Objection · I'm too old for this Principle: Permission to begin PRIMARY TEXT There is a quiet idea that this stuff belongs to people who grew up with it. We do not run the day that way. Commander moves at the pace of the room. Grant and Bill teach it in plain language, in person, with time to ask the question you would not ask on a webinar. What you bring is the part that is hard to teach — you know your business, your clients, and what actually needs doing. The tool is the easy half. By the end of the day you will have built a working assistant yourself. August 18 or August 19, on the Charleston coast. HEADLINE: Taught In Plain Language DESCRIPTION: In-person, at the pace of the room. Build your own AI assistant in a single day. BUTTON: Learn More WHY: Reframes experience as the scarce asset and technology as the trivial part, flipping the perceived disadvantage. ────────────────────────────────────────── J07 · Objection · I'll figure it out on YouTube Principle: Effort-cost contrast PRIMARY TEXT You could learn this from videos. That is true, and we are not going to pretend otherwise. The difference is what happens when it does not work. On a video, you pause, search again, and try a different creator. In the room, you raise your hand and Grant or Bill comes over and looks at your screen. Commander compresses the trial and error into one day and ends with a working assistant built around your business. The videos will still be there. This is the shortcut through them. August 18 or August 19, in person on the Charleston coast. HEADLINE: The Shortcut Through The Videos DESCRIPTION: One in-person Charleston day with Grant and Bill. Build instead of searching for the next tutorial. BUTTON: Learn More WHY: Concedes the objection immediately, which builds credibility, then competes on what video cannot offer. ────────────────────────────────────────── J08 · Objection · My business is too small/specific Principle: Specificity as feature PRIMARY TEXT Some of the best candidates for this are one-person operations with a process nobody else runs. Commander is not a template you receive. It is a day where you build an assistant around how your business actually works — your intake, your follow-up language, the reports you keep redoing. A solo agent, a loan officer, a two-person shop on the coast. The narrower your process, the more there is to hand off. You bring the specifics. You leave with something that fits them. One day, in person. August 18 or August 19. HEADLINE: Built Around Your Process DESCRIPTION: No templates. Build an assistant around how your business actually runs. August 18 or 19. BUTTON: Learn More WHY: Turns the disqualifier into the qualifier, so the reason not to come becomes the reason it works. ────────────────────────────────────────── J09 · Objection · I've paid for trainings before Principle: Tangible-artifact proof PRIMARY TEXT The usual pattern with a training is a notebook of good intentions and a folder you never open again. Commander is set up so that cannot be the outcome. It is a build day. The whole point is that you leave with a working AI assistant that you made, running on your work, that you can use the next morning. Not a recording. Not a workbook. A thing that exists because you built it in the room. If it does not work by the end of the day, we have not done our job. August 18 or August 19, on the Charleston coast. HEADLINE: You Leave With A Working Thing DESCRIPTION: A build day, not a lecture. Walk out with an AI assistant you made yourself. BUTTON: Learn More WHY: Sets a falsifiable standard for the day — a stronger trust signal than any promise about results. ────────────────────────────────────────── J10 · Objection · Not safe with client info Principle: Honest boundary setting PRIMARY TEXT Anyone holding client information should be asking what these tools touch. That question deserves a straight answer, not reassurance. Here is ours. We are not going to tell you it is all safe. What we will do is spend part of the day on where the lines are — what these tools retain, what settings matter, and what many professionals choose to keep out entirely. You decide what your assistant has access to. You can build something genuinely useful that never sees a client file. Bring your questions. Bring the hard ones. August 18 or August 19, in person on the Charleston coast. HEADLINE: You Decide What It Touches DESCRIPTION: We cover where the lines are, not blanket reassurance. One in-person Charleston day. BUTTON: Learn More WHY: Refusing to make a safety guarantee is itself the trust signal — the only honest way to handle this objection. ────────────────────────────────────────── I01 · Identity · The one who figures things out Principle: Identity-based motivation PRIMARY TEXT Some people read the manual. Others just start pushing buttons until the thing works. If that second one sounds familiar, Commander was built for that instinct. One day, in person, on the Charleston coast. Bring a laptop and a short list of the tasks you're tired of doing by hand. Leave with an AI assistant you built yourself — email triage, follow-up, scheduling, research. Not a lecture. Not a folder of notes. A working thing you made. August 18 or August 19. Pick the day that fits. Grant and Bill run the room. HEADLINE: Build It Yourself In One Day DESCRIPTION: A one-day, in-person AI assistant build on the Charleston coast. August 18 or 19. BUTTON: Learn More WHY: Flatters a trait people already claim, so signing up becomes consistent with who they think they are. ────────────────────────────────────────── I02 · Identity · The one who stays curious Principle: Commitment and consistency PRIMARY TEXT I have never met a genuinely curious person who regretted a day spent learning how something actually works. Commander is that kind of day. One session, in person, near the Charleston coast. Grant and Bill walk a room of non-technical professionals through building an AI assistant from scratch. Email triage. Follow-up. Scheduling. Research. Content drafts. You decide what yours does. No prior tech background needed. Just a laptop and a willingness to poke at things until they click. Two dates: August 18 and August 19. HEADLINE: One Day. One Working Assistant. DESCRIPTION: Build a real assistant in one in-person day. Charleston coast, August 18 or 19. BUTTON: Learn More WHY: Curiosity is a low-cost identity almost everyone accepts, so it recruits broadly without pressure. ────────────────────────────────────────── I03 · Identity · The small operator Principle: Underdog in-group pride PRIMARY TEXT A small operation can move faster than a big one. No committee. No approval chain. You decide on Tuesday and it's live by Thursday. That speed is the whole advantage. Commander is a one-day, in-person session on the Charleston coast where you build an AI assistant that handles the admin load a bigger shop would hire three people for. Email triage. Follow-up. Scheduling. Research. You build it in the room. You take it home working. August 18 or August 19. Grant and Bill run it. HEADLINE: Small Shop. Serious Leverage. DESCRIPTION: One-day, in-person build for solo operators and small teams. August 18 or 19. BUTTON: Sign Up WHY: Small operators love being told their size is an asset; reframes training as leverage rather than catch-up. ────────────────────────────────────────── I04 · Identity · Protects family evenings Principle: Role-based self-concept PRIMARY TEXT Around here, plenty of people would rather close the laptop before dinner than answer one more email at nine at night. Most of what stretches a workday isn't the meaningful work. It's the inbox, the follow-ups, the scheduling back-and-forth, the little research errands. Commander is one in-person day on the Charleston coast where you build an AI assistant to carry that layer. Roughly two hours a day handed back. You build it yourself, in the room, with Grant and Bill. You leave with it running. August 18 or August 19. HEADLINE: Get Your Evenings Back DESCRIPTION: Hand off inbox, follow-up, and scheduling to an assistant you build in one day. BUTTON: Learn More WHY: Benefit is family time rather than productivity, which lands harder with 35-60 and avoids income claims. ────────────────────────────────────────── I05 · Identity · Invests in themselves Principle: Self-investment signaling PRIMARY TEXT There's a certain kind of professional who books the class, shows up early, and sits close to the front. They've spent years getting good at their actual craft. They're not looking to become a technologist. They just want a real skill they can use Monday. Commander is one day, in person, on the Charleston coast. You build your own AI assistant — email triage, follow-up, scheduling, research — with Grant and Bill working the room. No coding. No prerequisites. You leave with the thing built and running. August 18 or August 19. HEADLINE: A Day Spent On Your Own Skills DESCRIPTION: One in-person day, one real skill. Charleston coast, August 18 or 19. BUTTON: Sign Up WHY: Frames the ticket as continuing education — an identity agents and loan officers already pay for annually. ────────────────────────────────────────── I06 · Identity · The builder / maker Principle: IKEA effect PRIMARY TEXT There's a specific satisfaction in making something that works. Charleston has a lot of people who chase that feeling. Commander is built around it. One day, in person, on the coast. You don't watch a demo — you build an AI assistant with your own hands and test it before you leave the room. Yours might sort email. Draft follow-ups. Handle scheduling. Do the research you keep putting off. Whatever you build, it's yours. You know how it works because you made it. August 18 or August 19. Grant and Bill run the day. HEADLINE: Leave With Something You Built DESCRIPTION: Not a lecture. A build day. Charleston coast, August 18 or 19. BUTTON: Book Now WHY: Build-it-yourself is the actual differentiator and doubles as an identity — hook and proof are the same thing. ────────────────────────────────────────── I07 · Identity · Would rather learn than outsource Principle: Autonomy and self-reliance PRIMARY TEXT You can pay someone to set all this up for you. Some people would rather understand it themselves. Same reason certain folks change their own oil, or read the closing documents line by line. Not stubbornness. Just a preference for knowing how your own operation runs. Commander is one in-person day on the Charleston coast. You build your own AI assistant — email triage, follow-up, scheduling, research — and you learn it well enough to change it later. No coding. Grant and Bill are in the room with you the whole day. August 18 or August 19. HEADLINE: Learn It Instead Of Renting It DESCRIPTION: Build and understand your own AI assistant in one in-person day. BUTTON: Learn More WHY: Names the competing option and repositions self-reliance as taste rather than thrift, avoiding price talk. ────────────────────────────────────────── I08 · Identity · The one others ask Principle: Status through usefulness PRIMARY TEXT In most offices there's one person everybody walks over to when something new shows up on the screen. It's rarely the most technical person. It's the one who took the time to actually sit down with it. Commander is a day for sitting down with it. One session, in person, near the Charleston coast. You build a working AI assistant — email triage, follow-up, scheduling, research — and you understand it well enough to explain it. That's a useful thing to be able to do in a town this size. August 18 or August 19. Grant and Bill run it. HEADLINE: Be The One With The Answer DESCRIPTION: Understand AI well enough to explain it. One-day build, August 18 or 19. BUTTON: Sign Up WHY: Social standing motivates many owners more than efficiency; the small-market line lands locally without naming anyone. ────────────────────────────────────────── I09 · Identity · Early but not reckless Principle: Aspirational moderation PRIMARY TEXT There's a difference between chasing every new thing and paying attention to the ones that stick around. AI assistants have moved past the novelty stage. They're doing ordinary, boring, useful work now — sorting email, drafting follow-ups, holding a calendar together, running research. Commander is one day, in person, on the Charleston coast, to get on the useful side of that without a big detour. You build your own assistant. You leave with it working. No coding. No prior background assumed. August 18 or August 19. HEADLINE: Steady Hands, New Tools DESCRIPTION: Practical AI for people who don't chase hype. Charleston coast, August 18 or 19. BUTTON: Learn More WHY: Gives cautious 45-60 professionals a flattering label for their hesitation instead of scolding it. ────────────────────────────────────────── I10 · Identity · Refuses to be intimidated Principle: Self-efficacy restoration PRIMARY TEXT New tools have a way of looking like they came with a language requirement. Most of them didn't. Commander is a room full of people who run businesses, sell houses, close loans, keep books. Not engineers. Everyone starts from the same place, and everyone builds a working AI assistant before the day ends. Email triage. Follow-up. Scheduling. Research. Whatever eats your afternoons. One day, in person, on the Charleston coast. Grant and Bill stay in the room. Nobody gets left behind on step four. August 18 or August 19. HEADLINE: No Tech Background Required DESCRIPTION: A room of non-technical professionals, all building working assistants in one day. BUTTON: Sign Up WHY: Naming the intimidation and dissolving it removes the top objection while the room description supplies belonging. ────────────────────────────────────────── S01 · Social Proof · voice: Christa Principle: Reluctant convert PRIMARY TEXT Hey. I thought the AI thing was mostly hype. I'm a loan officer, not a tech person. I said no to it twice before I said yes. Then Grant and Bill trained me on this exact system. I built my own assistant in one day, back in June. Not a demo. Mine. It reads my inbox first thing and tells me what actually needs me. It drafts my follow-ups. It preps my research before a call. I get about two hours a day back. That's dinner with my family instead of email at nine o'clock. They're running it here in Charleston on August 18 and 19. One day, pick your date. HEADLINE: I Didn't Think This Was For Me DESCRIPTION: One day in the Charleston area. You build your own AI assistant. August 18 or 19. BUTTON: Learn More WHY: Skeptic-to-convert is the most credible testimonial shape; 'said no twice' pre-empts the reader's own objection. ────────────────────────────────────────── S02 · Social Proof · voice: Christa Principle: Specificity as proof PRIMARY TEXT Hey. Here's the smallest thing my AI assistant does, and it's the one I'd miss most. Every morning it goes through my inbox and hands me a short list. What needs me today. What can wait. What it already drafted a reply for. That's it. Not glamorous. But I used to spend the first hour of every day just deciding what to do first. Grant and Bill trained me on this system in June. I built the thing myself in a single day, and I am not technical. They're teaching it in the Charleston area August 18 and 19. One day, your pick. HEADLINE: The Small Thing I'd Miss Most DESCRIPTION: Build your own AI assistant in one day near Charleston. August 18 or 19. BUTTON: Learn More WHY: A small checkable detail reads as true in a way big claims never do. ────────────────────────────────────────── S03 · Social Proof · voice: Christa Principle: Admitted error builds trust PRIMARY TEXT Hey. I was wrong about two things with AI, and one of them cost me about six months. First, I thought you had to be technical. You don't. I'm not. Grant and Bill trained me on this system and I built my own assistant in one day in June. Second, I thought it was a toy. Mine triages email, drafts follow-up, keeps my calendar honest, and pulls research before calls. About two hours a day back. Here's what I was right about. It is not magic. You have to tell it how you work. That part is on you. Charleston area, August 18 or 19. One day. HEADLINE: Two Things I Got Wrong DESCRIPTION: A one-day, hands-on build near Charleston with Grant and Bill. August 18 or 19. BUTTON: Learn More WHY: Admitting a real cost and naming a genuine limitation buys permission for the claim that follows. ────────────────────────────────────────── S04 · Social Proof · voice: Christa Principle: Peer recommendation PRIMARY TEXT Hey. People keep asking me what I actually did, so here's the short version. Grant and Bill trained me on their system. I spent one day building an AI assistant that works the way I work. I didn't watch someone else build it. I built it. Now it handles my email triage, my follow-up, my scheduling back-and-forth, and the research I used to do at night. Roughly two hours a day back. Same job, less grinding. They're running the one-day version in the Charleston area on August 18 and 19. If you've been curious, that's the door. HEADLINE: What I Tell People Who Ask DESCRIPTION: One day. You build it yourself. Charleston coast area, August 18 or 19. BUTTON: Learn More WHY: Framing it as an answer to a recurring question implies demand without inventing a statistic. ────────────────────────────────────────── S05 · Social Proof · voice: Christa Principle: Mundane detail signals honesty PRIMARY TEXT Hey. Nobody talks about the boring part, so I will. My AI assistant writes the follow-up emails I used to forget. Not the big impressive ones. The ordinary ones. The check-in on a Tuesday. The 'here's what's next' after a call. The reminder I always meant to send and didn't. I built it in a single day after Grant and Bill trained me on the system. In June. I'm not technical. That one boring habit is most of the two hours a day I got back. They're teaching this in the Charleston area, August 18 or 19. One day. HEADLINE: The Unglamorous Part Nobody Says DESCRIPTION: Build a working AI assistant in one day near Charleston. Run by Grant and Bill. BUTTON: Learn More WHY: Deliberately anti-hype — naming the unsexy win makes the two-hour figure feel earned. ────────────────────────────────────────── S06 · Social Proof · voice: Christa Principle: Honest before-and-after PRIMARY TEXT Hey. One week after I built my AI assistant, here's what was actually different. My inbox was sorted before I opened it. My follow-ups went out on time instead of three days late. I stopped doing research at ten at night. Honestly, week one was also a little clumsy. I had to correct it a lot. It got better because I kept telling it what I wanted. By the end of the month I had about two hours a day back. Grant and Bill trained me on this exact system. They're running the one-day build in the Charleston area August 18 and 19. HEADLINE: One Week In, Here's What Changed DESCRIPTION: A single day of hands-on building near Charleston. Pick August 18 or 19. BUTTON: Sign Up WHY: Admitting week one was clumsy makes the month-one result far more believable. ────────────────────────────────────────── S07 · Social Proof · voice: Christa Principle: Regret-framed advice PRIMARY TEXT Hey. If I could tell myself one thing back in May, it would be this. Stop researching it and go build it. I read about AI for months. Saved articles. Watched videos. Changed nothing. Then Grant and Bill trained me on their system and I built my own assistant in one day in June. One day did more than five months of reading did. It handles email triage, follow-up, scheduling and research now. About two hours a day back. They're running the one-day build in the Charleston area on August 18 and 19. Pick a date and go. HEADLINE: What I'd Tell Myself In May DESCRIPTION: One day, in person, on the Charleston coast. August 18 or 19. BUTTON: Sign Up WHY: Names the exact stall pattern of the perpetual researcher and gives them a self-recognition moment. ────────────────────────────────────────── S08 · Social Proof · voice: Christa Principle: Vivid turning point PRIMARY TEXT Hey. The moment it clicked for me was small. I asked my assistant to draft three follow-ups and it did them in my words. Not stiff. Not robotic. Mine. I changed one sentence and sent all three. I sat there for a second thinking, that used to be forty minutes of my afternoon. Grant and Bill trained me on this system in June. I built the whole thing in a single day and I am not a technical person. They're teaching the same one-day build in the Charleston area on August 18 and 19. One day. You leave with yours. HEADLINE: The Moment It Clicked For Me DESCRIPTION: One-day, in-person AI assistant build near Charleston. August 18 or 19. BUTTON: Learn More WHY: 'It sounded like me' answers the quiet fear that AI writing will embarrass them. ────────────────────────────────────────── S09 · Social Proof · voice: Christa Principle: Loss aversion, honest PRIMARY TEXT Hey. I don't think I could go back to my old mornings, and that surprises me more than anything. The old version. Open the laptop, stare at a full inbox, spend an hour sorting before I did one useful thing. Now the sorting is done. The drafts are waiting. I start with the work instead of the pile. Grant and Bill trained me on this system. I built my own assistant in one day in June, with no technical background, and it's been about two hours a day back since. Charleston area, August 18 and 19. One day, pick one. HEADLINE: I Can't Go Back To Old Mornings DESCRIPTION: One day near the Charleston coast with Grant and Bill. August 18 or 19. BUTTON: Learn More WHY: Contrasts two concrete mornings so the reader measures the gap themselves. ────────────────────────────────────────── S10 · Social Proof · voice: Christa Principle: Candor increases credibility PRIMARY TEXT Hey. Before anyone signs up for this, here's the honest part I'd want to know first. The whole day is built around you doing the work. It is not a lecture you can half-listen to. If that's not what you're after, skip it. And what you build is only as good as what you tell it about how you work. Be vague with it and it'll be vague right back. That part is on you. That said. Grant and Bill trained me on this exact system, I built a working assistant in one day, and I'm not technical. About two hours a day back since June. Charleston area, August 18 or 19. HEADLINE: The Honest Part, Before You Go DESCRIPTION: A working day, not a lecture. Charleston coast, August 18 or 19. BUTTON: Learn More WHY: Telling the wrong-fit reader to skip it is the strongest trust signal available. ────────────────────────────────────────── U01 · Urgency Principle: Fixed-date commitment PRIMARY TEXT August 18 and 19. Those are the two dates. Charleston, in person, one day, and you leave with a working AI assistant you built yourself. Not notes. Not a recording you'll get to eventually. A thing that runs your email triage, your follow-up, your scheduling. That's about two hours a day back. We're two weeks out. After the 19th, the next one isn't on the calendar yet. Pick your day and grab your spot. HEADLINE: Commander: Aug 18 or Aug 19 DESCRIPTION: One day in Charleston. Build your own AI assistant. Two dates only. BUTTON: Sign Up WHY: Leads with the hard date instead of a pitch, so the deadline reads as information rather than pressure. ────────────────────────────────────────── U02 · Urgency Principle: Calendar-fill reality PRIMARY TEXT Two weeks out is when August stops being flexible. Right now the 18th and 19th are probably still open on your calendar. In ten days something will have landed on them. That's just how it works. So here's the ask: look at those two dates before something else claims them. Commander is one day, in person, on the Charleston coast. You build a working AI assistant. Email triage, follow-up, scheduling, research. Roughly two hours a day back. Pick a day now while you still can. HEADLINE: Claim Aug 18 or 19 Now DESCRIPTION: Your August is about to fill up. Block one day and build an assistant that works. BUTTON: Sign Up WHY: Implementation-intention framing — asks for a calendar decision, not a purchase decision. ────────────────────────────────────────── U03 · Urgency Principle: Opportunity cost PRIMARY TEXT Do the math on one more quarter. Say you keep handling email, follow-up, and scheduling the way you handle it now. Call it two hours a day. Multiply that by the rest of the year. That's the real cost of "I'll look at AI later." Not a fee. Hours. Commander is one day. August 18 or 19, in person, Charleston coast. Grant and Bill walk you through building your own assistant. You leave with it working. Non-technical is the norm in that room, not the exception. See the details and pick your date. HEADLINE: One Day vs. One More Quarter DESCRIPTION: Every week without the system is another week doing it the slow way. Aug 18 or 19. BUTTON: Learn More WHY: Loss aversion with honest arithmetic — no dollar figures, just hours the reader recognizes. ────────────────────────────────────────── U04 · Urgency Principle: Unscheduled next chance PRIMARY TEXT There is no "next one" yet. August 18 and 19 are on the calendar. Whatever comes after them isn't scheduled. Not hidden, not a tactic. It just hasn't been set. So if you've been meaning to sit down and actually build an AI assistant instead of reading about them, this is the window that exists right now. One day, in person, Charleston coast. You walk out with a working assistant handling email, follow-up, scheduling, and research. Have a look and choose your day. HEADLINE: After Aug 19, Nothing Is Set DESCRIPTION: The next session isn't on the calendar. These two dates are. BUTTON: Learn More WHY: The most honest scarcity there is — names the limit and admits exactly why it exists. ────────────────────────────────────────── U05 · Urgency Principle: Decide now, not buy now PRIMARY TEXT You don't have to decide about AI today. You do have to decide about August 18 and 19. That's a smaller question. It's a calendar question. Commander is one day in person on the Charleston coast. Grant and Bill sit with you while you build your own assistant. Email triage. Follow-up. Scheduling. Content. Research. The people in that room are business owners, agents, loan officers. Mostly not technical. Two weeks out. Two dates. Take a look and see if one of them fits. HEADLINE: It's a Calendar Question DESCRIPTION: Not a decision about AI. A decision about one day in August. BUTTON: Learn More WHY: Shrinks the commitment to a single yes-or-no about a date — the lowest-friction way to create urgency. ────────────────────────────────────────── U06 · Urgency Principle: Physical capacity truth PRIMARY TEXT Hands-on rooms have a ceiling. Not a marketing thing. A room thing. Grant and Bill are walking around helping people actually build the assistant, and there's only so much of that to go around in a day. That's why Commander is one day, in person, and small by design. August 18 or 19, Charleston coast. You leave with a working assistant. Email triage, follow-up, scheduling, research. About two hours a day back. We're two weeks out. Worth looking at now rather than the week of. HEADLINE: A Room Holds What It Holds DESCRIPTION: Hands-on means limited by design. Aug 18 or 19 on the Charleston coast. BUTTON: Learn More WHY: Capacity urgency without a fabricated number — the constraint is explained rather than asserted. ────────────────────────────────────────── U07 · Urgency Principle: Gentle assumptive close PRIMARY TEXT If you've read this far more than once, you already know. That's usually the tell. The thinking is done. What's left is the date. August 18 or August 19. One day, in person, Charleston coast. You build your own AI assistant and leave with it running — email triage, follow-up, scheduling, content, research. Nobody's going to push you. That's not how Grant and Bill run a room, and it's not how this works. But the dates are the dates. Pick one when you're ready, and ready is probably now. HEADLINE: You've Already Thought About It DESCRIPTION: The thinking part is done. What's left is picking a day. BUTTON: Learn More WHY: Warm and anti-pressure on the surface while still forcing the decision point. ────────────────────────────────────────── U08 · Urgency Principle: Temporal landmark PRIMARY TEXT The kids go back, the calendar tightens, and Q4 shows up faster than anyone plans for. Late August is the last quiet stretch before all of that. It's a strange, useful window — the exact right time to fix how you work instead of just working harder through it. Commander is one day. August 18 or 19, in person, Charleston coast. You build a working AI assistant that handles email triage, follow-up, scheduling, and research. Roughly two hours a day back, going into the busiest part of the year. See the two dates and pick yours. HEADLINE: Fix It Before Q4 Arrives DESCRIPTION: Late August is the last quiet window. One day, Charleston coast. BUTTON: Learn More WHY: A temporal landmark everyone in this age range feels, which makes the date meaningful rather than arbitrary. ────────────────────────────────────────── U09 · Urgency Principle: Compounding delay cost PRIMARY TEXT Waiting isn't neutral. Every week without the system is another week of doing it the slow way. The follow-ups you meant to send. The inbox at ten at night. The research you keep putting off. None of that gets easier by itself. It stacks. Commander is one day to stop the stacking. August 18 or 19, in person, Charleston coast. You build your own AI assistant with Grant and Bill in the room, and you leave with it working. Two weeks out. Look at the dates and choose one. HEADLINE: Waiting Has a Cost Too DESCRIPTION: The slow way doesn't get faster on its own. One day, Charleston. BUTTON: Learn More WHY: Names specific recognizable daily frictions so the cost of delay feels concrete instead of abstract. ────────────────────────────────────────── U10 · Urgency Principle: Clean deadline clarity PRIMARY TEXT Short version. Commander. One day. Charleston coast, in person. August 18 or August 19 — pick one. You build your own AI assistant. Email triage, follow-up, scheduling, content, research. You leave with it working, not with a folder of notes. Most people in the room aren't technical. That's the point. Today is August 3. That's about two weeks. Details are at the link. HEADLINE: Aug 18 or 19. Charleston. DESCRIPTION: One day. In person. You leave with a working AI assistant you built. BUTTON: Sign Up WHY: Pure clarity with zero persuasion theater — stands out in a feed full of hype. ────────────────────────────────────────── N01 · Story · voice: Christa Principle: Narrative transportation PRIMARY TEXT The morning it broke for me, I had 61 unread emails and a client waiting on an answer I'd already written twice. I remember sitting in my car in a parking lot off the coast, not going in yet. Just scrolling. Deleting. Flagging things I knew I'd never come back to. I wasn't behind because I was lazy. I was behind because the small stuff never stopped. In June, Grant and Bill trained me on the exact system they teach. I'm not technical. I built my own AI assistant in one day. It handles my email triage now. My follow-up. My scheduling. My research. I got about two hours a day back. They're running Commander here in Charleston on August 18 and 19. One day. Pick the date that works. HEADLINE: Build Your AI Assistant In A Day DESCRIPTION: One-day, in-person AI assistant training in Charleston. August 18 or 19. BUTTON: Learn More WHY: Opens in-media-res with a concrete unglamorous scene, so the reader is inside the story before any pitch. ────────────────────────────────────────── N02 · Story · voice: Christa Principle: Small-moment realization PRIMARY TEXT It wasn't a big dramatic moment. It was a Tuesday, and I was rewriting the same follow-up email for the fourth time that week. Same words. Different name at the top. And I thought: I have done this exact thing hundreds of times. Why am I still the one doing it? That was the crack in the wall. Grant and Bill trained me on this system in June. I built my own AI assistant in a single day, and I want to be clear that I am not a technical person. Not even a little. Now it drafts the follow-up. It sorts what actually needs me. It handles scheduling and research. Roughly two hours a day, back in my hands. They're teaching it in Charleston August 18 and 19. HEADLINE: The Same Email, Over And Over DESCRIPTION: Learn the one-day system that handles email, follow-up, and scheduling. August 18 or 19. BUTTON: Learn More WHY: A boring realization is more believable than a dramatic one, and mirrors a moment nearly everyone has had. ────────────────────────────────────────── N03 · Story · voice: Christa Principle: Extended struggle arc PRIMARY TEXT For months I told myself I just needed a better system. A better calendar. A better app. A better morning routine. I tried all of it. I'd get organized on Monday and be buried again by Wednesday. The problem was never organization. The problem was volume. There was more small work than there were hours, and no app fixes that. In June, Grant and Bill trained me on the exact system they teach. In one day I built my own AI assistant. I'm not technical and I didn't need to be. Email triage. Follow-up. Scheduling. Research. About two hours a day came back. I use some of it for work. I use some of it for my family. That part matters more than I expected. Commander is in Charleston, August 18 and 19. HEADLINE: It Wasn't A Calendar Problem DESCRIPTION: A one-day, in-person build session in Charleston. Leave with a working AI assistant. BUTTON: Learn More WHY: Validates every failed productivity attempt the reader has made, then reframes the problem instead of blaming them. ────────────────────────────────────────── N04 · Story · voice: Christa Principle: Two-scene contrast PRIMARY TEXT Scene one: a Thursday in May. I'm at my desk at 9pm doing the work I couldn't get to during the day. Emails, mostly. Nothing hard. Just a lot. Scene two: a Thursday in July. Same desk. I'm done by dinner. What changed in between wasn't discipline. I've always had discipline. It's that in June, Grant and Bill trained me on this exact system, and I built my own AI assistant in one day. It triages my inbox. It handles follow-up and scheduling. It does research I used to do myself at night. About two hours a day, returned. I'm not technical. I want to keep saying that, because it's the part people don't believe. Commander runs in Charleston on August 18 and 19. HEADLINE: Same Desk. Two Different Nights. DESCRIPTION: Build a working AI assistant in one day. Charleston, August 18 or 19. BUTTON: Learn More WHY: Before/after told as two dated scenes gives the transformation a shape rather than a claim. ────────────────────────────────────────── N05 · Story · voice: Christa Principle: Vulnerable admission PRIMARY TEXT Here's an admission. I put this off for a while because I assumed AI meant learning to code, and I didn't want to look stupid in a room full of people who already got it. That's the real reason. Not time. Not money. Pride. In June, Grant and Bill trained me on the exact system they teach. There was no code. There were no prerequisites. I just followed the steps and by the end of the day I had a working assistant that was mine. It sorts my email. It drafts my follow-up. It handles scheduling and research. I got roughly two hours a day back. If you've been quietly avoiding this for the same reason I did, that's a normal place to start. Commander is in Charleston, August 18 and 19. HEADLINE: I Avoided This For The Wrong Reason DESCRIPTION: No coding. No prerequisites. One day in Charleston, August 18 or 19. BUTTON: Learn More WHY: Naming the pride objection disarms the single biggest silent blocker for non-technical professionals. ────────────────────────────────────────── N06 · Story · voice: Christa Principle: Letter to a friend PRIMARY TEXT Hey. I'm writing this the way I'd say it to you over coffee, because I think a lot of people in my world would get something out of it. You know how the actual job is maybe forty percent of the job? The rest is inbox, follow-up, calendar, looking things up. That was me. For a long time. In June, Grant and Bill trained me on this exact system. I built my own AI assistant in one day. I'm not technical. Nobody has ever accused me of being technical. Now it handles the triage, the follow-up, the scheduling, the research. About two hours a day came back. They're bringing Commander to Charleston on August 18 and 19. One day, in person. Pick whichever date works. No pressure from me. I just wouldn't feel right not mentioning it. HEADLINE: Telling You Like I'd Tell A Friend DESCRIPTION: One-day, in-person AI assistant build in Charleston. Two dates: August 18 or 19. BUTTON: Learn More WHY: Letter format plus an explicit 'no pressure' matches her anti-hard-sell voice and lowers defenses. ────────────────────────────────────────── N07 · Story · voice: Christa Principle: Sunday-night dread PRIMARY TEXT Sunday night used to have a feeling. Around 7pm the week ahead would start pressing on me before it even began. Not fear exactly. More like a running list. Who I owed a reply. What I forgot Friday. What Monday morning was going to look like when I opened the laptop. I'd sit there with the TV on and not watch it. In June, Grant and Bill trained me on the exact system they teach. I built my own AI assistant in one day, and I'm not technical. Monday mornings look different now. The inbox is already sorted. Follow-ups are drafted. My schedule and my research are handled. Roughly two hours a day back, and a quieter Sunday. Commander comes to Charleston August 18 and 19. HEADLINE: Sunday Night Used To Feel Different DESCRIPTION: Build your own AI assistant in a single day. Charleston coast, August 18 or 19. BUTTON: Learn More WHY: Sunday-night dread is near-universal among self-employed professionals; naming it earns instant recognition. ────────────────────────────────────────── N08 · Story · voice: Christa Principle: Overheard question PRIMARY TEXT My husband asked me a question in June that I didn't have a good answer for. He said: what would you actually do with an extra two hours a day? I stood there. I genuinely didn't know. I'd been so busy being busy that I'd stopped picturing anything on the other side of it. That week, Grant and Bill trained me on this exact system. I built my own AI assistant in one day. I'm not technical, and I keep saying that because it was the whole reason I almost didn't try. It handles my email triage, my follow-up, my scheduling, my research. The two hours are real. I've since figured out what to do with them. Most of it involves not being at my desk. Commander is in Charleston, August 18 and 19. HEADLINE: What Would You Do With Two Hours? DESCRIPTION: A one-day, in-person build. Charleston, August 18 or 19. BUTTON: Learn More WHY: A single overheard question is the most portable story form, and hands the reader a question they answer themselves. ────────────────────────────────────────── N09 · Story · voice: Christa Principle: Turning-point specificity PRIMARY TEXT The turning point wasn't the training itself. It was about four hours in, on that day in June, when the thing I was building actually did what I asked it to do. I'd typed something. It came back correct. I sat back in the chair and just looked at it. I had built that. Me. A person who calls her kid when the printer acts up. Grant and Bill trained me on this exact system, start to finish, in one day. No code. No background required. Now that assistant does my email triage, my follow-up, my scheduling, my research. About two hours a day came back to me. That's the moment they're setting up for you. Not a lecture. A working thing, built by your own hands. Commander. Charleston. August 18 and 19. HEADLINE: The Moment It Actually Worked DESCRIPTION: One day, in person, in Charleston. August 18 or 19. BUTTON: Learn More WHY: Sells the felt moment of capability rather than the feature list — what non-technical buyers actually purchase. ────────────────────────────────────────── N10 · Story · voice: Christa Principle: Quiet closing reflection PRIMARY TEXT I moved to Charleston from New Jersey in 2009. Every year since, the work has gotten a little fuller and the days a little shorter. You don't notice it happening. You just look up one day and realize you've been answering emails during dinner for a long time. In June, Grant and Bill trained me on the exact system they teach. I built my own AI assistant in a single day. I'm not technical. I want that on the record. It handles email triage, follow-up, scheduling, research. About two hours a day came back. I'm not going to tell you it changed my life. I'll tell you it gave me back some evenings, and at this point in mine, that counts for a lot. Commander is in Charleston, August 18 and 19. HEADLINE: It Gave Me Back Some Evenings DESCRIPTION: One-day AI assistant training on the Charleston coast. August 18 or 19. BUTTON: Learn More WHY: Deliberate understatement reads as honest in a feed full of overclaiming. ────────────────────────────────────────── M01 · Mechanism Principle: Concreteness over abstraction PRIMARY TEXT Here is the actual list of what an AI assistant handles. Not the hype version. The literal list. Reads your inbox and sorts what matters from what doesn't. Drafts replies in your voice for you to approve. Sends follow-up and tracks who responded. Handles the back-and-forth of scheduling. Researches a person or company before your call. Writes first drafts. Summarizes a forty-message thread into a paragraph. Keeps a running list of who owes you what. Commander is one day in Charleston. August 18 or August 19. You build the assistant yourself and take it home working. Pick your date on the details page. HEADLINE: What It Actually Does All Day DESCRIPTION: One day in Charleston with Grant and Bill. Build your own AI assistant. BUTTON: Learn More WHY: A plain enumerated list beats abstract claims for skeptics, and lets a reader self-identify with one task. ────────────────────────────────────────── M02 · Mechanism Principle: Reason-why compliance PRIMARY TEXT Most AI trainings hand you a slide deck. Here's the shape of our day instead, hour by hour. Morning: we pick the one part of your week that eats the most time. Then we set the assistant up and connect it to the work you actually do. Midday: we teach it your voice using things you've already written. Afternoon: we run it on real tasks with you watching, and fix what it gets wrong. End of day: it works, and you know why it works. Charleston. August 18 or August 19. Grant and Bill run it. See the full outline. HEADLINE: The Day, Broken Into Parts DESCRIPTION: A one-day build session on the coast. You leave with a working assistant, not notes. BUTTON: Learn More WHY: Giving the agenda shape removes the biggest unspoken objection: what will I actually be doing all day. ────────────────────────────────────────── M03 · Mechanism Principle: Definition reduces resistance PRIMARY TEXT "AI assistant" is a fuzzy phrase. Here's what it means in practice, defined narrowly. It means a tool you've configured to do specific recurring jobs: triage the inbox, draft the reply, chase the follow-up, summarize the long document, prep the research before a call. It is not a robot employee. It doesn't have judgment. It proposes, you approve. That's a smaller promise than what you've been hearing. It's also the part that's real, and it's roughly two hours a day back. Commander is one day in Charleston, August 18 or August 19. Read the details. HEADLINE: What "Assistant" Actually Means DESCRIPTION: A narrow, honest definition and a day to build one. Charleston coast, August 18 or 19. BUTTON: Learn More WHY: Deflating the term is more persuasive than inflating it for people already oversold on AI. ────────────────────────────────────────── M04 · Mechanism Principle: End-to-end demonstration PRIMARY TEXT One task, start to finish, so you can see how this works. Take follow-up. You finish a call. You tell the assistant what was said and what you promised. It writes the recap email in your voice. You read it, change a line, send it. It adds that person to a list with what you owe them and by when. Three days later it drafts the nudge. You approve or you don't. That one loop is most of what gets dropped in a busy week. We build loops like that in a single day in Charleston. August 18 or August 19. See how the day runs. HEADLINE: One Task, Explained Fully DESCRIPTION: Follow-up from call to recap to nudge, with you approving each step. BUTTON: Learn More WHY: Walking one familiar workflow end to end creates a simulation the reader maps onto their own week. ────────────────────────────────────────── M05 · Mechanism Principle: Processing fluency PRIMARY TEXT What to bring: a laptop and one part of your week you'd like handed off. That's it. No coding. No prior setup. No prep reading. What you leave with: an assistant you built and understand, running on your own accounts, doing the specific job you chose. Plus the ability to change it later, because you're the one who set it up. You don't leave with a workbook. You leave with a working thing. Commander is one day on the Charleston coast, run by Grant and Bill. August 18 or August 19. View both dates. HEADLINE: Bring A Laptop. Leave With This. DESCRIPTION: No coding, no prep. One day in Charleston and you go home with something that runs. BUTTON: Learn More WHY: The bring/leave frame is the fastest answer to 'what am I signing up for' and removes the effort objection. ────────────────────────────────────────── M06 · Mechanism Principle: Contrast clarifies value PRIMARY TEXT The difference between this and typing into ChatGPT is that the browser tab forgets you. Every session you re-explain your business, your clients, how you write. Then you copy the answer out and paste it somewhere useful yourself. An assistant is set up once. It holds your context, connects to the places your work actually lives, and runs the same job on a schedule instead of waiting for you to ask. You still review everything before it goes out. That part doesn't change. One day in Charleston. August 18 or August 19. See the details. HEADLINE: Not Just A Chat Window DESCRIPTION: Set it up once instead of re-explaining yourself daily. One day on the coast. BUTTON: Learn More WHY: Almost everyone here has tried a chatbot and been underwhelmed, so naming that experience earns the read. ────────────────────────────────────────── M07 · Mechanism Principle: Curiosity satisfied PRIMARY TEXT How it learns to write like you: you feed it things you already wrote. That's the whole trick. A handful of your real emails. The way you open, the way you close, how blunt you are, whether you use the person's first name twice. It pulls the pattern from those and drafts new messages the same way. You read each one before it sends. Early on you'll fix a few, and each fix makes the next draft closer. We do that step together during the day so it's tuned before you leave. Charleston. August 18 or August 19. Read more. HEADLINE: How It Learns Your Voice DESCRIPTION: It patterns off emails you've already written. You review every draft. BUTTON: Learn More WHY: 'How does it sound like me' is the top private question in this audience; answering it plainly builds credibility. ────────────────────────────────────────── M08 · Mechanism Principle: Honest limits build trust PRIMARY TEXT What this will not do, so nobody's surprised on August 19. It won't make decisions for you. It won't negotiate. It won't send anything to a client without you looking at it first, and we set it up that way on purpose. It won't replace judgment on anything that carries real consequences. It doesn't know what it doesn't know, so a person stays in the loop. What it does do is the drafting, sorting, chasing, and summarizing that fills your week. That's roughly two hours a day. One day in Charleston. August 18 or August 19. See what's covered. HEADLINE: The Honest Limits, Up Front DESCRIPTION: No decisions, no unsupervised sending. A person stays in the loop. BUTTON: Learn More WHY: Leading with limits disarms the AI-skeptical professional and signals nobody is selling a fantasy. ────────────────────────────────────────── M09 · Mechanism Principle: Jargon removal PRIMARY TEXT Four words people throw around, in plain English, before you decide if this is for you. Prompt: what you tell it to do. Written once, reused. Context: the background it keeps about your business so you stop re-explaining. Agent: a prompt that runs on its own schedule instead of waiting on you. Human in the loop: you approve before anything leaves your name. That's most of the vocabulary. If it sounded harder than that, that was the marketing, not the tool. Commander is one day in Charleston. August 18 or August 19. Learn more. HEADLINE: The Jargon, In Plain English DESCRIPTION: Four terms defined, no technical background needed. One day with Grant and Bill. BUTTON: Learn More WHY: A glossary delivers value inside the ad itself, which earns the click from a non-technical reader. ────────────────────────────────────────── M10 · Mechanism Principle: Vivid first-step imagery PRIMARY TEXT The first hour isn't a lecture. You open your laptop and we look at your actual inbox. We find the messages you answer over and over. We name the one job you'd hand off first if you could. Then the assistant gets set up and does that job once, badly, while you watch. Then you correct it. That's the whole method. Build, watch, correct, repeat, until it's right and you understand every piece of it. By the end of the day it runs and you can change it yourself. Charleston, August 18 or August 19. See both dates. HEADLINE: What The First Hour Looks Like DESCRIPTION: Laptop open, real inbox, build and correct until it works. BUTTON: Learn More WHY: Showing the first small step, including it failing at first, makes the day feel survivable rather than intimidating. ────────────────────────────────────────── L01 · Local · Proximity Principle: In-group proximity bias PRIMARY TEXT Most AI training happens somewhere else. This one is happening on the Charleston coast, on August 18 and August 19. One day. In person. You pick the date. It's a build day, not a lecture. Grant and Bill walk you through making your own AI assistant — the one that handles your email triage, your follow-up, your scheduling. You leave with a working thing you made. Not a folder of notes you'll never open. It's built for people who run something: agents, contractors, loan officers, solo practices. No coding background needed. Pick your date and read the details. HEADLINE: AI Build Day on the Coast DESCRIPTION: One day, in person, near Charleston. Build your own AI assistant. August 18 or 19. BUTTON: Learn More WHY: Geography in the first eight words is the single strongest lift on a Meta local campaign. ────────────────────────────────────────── L02 · Local · Proximity Principle: Zero-travel convenience PRIMARY TEXT No flight. No hotel. No conference badge. Just a drive over the bridge and one focused day. Commander is a one-day, in-person AI training happening in the Charleston area on August 18 and August 19. Pick whichever day works. You spend the day building your own AI assistant — email triage, follow-up, scheduling, research, content. The kind of work that quietly eats about two hours out of every day. Whether you're coming from Mount Pleasant, West Ashley, Summerville or downtown, you're home for dinner. See the full schedule and choose your date. HEADLINE: One Day. No Travel Required. DESCRIPTION: In-person AI assistant training in the Charleston area. Drive home the same night. BUTTON: Learn More WHY: Removes the biggest hidden cost of professional training and names real commutes so the reader pictures their drive. ────────────────────────────────────────── L03 · Local · Proximity Principle: Seasonal timing relevance PRIMARY TEXT Late August in the Lowcountry. The tourist crush is easing, school is starting back, and the calendar finally has a soft spot in it. That's the window. On August 18 and August 19, Grant and Bill are running Commander here on the coast — a single day where you build your own working AI assistant. Not a demo. Yours, running, before you leave. It handles the parts of the day that don't need you: sorting email, chasing follow-up, setting appointments, digging up research. One day now, before the fall pace picks back up. Choose August 18 or August 19. HEADLINE: The Quiet Week Before Fall DESCRIPTION: Build your own AI assistant in one day on the Charleston coast. BUTTON: Learn More WHY: Seasonal timing gives a non-manufactured reason to act now, sidestepping fake scarcity. ────────────────────────────────────────── L04 · Local · Proximity Principle: Small-market trust PRIMARY TEXT Charleston is a small market. The people in the room August 18 and 19 will be the ones you already pass in traffic. Agents. Contractors. Loan officers. Insurance folks. Small practices. People running something with too few hands. Commander is one day, in person, on the coast. Grant and Bill sit with you while you build an AI assistant that does your email triage, your follow-up, your scheduling, your research. You don't watch someone else build it. You build it. It's working when you walk out. Two dates. Same day of training. Pick one. HEADLINE: A Room of Charleston Owners DESCRIPTION: One-day, in-person AI build session on the Charleston coast. Non-technical welcome. BUTTON: Learn More WHY: Local rooms carry social proof a webinar can't; naming professions lets readers self-identify. ────────────────────────────────────────── L05 · Local · Proximity Principle: Local-relevance effect PRIMARY TEXT Here's what's happening on the coast on August 18 and August 19: a room full of Lowcountry business owners building AI assistants. Not studying them. Building them. Commander is one day, in person, run by Grant and Bill. You come in with the tasks that clog your week — the inbox, the follow-ups nobody got to, the scheduling back-and-forth, the research you keep pushing off. You leave with an assistant set up to take roughly two hours a day of that off your plate. No coding background required. Two dates, one day each. Read the details and claim your date. HEADLINE: Building, Not Studying DESCRIPTION: In-person AI assistant build day in the Charleston area. Two dates. BUTTON: Sign Up WHY: Build-versus-study is the clearest one-line articulation of the differentiator, landing before the scroll. ────────────────────────────────────────── L06 · Local · Direct Offer Principle: Processing fluency PRIMARY TEXT What: Commander, a one-day AI assistant training. When: August 18 or August 19, 2026. Pick one. Where: the Charleston coast area. In person. Who it's for: business owners and solo professionals. No technical background needed. What you leave with: your own working AI assistant, built by you, handling email triage, follow-up, scheduling, and research. Details and dates at the link. HEADLINE: Commander: One-Day AI Training DESCRIPTION: What, when, where, and what you walk out with. August 18 or 19. BUTTON: Learn More WHY: Format-driven fluency — every decision-relevant fact extractable in under six seconds. ────────────────────────────────────────── L07 · Local · Direct Offer Principle: Clarity beats cleverness PRIMARY TEXT One day. In person, Charleston area. You build your own AI assistant and take it home working. August 18 or August 19. Same training, two dates. Run by Grant and Bill. Built for people who aren't technical. The assistant handles email triage, follow-up, scheduling, content, and research — roughly two hours a day of work. That's the whole offer. Details at the link. HEADLINE: Build Your AI Assistant in a Day DESCRIPTION: In-person, Charleston area, August 18 or 19. Non-technical friendly. BUTTON: Learn More WHY: 'That's the whole offer' signals no upsell maze behind the click. ────────────────────────────────────────── L08 · Local · Direct Offer Principle: Cognitive ease PRIMARY TEXT Three things to know. It's one day. It's in person on the Charleston coast. You leave with something you built, not a stack of notes. Dates are August 18 and August 19, 2026. You attend one. The assistant you build takes on email triage, follow-up, scheduling, and research. Grant and Bill run it. Non-technical is the norm in the room. Pick a date at the link. HEADLINE: One Day. In Person. You Build It. DESCRIPTION: August 18 or 19 on the Charleston coast. Three things to know, then pick your date. BUTTON: Learn More WHY: Numbered promises up front trigger a completion instinct — they finish because they know how long it is. ────────────────────────────────────────── L09 · Local · Direct Offer Principle: Time-respect signaling PRIMARY TEXT Short version: a one-day, in-person class near Charleston where you build a working AI assistant for your business. August 18 or August 19, 2026. One day, not both. It takes over email triage, follow-up, scheduling, content, and research — around two hours a day. No coding required. Grant and Bill teach it. Link has the schedule. HEADLINE: The Short Version of Commander DESCRIPTION: One day near Charleston. Build a working AI assistant. Schedule at the link. BUTTON: Learn More WHY: An explicit promise of brevity that the ad then keeps, building trust before the click. ────────────────────────────────────────── L10 · Local · Direct Offer Principle: Concrete outcome PRIMARY TEXT You will not leave with notes. You will leave with an AI assistant you built, running, doing your work. Email triage. Follow-up. Scheduling. Content. Research. Roughly two hours a day of it. One day, in person, in the Charleston coast area. August 18 or August 19. No technical background needed. See the details and pick your date. HEADLINE: Leave With It Built, Not Explained DESCRIPTION: One-day in-person AI training near Charleston. You build it yourself. BUTTON: Sign Up WHY: Opens on the sharpest differentiator with no setup; the task list makes the promise picturable. ────────────────────────────────────────── X01 · Contrarian · Anti-Hype Principle: Reactance-aligned agreement PRIMARY TEXT Most AI advice is useless. Not wrong exactly. Just useless to a person with an actual job and an actual inbox. The threads, the newsletters, the 40-minute webinars that end in a pitch. You watch, you nod, you close the tab, and Monday looks exactly like it did. Commander is a one-day, in-person session in Charleston. You build one working AI assistant. Yours. It handles the repetitive parts of your day — email triage, follow-up, scheduling, drafting, research. You leave with the thing running, not with notes about the thing. August 18 or August 19. Details at the link. HEADLINE: One day. One working assistant. DESCRIPTION: A one-day, in-person build session in Charleston. August 18 or 19. BUTTON: Learn More WHY: Agrees with the reader's existing skepticism, lowering resistance before the offer appears. ────────────────────────────────────────── X02 · Contrarian · Anti-Hype Principle: Admitted downside PRIMARY TEXT This will not change your life. We should probably say that out loud before you read any further. It will change your mornings. That's the honest size of it. Commander is one day, in person, on the Charleston coast. You spend it building an AI assistant that handles the parts of your week you keep re-doing — sorting email, chasing follow-up, scheduling, first drafts, quick research. Roughly two hours a day back. Two hours is not a transformation. It's just two hours, every day, that used to belong to your inbox. August 18 or August 19. Details at the link. HEADLINE: Not life-changing. Morning-changing. DESCRIPTION: Build your own working AI assistant in one day. Charleston coast, August 18 or 19. BUTTON: Learn More WHY: Deliberately undersells against a category famous for overselling, making the modest claim credible. ────────────────────────────────────────── X03 · Contrarian · Anti-Hype Principle: Enemy is the hype PRIMARY TEXT The demos are the problem. Somebody types one clever sentence, the screen fills with magic, and the room claps. Then you go home and try it on your own messy work and it does not go like that. That gap is not you. Demos are built to look good in ninety seconds. Your business is not ninety seconds. Commander is a day of the unglamorous version. In person, Charleston, laptops open. You build one assistant that works on your actual email, your actual follow-up, your actual calendar. It will be less cinematic and considerably more useful. August 18 or August 19. Grant and Bill run it. HEADLINE: Less demo. More working thing. DESCRIPTION: One day in Charleston building an AI assistant on your real work. BUTTON: Learn More WHY: Names a shared frustration and absolves the reader of blame for it, building trust fast. ────────────────────────────────────────── X04 · Contrarian · Anti-Hype Principle: Refuting the prerequisite PRIMARY TEXT You do not need to learn prompting. It's a strange skill to build a career around. The tricks change every few months anyway, and the people selling prompt courses know that. What holds up is having a thing that runs. One assistant, set up around how you actually work, doing the same repetitive jobs every day without being re-explained. That's the whole point of Commander. One day, in person, on the Charleston coast. You build it, you test it on your own work, you take it home running. Email triage, follow-up, scheduling, drafting, research. No prior tech background needed. August 18 or August 19. HEADLINE: Skip the prompting courses. DESCRIPTION: Build one working AI assistant in a single day. No tech background needed. BUTTON: Learn More WHY: Removes the biggest perceived prerequisite keeping non-technical readers from acting. ────────────────────────────────────────── X05 · Contrarian · Anti-Hype Principle: Category exhaustion relief PRIMARY TEXT Nobody needs another newsletter about AI. There are enough. Some of them are even good. None of them have ever done your follow-up for you. The reading part of this is over. The doing part is a day of work with the software open and somebody sitting next to you when it gets stuck. Commander is that day. In person, Charleston coast. You build one AI assistant that handles email triage, follow-up, scheduling, content drafts, and research — the recurring stuff, not the interesting stuff. Run by Grant and Bill. August 18 or August 19. No pressure, no upsell theater. HEADLINE: Stop reading about it. Build it. DESCRIPTION: A one-day, in-person build session on the Charleston coast. BUTTON: Learn More WHY: Converts information fatigue into a reason to act — the end of consuming rather than more of it. ────────────────────────────────────────── X06 · Contrarian · Disqualification Principle: Honest reverse psychology PRIMARY TEXT Two kinds of people should skip this. First: anyone who wants to watch someone else do it. You'll have your laptop open the whole day. It's a working day, not a keynote. Second: anyone hoping to leave with a strategy document. There's no deck to take home. There's a thing that runs. Everybody else — Commander is one day, in person, on the Charleston coast. You build an AI assistant that takes over email triage, follow-up, scheduling, drafting, and research. Non-technical is fine. Most people here are. August 18 or August 19. HEADLINE: Two people should skip this day. DESCRIPTION: A working build day in Charleston. Laptops open, no keynote. BUTTON: Learn More WHY: Naming who should not come makes the invitation feel selective and honest rather than sold. ────────────────────────────────────────── X07 · Contrarian · Disqualification Principle: Scarcity of fit PRIMARY TEXT Skip this if you're already automating things on your own. You'd spend the day waiting on the rest of us, and we'd rather say that now than take your day. Commander is built for the other group. The people running a business or a book of clients who have watched AI happen from a distance for two years and never had a day to sit down and set one up properly. One day, in person, Charleston coast. You leave with a working assistant handling email triage, follow-up, scheduling, drafts, and research. Roughly two hours a day back. August 18 or August 19. Grant and Bill. HEADLINE: Not for the already-automated. DESCRIPTION: One day, in person, Charleston coast. Build your own working AI assistant. BUTTON: Learn More WHY: Turning away the advanced crowd signals the room will move at a pace the hesitant reader can survive. ────────────────────────────────────────── X08 · Contrarian · Disqualification Principle: Commitment escalation PRIMARY TEXT Don't come if you can only give us half the day. Commander doesn't work in pieces. You build one thing, start to finish, and the finish is the part that matters. Duck out at lunch and you've got a half-built assistant and a wasted morning. If you can give it the full day, here's what it is. In person, Charleston coast. You build an AI assistant around your own work — email triage, follow-up, scheduling, content, research. You leave with it running. No tech background required. No pressure to buy anything else. August 18 or August 19. Clear the calendar for one of them. HEADLINE: Full day or don't bother. DESCRIPTION: One uninterrupted day in Charleston building your own AI assistant. BUTTON: Learn More WHY: Asking for real commitment upfront raises perceived value and filters for people who will finish. ────────────────────────────────────────── X09 · Contrarian · Disqualification Principle: Seller says don't buy PRIMARY TEXT This isn't for everyone, and that's not a sales line. If your week is genuinely calm — inbox handled, follow-up going out on time, calendar under control — you don't need this. Keep your day. Commander is for the other kind of week. The one where the important work waits until seven at night because the small work ate everything before it. One day, in person, on the Charleston coast. You build an AI assistant that takes the small work. Email triage, follow-up, scheduling, first drafts, research. You leave with it working, not with a notebook. August 18 or August 19. HEADLINE: Only if your week is loud. DESCRIPTION: Build a working AI assistant in one day on the Charleston coast. BUTTON: Learn More WHY: Describes the problem state so precisely the right reader self-identifies without being told what they are. ────────────────────────────────────────── X10 · Contrarian · Disqualification Principle: Anti-pressure trust PRIMARY TEXT A short list of reasons not to sign up. You want to observe rather than build. You want a certificate. You want something that runs your business for you — this doesn't, it takes the repetitive parts off your plate and hands the rest back. Still here? Commander is one day, in person, Charleston coast. Grant and Bill walk a small group through building one AI assistant. Yours. Working. On your own email, follow-up, scheduling, and research. Nothing gets sold to you at the end. That's not how we run a room. August 18 or August 19. HEADLINE: Reasons not to sign up. DESCRIPTION: One day, in person, on the Charleston coast. You build it, you keep it. BUTTON: Learn More WHY: A negative headline stops the scroll and the no-upsell promise answers the reader's main fear.