Sponsored
$5/week ↗

More projects built with Dots

Continue exploring projects, experiments, and ideas from the Dots community.

His Dot caught an onboarding bug and drafted the fix PR unprompted

His Dot caught an onboarding bug and drafted the fix PR unprompted

My full app launch checklist 👇 1. Set up analytics. I use PostHog to track signups, onboarding, and the main thing people came to do. Test those events so you can see where people get stuck and whether they come back. 2. Set up crash reporting. I use Sentry to see what went wrong. Send a test error before launch so you know reports are coming through. 3. Build your welcome email sequence. I use Loops. Help people take their first step, then follow up with something useful. Test the signup trigger, timing, and links. 4. Give people a place to leave feedback. Make the board easy to find inside the app so people can report bugs, ask for features, and vote on requests. Setting all this up is important, but I think proactively watching it is the most important part, especially during the first 2–3 weeks. That’s when crashes, drop-off, and feedback help shape product decisions. What should you fix first? What’s confusing people? What do they want you to build? I used to have to watch all of this so closely myself. Now I’m giving that responsibility to dots, OpenAI’s remarkably capable, always-on agents powered by GPT-6 Astra. I’m sharing my launch date, checklist, and what a successful signup looks like, with access to the tools it needs. It can work with Codex and keep making progress between conversations. Here’s what I’d ask: “Watch my analytics, crash reports, welcome emails, and feedback board for the first three weeks after launch. Check daily, flag urgent issues, and bring me a weekly summary of what to fix or improve, with the evidence behind each suggestion. If the launch date or priorities change, update the plan. Ask me before changing code or sending emails.” You choose what it can access, review its findings, and can redirect or stop the work. I’ll leave a link to dots in my bio so you can try this for your next launch. @ChatGPT #chatgpt_partner
My Dot took care of demo week

My Dot took care of demo week

I worked on the dots live demo. Holly did a phenomenal job on stage today. If you've ever been there, you know the pressure is immense. She handled the recovery SO well. I flew to SF from Singapore for my 4th DevDay (and first an OAI employee). It's been a joy to get a small glimpse of what the dots team has been cooking. Truth be told, I was slightly skeptical of using dots when it was first introduced. I was already really comfortable using Codex and setting up plenty of automations. I wasn't sure how much more I'd get out of it. But a few personal examples that I can share publicly changed my mind. 1. En route to SF last week, my rideshare cancelled on me. There was the generic automated refund email. My dot immediately picked it up, knew I had a flight, and asked if I was okay. 2. During this trip, after days of DevDay prep, I woke up and told it, "Fuck my life, I'm so tired - what's on my cal today." It walked me through my day, then added one last thing: "Please take some time to eat and drink. Take one step at a time - you got it". Alone in a hotel room, that felt really reassuring. 3. On the building side, I've been using dot to spawn Codex threads that use CUA and ultrafast, and to proactively scan PRs for changes that might affect the demo. It's been useful for getting work done, and increasingly insightful and high-signal in ways I hadn't expected. I could delegate more confidently without repeating the same context for the umpteenth time. 4. Even this post came together with my dot, as I spoke to it throughout the day to investigate what happened and emotionally process it. Hope you give it a shot and see what I mean :)
Fusion Events' Dot audited his backlinks and found a broken one

Fusion Events' Dot audited his backlinks and found a broken one

A pleasant conversation isn't my benchmark for an AI assistant. Can it do something useful with the work I've already got going? In this demo, I called my Dot and gave it a real task: audit the backlinks to Fusion Events, identify worthwhile sites to approach, and work out how we'd approach them. The useful bit was wonderfully unglamorous. A broken backlink. An audit I could review. A correction email drafted with my signature and left unsent for me to approve. Nobody needs another robot confidently announcing that it has revolutionized their business. Fixing a broken link will do nicely, thanks. What interests me here is the context. I've already spent time working through projects in ChatGPT. Being able to pick up that work by phone matters more to me than starting another assistant from zero and explaining my business all over again. Thats how Im judging these tools: give them a specific job, inspect what comes back, and keep control of anything that goes out in my name. Want to try the same task? Give your assistant your exact website address and ask it to verify existing backlinks, separate confirmed findings from gaps in the data, and draft one specific correction request. Check the source page yourself before sending anything. If it cant show you the evidence, it isnt a verified finding. Start with a loose end in your business. See whether the assistant can actually help you close it. #dot #openai #coding #ai #aitips