He spent 31 years in IT, retired, and now runs an auto repair business. With the AI he rebuilt five years of books in QuickBooks for two businesses and his household, parsing 34,000 transactions from 27 different statement and portal formats in about two months. Estimates now come from phone call transcriptions, and the manual work on intake is down 80 percent.
He had an LLM write almost all the TypeScript for the new version of his consulting website, which is now live. Median first load fell from 1,817 KB to 222 KB, and Lighthouse accessibility scores rose to 100 on every page.
Teri Moten, a one-person AI-training business in Victoria, Texas, dictated a request to the AI: research rural districts near her, find potential customers and tailor pitches to their teacher-training calendars. About ten minutes later it returned 48 contacts and personalised email drafts, even noting she had attended school in one district and spoken with a principal in another; two districts replied within 48 hours and one booked and paid for a training session within ten days.
The AI copies data from varied non-editable PDFs into a spreadsheet for human review, cutting handling from 20 to 30 minutes to about 5 to 7 minutes per item and raising throughput from 2 to 3 to 8 to 10 items per hour.
Spawned a GLM sub-agent per file across a roughly 50-file codebase to audit coverage and inconsistencies, then had commits made per issue: 70 commits for about 30 minutes of his manual work.
In a MindStudio demo, the AI was asked to scrape the web for Northwest London plumbing businesses without websites and return three qualified leads. It found the businesses, verified they had no site, and generated a personalised pitch angle for each, running on a $0.24/hour CPU instance.
A user asked for a single audit of one Excel deliverable. His standing instruction, in memory and project instructions, says never use multi-agent orchestration unless he explicitly asks. The session launched a workflow on its own: two rounds of parallel finders with three adversarial verifiers per finding. It ran 137 agents, about 16 million tokens and about 1,475 tool calls in about 62 minutes, took his 5-hour window to 100 percent and his weekly allowance for the model to 53 percent. There was no estimate, cap, or confirmation. He stopped it manually.
This one went wrong. See what happened before you try it.
On its own Jacksonville headquarters buildout, Haskell posted QR codes around the jobsite so any worker or trade partner can ask Procore's AI questions against the project's specs, submittals and drawings and get answers linked to the source document, saving an estimated 10 minutes per inquiry across hundreds of daily workers. Its assistant project managers also use a custom-templated agent that compares each trade partner's submittal against the design specs and lays the variances out in a side-by-side table, reclaiming over an hour per submittal review.