Share your best AI workflow. We could show it to 2M+ people.

Start with the property, not a generic landscaping template. Upload photos, measurements, site constraints, current problems, future plans, budget limits, and the look you want. Then use AI to build a complete picture of how the property functions today and how it should evolve over time. Next, work area by area. For overcrowded garden beds, map every tree and shrub, then assess mature size, spacing, health, irrigation coverage, sightlines, and maintenance demands. From there, use AI to determine what should stay, what should move, what should be removed, and how each bed should be reshaped and edged. Convert each recommendation into an execution plan that includes: Step-by-step: 1. The target design 2. A step-by-step build sequence 3. Required materials and tools 4. Budget and priority level 5. Seasonal timing 6. A year-by-year maintenance plan Finally, connect every individual project into one master roadmap. Plan the garden beds, trees, lawn, irrigation, drainage, driveway, shelterbelts, recreation areas, and future buildings together so one improvement does not create a problem somewhere else. The result is a living property operating system. Add a new photo, issue, or idea, and the plan updates with the next best action.

My calendar is wall-to-wall meetings, so I built a Scheduled Claude Cowork task that automatically preps me for all of them (sort of like an AI Chief of Staff). Every morning, it scans my calendar, then pulls past emails, Slack, and my Granola notes for each call to build a context brief that takes 30 seconds to read before each meeting. It's simple and keeps me sharp for every meeting. Step-by-step: 1. I created a Scheduled Claude Cowork task that runs before my meeting day begins. 2. I had it scan my calendar and identify every meeting that needed preparation. 3. For each call, it pulled relevant past emails, Slack messages, and Granola notes. 4. I asked it to synthesize those sources into a short context brief with the information I would need in the room. 5. I read each brief in about 30 seconds immediately before the meeting.

I recently bought a house & had an inspection done as a closing condition. I uploaded the inspection report (80 pages) to Claude and asked it to make a list of home maintenance tasks by timeline (closing week, seasonally, etc.). Then, based on that list, I had it create one-off or annually recurring calendar events in my personal Google Calendar, with my husband invited to each event. It was super helpful because the inspection report clearly noted when the maintenance tasks were completed and suggested a frequency for the future. Step-by-step: 1. I uploaded the full 80-page home inspection report to Claude. 2. I asked it to extract every maintenance item and organize the work by closing week, season, and recurring frequency. 3. I had it use the report’s completion dates and recommended intervals to calculate when each task should happen next. 4. I reviewed the list for anything that needed to be corrected or combined. 5. I asked Claude to create one-off and annually recurring Google Calendar events and invite my husband to each one.

I wanted to reduce the time and mental effort it takes each morning to figure out what needs my attention across my inbox and calendar. I used Codex Automations to build Briefly, a daily AI-powered email and calendar brief that is automatically delivered to my inbox every day. Instead of manually searching through emails and checking separate calendar events, I can open one message from Briefly and immediately see what is happening, what needs action, and what is coming up. It has become a simple way for me to use AI proactively—not only when I ask a question, but as an automated system that helps me stay ahead of my emails, tasks, and schedule each day. Step-by-step: 1. I connected the email and calendar sources I wanted the automation to review. 2. I created a Codex Automation that runs each morning. 3. I instructed it to review recent and important emails, identify messages that need attention or follow-up, and check my calendar for upcoming meetings and commitments. 4. I had it turn that information into a concise daily brief. 5. I configured the brief to be delivered to my email automatically.

