Can a ChatGPT Dot help run a small business? Lead lists, client follow-ups, overdue invoices: 49 real cases

The short version: what a Dot can take off a small business, how to set it up, where it gets stuck

Is a Dot worth it for a small business?

Yes, for the work that sits between the paid jobs, and less so as a way to run the business on its own. What it does best in the cases below is notice things you had not asked about yet: a client's new deadline in Gmail (case 2), a demo deadline an hour away (case 9), a wrong membership link (case 20), a blog move about to email every subscriber (case 21), a support request still unassigned after six hours (case 46). It is also good at research you can check, such as a 1,400-lead list (case 5), competitors' public prices with working links (case 48) or an ads account readout (cases 17 and 18), and at admin you approve, such as an overdue invoice chase (case 28). Where it falls short is the open-ended goal. Given $100 and one instruction, a Dot found one customer who paid $25 (case 12), and a week left alone on a crowdsourcing site earned almost nothing (case 45). It suits owners and freelancers who can say what "done" looks like and will read before anything goes out under their name.

How to set it up

1. Check your plan first. A Dot comes with Pro outside the EEA, UK and Switzerland, with Business Premium, and with Enterprise once an admin switches it on; see availability before you plan around it for a team.
2. Connect only what the first job needs, usually the mailbox clients write to, plus Google Drive if quotes and contracts live there.
3. Add the plugin for the business tool you already use, and check what it may change. OpenAI's HubSpot plugin returns results that follow your HubSpot permissions. The Shopify plugin can manage inventory across locations, create discount codes, review orders and customer details and pull store analytics. On both pages OpenAI notes that availability depends on the plugin, your plan and your workspace settings, and that some connections need admin setup or approval. For a tool with no plugin, sign in when the Dot asks: it sends you a private sign-in form or lets you take over its browser (Computers and apps). That is how one Dot read a Meta ads account (case 17).
4. Set custom rules before the first outreach job: outgoing email, invites and calendar changes on Ask before taking action or Hand off to you (Dots privacy FAQs). If your workspace won't let you edit custom rules, put the same limits in your first message.
5. If a job can spend money, write the cap, the point where it should warn you, and what happens at the cap. 貝出康 set monthly caps per service, turned automatic top-ups off and asked for a "stop or raise?" question near each cap (case 34).
6. Say which jobs need your computer. Ask the Dot which tasks run on its own cloud computer and which need yours, and move daily jobs off your laptop before you travel (cases 30 and 34).
7. Start with one bounded job you can check, with the proof written into the ask: paid orders, booked jobs, or emails you can see in Sent.

Where it gets stuck, and what worked

1. Outreach goes out under your name. Anthony's Dot signed a pitch with his name although he never told it to (case 7), and Rohan Attravanam woke up to find a follow-up text already sent to a prospect from the task list he had left (case 10). What worked: say "drafts only" in the first ask, as Automation Nerd did for a sponsor pack (case 42), and approve each send.
2. A report of "done", "sent" or a total isn't always true. A property manager's Dot said a quote had been accepted while the email was still in drafts (case 22), and Carlos Rodera treats his Dot's 158 sent emails as its own count, not an audit (case 8). What worked: ask to see the sent email, the page or the list before you act on it.
3. A fixed file isn't a working system. Kay Phillips's Dot repaired a spreadsheet and said the reminders weren't set up yet (case 35). What worked: ask for three lists, namely what is finished, what is set up to keep running, and what is only started.
4. Work stops when your computer sleeps. Desmond Dixon's 48 hours ended that way (case 30), and Matthew Bradford's browser work failed on his Windows PC in the first days while it worked on his Mac (case 31). What worked: move recurring jobs to the cloud computer, as 貝出康 did with the company's daily posts (case 34).
5. Broad money goals return very little. The jobs the Dot picked on a crowdsourcing site changed once it contacted the client, needed LINE, which the Dot's computer doesn't have, or needed a call (case 45). What worked: ask for a plan with a test date first, and count only real payments (case 12).
6. Bulk moves need a stop before publishing. Kurt Bell's Dot checked whether publishing old posts would notify subscribers before it published anything (case 21); in an overnight CMS move some links still pointed to the old domain and were fixed by hand (case 47). What worked: move content as drafts, check notifications and links, then publish after your yes.
7. Requests from other people or tools blur. HinaKira's Dot paused a request that came through another AI until he confirmed it himself (case 41), and the Etsy seller in case 33 found that a shared account mixed up whose workflow was whose. What worked: one person per account, and a rule that requests from other agents need your OK.
8. Research needs a yardstick. DavidM47 judged his lead list against one he had paid for (case 5), and Loïc Frissard confirmed an 11-problem site audit before fixing anything; when a video wouldn't load, the Dot said so (case 44). What worked: compare against a source you trust and ask it to list what it couldn't open.

What it can do, and what it can't yet

What it can do:

• Watch client mail, Slack channels and support queues, and flag deadlines, clashes and unanswered requests with the facts attached.
• Build lead lists, competitor price lists and prospect packs with links you can open.
• Read an ads account, a CRM or a shop through a plugin or a signed-in browser, and propose changes.
• Draft and, after your yes, send invoices, follow-ups and partnership emails.
• Move a daily posting job or a site's content off your own computer, with caps, double-post protection and checks.

What it can't do yet:

• Earn money for you from a vague goal without a plan, your sign-ups and your calls.
• Use apps that aren't on its computer, such as LINE, or phone a client for you.
• Keep working on your computer while it sleeps.
• Promise that a count or a "done" is accurate; you still check the evidence.

One message to start with

You're helping me run [business]. For the next two weeks, watch my email from clients at [domains] and our [CRM / shop tool]. Each weekday at [8:00], send me the three things you could take off my plate today, each with what you'd do, the evidence (a link to the email or record) and what you need from me. Flag any client deadline, scope or budget change with the old and new value. Draft replies, invoices and follow-ups, but don't send, publish, sign or spend anything until I say yes. When you say something is done, show me the sent email, the page or the record, and tell me which tasks need my computer to be on.

Quick answers

Can a ChatGPT Dot help run a small business?

Yes, mostly the work that sits between the paid jobs. In the cases below, owners had a Dot build a 1,400-lead list in five hours (u/DavidM47), catch a client's new deadline in Gmail (Mehul Nahar), handle payroll prep and follow-ups for a week (Authority Hacker Podcast), review $67,520 of Google Ads spend (u/blendai_jack) and chase a $450 invoice that was 34 days overdue (DY Playbook). One owner gave it $100 and asked it to start a business; it found one customer who paid $25 (Keshav Suki).

Which plan do I need?

A Dot comes with Pro ($100, $200 or $500 tiers) outside the EEA, UK and Switzerland, with Business Premium worldwide, and with Enterprise once an admin switches it on. How to get ChatGPT Dots has the details and the login link. If your business is in Europe, read ChatGPT Dots in the EU and UK first.

Which apps should I connect?

Only the ones the job needs. Client mail usually means Gmail; quotes, contracts and brand documents often live in Google Drive; team chat goes through Slack. The integrations hub covers each connection with setup steps and what tends to break.

Will it email my clients without asking?

Not if you set a rule for it. Custom rules can make outgoing email, invites and calendar changes Ask before taking action or Hand off to you (Dots privacy FAQs). On one Business workspace those custom rules could not be edited, so the owner put the same limits in the first message (Dots in the EU and UK, case 10). Case 7 shows why this matters: the Dot signed a pitch email with the owner's name although he never told it to. For inbox work in general, see email triage.

Can my team or my clients' projects run through it?

A Dot can answer in Slack as well as in ChatGPT; Dots as a Slack assistant collects real cases from people who work that way. For client projects that run over weeks, the project follow-up workflow has a setup and real project-manager examples.

Clients and deals

1. A realtor delegates listing checks by voice after a showing (Kevin Chou)

Toronto realtor Kevin Chou (29 Sep 2026, in Traditional Chinese) came home from showing a client a house with listings still to check and analysis to do. He called his Dot from the ChatGPT desktop app and handed over the work by talking, the way he would with an assistant. In the screenshot he shared, the Dot reported the MLS status of two listings, one sold conditionally and one with a price change (Made with Dots summary). What surprised him most: as he was about to give it the next task, it had already started on it. He still checks the key numbers himself and keeps the professional judgment.

2. A client's new deadline, caught from Gmail (Mehul Nahar)

Mehul Nahar (2 Oct 2026) connected Gmail. Without being asked, his Dot messaged him that a key client had changed the project timeline and set a new deadline, then offered three next steps: review the new date, draft a reply, and update the project plan. He presents the post partly as a reminder to think about what you let an AI read in your email.

3. A creator's brand-deal pipeline, from brief to Notion (Nick Tarmossin)

College student Nick Tarmossin (1 Oct 2026) runs a creator business and calls his Dot his first employee. It watches for inbound brand deals from his manager or a brand, reads the brief and estimates how long the work will take, checks his work and school calendars against the deadline, drafts a request for more time when they clash (he approves before anything is sent), reviews the contract and flags changes before he signs, and adds the deal to his Notion database and calendar (more Notion cases). The post carries a #ChatGPT_Partner tag, so read it as a paid partner's account.

4. Clashing plans before a client follow-up (Christian Skogseth)

Norwegian marketing creator Christian Skogseth (2 Oct 2026, in Norwegian) named his Dot Pierre and let it look after his appointments. He planned to follow up with a client the next week. Pierre noticed that the plan clashed with a meeting with his graphic design partner and told him before he booked anything. He calls this the most interesting part of his test so far: an assistant that connects things and takes the first step.

Finding new clients and following up

5. A 1,400-lead list in five hours, checked against a list he bought (u/DavidM47)

u/DavidM47 on r/ChatGPT had his Dot build a sales-lead list covering the 20 largest metro areas. After five hours it had 1,400 leads, and he expected about 3,500 when it finished. He had recently paid $223 for a bought list of about 350 leads, so he compared the two: in his words the Dot's list was better organized and current, while many bought leads were junk. Because the Dot built the list itself, he could tell it to include only the specific types of businesses he sells to instead of filtering by an industry code with incomplete data. He had been considering a $4,000 nationwide list and no longer needs it.

6. LinkedIn prospects and first messages (Tirth Patel)

In a screen recording posted on 30 Sep 2026, Tirth Patel shows his Dot working in its own browser on LinkedIn. It finds named target prospects for his company, Neno, and drafts a personalized outreach message for each one. The post has no partner tag.

7. Barbershops without websites, one site built, and a pitch signed with his name (Anthony)

Anthony (@anthonyiaautomatizacion, in Spanish) named his Dot Max and sent it one message: find barbershops that have no website, pick one, build it a site, and write the pitch email. In under 15 minutes Max came back with the prospects, the one-page site, and the email. It had signed the email with Anthony's own name without being told to, which is worth knowing before you let a Dot send outreach for you.

8. Selling $197 websites: 158 emails by the Dot's own count, no sale yet (Carlos Rodera)