Training for a triathlon means three sports and a plan that is fiction by Wednesday. A static plan does not know I slept badly, skipped Tuesday's swim, or that Saturday's long ride wrecked me. Adjusting for that is what you actually pay a coach for. I wanted the adjusting without the retainer. So I built it in ChatGPT Work: a Project holding my plan, plus a scheduled agent run each morning that checks the plan against what my body actually did, then fixes the week. Disclosure: I built freddy, the connector feeding ChatGPT my training and recovery data, so I am not neutral here. Step-by-step: 1. Connect your sources at freddy.coach. For triathlon it is whatever records your swims, rides and runs: Garmin Connect, Polar, Suunto, WHOOP or intervals.icu. I use Oura for sleep and recovery, Garmin Connect for sessions, Hevy for strength. History backfills automatically, so the plan is built on your real training rather than what you tell it you did, which is usually flattering. 2. Add freddy as a custom connector: Settings, then Connectors or Apps and Connectors, then Add new, then custom MCP server. The URL is https://freddy.coach/mcp. Sign in and approve read access. Do it on the web; the mobile app cannot add custom connectors. 3. Connect Google Calendar and turn on write actions. This is the step people miss: write actions are off by default, so until they are enabled through action controls the agent can read your week but not change it. With writes on, ChatGPT Work creates and edits events. 4. Create a Project and put the durable facts in the project instructions: race date and distance, realistic weekly hours, immovable days, injury history, weakest discipline, and how blunt you want it. Long-lived facts only, never this week's session. 5. In the project, with freddy on, ask it to build the block: a periodised plan to race day, justified against your actual last 8 weeks rather than a textbook ramp. Keep the plan as a file in the project so every run starts from the same document, and have it write the week's sessions to the calendar with type, duration and intensity in the event body. 6. Schedule the daily run for mid morning, after you are up and your sources have synced. Last night's sleep does not exist anywhere until the watch or ring syncs, so a 5am run reports on the night before last. The standing prompt: "Using freddy, check whether I completed yesterday's planned session: pull yesterday's workouts with type, duration and intensity and compare against what the plan called for. Then pull last night's sleep and this morning's recovery including HRV and resting heart rate, plus training load over the last 7 days, compared against my own 30 day baseline rather than population norms. Then look at today's planned session on my calendar and decide whether it still makes sense. If it does, confirm in one line. If not, change the calendar event to the session I should actually do, put the reason in the event body, and update the plan file. Tell me what you changed and why, naming which source each conclusion came from. If two sources disagree, say so rather than averaging. Never compare HRV across different sources. If anything is ambiguous, such as an unrecorded session or a workout matching no planned one, ask me instead of guessing. Under 250 words." 7. Let it run a week before trusting it, and read what it changed rather than skimming. Expect to tune the instructions early: the usual failure is turning cautious after one poor night, fixed by a line saying a bad night is noise and to downgrade only on a trend or after a hard day. Two things to know. Depending on your approval settings, a run either makes the change or holds it for a tap. Know which you chose: it is the difference between waking to a changed calendar and a proposed one. And agent runs are metered, so keep the daily check narrow and save long reasoning for a weekly review. What surprised me is how good it is at catching the sessions I quietly did not do. It is easy to tell yourself you are on plan, harder when something reads yesterday's file and notes the intervals were short. Gotchas. Make it commit to one call on today's session; "listen to your body" is what you already had. Make it name the source behind each conclusion so you can tell a real finding from a confident guess. Never let it compare HRV across sources, because RMSSD and SDNN are different measurements, not different units, so mixing them looks meaningful while being nonsense. Scheduled runs auto-pause if ignored, so if the check stops arriving, look there before blaming the connector. It is not a certified coach and I would not rehab an injury with it. It is very good at holding a plan, watching what happened, and closing the gap before it becomes a lost week. Cost: freddy is free for one source, but this is cross source so it is the paid plan, $49 a year, on top of ChatGPT. Individual triathlon coaching runs a few hundred a month.