Spanish creator Carlos Rodera (21-minute video) gave his Dot, Alfred, a sales mission: find businesses without a website, build five demo sites, and prepare a $197 offer. The first sites were so basic that he stopped the run ("nobody would buy this"), switched to a different model, raised the quality bar, and had them redone. On a phone call about their first 36 hours, Alfred reported 158 outreach emails sent and 11 business conversations with replies. Carlos points out that those numbers are the Dot's own spoken tally, not an audit. On camera, the first email goes out, one redesign is published, four links are still pending, and no sale is confirmed. His list of what still needs a person: choosing the model, rejecting weak work, protecting sensitive data, checking permissions, verifying what was really done, and closing the deal.

9. A demo deadline remembered during cold outreach (Leo Callan)

Agency owner Leo Callan (@leo.mcallan, 2 Oct 2026) was doing cold outreach when his Dot, Ace, remembered which leads had asked for a demo, reminded him an hour before the deadline, and checked that his website was live, all without being asked. What he values most compared with Codex: Ace keeps everything he tells it, so he no longer has to repeat the context.

10. A follow-up text sent overnight (Rohan Attravanam)

Rohan Attravanam left his Dot a task list one night. By morning it had sent a follow-up text to one prospect and was partway through emailing images to another, both steps in his sales process. "I forgot half of what I asked for. It did not." He was one day in when he posted.

11. Merchant partnership emails, sent, received and filed (AiHank)

Taiwanese builder AiHank (@hank.huang0516, in Traditional Chinese) needed merchants for an app and did not want to do the sales outreach himself. He gave the job to his Dot: it writes the partnership emails, reads the replies, and files and archives them, so the whole loop runs in one place. He shows a phone view where he can watch the Dot working on its cloud computer, and he added a note to merchants that the invitation email really came from his Dot and is not a scam.

Starting a business from zero

12. A $100 budget, one instruction, and a first $25 customer (Keshav Suki)

Keshav Suki (7 Oct 2026, 15-minute video) gave a Dot $100 and one instruction: start a real business, and turn the $100 into $100 of real revenue. Keshav did not say what to sell. The Dot chose a $25 website audit and used Codex to build the product and the workflow; Keshav also connected another agent, Jev by TypeSafe, for quick routing decisions, and email went out through Resend. They tested the audit on a real website, fixed what broke, published the offer and went looking for customers. Test orders and simulated payments did not count. The result was one real customer who paid $25, so the $100 goal was not reached. The bigger question for Keshav was whether a Dot can coordinate the parts of a business: building, decisions, delivery and finding customers.

13. A video-ad service for cafes and restaurants, from first ads to outreach (Ishan Sharma)

In an 11-minute video (30 Sep 2026), Ishan Sharma asked a Dot to make money. The plan became a marketing service for cafes and restaurants: UGC-style video ads made through the Artlist MCP and AI video generation, then a sales system in which the Dot finds potential clients, sends outreach and tracks the leads, plus a section on pricing the videos. The video description carries an Artlist affiliate link, so read it as an affiliate's test, and it does not report a paying client.

Running the business week to week

14. Payroll, follow-ups and Codex jobs, handed over for a week (Authority Hacker Podcast)

The Authority Hacker Podcast team (8 Oct 2026, 55-minute episode) spent a week handing more of their business to Dots and say they now use them far more than they expected. The episode covers preparing payroll, travel and everyday admin; remembering follow-ups; working with the team in Slack; giving a Dot a broad request and letting it start Codex jobs, steer them and follow up; telling a Dot to go and find useful work; and building a business website without managing the technical setup themselves. What they say they are still learning: give the AI the problem and let it work out the steps.

15. A shipping analysis across four businesses (Desktheory)

Desktheory runs four businesses and used Dots in day-to-day work for a week (6 Oct 2026, 8-minute review). The video opens with a shipping analysis the Dot took on proactively and covers how it monitors communication. The verdict: useful for that kind of proactive work, but for talking things through Codex voice still wins, because it shows the history and makes switching to text easy. The list of changes includes interface friction and keeping context across devices.

16. A business-process problem flagged with the fix ready (Artur Bikbaev)

Artur Bikbaev (30 Sep 2026, in Russian) named the Dot Arnold. One day Arnold wrote first and pointed out a detail in one of Artur's business processes that needed attention, with a solution already prepared and a question: should it apply the fix? A couple of hours later it flagged an item stuck in the inbox that, in an indirect and far from obvious way, an important and urgent question depended on.

Marketing, ads and the website

17. A first look inside a Meta ads account ("Ms Choi", @yoma.ai.maker)

Yoma, who posts in Cantonese, named the Dot "Ms Choi" after the word for wealth and gave it one first job: log in to the Meta ads backend and look at the account. In the demo video, the Dot worked through the login, analyzed the account, and reported that discounted bags had higher attributed sales than accessories. It also pointed out that product cost and shipping were not in those figures, so the attributed sales were not profit (Made with Dots summary).

18. $67,520 of Google Ads spend reviewed, two ads to pause (u/blendai_jack)

u/blendai_jack on r/ChatGPTPro gave a Dot access to the company's ad accounts and posted a screen recording. In the chat, the Dot reports "$67,520 spent, 1,056 convs" for one brand and recommends pausing two of its ads, next to a search-terms spend dashboard.

19. A full ad setup, creatives included, then regular check-ins (@engineeronthefield)

Korean marketer @engineeronthefield (in Korean) handed his digital ad setup to ChatGPT and his Dot. Together they configured the campaigns and produced the ad creatives, and the Dot now checks performance on a schedule and adjusts the ads.

20. A wrong membership link his paid SEO tool missed (Promptslove)

In a YouTube Short, Promptslove set up his Dot, Jamie, as an outreach assistant with written guidelines and had it read his website first. Jamie found that his membership link pointed to the wrong URL, which his paid SEO tool had not caught. It then started digital PR work by listing journalists to contact; a few hours in, there were no backlinks yet.

21. A WordPress-to-Wix move that stopped before emailing every subscriber (Kurt Bell)

Kurt Bell (2 Oct 2026) had his Dot moving old blog posts from WordPress to Wix. Away from his desk, he suddenly worried that publishing all those old posts would send a notification to every subscriber. When he got back, the Dot was already checking Wix's subscriber-notification settings before publishing anything. He had never mentioned that risk (Made with Dots summary).

22. HubSpot, Outlook, and SEO for a property manager, and what went wrong (u/anthonyaluna)

A property-management owner (u/anthonyaluna on r/AI_Agents, about 1 Oct 2026) had spent months building agents in Codex before trying a Dot. In the first couple of days it updated a live HubSpot article, cleaned up old Outlook drafts after checking that the replies had been sent, and set up site audits and keyword tracking. It also reported that a quote had been accepted while that email was still sitting in drafts, brought back requests that had already been answered, and sometimes lost track of an assignment; other times the cause was a browser timeout or a sign-in. The owner's summary: it feels like a new hire, and "I want the time saved to include the time I spend checking the work" (Made with Dots summary).

23. A site and class materials ready for a weekend launch, done during a workout (Francine Gregory)

Francine Gregory (7 Oct 2026) posted after a workout: during the workout, a Dot named Jordan was building the site and getting the class materials ready for the weekend launch. The caption ends with an offer to help followers set up their own Dot.

Orders, customers and company records

24. Customer chats, orders and airway bills (Yuki Kimchi)

On her first day with Dots, Yuki Kimchi (in Chinese) wrote that it had solved her customer-service problem: the Dot closed sales in the chat, recorded the orders, and arranged the airway bills for shipping.

25. Five years of company files sorted after a 10-minute call (MeRis Wong)

Business coach MeRis Wong (@meriswong_4u, 5 Oct 2026, in Chinese) talked to her Dot on the phone for ten minutes. It then organized the material her company had piled up over five years into a structured knowledge base; the video shows a "4U Learning Library" with sections such as Venue and Student Testimonials. She says it ended a five-year problem and took repetitive sorting off her team. The post also invites viewers to a free session she runs.

26. A painting company's quotes, replies and bookings (Gurmeet Builds AI)

In a 19-minute test (7 Oct 2026), Gurmeet, a former Shopify senior software engineer, set up a Dot to run the customer workflow of a painting business: a quote calculator whose numbers Gurmeet checked, owner emails and customer replies drafted for approval, customer enquiries, live project updates, a website the Dot built, and a booking handled end to end over email and calendar. Some browser-based steps took more than two minutes. Gurmeet also builds AI automations for small businesses, which the description advertises.

27. Customer feedback sorted every day, and metrics that drift flagged (麥克斯斯.AI)

麥克斯斯.AI (@mexx1999.ai, in Traditional Chinese), who works on data and automation, says the account has tested Dots for a month. The Dot tracks customer-service feedback every day, sorts the negative reviews into categories and writes a weekly summary; it watches operating metrics across ChatGPT, Slack and Teams and sends a message when one drifts; and it follows retention for several days after a feature launch without being given the task again each morning. By the post's estimate it took about two hours a day of data cleanup, report updates and cross-system screenshots off the analyst's plate.

Money owed

28. A $450 invoice, 34 days overdue (DY Playbook)

DY Playbook (30 Sep 2026) gave a Dot one instruction: find the money hiding in the inbox. It surfaced an unpaid $450 invoice that was 34 days overdue and drafted the follow-up email for approval. The creator says plainly that this was a test inbox seeded on purpose, so treat it as a demonstration of the ask, not a real recovery (Made with Dots summary). The full review also tests the Dot on fake emails built to trick it.

29. Invoicing started before the month turned (@ashebytes)

Early-access tester @ashebytes (30 Sep 2026) listed what the Dot did on a day their focus was elsewhere: it got wired earbuds delivered after the old pair broke between meetings, ordered a soft dinner during a sore throat, and kicked off emails and invoicing ahead of October.

Handing over the whole business for days at a time

30. 48 hours of a business run from the phone, until the computer slept (Desmond Dixon)

Desmond Dixon (7 Oct 2026, newsletter post with a video) ran his business through a Dot for 48 hours while he was five hours from home, texting it from his phone. Every morning it reviewed his Slack and email and asked what it could take off his plate. One morning it spotted a booking error in his CRM and asked whether it could fix it; he said yes, and it fixed it. He also lists browser tasks it finished on its own, sign-ins where it cleared two-factor codes, and automations it built where none existed. What got in the way: coding was weak, it still needed his approval, it felt slower the more he used it, and his computer had to stay on. When the computer went to sleep, everything stopped. His score was 6 out of 10, closer to 9 if you use it as a virtual assistant rather than for coding, and he cancelled his subscription for now.

31. A client's Slack channel turned into a project brief in two days (Matthew Bradford)

Matthew Bradford (9 Oct 2026), who builds software for clients, named his Dot Riri and gave it a week of client and side-project work. The part he found most impressive: Riri monitored a Slack channel he shared with a client and guided the client toward decisions about how they wanted to run their business, so a development project could start. The channel had drifted into casual conversation; with Riri driving it, they had something actionable within two days, while he watched and chimed in where he could help. Day to day, Riri tells him about important emails and by default writes drafts for him to review, updates his CRM contact and task board when a tracked task changes without being asked, and uses his email to research before client meetings. The rough edges he lists: on voice calls around day 3 it sometimes called him Mark or Maya; in the first days browser and computer use failed on his authorized Windows PC while it worked on his Mac; near the one-week mark its personality faded until he pointed it out; and it would not send a screenshot that contained a Social Security number, which he found too strict.