I quickly capture my thoughts in Apple Notes, which serves as my mobile inbox. A scheduled Claude Cowork skill reads those notes through the desktop connector on my MacBook and processes them into my calendar and Obsidian. I organize notes using either the “Forever Notes” method (https://www.myforevernotes.com/docs/journal) or a simple YYYYMMDD daily-note format. Time-log notes record a start time, end time, and description, then save that information to the calendar app. The calendar holds the raw data, which I can extract into a separate Excel sheet if necessary. Planned schedules are checked against existing calendar entries. If an entry is already present, it is highlighted; if it is missing, it is added. This saves me the time and effort of opening a link or editing multiple fields in the calendar app. Random thoughts are filed into my second brain in Obsidian. They are processed with templates, moved to specific folders, or intentionally tagged. Apple Notes, Obsidian, Apple Calendar, and Google Apps are free. The only subscription I need is a Claude account to use Claude Cowork. Step-by-step: 1. I capture thoughts and other information in Apple Notes on my mobile device. 2. A scheduled Claude Cowork skill reads the notes through the desktop connector on my MacBook. 3. I organize the notes using the “Forever Notes” method or a YYYYMMDD daily-note format. 4. I process time-log notes containing a start time, end time, and description, then save them to the calendar app. 5. I check planned schedules against existing calendar entries, highlighting entries that are already present and adding those that are missing. 6. I extract the calendar’s raw data into a separate Excel sheet if necessary. 7. I process random thoughts in Obsidian with templates, move them to specific folders, or intentionally tag them.

I love golf, but many of the courses I most want to play are private and nearly impossible to access unless you know a member. Instead of manually emailing clubs, searching charity events, asking for introductions, and trying to remember who I contacted months ago, I built a Private Golf Access Agent in ChatGPT. The goal is to identify legitimate opportunities to play highly rated private clubs without simply paying my way in. I gave the agent 50 target clubs across the Northeast and Mid-Atlantic, including 10 “moonshot” courses where an invitation would be extremely difficult. The agent acts more like a golf-access researcher, relationship manager, and outreach assistant than a chatbot. It researches each club, identifies access paths, finds the right person, personalizes outreach, tracks every interaction, monitors opportunities, and recommends what to do next. I still approve every email before anything is sent. That matters because I don’t want the agent spamming clubs, inventing relationships, or continuing after someone says no. The system looks for legitimate paths, including professional introductions, complimentary charity or special-event opportunities, reciprocal access, personalized direct outreach, unused guest spots, golf-project requests, and long-term relationship opportunities. Step-by-step: 1. I divided the 50 clubs into moonshots, elite targets, and high-quality targets. 2. I had the agent research each club independently, including its leadership, PGA professionals, policies, events, social media, recent news, reviews, charitable connections, and possible introductions. 3. The agent identified the most appropriate contact and researched why that person made sense. 4. Before writing, it gathered specific details so each email was clearly personalized rather than a blast. 5. I trained its cold-outreach persona to sound like a blend of me and two or three sales trainers I admire, including Josh Braun-style low-pressure curiosity, short conversational writing, humor, and an easy way to say no. 6. The agent can learn new skills and add them to its protocol. For example, when it struggled to find employee email addresses, I taught it my Google search method. That method is now part of the workflow it uses for future clubs. 7. I tracked everything in a live Google Sheet showing the current status, progress, next action, opportunity status, and whether I need to approve something. The current status column is highlighted so I can check where every club stands in real time. The statuses include: Researching → Ready for AJ Review → Outreach Sent → Conversation Open → Opportunity Identified → Monitoring. 8. If there is no immediate path, the agent does not keep bothering the club. It moves the club into monitoring mode and waits for a better opportunity. 9. When someone responds, the system keeps the relationship history so future communication builds on the real conversation. The live tracker is shown in a Google Sheet status screenshot. What I like most is that the AI isn’t doing one isolated task. It handles the repetitive parts of an ongoing objective—research, qualification, contact discovery, personalization, organization, monitoring, and follow-up—while leaving the important judgment calls with me. Eventually, I want it operating like a 24/7 private-golf-access concierge: 50 clubs being researched and monitored, with me only getting involved when the agent finds something worth acting on. TOOLS USED: ChatGPT, Gmail, Google Sheets, Google Drive/Docs, web research, and AI agents/automations.

I have Claude connected to all my communication platforms (Slack, Notion, calendars, Granola, etc) and pulls a morning brief for me each day. I've curated so it provides me an interactive page each day with call prep, priority tasks, recommendations of tools to use to solve XYZ, recap of activities overnight, etc. Step-by-step: 1. I connected Claude to the communication platforms I use, including Slack, Notion, calendars, and Granola. 2. I defined the sections I wanted every morning: call prep, priority tasks, overnight activity, and recommended tools. 3. I had Claude gather the relevant updates from each connected source. 4. I asked it to turn the result into an interactive page instead of a long unstructured message. 5. I refined the brief over time so it consistently surfaced the information I actually use.

It starts when someone clicks “Find My Best AI Opportunity” on my website. Instead of going straight to a booking page, they enter a short AI chat. The assistant asks about their work, business, main pain point, AI experience, urgency, name, and email. The workflow runs in n8n. Once the chat has enough information, it creates an AI Readiness Summary, saves the lead in Notion, sends me an internal brief, and emails the visitor their summary with a link to book a 30-minute call through Cal.com. The result is a better-qualified call: the visitor gets useful value first, and I have the context I need before we meet. Step-by-step: 1. A visitor clicks “Find My Best AI Opportunity” on my website. 2. The visitor completes a short AI chat about their work, business, main pain point, AI experience, urgency, name, and email. 3. n8n uses the collected information to create an AI Readiness Summary. 4. The workflow saves the lead in Notion and sends me an internal brief. 5. The visitor receives their summary by email, along with a link to book a 30-minute call through Cal.com. 6. I review the context before the call, making it better qualified.

I kept struggling to stay consistent with social media for my own projects. Writing captions, choosing hashtags, designing graphics, and scheduling content across platforms was taking hours every week—time I would rather spend building. So I built AutoKonnekt. You give it one sentence or a website URL, and it generates a full month of on-brand social posts, including captions, hashtags, and AI-generated images. It then schedules them across Instagram, Facebook, LinkedIn, TikTok, Pinterest, X, and Threads. The hardest part was getting the AI to sound like a specific brand’s voice instead of producing generic marketing copy. That took a lot of iteration on the prompting side. It’s live now with a free plan if anyone wants to try it: https://autokonnekt.com I’d love to hear what the community thinks. For those of you managing social media manually, which part takes the most time? I’m trying to figure out what to build next. Step-by-step: 1. I enter one sentence describing the project or provide a website URL. 2. AutoKonnekt generates a month of on-brand social posts with captions, hashtags, and AI-generated images. 3. I use the generated content across Instagram, Facebook, LinkedIn, TikTok, Pinterest, X, and Threads. 4. AutoKonnekt schedules the posts across those platforms. 5. I iterate on the prompting to make the content sound like the specific brand instead of generic marketing copy.