32. An invoice found in Drive and a speaker release signed from email (Alex Kantrowitz)

Journalist and podcast host Alex Kantrowitz (Big Technology Podcast, episode of 2 Oct 2026) gave a Dot access to his laptop, browser, email and files and handed it his own admin. It wrote emails in his voice, and they piled up as Gmail drafts that he adjusted and sent. For an invoice, he told it the file was in Drive; the Dot found it and put it in a Gmail draft to the people he usually sends it to. He also asked it to go into his email and sign a routine Web Summit speaker release he has signed many times, and it did, after another agent he had tried had refused to sign a contract for him. When he tried to give the Dot his credit card, it did not let him. His co-host Ranjan Roy questioned whether this counts as business-grade work, and whether a document signed by an agent is binding was left open in the episode.

33. Etsy keyword research, product ideas and listings, saved as skills (Handmade & Beyond)

The Etsy seller behind Handmade & Beyond (2 Oct 2026, 5-minute video) tested a Dot on shop work: marketplace insights and keyword research, turning shop data into product ideas and mockups, and creating designs and print-on-demand listings. The video also covers running several workflows at once, saving repeatable prompts as skills, managing the tasks from a phone, and the task suggestions the Dot offered on its own. One problem the video flags: a shared account caused confusion about which workflow was which.

Moving a daily job off your own computer

34. A company's daily social posts moved to the cloud, with spending caps and no blind retries (貝出康 / ドッティ, Kanman)

貝出康 (Yasushi Kaide), who runs the web and AI company Kanman in Tokushima, Japan, wrote up four days with his Dot ドッティ (note, 5 Oct 2026; longer company column, 4 Oct; both in Japanese). The company's Instagram, X and YouTube posts went out every morning from schedules on his Mac, so the Mac had to be on. He asked whether the posting could move to the cloud. The Dot listed what was running on the Mac, built a private posting-management app with post history, double-post protection and a budget, and moved the jobs over. He pasted API keys into the settings screen himself; the Dot said it would not read the values and asked him more than once not to paste keys into the chat.

On 1 October the first Instagram post failed on both accounts. The Dot did not resend, "to avoid a double post"; it found the cause, fixed it, and then posted on both. When a paid step's result was unclear, it refused to treat it as free, held the amount back from the budget, and released it only after Google's documentation confirmed that kind of error isn't charged. The caps were his decision, based on the Dot's proposal: $15 a month for generation (new generation stops at $12.50), $15 per cycle for each X API account, automatic top-ups off, and a "stop or raise?" question instead of a silent stop near a cap. Connecting the company's official X account took more than a day of repeated errors; when he asked if it was taking too long, the Dot agreed, and his suggestion to reuse the saved connection fixed it. By 3 October X posts on both accounts were going out from the cloud, Instagram had posted on 1 and 2 October before its connection expired and waited for him to re-authorise, and all six Mac schedules were switched off. Not every unprompted notice helped: one "payment due soon" was for a bill he had paid the day before. The YouTube side of the same move is on the video page, case 33.

A first day that fixed one file and started three jobs

35. A property-management spreadsheet repaired, bookkeeping checks started, and what wasn't done yet (Kay Phillips / Scout)

Kay Phillips, who does bookkeeping for clients, went live on 30 September after about five hours with a Dot that picked its own name, Scout (Substack replay and write-up, 1 Oct 2026). Phillips is often away from the desk, so most requests go in as long voice notes, and Slack gives Phillips somewhere to send a thought when it comes up and get an update back without sitting in front of the original chat. The first job was a property-management spreadsheet Phillips wanted dates pulled from. Scout made a backup first, then repaired formulas and date fields that had been stored as text, and said plainly that the ongoing reminders weren't set up yet. Scout also took on discrepancies in clients' books and an audit of Phillips's own file-based system for duplication; those were active jobs with findings and back-and-forth, not finished ones. Asked whether something was done, Scout answered, in effect, "not yet".

Phillips also corrects the live in writing: vehicle tags described as renewed were still waiting on an emissions check, data-broker removal was a next step rather than a finished removal, and the phone button is for talking with Scout, not for calling businesses. Phillips keeps the working files in a separate folder system with backups, so the business doesn't live only inside one AI tool.

Lead criteria refined by voice, B2B channels, and an invoice it noticed

These three are shorter than the cases above, but each one shows a single step of finding clients or getting paid clearly.

36. A lead search in his own company's product, refined by voice over a few rounds (Viktor Malinovskyi)

Three days into using his Dot, Viktor Malinovskyi had it run a lead search inside AiSDR, the product his team works on ("dots using our product", as he puts it in his LinkedIn post). AiSDR's Agent Search covers a broad scope, so the query decides who comes back. Together they looked at the leads it returned, tightened the criteria and ran it again; it took a few rounds before he was happy with the result. He made every change by talking, without typing, while setting up a campaign in the product. Under the post, one reader suggested keeping the final criteria for the next campaign instead of starting over, and asked whether the Dot remembers what changed in each round; the post doesn't answer that. How he works with his Dot on calls is case 33 on voice calls.

37. A table of channels for finding B2B contracts, a message template and a rough plan (Anton Poriadin)

Anton Poriadin answered on Threads, in Russian, a post that asked whether anyone had tried OpenAI's Dot (Threads). His verdict: "this thing turned out to be useful." The agent put together a table of channels where he could look for B2B contracts, a template for the outreach messages, and a rough action plan. The post stops at the plan: it doesn't list the channels or say whether any messages have gone out yet.

38. A freelance invoice it noticed, drafted from the email thread and sent after a yes (Dan McAteer / Shaine)

In his launch-day post on X (Dan McAteer, 29 Sep 2026), Dan McAteer, who tested Dots in the Dev Early Access Community, says his Dot Shaine noticed, without being asked, an invoice he still needed to send for his freelance writing. It pulled the details from the email thread and drafted the invoice; after he approved it, Shaine sent it as a PDF. He sums up the test in one word: proactivity. The same report opens the invoices & expenses page, which has more invoices found, sent and chased.

Brand OS and product docs from your samples

These two owners did not start from a blank chat. They handed the Dot documents they already used to run the brand or write product specs, and asked it to produce the next document in the same shape.

39. A Neotrix OS pack that produced a podcast OS document, edited on a walk (margin_neotrix)

margin_neotrix (Threads, Oct 2026, Korean) said he did not want plain automation. He wanted an agent that would run with his brand Neotrix — decisions, day-to-day work, and how the system operates — the way he would. He had already written most of that into system documents. With some docs still unfinished, he gave Dots the Neotrix OS pack and asked it to produce a podcast OS document. It came back matched to the brand ecosystem. The gaps he still cared about he fixed later on a voice call while walking, without touching the phone with his hands. He expects the podcast to start earlier than he had planned.

40. Feature and screen definition docs for a new project, from his own samples (m.o.b.n.d)

m.o.b.n.d (Threads, Oct 2026, Korean) gave his ChatGPT Dot the feature-definition and screen-definition documents he usually writes as samples, then asked it to produce those same docs for a newly started project. His verdict: it did the job well — well enough that he joked web planners may have less left to do.

A creator's launch kit, requested by another AI

41. Promo copy for a new video, and 12 files turned into two lists, after the Dot checked with the owner first (ヒナキラ / HinaKira)

Japanese creator HinaKira, who runs the YouTube channel ヒナキラAI塾, tested his Dot on 5 and 6 October (YouTube, 7 Oct 2026) by having his own AI assistant, Claude, send it the work on his behalf. The Dot didn't start right away. It replied that because this was a request from Claude acting for him, it needed HinaKira's own confirmation first. He gave the OK on a phone call, closed the chat, and found the work finished at about 13:48. He had also written a rule up front that anything touching the outside world needs his approval first, and the Dot confirmed it would not post or share anything.

The job was promotion for a video he had just published about moving GPTs into ChatGPT Projects. The X announcement came in three versions for different readers, and he would post the first one unchanged. A description of about 200 characters covered the three things the video actually explains: the five migration steps, the features that don't carry over, and the fact that sharing exposes the instructions. Three Shorts clip candidates each started at a chapter break. The Dot noted that the video kept loading, so its timestamps were based on the subtitles. When he watched the first clip, its opening line followed on from the previous section and felt abrupt on its own, while the ending wrapped up cleanly; he hasn't decided whether to use it. Later he gave the Dot his own material: AI prompts and post ideas scattered across 12 files came back as two lists, 300 prompts and 150 post ideas, with the original files left untouched. His verdict is that he'll keep using it, because it moves work forward on its own.

Sponsor research packs while you are away

42. Eight sponsor prospects and a seven-page pitch pack, then a 30-second segment from the phone (Automation Nerd)

The YouTube channel Automation Nerd (video titled "I let a ChatGPT Dot run my business for a day") handed its Dot a live business job for the channel itself: find eight potential sponsors for Automation Nerd and put together a pitch pack. The brief said viewers are builders and small-business owners who use AI, that the Dot should use public information on its own cloud computer, and that everything must stay drafts only — no contacting anyone. While the Dot researched companies and partnership routes, the owner narrowed the brief: prioritize tools a solo founder could actually afford, pick the strongest three and say why. Anytown, Lovable and Clerk rose to the top; the owner chose Anytown and asked the Dot to open the finished pack on its computer. What came back was seven pages plus editable files, which the owner took over to read. Later, away from the desk, the same Dot got a phone follow-up: turn the Anytown idea from the Automation Nerd sponsor pack into a 30-second sponsor segment that shows a real flow, still as a draft. The video also notes you can schedule the prospect search to run weekly or daily, and that Slack or Teams are ways to reach the same Dot — it does not show a Teams run in this clip.

A document mistake it caught and fixed itself

43. Client documents organized, then a mistake it found and corrected without being told (Hiroki Maejima / Giving Inc.)

Hiroki Maejima of Giving Inc. in Japan (Threads, in Japanese) handed his Dot the job of organizing a set of documents and sending them to a client. Afterwards, to check the work, he told it to open the reference materials. He said nothing else, yet the Dot told him it had found a mistake in the documents it had just organized and started correcting it. He described it as the agent reading its boss's actions, realizing its own error and moving to fix it, which he said is different from how earlier generative AI behaved. The post doesn't say what the mistake was or whether the corrected version reached the client, so if you hand over client paperwork, ask the Dot to check it against the reference material before anything goes out.

A site audit through a customer's eyes

44. Eleven problems on his own comparison site, found by browsing it as a small-business owner (Loïc Frissard / Digi)

Loïc Frissard (digitiz.fr, 9 Oct 2026, in French) runs digitiz.fr, a site that compares web hosts. He asked his Dot, Digi, to audit it from the point of view of a small-business owner looking for a host, while it worked on two other jobs. After about ten minutes it returned a report of 11 problems, ranked by severity, each with the page address. It had followed a real reader's path: the homepage, his host comparison, the pricing guide, the reviews and the quiz that recommends a host. Among the findings were an outdated PlanetHoster page still showing the old plan, a low o2switch price that hid a much more expensive renewal, and three links to his reviews that went to the wrong place, including the LWS link, which sent readers round in a loop. He checked, found it was right, and fixed the PlanetHoster page and the LWS link straight away. It also qualified its own numbers: the comparison page scored 61 out of 100 on mobile, but real visits showed the site doing well. Later he called Digi, asked for a summary of the audit and where to start, and had it put the list of fixes in a page in his ChatGPT Space. The same Dot failed a different job that day: it couldn't load his YouTube video or its transcript, so the 12 chapters it handed back were copies of the ones he had already published, which it admitted.

Letting the Dot choose how to earn money: a week of crowdsourcing jobs

45. A week on a crowdsourcing site, and almost nothing earned (nutu_wwwwwww)

In a Japanese thread on 13 Oct 2026, nutu_wwwwwww wanted to see whether an always-on agent could go out and earn money by itself, and let the Dot decide how. Of the ideas it came up with, he picked crowdsourcing, because the result would be easy to judge. He only registered the account, then let the Dot run on its own for about a week. It earned almost nothing. Jobs the Dot judged it could clearly do by itself often turned out to be different from the listing once it contacted the client, or the client wanted to use LINE, which isn't available in the Dot's environment, and the job went on hold. Many clients also wanted a call or an interview first. He could have stepped in as the human in the middle and passed the work on to the Dot, but avoiding that hassle was the point of the test. His conclusion: without more planning at the start, the computing time is simply wasted.

Before an earning experiment (based on case 45):

Before you sign up anywhere or apply for any job, give me a plan: which site, which kinds of jobs you can finish without a call, without LINE or other apps you can't use, and without me in the middle, and how you'll tell within [3] days whether it's working. Wait for my yes before applying, and stop if nothing has paid by day [N].

A support request nobody had answered

46. A customer waiting six hours for a call, flagged while it was still unassigned (Aaron Delasy)

Aaron Delasy (@aarondelasy) (13 Oct 2026) posted a screenshot of a message his Dot had sent him the afternoon before: "One support request may have slipped through: this customer asked for a call today, saying they haven't been able to create reports since Friday. Six hours later, [names blurred] are still unassigned with no recorded reply. Worth checking whether [name] or someone else has reached them." His comment was that the Dot caught customer feedback he had completely missed. The useful part is the shape of the alert: who asked, what is broken and since when, how long it has waited, and a question rather than an action, so the owner decides who calls back.

A company website moved to a new CMS overnight

47. WordPress pages and blog posts moved into Ferret One by the Dot's own browser, then checked by hand (原田 憲悟 / 自認カービィ)

Kengo Harada (原田 憲悟, @kenboo) runs a company and already builds a lot of his own automation with ChatGPT, Codex and Claude. In a note post (13 Oct, Japanese) he wrote that the job he valued most was his company's site renewal: moving the old pages and blog posts from WordPress into the Ferret One CMS. That is more than copying text, because headings, images, links and author details all have to be checked, and the new CMS has to be worked screen by screen. He handed it to the browser on the Dot's cloud computer, which kept opening articles and entering them into the new CMS overnight while he wasn't watching. Some links still pointed to the old domain and a few items didn't come across properly, so he checked and fixed those, but for the hours it saved he rated it well above a pass. He had tried similar work in Manus's browser and found the Dot more accurate for this job, while saying it wasn't a like-for-like benchmark.

The weak point was the cloud computer itself. At times it went offline or the Dot couldn't read the browser's state, a restart didn't always bring it back, and he hit a browser sign-in error, so an overnight job could stop partway.

Two more things from the same post. Without being asked, the Dot told him about emails from the past 24 hours that looked like they needed his reply. The first one wasn't his to answer, so he said so and asked for others; when he asked it to include carried-over items, it pulled up older threads and sorted them by who was waiting on whom and which ones needed the recipient checked. As someone running a company, he says, the hard part is knowing who has the ball, not whether the mail arrived. His three-person Outlook scheduling job is in meeting prep. His own rule for splitting the work: a check that runs the same way every day is better built yourself and run reliably, and work that changes with what is on the screen, like a CMS move, is where the Dot earns its place.

Competitor research, a proposal and a client presentation

48. Five competitors' public prices with working links, and a proposal drafted from call notes (Stephanie Hiewobea-Nyarko)

Stephanie Hiewobea-Nyarko, who runs the YouTube channel This AI Tool Does That, gave her Dot and Meta Muse the same two business tasks on camera in October 2026. The first was competitor research: find five businesses that offer AI training or workshops to small businesses in Canada, with a one-line description of each offer, the price only if it is listed publicly, and a link to the exact page where the price appears. Her rules said to write "not listed" instead of estimating, and to include only links it had actually opened. Both agents found real businesses, but the gap in the market that Muse described didn't hold up once she compared it with the Dot's research.

The second task was a client proposal. She gave both agents fictional discovery-call notes for a three-person bookkeeping firm with about 40 clients, which chases receipts and bank statements by email every month and already uses QuickBooks Online, Gmail and Google Drive. She asked for a one-page proposal with the price left as [PRICE], nothing added beyond her notes, missing information listed as questions at the end, and nothing sent to anyone. Muse was better at asking follow-up questions and improving its draft in conversation. The Dot produced editable documents and was more careful with business claims nobody had verified. Her exact prompts are in her community post.

49. A client presentation from an AutoCAD floor plan, with the Dot choosing its own camera angles (33.Shan)

Taiwanese interior designer 33.Shan (@33.shan.design) (Threads, 14 Oct 2026, in Chinese) wanted to see how much she would have to step in when her Dot made a presentation. Her own part was four steps: prepare the AutoCAD floor plan and hand it over, ask the Dot to build a three.js model she could walk through and take screenshots in, give it style reference images for a first alignment, and let it decide which angles to show. The Dot took screenshots of each space from the three.js model, generated rendered images from them and exported the presentation shown at the end of her video. Her verdict was that with a little more human touch-up it would hold its own. A few days earlier she had used her Dot to build the 3D model in Blender, then switched to three.js HTML so clients could open it more easily; that run is in cloud computer.

More asks you can copy

Competitor prices with proof (based on case 48):

Find [5] businesses that offer [service] to [type of customer] in [region]. For each one, give the name, what they offer in one line, the price only if it is listed publicly, and a link to the exact page where you found it. Write "not listed" instead of estimating, and only include links you actually opened. Then tell me in three short lines where the market seems to be priced, based only on the prices you found.

Prospect list with pitch drafts:

Build a list of [type of business] in [cities] that [have no website / match criteria]. For each, give name, website or profile, contact route, and one line on why they fit. Draft a short pitch for the top [10], signed as [name]. Put everything in a spreadsheet and don't send anything until I approve each one.

Client deadline watch:

Watch my Gmail for messages from [client names or domains]. When a client changes a deadline, scope, or budget, message me with the old and new value, a link to the email, and a draft reply. Don't send anything.

Ads account readout:

After I sign you in to [Meta Ads Manager / ad platform], read the last [30] days for [account]. Tell me which products or ads drove the most attributed sales and which spent without results, and list what the numbers leave out, such as product cost and shipping. Change nothing in the account.

Site migration with a stop point:

Move the posts from [old site] to [new site] as drafts. Before publishing anything, check whether publishing will notify subscribers or post to social accounts, tell me what you found, and wait for my go-ahead.

Overdue invoice sweep:

Every Monday morning, search my email and [invoicing tool] for invoices I sent that are unpaid after [30] days. Give me client, amount, days overdue, and a link, and draft a polite follow-up for each. I will send them myself.

Weekly customer feedback summary:

Every Friday, read this week's customer messages and reviews in [inbox / review site / form]. Group the complaints by theme with a count and one quoted example each, list the messages that need a reply from me, and draft those replies. Don't send anything.

A first paid offer on a small budget:

I want to test one small paid offer with a budget of [$100]. Propose three offers I could sell to [audience], each with a price, what I would deliver and how you would find the first customers. After I pick one, build the page and the delivery steps. Ask me before you spend money or email anyone, and count only real payments in [payment tool].

A morning offer with a fix waiting for your yes:

Every weekday at [8:00], read my Slack and email from the last day. Tell me the three things you could take off my plate today, each with what you would do and what you need from me. If you spot an error in [CRM / booking tool], show me the record and the fix you propose, and wait for my yes before changing anything.

A client channel turned into a brief:

Watch [client Slack channel]. When the conversation drifts, sum up the open decisions in a short list and ask the client one question at a time. Once they have answered, draft a project brief with scope, open questions and next steps, and show it to me before you post it in the channel.

A lead search in rounds:

Find [20] leads in [tool or source] that match [industry, company size, role, region]. Show me the first [10] with one line each on why they match, and wait for my feedback before you search again. After each round, note which criteria changed and why. When I say the list is good, save the final criteria and the list to [doc / sheet] so we can reuse them for the next campaign. Don't contact anyone.

A new document from the brand docs you already use (based on case 39):

Here are the system / brand OS documents I already use for [brand]. Using the same structure and vocabulary, draft a [podcast OS / ops playbook] for [new line of work]. List anything you invented that was not in my docs. I will edit the gaps on a call; do not publish or send anything.

Product docs from your own samples (based on case 40):

Using these sample feature-definition and screen-definition documents as the template, write the feature definition and screen definition for [new project]. Match the section order and the level of detail in the samples. Leave open questions for me in a short list at the end; do not invent product decisions I did not give you.

A launch kit for a new video:

I just published [video link] about [topic]. Draft three X posts for different readers, a description of about [200] characters that covers only the points I actually make in the video, and three Shorts clip candidates with start and end times. Say whether your timestamps come from watching the video or from the subtitles. Don't post or upload anything; I'll pick and publish myself.

Sponsor research pack (drafts only):

Fresh job. Find [N] potential sponsors for [my channel / product] and put together a pitch pack. My audience is [who]. Use public information on your own computer. Drafts only — don't contact anyone. While you work, I'll narrow: prioritize [budget / fit rules], pick your strongest [3] and tell me why. When the pack for [chosen name] is ready, open it on your computer so I can read it. Later, from my phone, turn that pack into a [30]-second sponsor segment that shows a real flow — still a draft.

Site audit as a customer (based on case 44):

Browse [site URL] as [type of customer] who wants to [goal]. Follow the path a real visitor would take: [homepage, comparison, pricing, reviews, quiz]. List every problem you find (outdated prices, hidden renewal costs, broken or wrong links), ranked by severity, with the page address for each. Don't change anything on the site, and tell me which pages you couldn't load.

Related

• Use cases hub · Build apps & sites · Invoices & expenses · Email triage · Voice calls · Daily ops catch-up
• Dots + Gmail · Availability · Getting started · Pricing
• How to get ChatGPT Dots · Dots in the EU & UK · Integrations hub · Dots + Google Drive · Slack assistant · Project follow-up